Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Skuzzy on July 07, 2014, 12:30:20 PM
-
There seems to be an issue with Verizon. If you are seeing the error message stating you cannot connect to the "Game Manager", and you are certain your firewall is not blocking, AND you have reset your router, then we would like to see a Ping Plot (http://www.pingplotter.com/downloads/pngplt_1.exe) from you.
Please post the text output or image of your scan in this thread. Thank you.
-
I can ping .149 but neither .153 nor .154 respond. No problem entering arenas though (last night anyway).
Bytes Source Seq Time Units
64 71.252.137.149 1 67.5 ms
64 71.252.137.149 2 68.1 ms
64 71.252.137.149 3 69.3 ms
64 71.252.137.149 4 68.1 ms
64 71.252.137.149 5 67.6 ms
64 71.252.137.149 6 67.7 ms
64 71.252.137.149 7 68.3 ms
64 71.252.137.149 8 69.2 ms
64 71.252.137.149 9 68.6 ms
64 71.252.137.149 10 68.9 ms
Time minimum: 67.50 ms
Time average: 68.25 ms
Time maximum: 69.30 ms
Packets transmitted: 10
Packets received: 10
Successful packets: 100%
Traceroute to 71.252.137.154:
Hop Hostname IP Time 1
1 ubuntu.local 192.168.1.100 0.094
1 192.168.1.1 192.168.1.1 4.387
1 192.168.1.1 192.168.1.1 1.313
2 10.183.12.1 10.183.12.1 8.236
3 172.30.12.33 172.30.12.33 23.400
4 12.249.197.9 12.249.197.9 26.406
5 cr81.sj2ca.ip.att.net 12.122.110.110 29.706
6 cr1.sffca.ip.att.net 12.122.1.117 37.359
7 gar23.sffca.ip.att.net 12.122.114.5 30.187
9 vlan90.csw4.SanJose1.Level3.n et 4.69.152.254 97.030
10 ae-82-82.ebr2.SanJose1.Level3.net 4.69.153.25 101.658
11 ae-2-2.ebr2.SanJose5.Level3.net 4.69.148.141 98.212
12 ae-1-100.ebr2.SanJose5.Level3.net 4.69.148.110 96.717
13 ae-6-6.ebr2.LosAngeles1.Level3.net 4.69.148.201 99.779
14 ae-83-83.csw3.Dallas1.Level3.net 4.69.151.157 97.508
15 ae-93-93.csw4.Dallas1.Level3.net 4.69.151.169 97.350
16 ae-2-2.ebr1.Miami1.Level3.net 4.69.140.134 96.676
17 ae-1-51.edge2.Miami1.Level3.net 4.69.138.70 97.539
18 ae-1-51.edge2.Miami1.Level3.net 4.69.138.70 98.776
19 A-SUR-NET-I.edge2.Miami1.Level3.net 4.31.223.78 103.315
20 63.245.70.26 63.245.70.26 131.259
21 63.245.70.26 63.245.70.26 125.749
22 xe-0-1-0-h1-hfc02.flowja.com 72.252.25.179 142.215
I have no idea why it goes to Dallas then out to Miami to get lost. The traceroute to .149 is much cleaner:
Hop Hostname IP Time 1
1 ubuntu.local 192.168.1.100 0.093
1 192.168.1.1 192.168.1.1 2.016
1 192.168.1.1 192.168.1.1 1.271
2 10.183.12.1 10.183.12.1 8.522
3 172.30.12.33 172.30.12.33 21.528
4 12.249.197.9 12.249.197.9 25.966
5 cr81.sj2ca.ip.att.net 12.122.110.110 28.393
6 cr1.sffca.ip.att.net 12.122.1.117 29.299
7 12.122.114.53 12.122.114.53 27.214
8 att-gw.sj.alter.net 192.205.36.62 27.610
9 B100.DLLSTX-LCR-21.verizon-gni.net 130.81.199.59 68.837
11 static-71-252-137-149.dllstx.fios.verizon.net 71.252.137.149 69.686
-
This looks like a bad route injection from an ISP in Jamaica.
They look like they are trying to claim our IP address as there own.
Not good.
-
New game plan.
I need anyone and everyone to post up a trace route or Ping Plot to the following addresses.
71.252.137.149
71.252.137.151
71.252.137.153
Thank you for the help.
-
Here's .151:
Hop Hostname IP Time 1
1 ubuntu.local 192.168.1.100 0.095
1 192.168.1.1 192.168.1.1 2.122
1 192.168.1.1 192.168.1.1 1.266
2 10.183.12.1 10.183.12.1 9.564
3 172.30.12.33 172.30.12.33 24.663
4 12.249.197.9 12.249.197.9 25.833
5 cr81.sj2ca.ip.att.net 12.122.110.110 29.143
6 cr1.sffca.ip.att.net 12.122.1.117 32.041
7 12.122.114.53 12.122.114.53 30.381
8 att-gw.sj.alter.net 192.205.36.62 26.792
9 P0-8-0-0.DLLSTX-LCR-21.verizon-gni.net 130.81.199.35 69.543
11 static-71-252-137-151.dllstx.fios.verizon.net 71.252.137.151 68.387
-
C:\>tracert 71.252.137.149
Tracing route to static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 10 ms 10 ms 10 ms bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
3 8 ms 9 ms 8 ms dist2-vlan60.mrdnct.sbcglobal.net [66.159.184.22
7]
4 12 ms 11 ms 11 ms 12.83.97.130
5 40 ms 39 ms 39 ms gar13.cgcil.ip.att.net [12.122.132.121]
6 36 ms 41 ms 36 ms 0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
7 59 ms 59 ms 59 ms B200.DLLSTX-LCR-21.verizon-gni.net [130.81.162.1
53]
8 * * * Request timed out.
9 60 ms 60 ms 60 ms static-71-252-137-149.dllstx.fios.verizon.net [7
1.252.137.149]
Trace complete.
C:\>tracert 71.252.137.151
Tracing route to static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 10 ms 10 ms 10 ms bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
3 * 9 ms 8 ms dist1-vlan60.mrdnct.sbcglobal.net [66.159.184.22
6]
4 10 ms 11 ms 12 ms 12.83.32.254
5 35 ms 35 ms 36 ms gar13.cgcil.ip.att.net [12.122.132.121]
6 32 ms 32 ms 32 ms 0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
7 57 ms 56 ms 55 ms P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net [130.81.1
51.243]
8 * * * Request timed out.
9 56 ms 56 ms 55 ms static-71-252-137-151.dllstx.fios.verizon.net [7
1.252.137.151]
Trace complete.
C:\>tracert 71.252.137.153
Tracing route to static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 10 ms 10 ms 10 ms bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
3 8 ms 8 ms 8 ms dist2-vlan60.mrdnct.sbcglobal.net [66.159.184.22
7]
4 11 ms 11 ms 11 ms 12.83.97.130
5 40 ms 39 ms 39 ms gar13.cgcil.ip.att.net [12.122.132.121]
6 37 ms 36 ms 37 ms 0.ae10.BR3.CHI13.ALTER.NET [204.255.168.165]
7 65 ms 60 ms 59 ms P0-8-0-0.DLLSTX-LCR-22.verizon-gni.net [130.81.1
99.37]
8 * * * Request timed out.
9 60 ms 60 ms 60 ms static-71-252-137-153.dllstx.fios.verizon.net [7
1.252.137.153]
Trace complete.
-
Now .153 and .154 work. Very weird.
Hop Hostname IP Time 1
1 ubuntu.local 192.168.1.100 0.092
1 192.168.1.1 192.168.1.1 4.309
1 192.168.1.1 192.168.1.1 1.276
2 10.183.12.1 10.183.12.1 8.979
3 172.30.12.33 172.30.12.33 21.858
4 12.249.197.9 12.249.197.9 24.687
5 cr81.sj2ca.ip.att.net 12.122.110.110 31.419
6 cr1.sffca.ip.att.net 12.122.1.117 32.274
7 12.122.114.53 12.122.114.53 28.589
8 att-gw.sj.alter.net 192.205.36.62 28.114
9 P0-0-0-0.DLLSTX-LCR-22.verizon-gni.net 130.81.151.245 68.041
11 static-71-252-137-153.dllstx.fios.verizon.net 71.252.137.153 70.026
Hop Hostname IP Time 1
1 ubuntu.local 192.168.1.100 0.089
1 192.168.1.1 192.168.1.1 1.302
1 192.168.1.1 192.168.1.1 1.254
2 10.183.12.1 10.183.12.1 8.071
3 172.30.12.33 172.30.12.33 42.024
4 12.249.197.9 12.249.197.9 34.799
5 cr81.sj2ca.ip.att.net 12.122.110.110 29.662
6 cr1.sffca.ip.att.net 12.122.1.117 29.202
7 12.122.114.53 12.122.114.53 28.614
8 att-gw.sj.alter.net 192.205.36.62 27.681
9 B100.DLLSTX-LCR-21.verizon-gni.net 130.81.199.59 69.412
11 static-71-252-137-154.dllstx.fios.verizon.net 71.252.137.154 69.536
-
From space coast in Florida
-
It appears to get worse as PingPlotter runs longer.
-
same result on all 3 with 15-17 hops
ending and stoping at
72.252.25.179 xe-0-1-0-h1-hfc02.flowja.com
-
I called the ISP in Jamaica, but they support people would not allow me to talk to one of their networking engineers. I managed to get an email address and have sent off an email detailing the problem.
Not sure if anything will come of it. Hopefully, they will realize what they have done and correct it quickly.
-
Here are mine.....
Target Name: static-71-252-137-149.dllstx.fios.verizon.net
IP: 71.252.137.149
Date/Time: 7/7/2014 4:45:15 PM to 7/7/2014 4:45:44 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 30 0 0.0 10 20 15 WRT610N [192.168.1.1]
2 30 0 0.0 19 49 29 [10.241.112.1]
3 30 0 0.0 19 40 29 dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
4 30 0 0.0 19 49 29 crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
5 30 0 0.0 19 59 36 bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
6 30 0 0.0 19 70 33 xe-5-0-3.bar2.Boston1.Level3.net [4.53.56.169]
7 30 0 0.0 29 50 40 ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
8 30 0 0.0 29 69 42 ae-47-47.ebr1.NewYork2.Level3.net [4.69.201.46]
9 30 23 76.7 29 50 37 ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10 30 0 0.0 29 90 39 [208.51.134.134]
11 30 0 0.0 29 69 40 [64.215.195.34]
12 30 0 0.0 59 90 78 P0-0-0-0.DLLSTX-LCR-22.verizon-gni.net [130.81.151.245]
13 30 30 100.0 0 0 0 [-]
14 30 0 0.0 69 99 79 static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]
Target Name: static-71-252-137-151.dllstx.fios.verizon.net
IP: 71.252.137.151
Date/Time: 7/7/2014 4:46:41 PM to 7/7/2014 4:47:10 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 30 0 0.0 15 31 27 WRT610N [192.168.1.1]
2 30 0 0.0 31 62 47 [10.241.112.1]
3 30 0 0.0 31 62 47 dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
4 30 0 0.0 31 77 48 crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
5 30 0 0.0 31 78 48 bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
6 30 0 0.0 30 124 54 xe-4-2-0.bar2.Boston1.Level3.net [4.53.56.129]
7 30 0 0.0 31 77 52 ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
8 30 0 0.0 31 77 53 ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.50]
9 28 19 67.9 31 62 51 ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10 30 0 0.0 31 124 53 [208.51.134.134]
11 30 0 0.0 31 62 47 [208.49.136.38]
12 30 0 0.0 77 109 94 P0-0-0-0.DLLSTX-LCR-21.verizon-gni.net [130.81.151.243]
13 30 30 100.0 0 0 0 [-]
14 30 0 0.0 77 109 97 static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]
Target Name: static-71-252-137-153.dllstx.fios.verizon.net
IP: 71.252.137.153
Date/Time: 7/7/2014 4:47:49 PM to 7/7/2014 4:48:19 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 30 0 0.0 15 31 25 WRT610N [192.168.1.1]
2 30 0 0.0 31 62 54 [10.241.112.1]
3 30 0 0.0 31 62 53 dtr02sbdgma-tge-0-0-0-3.sbdg.ma.charter.com [96.34.84.158]
4 30 0 0.0 31 77 52 crr03oxfrma-tge-0-1-0-1.oxfr.ma.charter.com [96.34.80.162]
5 30 0 0.0 31 77 51 bbr01oxfrma-bue-1.oxfr.ma.charter.com [96.34.2.12]
6 30 0 0.0 31 109 53 xe-4-2-0.bar2.Boston1.Level3.net [4.53.56.129]
7 30 0 0.0 31 62 52 ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
8 30 0 0.0 31 77 51 ae-48-48.ebr1.NewYork2.Level3.net [4.69.201.50]
9 26 19 73.1 31 78 55 ae-1-51.ear1.NewYork2.Level3.net [4.69.138.201]
10 30 0 0.0 31 77 53 [208.51.134.134]
11 30 0 0.0 46 77 57 [64.215.195.34]
12 30 0 0.0 77 124 97 B100.DLLSTX-LCR-21.verizon-gni.net [130.81.199.59]
13 30 30 100.0 0 0 0 [-]
14 30 0 0.0 78 109 98 static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]
-
I am assuming all of you who have the same, or similar, traces for all three IP addresses, are also working just fine.
-
Have been able to connect to AH however the lost count for LW Arena cycles frequently from 0 to 1 while watching ping details.
-
Have been able to connect to AH however the lost count for LW Arena cycles frequently from 0 to 1 while watching ping details.
That could happen at any router from you to the servers. You would need to run Ping Plotter, for a few minutes, to capture where that is happening.
-
That could happen at any router from you to the servers. You would need to run Ping Plotter, for a few minutes, to capture where that is happening.
Ran PingPlotter on 71.252.137.154.
-
Here's mine
-
I am assuming all of you who have the same, or similar, traces for all three IP addresses, are also working just fine.
Yes Skuzzy, while mines not pretty, I CAN connect ok.
-
(http://i1314.photobucket.com/albums/t572/Schen88/Capture_zpsca48b982.jpg)
(http://i1314.photobucket.com/albums/t572/Schen88/49_zpsd68240a8.jpg)
(http://i1314.photobucket.com/albums/t572/Schen88/51_zps12ad4617.jpg)
Correction I ran ping plotter again and on all the tests of
71.252.137.153
71.252.137.154
and now this.....
(http://i1314.photobucket.com/albums/t572/Schen88/wtf_zpsc109a160.jpg)
-
Here's an updated longer one of mine still unable to connect,may be forced to cancel my subscription if I am unable to connect.,runnin a trace on .151 now will add as soon as its done a 15 minute or better run.
-
Ran PingPlotter on 71.252.137.154.
Your ISP is using Xo Communications as their Internet transport and it appears XO is having issues with congestion or other problems.
You would need to contact your ISP's Tier 2 support (not the first line of defense support which is not going to help at all) and notify them of the issue. They will not confirm there is a problem, as it would mean they would be required to address it. However, the problem may suddenly clear itself up after you notify them, unless XO is not able to correct the issue.
-
Here's mine
Nothing appears to be wrong in your trace/Ping Plot. If you are having problems connecting to the game, then it coul d be something local to your computer. I am starting to suspect Kaspersky may have an update in the wild which is blocking some access, especially to the Early War arena.
-
(http://i1314.photobucket.com/albums/t572/Schen88/Capture_zpsca48b982.jpg)
(http://i1314.photobucket.com/albums/t572/Schen88/49_zpsd68240a8.jpg)
(http://i1314.photobucket.com/albums/t572/Schen88/51_zps12ad4617.jpg)
Correction I ran ping plotter again and on all the tests of
71.252.137.153
71.252.137.154
and now this.....
(http://i1314.photobucket.com/albums/t572/Schen88/wtf_zpsc109a160.jpg)
Those Ping Plots are looking normal now. If you still cannot connect, what anti-xxx software are you using?
-
Your ISP is using Xo Communications as their Internet transport and it appears XO is having issues with congestion or other problems.
You would need to contact your ISP's Tier 2 support (not the first line of defense support which is not going to help at all) and notify them of the issue. They will not confirm there is a problem, as it would mean they would be required to address it. However, the problem may suddenly clear itself up after you notify them, unless XO is not able to correct the issue.
Thank you Skuzzy. My provider is Brighthouse. Will call them today.
-
New game plan.
I need anyone and everyone to post up a trace route or Ping Plot to the following addresses.
71.252.137.149
71.252.137.151
71.252.137.153
Thank you for the help.
.149 (http://i478.photobucket.com/albums/rr149/Rich46yo/149_zpse3adb219.png)
.151 (http://i478.photobucket.com/albums/rr149/Rich46yo/151_zps2cca776e.png)
.153 (http://i478.photobucket.com/albums/rr149/Rich46yo/153_zps3b1fcc58.png)
Still cant get on LWA. The game freezes up when I try. Every other arena, and every other program, on the computer is fine.
-
Where does it freeze up?
What anti-virus is installed on your computer?
-
Where does it freeze up?
What anti-virus is installed on your computer?
Resetting my router solved it.
-
Resetting my router solved it.
Good to hear.
-
Those Ping Plots are looking normal now. If you still cannot connect, what anti-xxx software are you using?
still cant connect, im using trend micro as a antivirus software.... still not able to connect to the main arena,
currently talking with my tech support to hopefully refresh BGP tables.
-
still cant connect, im using trend micro as a antivirus software.... still not able to connect to the main arena,
currently talking with my tech support to hopefully refresh BGP tables.
I assume you disable your anti-virus before running the game.
-
ping plotter stuff for me. :bhead :furious no way to send email from me to support@hitechcreations.com Can't get the dern ping plotter image to copy and past into the buffer in this BBS.
Target Name: static-71-252-137-153.dllstx.fios.verizon.net
IP: 71.252.137.153
Date/Time: 7/8/2014 9:42:06 PM
1 1 ms [192.168.2.1]
2 6 ms [10.252.0.1]
3 8 ms 173-219-249-18-link.sta.suddenlink.net [173.219.249.18]
4 26 ms 173-219-249-248-link.sta.suddenlink.net [173.219.249.248]
5 * [-]
6 * [-]
7 47 ms TenGigE0-3-1-0.GW2.CHI13.ALTER.NET [152.179.92.5]
8 * [-]
9 30 ms static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]
Ping statistics for static-71-252-137-153.dllstx.fios.verizon.net
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 30ms, Maximum = 30ms, Average = 30ms baloney! I got 100% packet loss on this one between 4-5, 5-6,7-8!!!
Target Name: static-71-252-137-151.dllstx.fios.verizon.net
IP: 71.252.137.151
Date/Time: 7/8/2014 9:52:40 PM
1 0 ms 0 ms 0 ms [192.168.2.1]
2 12 ms 8 ms 7 ms [10.252.0.1]
3 12 ms 10 ms 6 ms 173-219-249-18-link.sta.suddenlink.net [173.219.249.18]
4 22 ms 27 ms 21 ms 173-219-249-248-link.sta.suddenlink.net [173.219.249.248]
5 25 ms 30 ms 18 ms ae2-115.dal33.ip4.tinet.net [46.33.80.101]
6 N/A 59 ms 52 ms xe-2-0-0.chi11.ip4.tinet.net [89.149.187.89]
7 N/A N/A 46 ms TenGigE0-3-1-0.GW2.CHI13.ALTER.NET [152.179.92.5]
8 * * * [-]
9 30 ms 22 ms * static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]
Ping statistics for static-71-252-137-151.dllstx.fios.verizon.net
Packets: Sent = 3, Received = 2, Lost = 1 (33.3%)
Round Trip Times: Minimum = 22ms, Maximum = 30ms, Average = 26ms more tube steak!!!! 100% PL again.
Target Name: static-71-252-137-149.dllstx.fios.verizon.net
IP: 71.252.137.149
Date/Time: 7/8/2014 9:54:07 PM
1 0 ms [192.168.2.1]
2 9 ms [10.252.0.1]
3 8 ms 173-219-249-18-link.sta.suddenlink.net [173.219.249.18]
4 24 ms 173-219-249-248-link.sta.suddenlink.net [173.219.249.248]
5 * [-]
6 47 ms xe-4-1-0.chi11.ip4.tinet.net [141.136.109.149]
7 34 ms B200.DLLSTX-LCR-22.verizon-gni.net [130.81.162.161]
8 53 ms B200.DLLSTX-LCR-21.verizon-gni.net [130.81.162.153]
9 * [-]
10 47 ms static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]
Ping statistics for static-71-252-137-149.dllstx.fios.verizon.net
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 47ms, Maximum = 47ms, Average = 47ms again, at least two instances of 100% PL (per scan)!!!!! :furious :bhead :bhead :bhead :bhead
-
I will reset my suddenlink.net modem tonight, and feed the squirrels that package up the electrons in paper bags.
-
I will reset my suddenlink.net modem tonight, and feed the squirrels that package up the electrons in paper bags.
If you are located in Texas, then you need to point them to the traces you took and ask why they are routing the data through Chicago when the final destination is also in Texas.
-
1 Call to my ISP which they denied any problems going on with my Connection or my Internet activity the next few hours I was able to connect to AH arena's
Still a little unstable but at least I got my AH FIX FOR THE DAY!! :rock
-
It seems to be much better than yesterday. I am getting reports from several players who could not play they are now reaching the servers just fine. Hopefully, today will finally see everything back to normal.
-
Your ISP is using Xo Communications as their Internet transport and it appears XO is having issues with congestion or other problems.
You would need to contact your ISP's Tier 2 support (not the first line of defense support which is not going to help at all) and notify them of the issue. They will not confirm there is a problem, as it would mean they would be required to address it. However, the problem may suddenly clear itself up after you notify them, unless XO is not able to correct the issue.
Just spoke with Tier 3 support at Brighthouse and they did the same old song and dance. I asked directly how could we get the message to XO about the dropped packets and never got an answer.
They did offer to upgrade my cable modem for free "just in case" I decided to upgrade my service in the future. I explained that the bandwidth requirement of this game has nothing to do with XO dropping packets.
So they are coming out tomorrow to give me a new modem and check out the local equipment.
Let's hope they do something about the dropped packets at XO.
-
Just got off the phone with XO. Yes they did actually talk to me!
In case you're curious, technician said in so many words..."our engineers need to tweak policy so you don't see packet loss when you ping us, we're not really dropping data packets. We sure do get a lot of calls about that."
-
Just got off the phone with XO. Yes they did actually talk to me!
In case you're curious, technician said in so many words..."our engineers need to tweak policy so you don't see packet loss when you ping us, we're not really dropping data packets. We sure do get a lot of calls about that."
Of course they are going to say that. If you are getting disco's and you do a Ping Plot (by the way, you can chose to use another protocol in Ping Plot, and not ICMP), and see packet loss in the path, you can be pretty certain that there really is packet loss happening.
Aces High does a lot of things to help maintain a connection. It just cannot do much when there is no data to work with (ie packet loss).
-
https://www.dropbox.com/s/myedwn5ydaoilm1/Screenshot%202014-07-09%2012.19.46.png,roy here's another trace route screen shot if you want to take a look at as of today I haven't tried to connect yet just reinstaling the game now.
-
https://www.dropbox.com/s/myedwn5ydaoilm1/Screenshot%202014-07-09%2012.19.46.png,roy here's another trace route screen shot if you want to take a look at as of today I haven't tried to connect yet just reinstaling the game now.
That trace looks pretty normal. Run a trace to 71.252.137.151 and see if they match. if they do, then you should be good to go. If they do not, then the Internet is still healing for you.
-
Of course they are going to say that. If you are getting disco's and you do a Ping Plot (by the way, you can chose to use another protocol in Ping Plot, and not ICMP), and see packet loss in the path, you can be pretty certain that there really is packet loss happening.
Aces High does a lot of things to help maintain a connection. It just cannot do much when there is no data to work with (ie packet loss).
It was hard not to laugh while I was talking with him! All I can do is shake my head and quietly look for a new ISP.
-
YES,fresh reinstall of the game,my ISP set me up with a new ip (for free) and was an instant connection to the game.Pings on all the arenas are constant and around 100 or under.Thanks for the support Roy and the tips.
-
Game is good to go for me too skuzzy thanks for taking this serious, even though it really seemed to effect Canadians mostly, my ping is holding 110 to 150 with minor bounces, but I can play and thats still not all that bad.
-
Good to hear.
Problems like this can be so frustrating as all you can do is sit back and wait for the fixes to propagate.
We appreciate the patience everyone showed. <S>
-
Good to hear.
Problems like this can be so frustrating as all you can do is sit back and wait for the fixes to propagate.
We appreciate the patience everyone showed. <S>
Yes frustrating, you mean almost throwing your joystick across the room, yelling at a computer frustrating, I can relate... :bolt:
Again thanks im sure it wasn't an easy find or solution.
-
Finding the problem was not that hard. Getting them to correct it took more time than I would have liked, and then just having to wait on the Internet to catch up was really painful.
-
Here's mine. Northern Delaware on Comcast.
149:
Target Name: static-71-252-137-149.dllstx.fios.verizon.net
IP: 71.252.137.149
Date/Time: 7/13/2014 12:59:27 PM
2 N/A 42 ms 21 ms 11 ms N/A 11 ms te-9-2-ur01.limestonedr.de.panjde.comcast.net [68.85.78.73]
3 8 ms 10 ms 10 ms 9 ms N/A 11 ms te-1-1-ur02.limestonedr.de.panjde.comcast.net [68.85.35.34]
4 13 ms 48 ms 9 ms 10 ms N/A 9 ms ge-3-22-ur01.williamsport.pa.pitt.comcast.net [68.86.211.161]
5 N/A N/A N/A N/A N/A 14 ms pos-5-15-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.249]
6 15 ms 13 ms 14 ms 14 ms N/A 14 ms he-0-10-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
7 13 ms 12 ms 16 ms 13 ms N/A 12 ms n-a.GW12.IAD8.ALTER.NET [152.179.50.205]
8 67 ms 51 ms 54 ms 51 ms N/A 50 ms B100.DLLSTX-LCR-21.verizon-gni.net [130.81.199.59]
9 * * * * N/A * [-]
10 50 ms 66 ms 50 ms 52 ms N/A 49 ms static-71-252-137-149.dllstx.fios.verizon.net [71.252.137.149]
Ping statistics for static-71-252-137-149.dllstx.fios.verizon.net
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 49ms, Maximum = 66ms, Average = 53ms
151:
Target Name: static-71-252-137-151.dllstx.fios.verizon.net
IP: 71.252.137.151
Date/Time: 7/13/2014 1:02:36 PM to 7/13/2014 1:04:51 PM
2 65 ms 13 ms 17 ms 10 ms 13 ms 8 ms 60 ms 8 ms 10 ms 11 ms te-9-2-ur01.limestonedr.de.panjde.comcast.net [68.85.78.73]
3 N/A 10 ms 96 ms 10 ms 43 ms 11 ms 41 ms 10 ms 11 ms 11 ms xe-2-0-3-0-ar03.coatesville.pa.panjde.comcast.net [68.86.153.229]
4 N/A N/A 11 ms N/A N/A N/A N/A N/A N/A 10 ms so-20-0-0-0-ar03.newcastle.de.panjde.comcast.net [68.86.208.141]
5 N/A N/A N/A N/A N/A N/A 17 ms N/A 15 ms 17 ms pos-5-12-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.137]
6 16 ms 18 ms 14 ms 12 ms 16 ms 15 ms 13 ms 15 ms 30 ms 30 ms he-0-11-0-1-pe07.ashburn.va.ibone.comcast.net [68.86.83.78]
7 14 ms 13 ms 14 ms 15 ms 15 ms 13 ms 46 ms 15 ms 15 ms 14 ms n-a.GW12.IAD8.ALTER.NET [152.179.50.205]
8 55 ms 54 ms 53 ms 51 ms 53 ms 51 ms 59 ms 52 ms 53 ms 54 ms B200.DLLSTX-LCR-22.verizon-gni.net [130.81.162.161]
9 * * * * * * * * * * [-]
10 62 ms 51 ms 53 ms 52 ms 53 ms 52 ms 67 ms 53 ms 52 ms 53 ms static-71-252-137-151.dllstx.fios.verizon.net [71.252.137.151]
Ping statistics for static-71-252-137-151.dllstx.fios.verizon.net
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 51ms, Maximum = 67ms, Average = 54ms
And 153:
Target Name: static-71-252-137-153.dllstx.fios.verizon.net
IP: 71.252.137.153
Date/Time: 7/13/2014 1:05:26 PM to 7/13/2014 1:07:41 PM
2 428 ms 9 ms 14 ms 9 ms 10 ms 10 ms 10 ms 9 ms 9 ms 10 ms te-9-2-ur01.limestonedr.de.panjde.comcast.net [68.85.78.73]
3 N/A 10 ms 9 ms 10 ms 11 ms 42 ms 11 ms 11 ms 10 ms 10 ms xe-2-0-3-0-ar03.coatesville.pa.panjde.comcast.net [68.86.153.229]
4 N/A N/A N/A N/A 10 ms N/A N/A 11 ms N/A 11 ms so-18-1-0-0-ar03.newcastle.de.panjde.comcast.net [68.86.208.125]
5 N/A 17 ms N/A N/A N/A 14 ms N/A N/A N/A 19 ms pos-5-15-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.249]
6 N/A 14 ms 15 ms 15 ms 15 ms 13 ms 29 ms 14 ms 14 ms 13 ms he-0-12-0-1-pe07.ashburn.va.ibone.comcast.net [68.86.83.86]
7 N/A 14 ms 13 ms 15 ms 15 ms 15 ms 14 ms 29 ms 14 ms 15 ms n-a.GW12.IAD8.ALTER.NET [152.179.50.205]
8 N/A 52 ms 54 ms 52 ms 52 ms 53 ms 54 ms 51 ms 53 ms 57 ms B100.DLLSTX-LCR-21.verizon-gni.net [130.81.199.59]
9 N/A * * * * * * * * * [-]
10 55 ms 52 ms 52 ms 56 ms 51 ms 53 ms 51 ms 53 ms 54 ms 52 ms static-71-252-137-153.dllstx.fios.verizon.net [71.252.137.153]
Ping statistics for static-71-252-137-153.dllstx.fios.verizon.net
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 51ms, Maximum = 56ms, Average = 52ms
-
Okay, it is showing packet loss in Comcast's network. On occasion, right at the second hop (your connection). Pretty messy.
Have you tried power cycling your router? If you have, then your connection is suspect.
-
That was just after a power cycle. I noticed that second hop goes from a very local server then up into PA near Philly then back down near here before heading south to VA. You think them interwebs would take a smarter route! You wouldn't drive that way!
Factor in a hot day and some nasty storms this past week. Don't appear to be having problems but my flying time has been scarce. Just posted for your info
-
Skuzzy here's something I haven't seen before captured Friday 7/11 @ 2033 CST.
I didn't open AH until immediately after seeing this. Arenas were all up and appeared to have stable ping.
Sorry meant to post earlier.
(http://i61.tinypic.com/33kskxv.jpg)
(http://i58.tinypic.com/11mauts.jpg)
-
aberdeen sd midco cable
-
aberdeen sd midco cable
Let it run 5-10 minutes pinging every second to get a good sample for the averages.