Here's a weird one for you guys. It's not causing me any problems, but it's peculiar. Why is it that when I run a tracert from any machine connected in my home network, the only host that responds is my router, and the machine that I am tracing to. For example:
C:\Documents and Settings\bill.LAN>tracert www.google.ca
Tracing route to www.l.google.com
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 35 ms 37 ms 34 ms 18.104.22.168
It seems to determine the correct number of hops to each site, and I can understand certain hops along the way not responding to ICMP echo, but no matter where I trace none of them respond. This happens both from my XP Pro machine and my Windows 2003 server. I am only running through an el-cheapo D-Link 514 router, and can't see anything that it could be doing to cause this. I'm stumped! I thought for a moment that perhaps my ISP was doing some weird traffic shaping of some sort, however when I connect directly to the modem it traces fine!
C:\Documents and Settings\bill.LAN>tracert 22.214.171.124 -d
Tracing route to 126.96.36.199 over a maximum of 30 hops
1 * * * Request timed out.
2 7 ms 6 ms 9 ms 188.8.131.52
3 50 ms 32 ms 33 ms 184.108.40.206
4 53 ms 30 ms 32 ms 220.127.116.11
5 32 ms 44 ms 31 ms 18.104.22.168
6 33 ms 34 ms 47 ms 22.214.171.124
7 34 ms 33 ms 43 ms 126.96.36.199
8 78 ms 32 ms 33 ms 188.8.131.52
Can anyone else think of a reason this might be happening? I know it's something in the router, but I have no clue what setting is causing this.