Constant disconnects

[rainnman]

Seems like we are back in a pattern of problems which cause constant disconnects.  Starting yesterday  I have been unable to stay connected for more than 8 to ten minutes.  Have run ping plotter and the only problems that come up are well within the ATT system.  Address 63.241.192.4 mdf1-bi8k-1-eth-1-4.dal1.attens.net is running a 5 percent or higher packet loss every 2.5 seconds.  That is the hop prior to the server.  Also address 12.122.138.5gar5.dlstx.ip.att .net is running an average of 2.5 percent packet loss every 2.5 seconds.  The ping times are all in the green but still showing constant packet loss.  The end result is udp stops tcp takes over and 2 seconds later disconnect.

[Denholm]

This has been ongoing. It sounds as if AT&T is working on the issue.

Here is another thread reporting the same issue: http://bbs.hitechcreations.com/smf/index.php/topic,257073.0.html

[drdeathx]

Seems like we are back in a pattern of problems which cause constant disconnects.  Starting yesterday  I have been unable to stay connected for more than 8 to ten minutes.  Have run ping plotter and the only problems that come up are well within the ATT system.  Address 63.241.192.4 mdf1-bi8k-1-eth-1-4.dal1.attens.net is running a 5 percent or higher packet loss every 2.5 seconds.  That is the hop prior to the server.  Also address 12.122.138.5gar5.dlstx.ip.att .net is running an average of 2.5 percent packet loss every 2.5 seconds.  The ping times are all in the green but still showing constant packet loss.  The end result is udp stops tcp takes over and 2 seconds later disconnect.

Try resetting your router. Unplug ethernet, power and cable for a few minutes. When I ran ping plotter my level 3 changed to Chicago now its back to Atlanta. May be worth a try.

[Denholm]

The problem is at the AT&T gateway to HTC's server, not with Level3. This is described toward the bottom of the following thread:

http://bbs.hitechcreations.com/smf/index.php/topic,257073.0.html

[SaltUbar]

Hi guys,

I have come back onto AH after being off for a year due to slow screen refreshes in the hanger.  I was pleased to see that there is a Vista version and have installed it.

I now have disconnects every 5 to 8 minutes.  i have run ping plotter and found that I have had some packet loss between my router and my ISP's router.  This has been fixed today. 
I have also set the QoS settings on my router to

1. Low priority for Http on port 80
2. High priority for UDP on ports 2000 to 5000

ping plotter tells me that I am clean with no packet loss to AH.

However I am still getting disconnects every 5 to 8 minutes.  I have plenty of system resources and have stopped most of the noncritical processes, including disabling my firewall and allowing bidirectional UDP at the router. 

How certain is AH technical staff that this disco is network related?

Regards Ubar

[Denholm]

It's actually ports 2000-6000.

The problem may not be on your end. The packet loss could be occurring further down the pipes either with your ISP or some other ISP. If you can show us the results of your PingPlot, I'm sure we can tell you where the problem appears to be arising.

[Skuzzy]

traceroute 24.22.254.211
traceroute to 24.22.254.211 (24.22.254.211), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.671 ms  0.529 ms  0.471 ms
 2  mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201)  0.270 ms  0.359 ms  0.267 ms
 3  gar5.dlstx.ip.att.net (12.122.255.225)  1.509 ms  1.234 ms  1.130 ms
 4  cr2.dlstx.ip.att.net (12.122.138.6)  2.004 ms  1.764 ms  1.381 ms
 5  ggr3.dlstx.ip.att.net (12.122.138.21)  1.254 ms  1.262 ms  1.189 ms
 6  * * *
 7  cr1-pos-0-0-3-0.losangeles.savvis.net (204.70.192.249)  33.865 ms  33.687 ms  33.711 ms
 8  er2-tengig-2-1.lay.savvis.net (204.70.198.6)  33.845 ms  33.733 ms  33.748 ms
 9  comcast-net.lay.savvis.net (208.172.41.162)  34.159 ms  34.873 ms  34.529 ms
10  pos-0-15-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.85)  47.895 ms  47.971 ms  47.991 ms
11  pos-0-15-0-0-cr01.portland.or.ibone.comcast.net (68.86.85.198)  60.732 ms  60.309 ms  60.455 ms
12  pos-0-14-0-0-ar01.burien.wa.seattle.comcast.net (68.86.90.222)  64.124 ms  64.013 ms  63.754 ms
13  be-40-ar01.seattle.wa.seattle.comcast.net (68.85.240.94)  65.338 ms  65.462 ms  64.671 ms
14  te-5-1-ur02.ferndale.wa.seattle.comcast.net (68.86.96.106)  66.601 ms  66.427 ms  66.732 ms
15  te-5-3-ur01.ferndale.wa.seattle.comcast.net (68.86.96.109)  67.477 ms  67.594 ms  67.490 ms
16  te-9-3-ur01.burlington.wa.seattle.comcast.net (68.86.96.114)  68.676 ms  68.751 ms  68.644 ms
17  ge-3-0-0-ten02.burlington.wa.seattle.comcast.net (68.86.113.178)  67.513 ms  67.631 ms  67.623 ms
18  c-24-22-254-211.hsd1.wa.comcast.net (24.22.254.211)  75.328 ms  87.620 ms  77.148 ms
19  * * *
20  * * *
21

Comcast has switched to Savvis for connectivity to the Internet.  Savvis has a routing problem, show above, which is causing most players within Comcast to get very high disco rates.

Comcast users need to complain long and loud about this to Comcast.  Savvis could care less about fixing it for us, but if Comcast was to tell them to fix it, then it might get fixed.