Author Topic: Lasat Hop before sever (Read 1426 times)

Hajo · « **on:** November 18, 2007, 07:54:16 PM »

Skuzzy......connections to night a new high for Lag. Used Ping Plotter and traced a problem with hop before server. 40MS usually my connection speed and according to the clipboard pings were as high as 222ms.

I've logged on also and went to tower, half the graphics loaded and my PC froze and I had to reboot. This has happened at least half a dozen times in the last week.

What's the story?

Hajo · « **Reply #1 on:** November 18, 2007, 08:05:03 PM »

Skuzzy here is the address.

mdf1-bi8k-2eth-2-1-dal1.attens.net (63.241.192.198)

By the way at hop it stated destination was not obtainable. 33% packett loss and the two hops behind it weren't able to be connected to.

Fencer51 · « **Reply #2 on:** November 18, 2007, 08:15:29 PM »

Major server hiccup on the Blue Arena about 8:21 to 8:23 eastern. Text went down, but vox stayed up. No damage was taken to planes or tanks. then after about 2 mins the arena "caught up" in a rush with damage put to targets which had taken damage. Was rather intense.. Losta explosions all at once.

The Fugitive · « **Reply #3 on:** November 18, 2007, 08:26:23 PM »

Skuzzy says the next to the last hop being messed up usually means the problem is in the return trip. Email him you IP address and ask him to ping back to look for trouble.

Hajo · « **Reply #4 on:** November 18, 2007, 09:23:36 PM »

El Fugitivo thanks! Will do soon as I discover my IP addrews

WMLute · « **Reply #5 on:** November 18, 2007, 10:09:05 PM »

Hajo, I have the same prob. as you w/ the last hop.
mdf1-bi8k-2eth-2-6-dal1.attens.net (63.241.192.196)
not quite the same as yours, but basically the same.

I was on the phone w/ ATT the other week, and I had them look @ that hop for me, and they said there was deff. some problems on it, and would shoot it up to ther Eng. to look @.

Skuzzy, I have packet loss on ALL THe ATT Dallas hops. Any way for you to raise cain w/ ATT and get them to actually DO something about this?

The Fugitive · « **Reply #6 on:** November 19, 2007, 07:48:16 AM »

Quote

Originally posted by Hajo
........

mdf1-bi8k-2eth-2-1-dal1.attens.net (63.241.192.198)

...if this is the one thats giving you the trouble in the list, just send him the first one or two from the list and he should be good.

Skuzzy · « **Reply #7 on:** November 19, 2007, 09:35:44 AM »

You are asking for me to speculate given incomplete information. I would rather not do that.

The routes at the colocation are 100% asynchronous. You cannot see what condition the return path is in. I can, but I need to know where the final point is in the return.

More than happy to check this out.

Hajo · « **Reply #8 on:** November 19, 2007, 10:20:30 AM »

Skuzzy will do. Will take a plot and send.

Hajo

WMLute · « **Reply #9 on:** November 19, 2007, 10:54:24 AM »

I am on a T1 line hosted/managed by ATT that goes (is hubbed?) in Dallas. I have 4 hops from the managed T1 in Dallas to the HTC server, all ATT. I almost always have 10-40% packet loss on all four hops. It is rare that i can ping the HTC server and not see packet loss on one if not all 4 of those hops.

Target Name: N/A
IP: 206.16.60.38
Date/Time: 11/19/2007 10:52:40 AM

2 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms [12.185.253.81]
3 85 ms 102 ms 101 ms 20 ms 77 ms 47 ms 88 ms 87 ms 97 ms 40 ms [12.86.250.77]
4 88 ms 95 ms 95 ms 22 ms 85 ms 57 ms 99 ms 97 ms 89 ms 52 ms tbr2.dlstx.ip.att.net [12.123.16.222]
5 82 ms 91 ms 97 ms 20 ms 82 ms 59 ms 101 ms 99 ms 101 ms 61 ms br2.dlstx.ip.att.net [12.123.16.213]
6 101 ms * * 21 ms 84 ms 69 ms * * * 78 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
7 * * * 21 ms * * * * * * mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
8 97 ms 34 ms 99 ms 21 ms 96 ms 59 ms 101 ms 40 ms 75 ms 76 ms [206.16.60.38]

Target Name: N/A
IP: 206.16.60.41
Date/Time: 11/19/2007 11:10:49 AM

2 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms [12.185.253.81]
3 74 ms 85 ms 119 ms 193 ms 110 ms 206 ms 96 ms 44 ms 85 ms 32 ms [12.86.250.77]
4 89 ms * 108 ms * 106 ms * 108 ms 53 ms 92 ms 47 ms tbr2.dlstx.ip.att.net [12.123.16.222]
5 76 ms 45 ms 98 ms * * * 95 ms 78 ms 93 ms 42 ms br2.dlstx.ip.att.net [12.123.16.213]
6 81 ms * * * * * * 71 ms * 75 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
7 * 21 ms * * * * * * * * mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
8 124 ms 36 ms 85 ms 143 ms 152 ms 224 ms 105 ms 85 ms 68 ms 36 ms [206.16.60.41]

Skuzzy · « **Reply #10 on:** November 19, 2007, 02:09:16 PM »

That's not good.

kilz · « **Reply #11 on:** November 19, 2007, 03:58:28 PM »

where do you find the IP for AH arenas again

kilz · « **Reply #12 on:** November 19, 2007, 04:08:24 PM »

kilz · « **Reply #13 on:** November 19, 2007, 04:09:00 PM »

so can anyone tell me what the heck that thing says

WMLute · « **Reply #14 on:** November 19, 2007, 04:43:25 PM »

i'm not Skuzzy, but if you are getting 100% packet loss on the 1st hop, that's your computer/router/modem.