Author Topic: Skuzzy, No ping to MA (Read 600 times)

Roscoroo · « **on:** July 12, 2006, 01:40:58 PM »

Tuesday night my connect in the main went really wierd . super warps , no kill messages , ect ,

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/12/2006 11:09:16 AM

1 * * * * * * [-]
2 9 ms 9 ms 9 ms 8 ms 7 ms 9 ms ge-1-21-ur01.everett.wa.seattle.comcast.net [68.86.177.1]
3 9 ms 9 ms 9 ms 10 ms 9 ms * 10g-9-1-ur02.bellevue.wa.seattle.comcast.net [68.86.96.73]
4 12 ms 10 ms 10 ms 9 ms * 10 ms 10g-9-3-ur01.bellevue.wa.seattle.comcast.net [68.86.96.69]
5 12 ms * * * * * 10g-9-3-ar01.burien.wa.seattle.comcast.net [68.86.96.66]
6 13 ms 12 ms 11 ms 11 ms 13 ms 12 ms [12.118.106.5]
7 67 ms 66 ms 69 ms 68 ms 66 ms 66 ms gbr1-a31s1.st6wa.ip.att.net [12.127.6.134]
8 74 ms 73 ms 72 ms 74 ms 73 ms 73 ms tbr2-cl10.sffca.ip.att.net [12.122.12.113]
9 77 ms 76 ms 77 ms 77 ms 75 ms 75 ms tbr1-cl30.sffca.ip.att.net [12.122.9.137]
10 70 ms 71 ms 71 ms 69 ms 72 ms 71 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
11 72 ms 71 ms 74 ms 73 ms 72 ms 74 ms tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
12 89 ms 68 ms 67 ms 69 ms 69 ms 68 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
13 67 ms 67 ms 66 ms 66 ms 67 ms 66 ms [12.122.255.78]
14 333 ms 69 ms 69 ms 71 ms 508 ms 69 ms [63.241.192.42]
15 68 ms 68 ms 69 ms 71 ms 68 ms 70 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 68ms, Maximum = 71ms, Average = 69ms

Target Name: N/A
IP: 206.16.60.38
Date/Time: 7/12/2006 11:39:37 AM to 7/12/2006 11:40:03 AM

1 * * * * * * N/A N/A * [-]
2 9 ms 9 ms 8 ms 10 ms 9 ms 8 ms N/A N/A 8 ms ge-1-21-ur01.everett.wa.seattle.comcast.net [68.86.177.1]
3 10 ms 10 ms 10 ms 9 ms 11 ms * N/A N/A 10 ms 10g-9-1-ur02.bellevue.wa.seattle.comcast.net [68.86.96.73]
4 * * * * * * * * 8 ms 10g-9-3-ur01.bellevue.wa.seattle.comcast.net [68.86.96.69]
5 * * 12 ms * 11 ms 12 ms N/A N/A * 10g-9-3-ar01.burien.wa.seattle.comcast.net [68.86.96.66]
6 11 ms 11 ms 14 ms 12 ms 12 ms 11 ms N/A N/A 12 ms [12.118.60.17]
7 70 ms 70 ms 70 ms 69 ms 69 ms 70 ms N/A N/A 71 ms [12.127.6.90]
8 69 ms 69 ms 72 ms 70 ms 69 ms 68 ms N/A N/A 69 ms tbr2-cl10.sffca.ip.att.net [12.122.12.113]
9 69 ms 69 ms 69 ms 68 ms 69 ms 69 ms N/A N/A 304 ms tbr1-cl30.sffca.ip.att.net [12.122.9.137]
10 65 ms 66 ms 67 ms 66 ms 66 ms 65 ms N/A N/A 66 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
11 71 ms 70 ms 71 ms 68 ms 70 ms 69 ms N/A N/A 70 ms tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
12 130 ms 65 ms 64 ms 66 ms 65 ms 65 ms N/A N/A 66 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
13 61 ms 65 ms 63 ms 61 ms 62 ms 62 ms N/A N/A 63 ms [12.122.255.78]
14 63 ms 62 ms 62 ms 62 ms 62 ms 63 ms N/A N/A 62 ms mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
15 61 ms 62 ms 62 ms 60 ms 62 ms 62 ms N/A N/A 62 ms [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 60ms, Maximum = 62ms, Average = 61ms

Skuzzy · « **Reply #1 on:** July 12, 2006, 01:56:32 PM »

I hop you sent that to Comcast. See hops #4 and 5 in your traces. Both in Comcast's network. Comcast has been having some problems the last few weeks. Not sure what is going on with them.

Roscoroo · « **Reply #2 on:** July 12, 2006, 02:12:03 PM »

they told us they were doing work in the area ... a plus from an isp

The weird ? is why do i get a ping from the .38 arena's and no ping from the MA .39 arena ??? and is this whats causing my anonomalies ?

Roscoroo · « **Reply #3 on:** July 15, 2006, 12:40:21 AM »

no VC now in any arena and getting the nasty udp switch message ...

Skuzzy · « **Reply #4 on:** July 16, 2006, 06:46:24 AM »

Are the problems still showing up in Comcast's network? Seems they are really having some problems.

Roscoroo · « **Reply #5 on:** July 16, 2006, 01:39:59 PM »

yea same thing last night .. udp switch and no voice either way ..

my hops are junk ..

here's the plot as of right now
Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/16/2006 11:37:04 AM

1 * * * * * [-]
2 9 ms 9 ms 9 ms 8 ms 9 ms ge-1-21-ur01.everett.wa.seattle.comcast.net [68.86.177.1]
3 9 ms 9 ms 10 ms 8 ms * [68.86.96.73]
4 10 ms * 11 ms 9 ms 11 ms 10g-9-3-ur01.bellevue.wa.seattle.comcast.net [68.86.96.69]
5 * * 11 ms * * 10g-9-3-ar01.burien.wa.seattle.comcast.net [68.86.96.66]
6 11 ms 15 ms 12 ms 21 ms 22 ms [12.118.106.5]
7 83 ms 81 ms 83 ms 83 ms 81 ms gbr1-a30s1.st6wa.ip.att.net [12.127.6.142]
8 82 ms 82 ms 84 ms 82 ms 83 ms tbr2-cl11.cgcil.ip.att.net [12.122.10.61]
9 80 ms 80 ms 81 ms 80 ms 79 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
10 84 ms 79 ms 94 ms 80 ms 81 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
11 77 ms 78 ms 101 ms 78 ms 76 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
12 82 ms 81 ms 81 ms 81 ms 82 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
13 84 ms 79 ms 79 ms 79 ms 77 ms [12.122.255.78]
14 * 78 ms 78 ms 328 ms 79 ms [63.241.192.42] <15 78 ms 79 ms 79 ms 79 ms 77 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 77ms, Maximum = 79ms, Average = 78ms

Skuzzy · « **Reply #6 on:** July 16, 2006, 02:52:00 PM »

So Comcast is still stumbling about a bit. Hope #14 does not mean anything Rosco. All bets are off after hop #5 in Comcast's network.

Heck, you have problems in the first 4 hops after the data leaves your computer. Seems Comcast needs to address this.

Roscoroo · « **Reply #7 on:** July 16, 2006, 02:58:16 PM »

yea its ussually been ok .. its the 3-5 hops that are killing me .. and the no voice whatsoever ... gonna swap to my old hd that was working perfect on my dsl connect this afternoon and see if vc comes back , ill even bypass the gateway and go direct connect if i need to just to test this mess . no voice will be a pain come next saturday.

Roscoroo · « **Reply #8 on:** July 16, 2006, 04:14:42 PM »

same thing after going back to my older hd .. everything runs fine ... except

i have no ping to the MA ... 100% packet loss

I do have a ping to the other arena's but no voice trans or rec at all .

ping plot still going bad at hop 5 then cascading back down

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/16/2006 1:48:59 PM

1 * * * * [-]
2 9 ms 8 ms 7 ms 7 ms ge-1-21-ur01.everett.wa.seattle.comcast.net [68.86.177.1]
3 11 ms 12 ms 10 ms 10 ms 10g-9-1-ur02.bellevue.wa.seattle.comcast.net [68.86.96.73]
4 10 ms 9 ms * 8 ms 10g-9-3-ur01.bellevue.wa.seattle.comcast.net [68.86.96.69]
5 * 12 ms 11 ms * 10g-9-3-ar01.burien.wa.seattle.comcast.net [68.86.96.66]
6 12 ms 11 ms 13 ms 11 ms [12.118.106.5]
7 81 ms 81 ms 81 ms 82 ms gbr1-a30s1.st6wa.ip.att.net [12.127.6.142]
8 83 ms 84 ms 83 ms 80 ms tbr2-cl11.cgcil.ip.att.net [12.122.10.61]
9 89 ms 80 ms 82 ms 86 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
10 90 ms 81 ms 82 ms 82 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
11 79 ms 81 ms 76 ms 77 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
12 82 ms 82 ms 82 ms 82 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
13 78 ms 77 ms 78 ms 78 ms [12.122.255.78]
14 83 ms 79 ms 79 ms 79 ms [63.241.192.42]
15 83 ms 79 ms 77 ms 78 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 77ms, Maximum = 83ms, Average = 79ms

Roscoroo · « **Reply #9 on:** July 19, 2006, 01:09:14 AM »

I learned how to fix the no ma ping ... finally ...

still getting a few bad hops in my ping plot but its not hurting gameplay as bad as the no ping was talk about some wierd annomilies ... FE was so bad it was unplayable .

Skuzzy · « **Reply #10 on:** July 19, 2006, 06:25:30 AM »

I hope you have been sending these plots to Comcast.

Roscoroo · « **Reply #11 on:** July 19, 2006, 02:49:13 PM »

yes i sent them 10 plots and called once ... I was led to believe there working on it ..... and being in the Main microsoft backyard they probely will ..