Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: RightF00T on April 23, 2007, 09:09:31 PM
-
Well, I recently resubcribed after a decently long hiatus and I come back to find I get booted like clockwork! I'll be in a rope with the planes still flying fine(no warping, no frozen planes) and I'll instantly get the Host Connection Lost popup. I don't lose UDP or anything just instant boot. I'd like to get some insight please.
2.8Ghz Celeron
512MB Ram
ATI 9200SE Vid Card
The only thing I can foresee is the desktop I'm playing on is crossovered at 100Mbps to a laptop that has a wireless connect at 11Mbps. The wireless transmitter is about 20 ft away and I cant really move closer. Wireless card for desktop? I would think I would get lost UDP before this happens
Ping:
Target Name: N/A
IP: 206.16.60.39
Date/Time: 4/23/2007 10:03:22 PM to 4/23/2007 10:05:07 PM
1 * * * * * * * N/A [-]
2 4 ms 3 ms 4 ms 2 ms 2 ms 3 ms 2 ms 3 ms [10.2.15.1]
3 5 ms 3 ms 3 ms 3 ms 3 ms 3 ms 3 ms 3 ms [192.168.100.1]
4 20 ms 10 ms 10 ms 10 ms 9 ms 10 ms 10 ms 11 ms [68.216.218.69]
5 12 ms 11 ms 10 ms 10 ms 11 ms 10 ms 10 ms 10 ms [68.216.218.85]
6 25 ms 24 ms 26 ms 23 ms 24 ms 24 ms 24 ms 23 ms ber00rmo-ge-0-2-2.bellsouth.net [205.152.134.81]
7 42 ms 24 ms 60 ms 24 ms 23 ms 23 ms 23 ms 24 ms ixc01int-pos-6-0-0.bellsouth.net [65.83.239.106]
8 25 ms 157 ms 24 ms 25 ms 25 ms 23 ms 26 ms 23 ms ixc00int-ge-1-0-0.bellsouth.net [205.152.26.64]
9 17 ms 16 ms 16 ms 17 ms 16 ms 16 ms 17 ms 29 ms axr01clt-so-2-0-0.bellsouth.net [65.83.239.66]
10 25 ms 17 ms 17 ms 17 ms 17 ms 19 ms 16 ms 16 ms axr00clt-so-0-0-0.bellsouth.net [65.83.238.10]
11 24 ms 166 ms 24 ms 23 ms 36 ms 24 ms 99 ms 23 ms ixc01gsp-pos-6-0-0.bellsouth.net [65.83.239.65]
12 23 ms 24 ms 25 ms 23 ms 47 ms 24 ms 106 ms 24 ms ixc00gsp-ge-0-0-0.bellsouth.net [205.152.123.64]
13 25 ms 24 ms 24 ms * * 24 ms 24 ms N/A axr00asm-so-2-3-0.bellsouth.net [65.83.239.86]
14 41 ms 28 ms 23 ms 30 ms 34 ms 23 ms 73 ms 23 ms pxr00asm-2-0-0.bellsouth.net [65.83.236.2]
15 23 ms 23 ms 23 ms 23 ms 24 ms 23 ms 25 ms 26 ms so-1-0-0.gar1.Atlanta1.Level3.net [67.72.8.5]
16 29 ms N/A N/A N/A 25 ms N/A N/A 23 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
17 89 ms 41 ms 24 ms 213 ms 26 ms 24 ms 27 ms 24 ms [192.205.34.57]
18 63 ms 55 ms 53 ms 51 ms 52 ms 53 ms 53 ms 54 ms [12.122.96.70]
19 53 ms 53 ms 54 ms 52 ms 54 ms 54 ms 55 ms 52 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
20 54 ms 52 ms 52 ms 52 ms 51 ms 53 ms 50 ms 51 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
21 51 ms 60 ms 55 ms 53 ms 51 ms 53 ms 53 ms 51 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
22 52 ms 52 ms 53 ms 53 ms 182 ms 52 ms 52 ms 54 ms mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
23 53 ms 52 ms 52 ms 50 ms 54 ms 52 ms 52 ms 51 ms [206.16.60.39]
Ping statistics for 206.16.60.39
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 50ms, Maximum = 54ms, Average = 52ms
-
Just booted yet again, after climbing to 21k and having the upperhand on cons over a CV. Instant boot, keep in mind and I had Netstat pulled up in corner and no sign of connection issues
Target Name: N/A
IP: 206.16.60.39
Date/Time: 4/23/2007 10:12:29 PM
1 N/A []
2 3 ms [10.2.15.1]
3 4 ms [192.168.101.1]
4 12 ms [68.216.218.65]
5 12 ms [68.216.218.37]
6 25 ms ber00rmo-ge-0-2-2.bellsouth.net [205.152.134.81]
7 24 ms ixc01int-pos-6-0-0.bellsouth.net [65.83.239.106]
8 24 ms ixc00int-ge-1-0-0.bellsouth.net [205.152.26.64]
9 18 ms axr01clt-so-2-0-0.bellsouth.net [65.83.239.66]
10 N/A []
11 24 ms ixc01gsp-pos-6-0-0.bellsouth.net [65.83.239.65]
12 23 ms ixc00gsp-ge-0-0-0.bellsouth.net [205.152.123.64]
13 N/A []
14 23 ms pxr00asm-so-2-0-0.bellsouth.net [65.83.236.2]
15 28 ms so-1-0-0.gar1.Atlanta1.Level3.net [67.72.8.5]
16 76 ms ae-22-56.car2.Atlanta1.Level3.net [4.68.103.163]
17 45 ms [192.205.34.61]
18 92 ms [12.122.96.70]
19 54 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
20 50 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
21 53 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
22 53 ms mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
23 57 ms [206.16.60.39]
Ping statistics for 206.16.60.39
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 57ms, Maximum = 57ms, Average = 57ms
-
1 minute later
Target Name: N/A
IP: 206.16.60.39
Date/Time: 4/23/2007 10:12:29 PM to 4/23/2007 10:14:14 PM
1 * * * * * * * N/A [-]
2 3 ms 3 ms 6 ms 3 ms 4 ms 3 ms 3 ms 3 ms [10.2.15.1]
3 4 ms 3 ms 3 ms 3 ms 8 ms 3 ms 3 ms 4 ms [192.168.101.1]
4 12 ms 10 ms 10 ms 13 ms 11 ms 15 ms 12 ms 11 ms [68.216.218.65]
5 12 ms 11 ms 10 ms 16 ms 10 ms 13 ms 10 ms 10 ms [68.216.218.37]
6 25 ms 24 ms 108 ms 28 ms 24 ms 24 ms 26 ms 25 ms ber00rmo-ge-0-2-2.bellsouth.net [205.152.134.81]
7 24 ms 26 ms 24 ms 242 ms 26 ms 24 ms 24 ms 29 ms ixc01int-pos-6-0-0.bellsouth.net [65.83.239.106]
8 24 ms 54 ms 25 ms 36 ms 24 ms 40 ms 27 ms 97 ms ixc00int-ge-1-0-0.bellsouth.net [205.152.26.64]
9 18 ms 16 ms 17 ms 18 ms 18 ms 24 ms 29 ms 16 ms axr01clt-so-2-0-0.bellsouth.net [65.83.239.66]
10 * 23 ms 19 ms 23 ms 27 ms 17 ms 16 ms 17 ms axr00clt-so-0-0-0.bellsouth.net [65.83.238.10]
11 24 ms 25 ms 74 ms 144 ms 27 ms 24 ms 24 ms 124 ms ixc01gsp-pos-6-0-0.bellsouth.net [65.83.239.65]
12 23 ms 25 ms 28 ms 26 ms 23 ms 25 ms 33 ms 38 ms ixc00gsp-ge-0-0-0.bellsouth.net [205.152.123.64]
13 * 24 ms 26 ms 24 ms 24 ms 23 ms * 67 ms axr00asm-so-2-3-0.bellsouth.net [65.83.239.86]
14 23 ms 23 ms 31 ms 23 ms 66 ms 31 ms 23 ms 38 ms pxr00asm-so-2-0-0.bellsouth.net [65.83.236.2]
15 28 ms 25 ms 26 ms 34 ms 32 ms 27 ms 27 ms 26 ms so-1-0-0.gar1.Atlanta1.Level3.net [67.72.8.5]
16 N/A N/A N/A N/A 28 ms N/A N/A 31 ms ae-12-55.car2.Atlanta1.Level3.net [4.68.103.131]
17 45 ms 24 ms 26 ms 24 ms 25 ms 224 ms 27 ms 26 ms [192.205.34.61]
18 92 ms 58 ms 53 ms 52 ms 56 ms 53 ms 55 ms 89 ms [12.122.96.70]
19 54 ms 100 ms 58 ms 53 ms 76 ms 52 ms 53 ms 55 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
20 50 ms 54 ms 52 ms 67 ms 55 ms 55 ms 58 ms 54 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
21 53 ms 51 ms 53 ms 54 ms 55 ms 52 ms 54 ms 92 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
22 53 ms 56 ms 57 ms 102 ms 54 ms 57 ms 54 ms 56 ms mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
23 57 ms 51 ms 59 ms 54 ms 55 ms 54 ms 53 ms 56 ms [206.16.60.39]
Ping statistics for 206.16.60.39
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 51ms, Maximum = 59ms, Average = 54ms
-
Seems the network issue is within Bellsouth. Have you sent this to them?
-
Skuzzy I was thinking it was the way I was connecting to the internet. Are there any settings to tweak to make a Wireless connection more stable? Its just really weird that I will have a solid connection and then instant boot, yet I load up a webpage immediately and it loads right up.
-
when i first got cable and decided to setup my apartment with 802.11g, I got some cheap D-link wireless router from Target... it seemed to work with "typical internet usage", browsing, email, etc. but would absolutely not work with any type of online game.
I decided to get a linksys wireless router, and now everything works, including games. I have no idea why, but I ain't complaining.. we have 3 laptops using the same connection (all in aces high at the same time, to boot), and have minimal connection issues (though yesterday I did lose udp and got disco'd once).
so, my solution was a new router, and I still dont know why the old one didn't work properly.
-
Wireless will never be as reliable as a wired connection. There are always bit errors in a wireless connection. Fortunately, TCP can take care of that by re-trying the packet. However, UDP packets with errors are just lost.
Relaying through another PC to get to the wireless connection also introduces a potential for more problems.
Simepl enough to test all this out. Just connect directly to the Internet connection, by-passing the wireless and PC.
But, the trace you posted does have packet loss problems in the Bellsouth network.