Author Topic: Hop 4 error (Read 654 times)

MajWoody · « **on:** April 27, 2006, 11:58:44 AM »

I am having trouble with one of my hops but I don't know how to go about fixing it. I am very ignorant in the ways of hops etc.
Here is my tracerout

Target Name: N/A
IP: 206.16.60.38
Date/Time: 4/27/2006 9:55:45 AM

1 6 ms 8 ms 8 ms 6 ms 23 ms 11 ms [73.88.196.1]
2 11 ms 7 ms 6 ms 8 ms 20 ms 27 ms [68.87.218.101]
3 17 ms 7 ms 6 ms 6 ms 8 ms 8 ms [68.87.216.49]
4 15 ms * 14 ms * * * [68.87.216.29]
5 7 ms 11 ms 10 ms 8 ms 9 ms 14 ms [12.118.177.49]
6 84 ms 83 ms 85 ms 84 ms 83 ms 96 ms gr1-p350.st6wa.ip.att.net [12.123.44.126]
7 82 ms 83 ms 84 ms 94 ms 82 ms 93 ms tbr1-p012601.st6wa.ip.att.net [12.122.12.161]
8 85 ms 84 ms 101 ms 86 ms 83 ms 86 ms tbr2-cl10.sffca.ip.att.net [12.122.12.113]
9 106 ms 104 ms 106 ms 105 ms 105 ms 106 ms tbr1-cl30.sffca.ip.att.net [12.122.9.137]
10 105 ms 105 ms 106 ms 107 ms 105 ms 108 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
11 92 ms 86 ms 86 ms 85 ms 97 ms 91 ms tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
12 104 ms 104 ms 105 ms 104 ms 117 ms 104 ms gbr2-p10.dlstx.ip.att.net [12.122.12.62]
13 104 ms 104 ms 104 ms 106 ms 105 ms 104 ms ar1-a300s2.dlstx.ip.att.net [12.127.2.5]
14 106 ms 105 ms 104 ms 109 ms 105 ms 113 ms mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
15 102 ms 102 ms 101 ms 114 ms 101 ms 110 ms mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
16 105 ms 104 ms 104 ms 106 ms 103 ms 106 ms [206.16.60.38]

Help please!!!!

Auger · « **Reply #1 on:** April 27, 2006, 08:13:38 PM »

It appears that the link between hops 3 and 4 is flaky, or hop 4 is over subscribed and is dropping packets. In either case, it's a problem with Comcast. It is very likely that they already know about it. If you're lucky, it is a bad card in a router and they'll have it fixed soon. If you're unlucky, it's a saturated link and it will get fixed this quarter, maybe.

MajWoody · « **Reply #2 on:** April 29, 2006, 09:54:13 AM »

I checked with Comcast & they deny that theres anything wrong. They are going to send someone over to check out my modem etc. I don't see how my modem can have anything to do with packet loss 4 hops away.

MajWoody · « **Reply #3 on:** May 01, 2006, 04:32:06 AM »

Skuzzy · « **Reply #4 on:** May 01, 2006, 05:42:43 AM »

Show your ISP this trace route and ask them to explain it. If there is no problem with thier network, then why is there packet loss/timeouts at that hop?

That particular hop is the gateway between Comcast and AT&T. The issue is showing up at Comcast's hop, which normally indicates either a router which is swamped, incorrect routing, or both.

MajWoody · « **Reply #5 on:** May 03, 2006, 08:29:39 PM »

Skuzzy,

I had Comcast come out to my house yesterday. They said it was not their end. He said after it leaves their hub in Beaverton Oregon it is just the net after that. I don't know squat about this kind of stuff so I couldn't argue with him too well. The first 4 hops don't show up as to who they are or anything so I don't know how to find out who owns them. The rest show up as at&t.
I don't know what to do at this point & my packet loss is horrible.

Any ideas?

MajWoody · « **Reply #6 on:** May 05, 2006, 02:06:06 AM »

Skuzzy · « **Reply #7 on:** May 05, 2006, 07:04:26 AM »

As the hop in question is thier gateway to the net, it is thier problem. Did you show them the traceroute/Pibg Plot?

Even if the problem is one hop away from them, they are obliged to file a trouble ticket with the other ISP.

I have already filed several trouble reports to AT&T about various Comcast issues, here of late.

MajWoody · « **Reply #8 on:** May 05, 2006, 05:35:59 PM »

Yes I showed it to the tech & the above is the reply I got. Now what do I do to resolve it with them if they don't own up to the problem? I don't have any other cable options other than Comcast.

I'm getting frustrated with them:mad:

Auger · « **Reply #9 on:** May 06, 2006, 02:11:10 AM »

MajWoody, how good are you with ping and output redirection? One way to get good evidence to show them that it is their problem is to run a command such as

ping -n 1000 68.87.216.29 > pingtest.txt

which will ping the router in question 1000 times and record the result in the file named pingtest.txt. If the numbers vary by more than 10 or 20 milliseconds between pings, or if a large number (more than 20) get dropped, you have very good evidence that it is their problem. Who you would give that file to that will actually care may be problematic, but you could start with someone in tech support and try to work your way up from there.

You may want to run that in the backround. It will take a bit over 15 minutes at the rate of 1 ping each second. If you don't want that much data, 100 pings will be enough if it is a really bad link.

MajWoody · « **Reply #10 on:** May 06, 2006, 08:16:45 PM »

Thanks Auger but I showed them my tracerout & even ran it multiple times with the tech here & I showed him all the dropped packets. He said it wasn't Comcast. It's like talking to a brick wall.
Thanks for the info though.