Looks like my call to the FBI has worked.

OK, there is probably some sort of weird routing problem and it might not be your problem at all.

You might be able to debug it yourself using traceroute; find out at which common point the routing stops. If a traceroute doesn't get out of your network, you know it's you. If it gets to your provider but not out, you know it's them.

Compare the traceroute from your shell account to the home account. Might be interesting.

Okay, on my machine, any website I try a traceroute on gives results similar to the following:

traceroute to time.gov (132.163.4.203), 30 hops max, 38 byte packets
1 router (192.168.0.1) 0.451 ms 0.378 ms 0.343 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *


And it continues to add a 'hop' and three little astericks very slowly until I control-C. Even cellar.org and google.com give these results, and I can reach them just fine!

Could it be some problem with my router? I have a privoxy proxy too, but turning it off doesn't change anything, so I doubt it's that. Plus, that wouldn't affect the traceroute.

Traceroutes from my shell account provide results that look normal.

I rebooted the router through the web-based admin menu, and now I CAN access the two sites! But traceroutes still all return identical results.

Crazy router..

<b>[edit]</b>

Upgraded the router firmware, still traceroute didn't work. But then I discovered traceroute's '-I' switch, and that got it to work. Found others on Usenet with Dlink routers with similar problems.

Hrmm.

I think your version is corrupted, UT.

In your version, Savidge shakes his head no, but with Snopes he nods his head -- yes.

ages since i've used traceroute underwindows but aren't the *s just timeouts?

wow.

is there a world hall of fame for threadjacking?

-sm