Author Topic: disconnect issues please help (Read 536 times)

66thhellcats.co · « **on:** July 15, 2006, 04:26:54 AM »

hey guys. When u guys did that patch a few weeks ago i started getting discoed. I love udp anywhere from 5mins to 1hr i can gaurante in a 2hr session ill get discoed 3-4 times. This is the only game it happens with can you please help.

Schatzi · « **Reply #1 on:** July 15, 2006, 06:30:01 AM »

Can you run a pingplot and post it?

66thhellcats.co · « **Reply #2 on:** July 15, 2006, 05:18:37 PM »

ummmmmmmmm whats that and how do i do it

Schatzi · « **Reply #3 on:** July 15, 2006, 07:12:53 PM »

http://www.pingplotter.com

Install the freeware pingplotter and run traces to the MA and Other Arena addies.

Quote

First, the server IP addresses, to be used for traces/ping plots.

Main Arena Server Address: 206.16.60.39
All other arenas: 206.16.60.38

You can copy the Info of a pingplot under EDIT > SAVE AS TEXT... just paste that in here.

I also recommend you check the stickies in Tech Support for Hints&Tips on internet connection.

Edit: I just had another idea.... check your Firewall/AV... make sure Aces High is still allowed after installing the new version.

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

Comcast has been having a lot of problems with thier network lately. Run a PingPlot (http://www.pingplotter.com) to 206.16.60.39 and see what it shows.

You are looking for packet loss (PL %) in the second (if I recall) column.

If it happesn on the last hop before the server (206.16.60.39), then I need to run a reverse plot back to you as all data packets runs on an asynchronous path.

wigglepog · « **Reply #5 on:** July 16, 2006, 08:53:10 PM »

I have been getting discoed alot lately. No UDP message or even host lost message...just straight to desktop. Here is my pingplot( I don't know what any of it means). Please help.

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/16/2006 9:27:29 PM

1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms dslmodem.domain.actdsltmp [192.168.0.1]
2 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms mdsnwikwbas08-lo10.network.tds.net [69.129.192.1]
3 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms mdsnwikwlcr51-gi3-4.network.tds.net [64.50.227.105]
4 10 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms mdtnwiallcr52-gi2-8.network.tds.net [64.50.226.181]
5 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms mdtnwialcor72-gi2-1.network.tds.net [64.50.226.173]
6 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms chcgildtcor01-p0-0.network.tds.net [64.50.239.25]
7 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 20 ms 10 ms 11 ms 10 ms aer1-ge-6-2.chicagoequinix.savvis.net [208.174.226.69]
8 20 ms * 10 ms 20 ms 10 ms * 10 ms 10 ms 10 ms * bpr2-ae2.ChicagoEquinix.savvis.net [208.175.9.138]
9 20 ms -32764 ms -32764 ms 20 ms 20 ms 20 ms -32764 ms 20 ms 20 ms 20 ms dcr2-so-6-3-0.Chicago.savvis.net [208.175.10.253]
10 10 ms -32764 ms -32764 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms allegiance-gw.dlstx.ip.att.net [192.205.32.225]
11 60 ms -32764 ms 60 ms * 61 ms 60 ms -32764 ms 60 ms 60 ms 60 ms tbr2-p033301.cgcil.ip.att.net [12.123.6.26]
12 -32764 ms -32764 ms 60 ms 60 ms 60 ms 60 ms -32764 ms -32764 ms 60 ms 60 ms tbr2-p033301.cgcil.ip.att.net [12.123.6.26]
13 60 ms -32764 ms -32764 ms 60 ms 61 ms 60 ms -32764 ms 60 ms 60 ms 60 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
14 60 ms -32764 ms -32764 ms 60 ms 60 ms 60 ms -32764 ms 60 ms 60 ms 60 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
15 -32764 ms 60 ms 60 ms -32764 ms 60 ms 60 ms 60 ms -32764 ms 60 ms 61 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
16 60 ms -32764 ms 61 ms 60 ms 60 ms 60 ms -32764 ms 60 ms 60 ms 61 ms [12.122.255.82]
17 60 ms -32764 ms -32764 ms 60 ms 60 ms 60 ms -32764 ms 60 ms 60 ms 60 ms [12.122.255.82]
18 60 ms 60 ms 60 ms 60 ms 60 ms 60 ms 60 ms 60 ms 60 ms 60 ms [206.16.60.39]

Schatzi · « **Reply #6 on:** July 17, 2006, 02:06:09 AM »

Eeek... Savvis again.

When your packets hit Savvis in Chicago (Hop 8) all bets are off. This looks not good. Im not sure if you should contact them or if Skuzzy will do it (they had problems in the past)

But CTD without getting the Host Connection Lost message sounds actually more like a game / hardware problem to me. Not sure if your connect can cause that too.

wigglepog · « **Reply #7 on:** July 17, 2006, 12:44:40 PM »

Thanks for checking this, Schatzi. Interestingly, I've been running the pingplot some more, and found that are even more problems (consitently) further down the line (hop 13 here)... and yeah I agree with the sudden ctd. It happens within seconds of entering the MA. I don't really do any other online games so it is difficult for a 'reality' check on this. I did go into 'Second Life' for a while (it is constantly downloading and rendering graphics) and no problem. No other program on or offline is crashing or throwing me out to desktop.

Here's a newer plot showing the hop 13 packet loss....

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/17/2006 1:19:07 PM

1 10 ms 0 ms dslmodem.domain.actdsltmp [192.168.0.1]
2 10 ms 10 ms mdsnwikwbas08-lo10.network.tds.net [69.129.192.1]
3 10 ms 10 ms mdsnwikwlcr51-gi3-4.network.tds.net [64.50.227.105]
4 20 ms 20 ms mdtnwiallcr52-gi2-8.network.tds.net [64.50.226.181]
5 20 ms 20 ms mdtnwialcor72-gi2-1.network.tds.net [64.50.226.173]
6 10 ms 10 ms chcgildtcor01-p0-0.network.tds.net [64.50.239.25]
7 10 ms 10 ms aer1-ge-6-2.chicagoequinix.savvis.net [208.174.226.69]
8 20 ms 10 ms bpr2-ae2.ChicagoEquinix.savvis.net [208.175.9.138]
9 -32764 ms 20 ms dcr2-so-6-3-0.Chicago.savvis.net [208.175.10.253]
10 -32764 ms 20 ms allegiance-gw.dlstx.ip.att.net [192.205.32.225]
11 -32764 ms 10 ms allegiance-gw.dlstx.ip.att.net [192.205.32.225]
12 60 ms 60 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]
13 * 60 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
14 -32764 ms 60 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
15 -32764 ms 61 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
16 -32764 ms 61 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
17 60 ms 60 ms [12.122.255.82]
18 60 ms 60 ms [206.16.60.39]

Schatzi · « **Reply #8 on:** July 17, 2006, 01:15:20 PM »

Theres a simple thing you can do to check out the CTD issues. Go to OFFLINE mode - if it still crashes, the connect is not your only problem. If it doesnt, all bets are off what causes it.

66thhellcats.co · « **Reply #9 on:** July 17, 2006, 01:38:11 PM »

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/17/2006 2:35:57 PM to 7/17/2006 2:37:27 PM

1 * * * * * * * [-]
2 7 ms 7 ms 6 ms 8 ms 8 ms 7 ms 7 ms ge-2-3-ur01.eastwindsor.nj.panjde.comcast.net [68.86.220.41]
3 12 ms 9 ms 8 ms 6 ms 7 ms 8 ms 8 ms po10-ur02.eastwindsor.nj.panjde.comcast.net [68.86.209.214]
4 12 ms 9 ms 9 ms 8 ms 7 ms 7 ms 7 ms po10-ur01.ebrunswick.nj.panjde.comcast.net [68.86.209.218]
5 11 ms 7 ms 7 ms 8 ms 8 ms 8 ms 8 ms po10-ur02.ebrunswick.nj.panjde.comcast.net [68.86.209.222]
6 7 ms 9 ms 8 ms 7 ms 7 ms 9 ms 9 ms po10-ur01.avenel.nj.panjde.comcast.net [68.86.209.226]
7 13 ms 9 ms 8 ms 8 ms 8 ms 8 ms 9 ms po10-ur02.avenel.nj.panjde.comcast.net [68.86.209.230]
8 10 ms 8 ms 10 ms 10 ms 9 ms 8 ms 8 ms po10-ur01.union.nj.panjde.comcast.net [68.86.209.234]
9 8 ms 9 ms 8 ms 7 ms 10 ms 9 ms 9 ms po10-ur02.union.nj.panjde.comcast.net [68.86.209.238]
10 10 ms 10 ms 9 ms 9 ms 8 ms 8 ms 10 ms po10-ur01.jerseycity.nj.panjde.comcast.net [68.86.209.242]
11 8 ms 8 ms 10 ms 10 ms 9 ms 9 ms 9 ms po10-ur02.jerseycity.nj.panjde.comcast.net [68.86.209.246]
12 9 ms 9 ms 9 ms 8 ms 13 ms 10 ms 10 ms po10-ur01.narlington.nj.panjde.comcast.net [68.86.209.250]
13 11 ms 10 ms 10 ms 9 ms 9 ms 11 ms 10 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.209.254]
14 15 ms 8 ms 10 ms 10 ms 9 ms 9 ms 9 ms ar01.plainfield.nj.panjde.com cast.net [68.86.208.5]
15 9 ms 9 ms 8 ms 10 ms 10 ms 10 ms 89 ms GE-2-0-cr01.plainfield.nj.core.comcast.net [68.86.211.2]
16 11 ms 12 ms 12 ms 10 ms 9 ms 11 ms 11 ms [12.118.102.21]
17 55 ms 54 ms 53 ms 53 ms 53 ms 53 ms 52 ms tbr2-p032501.n54ny.ip.att.net [12.123.3.86]
18 53 ms 51 ms 51 ms 52 ms 52 ms 52 ms 52 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
19 48 ms 49 ms 48 ms 48 ms 47 ms 50 ms 50 ms tbr1-cl17.attga.ip.att.net [12.122.10.70]
20 53 ms 47 ms 46 ms 46 ms 45 ms 45 ms 45 ms tbr2-cl1835.attga.ip.att.net [12.122.9.158]
21 50 ms 49 ms 51 ms 50 ms 50 ms 51 ms 49 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
22 50 ms 50 ms 107 ms 50 ms 50 ms 50 ms 49 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
23 47 ms 48 ms 46 ms 47 ms 45 ms 44 ms 46 ms [12.122.255.82]
24 49 ms 46 ms 48 ms 48 ms 47 ms 47 ms 47 ms [63.241.192.42]
25 51 ms 48 ms 46 ms 46 ms 48 ms 48 ms 47 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 46ms, Maximum = 51ms, Average = 47ms

fuzeman · « **Reply #10 on:** July 17, 2006, 02:08:48 PM »

Wigglepog, generally speaking once you get a bad hop the results after arent 100% accurate so at this point worry about #8 and Savvis.

66thhellcats, that looks AOK to me. Low #s and fairly consistant. Not an asterick in the whole thing. That is as long as you covered up yoiur address in that first hop.
Next try running one when you are having a problem and let it run for some time. More pings you record the better info it gives.
If you mean dropping to desktop, another program could be activating itself and minimizing AH.
As Skuzzy mentioned Comcast is having 'issues.'

Schatzi · « **Reply #11 on:** July 17, 2006, 03:19:04 PM »

66thhellcats, your pingplot looks VERY clean to me. Not a hair of trouble in sight there...

Are you sure its a connection problem and not the game crashing for another reason? (Longer lockups can result in a Host Connection Lost as well).

Run a dxdiag. Check your drivers and CPU and GC temperature.

Are you having similar problems when playing OFFLFINE mode?

66thhellcats.co · « **Reply #12 on:** July 17, 2006, 05:29:03 PM »

strickly happens in online mode doesnt happen with any othe rgame i play. The odd thing is that its never the same. Meaning it could happen the first 2 mins im on it will say lost udp then 30 secs later host lost connection. sometimes its a few hrs its very random.

wrag · « **Reply #13 on:** July 17, 2006, 06:30:18 PM »

Lately, the last 2 weeks or so, I've been having something very much like that happen.

I go online, enter MA, and from that point on I can CTD no message, ...well once I had a message.. said AH had encountered a problem and had to close, ... usually no warning no message nuthing.

Happened twice now when I went to hanger to select a diffrent plane. Other times can be flying or most anything and poof desktop. Connect seems ok but???

Holding off on doing anything until oh say wednesday. May have DSL hooked up and running then.

66thhellcats.co · « **Reply #14 on:** July 17, 2006, 07:53:34 PM »

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/17/2006 8:51:23 PM to 7/17/2006 8:52:53 PM

1 * * * * * * * * * N/A [-]
2 8 ms 8 ms 9 ms 6 ms 21 ms * * 8 ms 10 ms 7 ms ge-2-3-ur01.eastwindsor.nj.panjde.comcast.net [68.86.220.41]
3 8 ms 8 ms 9 ms 6 ms 7 ms * * 9 ms 11 ms 7 ms po10-ur02.eastwindsor.nj.panjde.comcast.net [68.86.209.214]
4 8 ms 7 ms 7 ms 8 ms 9 ms * * 8 ms 11 ms 9 ms po10-ur01.ebrunswick.nj.panjde.comcast.net [68.86.209.218]
5 8 ms 9 ms 9 ms 9 ms 9 ms * * 8 ms 11 ms 7 ms po10-ur02.ebrunswick.nj.panjde.comcast.net [68.86.209.222]
6 9 ms 9 ms 16 ms 10 ms 10 ms * * 9 ms 10 ms 9 ms po10-ur01.avenel.nj.panjde.comcast.net [68.86.209.226]
7 9 ms 11 ms 8 ms 10 ms 9 ms * * 9 ms 8 ms 9 ms po10-ur02.avenel.nj.panjde.comcast.net [68.86.209.230]
8 9 ms 9 ms 9 ms 10 ms 9 ms * * 11 ms 17 ms 9 ms po10-ur01.union.nj.panjde.comcast.net [68.86.209.234]
9 9 ms 9 ms 9 ms 11 ms 19 ms * * 9 ms 8 ms 9 ms po10-ur02.union.nj.panjde.comcast.net [68.86.209.238]
10 10 ms 8 ms 10 ms 14 ms 11 ms * * 8 ms 9 ms 10 ms po10-ur01.jerseycity.nj.panjde.comcast.net [68.86.209.242]
11 9 ms 10 ms 11 ms 12 ms 8 ms * * 10 ms 9 ms 9 ms po10-ur02.jerseycity.nj.panjde.comcast.net [68.86.209.246]
12 11 ms 11 ms 10 ms 9 ms 11 ms * * 11 ms 10 ms 9 ms po10-ur01.narlington.nj.panjde.comcast.net [68.86.209.250]
13 11 ms 11 ms 14 ms 9 ms 11 ms * * 10 ms 12 ms 10 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.209.254]
14 9 ms 20 ms 11 ms 10 ms 11 ms * * 12 ms 10 ms 11 ms ar01.plainfield.nj.panjde.com cast.net [68.86.208.5]
15 10 ms 10 ms 13 ms 10 ms 9 ms * * 11 ms 9 ms 9 ms GE-2-0-cr01.plainfield.nj.core.comcast.net [68.86.211.2]
16 12 ms 10 ms 10 ms 12 ms 13 ms * * 12 ms 15 ms 11 ms [12.118.102.21]
17 60 ms 52 ms 54 ms 54 ms 56 ms * * 54 ms 53 ms 54 ms tbr2-p032501.n54ny.ip.att.net [12.123.3.86]
18 53 ms 51 ms 52 ms 51 ms 54 ms * * 60 ms 69 ms 51 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
19 49 ms 49 ms 49 ms 49 ms 52 ms * * 49 ms 51 ms 50 ms tbr1-cl17.attga.ip.att.net [12.122.10.70]
20 45 ms 46 ms 48 ms 47 ms 47 ms * * 52 ms 45 ms 46 ms tbr2-cl1835.attga.ip.att.net [12.122.9.158]
21 52 ms 53 ms 54 ms 49 ms 49 ms * * * 50 ms 50 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
22 50 ms 49 ms 51 ms 49 ms 50 ms * * 50 ms 53 ms 49 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
23 47 ms 45 ms 46 ms 53 ms 47 ms * * 46 ms 47 ms 47 ms [12.122.255.82]
24 47 ms 49 ms 49 ms 48 ms 56 ms * * 51 ms 48 ms 48 ms [63.241.192.42]
25 47 ms 47 ms 48 ms 47 ms 61 ms * * 52 ms 48 ms 47 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 10, Received = 8, Lost = 2 (20.0%)
Round Trip Times: Minimum = 47ms, Maximum = 61ms, Average = 49ms

Target Name: N/A
IP: 206.16.60.39
Date/Time: 7/17/2006 8:51:23 PM to 7/17/2006 8:52:53 PM

1 * * * * * * * * * * [-]
2 8 ms 8 ms 9 ms 6 ms 21 ms * * 8 ms 10 ms 7 ms ge-2-3-ur01.eastwindsor.nj.panjde.comcast.net [68.86.220.41]
3 8 ms 8 ms 9 ms 6 ms 7 ms * * 9 ms 11 ms 7 ms po10-ur02.eastwindsor.nj.panjde.comcast.net [68.86.209.214]
4 8 ms 7 ms 7 ms 8 ms 9 ms * * 8 ms 11 ms 9 ms po10-ur01.ebrunswick.nj.panjde.comcast.net [68.86.209.218]
5 8 ms 9 ms 9 ms 9 ms 9 ms * * 8 ms 11 ms 7 ms po10-ur02.ebrunswick.nj.panjde.comcast.net [68.86.209.222]
6 9 ms 9 ms 16 ms 10 ms 10 ms * * 9 ms 10 ms 9 ms po10-ur01.avenel.nj.panjde.comcast.net [68.86.209.226]
7 9 ms 11 ms 8 ms 10 ms 9 ms * * 9 ms 8 ms 9 ms po10-ur02.avenel.nj.panjde.comcast.net [68.86.209.230]
8 9 ms 9 ms 9 ms 10 ms 9 ms * * 11 ms 17 ms 9 ms po10-ur01.union.nj.panjde.comcast.net [68.86.209.234]
9 9 ms 9 ms 9 ms 11 ms 19 ms * * 9 ms 8 ms 9 ms po10-ur02.union.nj.panjde.comcast.net [68.86.209.238]
10 10 ms 8 ms 10 ms 14 ms 11 ms * * 8 ms 9 ms 10 ms po10-ur01.jerseycity.nj.panjde.comcast.net [68.86.209.242]
11 9 ms 10 ms 11 ms 12 ms 8 ms * * 10 ms 9 ms 9 ms po10-ur02.jerseycity.nj.panjde.comcast.net [68.86.209.246]
12 11 ms 11 ms 10 ms 9 ms 11 ms * * 11 ms 10 ms 9 ms po10-ur01.narlington.nj.panjde.comcast.net [68.86.209.250]
13 11 ms 11 ms 14 ms 9 ms 11 ms * * 10 ms 12 ms 10 ms po70-ar01.verona.nj.panjde.comcast.net [68.86.209.254]
14 9 ms 20 ms 11 ms 10 ms 11 ms * * 12 ms 10 ms 11 ms ar01.plainfield.nj.panjde.com cast.net [68.86.208.5]
15 10 ms 10 ms 13 ms 10 ms 9 ms * * 11 ms 9 ms 9 ms GE-2-0-cr01.plainfield.nj.core.comcast.net [68.86.211.2]
16 12 ms 10 ms 10 ms 12 ms 13 ms * * 12 ms 15 ms 11 ms [12.118.102.21]
17 60 ms 52 ms 54 ms 54 ms 56 ms * * 54 ms 53 ms 54 ms tbr2-p032501.n54ny.ip.att.net [12.123.3.86]
18 53 ms 51 ms 52 ms 51 ms 54 ms * * 60 ms 69 ms 51 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
19 49 ms 49 ms 49 ms 49 ms 52 ms * * 49 ms 51 ms 50 ms tbr1-cl17.attga.ip.att.net [12.122.10.70]
20 45 ms 46 ms 48 ms 47 ms 47 ms * * 52 ms 45 ms 46 ms tbr2-cl1835.attga.ip.att.net [12.122.9.158]
21 52 ms 53 ms 54 ms 49 ms 49 ms * * * 50 ms 50 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
22 50 ms 49 ms 51 ms 49 ms 50 ms * * 50 ms 53 ms 49 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
23 47 ms 45 ms 46 ms 53 ms 47 ms * * 46 ms 47 ms 47 ms [12.122.255.82]
24 47 ms 49 ms 49 ms 48 ms 56 ms * * 51 ms 48 ms 48 ms [63.241.192.42]
25 47 ms 47 ms 48 ms 47 ms 61 ms * * 52 ms 48 ms 47 ms [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 10, Received = 8, Lost = 2 (20.0%)
Round Trip Times: Minimum = 47ms, Maximum = 61ms, Average = 49ms

I GOT DISCOED THIS IS THE THINGY FROM IT