First line in Tracert

J

jephperro

Hello,

I have a question about the first line in tracert.

We just had some network guys come in and set up a new network and
firewall. Things suddenly got a lot slower accessing the internet.
In every tracert, the first line times out.

Is this a DNS problem? Like is it trying to resolve using the local
domain server first, then giving up and trying the ISP's?

Here's an example:
tracert www.yahoo.com
Click to expand...

Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158]
over a maximum of 30 hops:

1 * * * Request timed out.
2 18 ms 30 ms 15 ms rd1bb-ge5-0-0-21.vc.shawcable.net
[64.59.159.242]
3 8 ms 18 ms 12 ms rc1bb-ge5-0-0.vc.shawcable.net
[66.163.69.105]
4 12 ms 12 ms 15 ms rc1wt-pos4-0-0.wa.shawcable.net
[66.163.76.126]
5 12 ms 14 ms 11 ms six.yahoo.com [198.32.180.98]
6 13 ms 12 ms 14 ms ge-0-2-0.pat2.swp.yahoo.com
[216.115.110.33]
7 18 ms 19 ms 14 ms UNKNOWN-216-115-110-39.yahoo.com
[216.115.110.39]
8 34 ms 33 ms 40 ms so-3-0-0.pat1.sjc.yahoo.com
[216.115.110.36]
9 43 ms 34 ms 37 ms g-0-0-0-p170.msr2.sp1.yahoo.com
[216.115.107.81]
10 32 ms 36 ms 34 ms te-9-1.bas-a1.sp1.yahoo.com
[209.131.32.23]
11 38 ms 33 ms 35 ms f1.www.vip.sp1.yahoo.com
[209.131.36.158]
 
C

Chuck [MVP]

Hello,

I have a question about the first line in tracert.

We just had some network guys come in and set up a new network and
firewall. Things suddenly got a lot slower accessing the internet.
In every tracert, the first line times out.

Is this a DNS problem? Like is it trying to resolve using the local
domain server first, then giving up and trying the ISP's?

Here's an example:
tracert www.yahoo.com
Click to expand...

Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158]
over a maximum of 30 hops:

1 * * * Request timed out.
2 18 ms 30 ms 15 ms rd1bb-ge5-0-0-21.vc.shawcable.net
[64.59.159.242]
3 8 ms 18 ms 12 ms rc1bb-ge5-0-0.vc.shawcable.net
[66.163.69.105]
4 12 ms 12 ms 15 ms rc1wt-pos4-0-0.wa.shawcable.net
[66.163.76.126]
5 12 ms 14 ms 11 ms six.yahoo.com [198.32.180.98]
6 13 ms 12 ms 14 ms ge-0-2-0.pat2.swp.yahoo.com
[216.115.110.33]
7 18 ms 19 ms 14 ms UNKNOWN-216-115-110-39.yahoo.com
[216.115.110.39]
8 34 ms 33 ms 40 ms so-3-0-0.pat1.sjc.yahoo.com
[216.115.110.36]
9 43 ms 34 ms 37 ms g-0-0-0-p170.msr2.sp1.yahoo.com
[216.115.107.81]
10 32 ms 36 ms 34 ms te-9-1.bas-a1.sp1.yahoo.com
[209.131.32.23]
11 38 ms 33 ms 35 ms f1.www.vip.sp1.yahoo.com
[209.131.36.158]
Click to expand...

The Hop 1 time out? That's a router that doesn't respond to pings. Maybe your
router is set to not respond, thanks to advice by Steve Gibson.
<http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html>
http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
G

Gordon

Chuck said:
The Hop 1 time out? That's a router that doesn't respond to pings. Maybe your
router is set to not respond, thanks to advice by Steve Gibson.
<http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html>
http://nitecruzr.blogspot.com/2005/05/security-by-obscurity.html
Click to expand...

That's answered a query I had! I was having huge problems with NNTP
access, and one of the things the ISP asked for was a tracert to the
news server. I got "hop 1 timed out" and now i know why!
Thanks for that!
 
C

Chuck [MVP]

That's answered a query I had! I was having huge problems with NNTP
access, and one of the things the ISP asked for was a tracert to the
news server. I got "hop 1 timed out" and now i know why!
Thanks for that!
Click to expand...

One of the details that's so easy to overlook. Thanks for the feedback!

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Top