Are you a Google Analytics enthusiast?
More SEO Content
Scroogle Showing Page Not Found
Posted 05 December 2003 - 09:55 PM
Posted 05 December 2003 - 10:13 PM
Try this. Go to your command prompt (in Windows XP that would be located at Start > Programs > Accessories > Command Prompt).
Type in: nslookup www.scroogle.org and hit enter.
Does that give you the Scroogle info?
Also, you could try going directly to Scroogle's IP number since they apparently have a dedicated IP. I don't like posting IP's on public forums, so I'll PM that to you in just a second.
Check to make sure that IP isn't in your firewall's "banned" list also. If it's something in the firewall on their end, there's not going to be a lot you can do to overcome it, except maybe to use one of the browser anonymizer services out there on the 'Net that will report a different IP number for you to their server.
Try those two and post back what happened if you still can't get through to Scroogle.
Posted 05 December 2003 - 10:37 PM
This is the info I got from the command you told me to type:
Address: my IP is here
Non authorative answer:
Address: the IP you PM'd me is here
I checked my firewalls and it is off on XP although I do run a SMC router which clones my IP for all other networks here but checked and no IPs are banned on it.
What are the browser anomizers out there, any suggestions?
I thank you for this info, its really just a curiousity thing now to look at the site...one of those pet peeves
Posted 05 December 2003 - 10:48 PM
Just put the Scroogle.org addy in the little form box in the upper right corner of the first page.
If that works, the server they're on likely has performed a bit of over-blocking of your IP block in their firewall. The DNS looks like you should be getting there.
Posted 05 December 2003 - 10:55 PM
Now I must ask, what is over-blocking of my IP and why did they choose mine? LOL!
Posted 06 December 2003 - 08:19 AM
Say for instance the Sys Admin noticed someone from IP 111.222.333.444 trying to hack into their system. Or saw that someone from that same IP number was spamming the server constantly. And perhaps they've seen the same type of rogue activity coming from IP 18.104.22.168 in the past.
From the Sys Admin point of view it is easier (not smarter, but easier) to simply block all access to the server from all IP's starting with 111.222 than it is to set up multiple blocks for multiple IP number. It's one line in the firewall ruleset (22.214.171.124/16) instead of 2 or 10 or 200 lines containing the exact offending IP numbers.
Unfortunately a lot of places, even major ISP's, follow such practices whether they should or not. However, since there could be over 65,000 individual IP number in that range (from 126.96.36.199 through 188.8.131.52) they end up blocking a lot of unsuspecting, completely legitimate people from the server when they should really be blocking only 1 or 2.
Posted 06 December 2003 - 12:17 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users