tracert

[Vigo]

I can't do a tracert through the cmd prompt. I can ping any ip or domain name but if I try a tracert I get a trace to 10.3.48.1 and then 19 time outs after. I assume that I'm tracing the ip of my router but that isn't my router's IP. Nor is it my cable modems. I did a nslookup though and it doesn't belong to a domain name.

Is it my router? Is the router the reason I can't run a tracert on anything? And if it is, or isn't- how can I get around the block and get a tracert through?

[LiVeWiRe]

Vigo,

How many 'hops' does it take to get to the '10.3.48.1' address? It could be that it's a firewall or maybe a router on your ISP's network that is blocking the tracert from that point forward.

Just FYI, here's a link to a very useful website:

http://www.dnsstuff.com/

HTH,
-LW

[Vigo]

First hop. After that I get timeouts. ISP router sounds likely... Thanks for the link. I can do a tracert using that website. So back to the original questions:

Why can't I do a tracert through the command line and how do I "fix" it so I can?

[akrytus]

Thats tough, my guess would be perhaps you hit a router, ie your isp, that wont pass the icmp packets or more then likely doesnt reply with a icmp type 11. This means the original ttl for the tracert is exceeding and needs to increase. This would certainly cause a time-out.

Since you are using the website to perform your tracert, the initial hops are to different routers then from your house. So more then likely it never hits the router that you get stuck on, therefore a successfull tracert command. Let me know if that helps or if I am way off base.

[Vigo]

Well it makes sense, but I'm already guessing as much. I guess I'll try giving the cable company a call. I just wanted to see if anyone had any ideas to get the trace to pass through.

Doing a tracert through a website isn't much use.

[LiVeWiRe]

Vigo,

Unfortunately, IF it is your ISP's router or firewall then there's probably not much you can do.

If they are blocking traceroutes then I'm sure they have their reasons...

-LW

[akrytus]

Yeah, if it is your ISP, not sure if they would change their rules just for you! Besides, why do you wish to tracert so bad?

[glc]

Are you sure you don't have a proxy enabled in your Internet Options, Connections, LAN settings?

[Metaphorically]

Tracert is a perfectly legitimate use of your connection. I've never heard a reason for an ISP to block it, but ISPs often do things without much consideration for users that do something besides the standard web and email access. As an aside, doesn't tracert do the same thing as a ping (and maybe a dns lookup) to each hop on the route? So shouldn't tracert work if ping does?

[Vigo]

Thats what I was thinking. I can ping but I can't trace. No proxy on my network. Since I'm not pinging the routers IP it must be the cable companies router I guess.

Why tracert? I'd just like to know how many hops I'm taking from my house- especially in reference to my webserver. And sometiems where (though thats just curiosity).