+ Reply to Thread
Results 1 to 9 of 9
Discussion: Battlefield 2142 / Battlefield 2142 - Technical Support & FAQs - Server ping unstable/need analysis of test results - This is not a new subject for me. I have posted about this a couple
-
09-01-2009, 02:02 AM #1
- Join Date
- Aug 2008
- Location
- Shooting down Repaq and Tom Da Slaya's Gunship with a SAAW after being TV missled....ok National City, CA
- Posts
- 399
Server ping unstable/need analysis of test results
This is not a new subject for me. I have posted about this a couple of times. For a couple of years now my server ping has been unstable. My ISP recently upgraded the node where I connect to their server. There has been some improvement in my overall ping. Whereas it used to be around 110-120 ms. It is now between 80-85 ms. However this has not solved the instability/ping spikes. Someone suggested this is a sign of continued congestion on my ISP server. BTW, this happens on all servers in bf2142. I have performed a ping test and a trace route and was hoping somebody at TG might have some suggestions.
Here are the ping test results:
Pinging 64.34.163.112 with 32 bytes of data:
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=110ms TTL=119
Reply from 64.34.163.112: bytes=32 time=85ms TTL=119
Reply from 64.34.163.112: bytes=32 time=87ms TTL=119
Reply from 64.34.163.112: bytes=32 time=86ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=99ms TTL=119
Reply from 64.34.163.112: bytes=32 time=95ms TTL=119
Reply from 64.34.163.112: bytes=32 time=111ms TTL=119
Reply from 64.34.163.112: bytes=32 time=109ms TTL=119
Reply from 64.34.163.112: bytes=32 time=80ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=80ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=92ms TTL=119
Reply from 64.34.163.112: bytes=32 time=137ms TTL=119
Reply from 64.34.163.112: bytes=32 time=80ms TTL=119
Reply from 64.34.163.112: bytes=32 time=91ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=100ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=91ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=80ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=93ms TTL=119
Reply from 64.34.163.112: bytes=32 time=105ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=87ms TTL=119
Reply from 64.34.163.112: bytes=32 time=109ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=79ms TTL=119
Reply from 64.34.163.112: bytes=32 time=91ms TTL=119
Reply from 64.34.163.112: bytes=32 time=90ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=108ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=109ms TTL=119
Reply from 64.34.163.112: bytes=32 time=96ms TTL=119
Reply from 64.34.163.112: bytes=32 time=110ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=90ms TTL=119
Reply from 64.34.163.112: bytes=32 time=85ms TTL=119
Reply from 64.34.163.112: bytes=32 time=120ms TTL=119
Reply from 64.34.163.112: bytes=32 time=90ms TTL=119
Reply from 64.34.163.112: bytes=32 time=126ms TTL=119
Reply from 64.34.163.112: bytes=32 time=104ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=93ms TTL=119
Reply from 64.34.163.112: bytes=32 time=130ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=99ms TTL=119
Reply from 64.34.163.112: bytes=32 time=122ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=110ms TTL=119
Reply from 64.34.163.112: bytes=32 time=93ms TTL=119
Reply from 64.34.163.112: bytes=32 time=128ms TTL=119
Reply from 64.34.163.112: bytes=32 time=96ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Reply from 64.34.163.112: bytes=32 time=95ms TTL=119
Reply from 64.34.163.112: bytes=32 time=86ms TTL=119
Reply from 64.34.163.112: bytes=32 time=92ms TTL=119
Reply from 64.34.163.112: bytes=32 time=101ms TTL=119
Reply from 64.34.163.112: bytes=32 time=97ms TTL=119
Reply from 64.34.163.112: bytes=32 time=83ms TTL=119
Reply from 64.34.163.112: bytes=32 time=153ms TTL=119
Reply from 64.34.163.112: bytes=32 time=85ms TTL=119
Reply from 64.34.163.112: bytes=32 time=100ms TTL=119
Reply from 64.34.163.112: bytes=32 time=127ms TTL=119
Reply from 64.34.163.112: bytes=32 time=143ms TTL=119
Reply from 64.34.163.112: bytes=32 time=85ms TTL=119
Reply from 64.34.163.112: bytes=32 time=113ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=84ms TTL=119
Reply from 64.34.163.112: bytes=32 time=124ms TTL=119
Reply from 64.34.163.112: bytes=32 time=85ms TTL=119
Reply from 64.34.163.112: bytes=32 time=94ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=81ms TTL=119
Reply from 64.34.163.112: bytes=32 time=97ms TTL=119
Reply from 64.34.163.112: bytes=32 time=97ms TTL=119
Reply from 64.34.163.112: bytes=32 time=102ms TTL=119
Reply from 64.34.163.112: bytes=32 time=82ms TTL=119
Ping statistics for 64.34.163.112:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 153ms, Average = 93ms
I have bolded some examples where my ping jumps.
Tracer Route results:
Tracing route to 64.34.163.112 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 21 ms 10.146.120.1
3 9 ms 9 ms 21 ms 68.6.11.170
4 11 ms 30 ms 23 ms 68.6.8.236
5 24 ms 12 ms 57 ms elcndsrj01-xee500.r2.sd.cox.net [68.6.8.14]
6 40 ms 71 ms 99 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 81 ms 39 ms 51 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124.134]
8 63 ms 62 ms 72 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.124.118]
9 92 ms 98 ms 93 ms 10ge-ten1-1.atl-101mar-cor-1.peer1.net [216.187.120.226]
10 74 ms 75 ms 78 ms 10ge.xe-1-0-0.wdc-eqx-dis-1.peer1.net [216.187.115.37]
11 100 ms 77 ms 75 ms 10ge.ten1-2.wdc-sp2-cor-1.peer1.net [216.187.115.234]
12 74 ms 74 ms 74 ms 216.187.120.234
13 80 ms 83 ms 92 ms 64.34.163.112
I would welcome any thoughts and suggestions.
AB
"Press the red shiny button"~Vortex
"I may give out, but I'll never give in." ~ Lou Bond "To the Establishment"
-
09-02-2009, 04:22 AM #2
Re: Server ping unstable/need analysis of test results
The second one is mine. Couple of facts:
- I'm on the west coast as well (Vancouver BC)
- ISP is Rogers Telecommunications
- Time interval is the same (100 seconds)
- test is done at midnight Pacific/3AM Eastern -- largely unaffected by network congestion
Your ping definitely spikes higher and more often than mine, though we're from the same region. Granted, the average of your non-spike pings is lower than mine.
Can't really suggest solutions.Fight!
-
09-02-2009, 11:34 AM #3
- Join Date
- Mar 2008
- Location
- Potomac, VA
- Age
- 32
- Posts
- 579
Re: Server ping unstable/need analysis of test results
Maybe less a software issue and more of a hardware issue?
What kind of service connection is it, DSL, Cable, Fiber? I ask because it seems you may have a short between yourself and the node, i.e. a nicked cable line, or frayed, bent unsheathed dsl or cable. Your ISP should be able to check the speed coming into your house back to the junction box, if that is okay, have them check the speed to your PC.
Good Luck,
A
-
09-02-2009, 05:58 PM #4
- Join Date
- Aug 2008
- Location
- Shooting down Repaq and Tom Da Slaya's Gunship with a SAAW after being TV missled....ok National City, CA
- Posts
- 399
Re: Server ping unstable/need analysis of test results
I did my ping test at 8pm Pacific time. Zho, I typically ping a little lower than you despite us both being on the west coast of the North American continent. In terms of distance I am probably a little closer to the TG server than you. Not by much though. Nice graphs btw.
Originally Posted by Zhohar
The second one is mine. Couple of facts:
- I'm on the west coast as well (Vancouver BC)
- ISP is Rogers Telecommunications
- Time interval is the same (100 seconds)
- test is done at midnight Pacific/3AM Eastern -- largely unaffected by network congestion
Your ping definitely spikes higher and more often than mine, though we're from the same region. Granted, the average of your non-spike pings is lower than mine.
Can't really suggest solutions.
I use a cable modem. Technicians from my ISP have come out a couple of times to replace connections and check the signal from the house to the server. According to them everything is working fine. Another technician came yesterday and replace some connections in the cable box at the front of the drive way. I told him about the ping spikes and he gave me a contact number. I am thinking of sending him my ping test results. Originally Posted by Aumen1
I appreciate the feedback."Press the red shiny button"~Vortex"I may give out, but I'll never give in." ~ Lou Bond "To the Establishment"
-
09-04-2009, 03:21 PM #5
Re: Server ping unstable/need analysis of test results
I have the same problem, AB. Question: Are you the only one using your Internet connection, or do you have other computers on a home network?
The only information I've been able to find that might even suggest a solution involve the ports used for 2142. Apparently, some of the ports it uses are not ports you can forward on a normal router; they have to be set up as bridged connections by your ISP. (I have Comcast and am on the east coast, btw.) I don't know if that could be the root cause, but it's a curiosity. If you find a resolution, please let us know--I'd love to see if I can fix the issues I have, as well.
-
09-08-2009, 03:32 PM #6
Re: Server ping unstable/need analysis of test results
Wow, thanks for posting this. Not so much about what's going on with your ping but rather it reminded me to check my connection to see if the problems I was having were from my machine or the net.
And here I finally got BF2142 working on W7, PB playing nice and the game was jerking all over the place. Was about to come on here to whine about W7 when it's clear it is something with the network around here.Code:{grey@teleute:~} mtr --report -c 100 64.34.163.112 HOST: teleute Loss% Snt Last Avg Best Wrst StDev 1. nv-69-68-200-1.sta.embarqhsd 0.0% 100 27.2 59.6 26.4 412.9 62.2 2. nv-65-173-89-249.sta.embarqh 27.0% 100 73.9 68.1 26.7 379.6 73.9 3. 223.143.250.213 0.0% 100 27.1 60.5 26.6 340.3 59.5 4. te-3-3.car1.LasVegas1.Level3 0.0% 100 41.9 60.6 27.1 306.2 54.1 5. ae-11-11.car2.LasVegas1.Leve 0.0% 100 43.9 74.9 27.1 308.6 58.1 6. ae-2-2.car1.SaltLakeCity1.Le 0.0% 100 55.8 79.2 35.0 295.4 65.5 7. ae-11-11.car2.SaltLakeCity1. 0.0% 100 50.0 78.3 35.0 273.5 66.9 8. ae-5-5.ebr1.Denver1.Level3.n 1.0% 100 58.4 86.9 46.6 279.2 61.4 9. ae-1-100.ebr2.Denver1.Level3 0.0% 100 47.1 86.8 46.8 278.5 53.5 10. ae-3.ebr1.Chicago2.Level3.ne 0.0% 100 81.5 104.7 70.1 385.2 63.1 11. ae-1-100.ebr2.Chicago2.Level 0.0% 100 92.5 109.1 70.0 357.8 61.5 12. ae-2-2.ebr2.Washington1.Leve 0.0% 100 88.8 124.2 88.0 385.8 62.4 13. ae-92-92.csw4.Washington1.Le 0.0% 100 93.4 130.8 88.5 369.2 64.4 14. ae-4-99.edge2.Washington3.Le 0.0% 100 89.3 123.8 89.0 513.2 64.3 15. PEER-1-NETW.edge2.Washington 0.0% 100 91.6 125.4 88.8 513.6 63.7 16. ??? 100.0 100 0.0 0.0 0.0 0.0 0.0 17. ??? 100.0 100 0.0 0.0 0.0 0.0 0.0 18. 64.34.163.112 1.0% 100 116.8 122.8 89.8 497.8 61.8
"...the rules aren't there to enumerate what is always correct but what is always wrong..."
-
09-19-2009, 03:25 AM #7
- Join Date
- Sep 2009
- Posts
- 10
Re: Server ping unstable/need analysis of test results
hxxp://img171.imageshack.us/img171/9256/pings.jpg
Hey Armored it's Cableguy619 from =TRR= and well you know where else. The link above is a ping test from my server and your server at the exact same time. You can notice at 1 point I get a ping Spike on your server and not mine. Now I don't know how bad it gets for you from one day to the next, but this was for 2 min so you can see I seem to have gotten some spikes or another. I noticed a few bad spikes before I caught this and was pinging my server so I dont have all the data, but this screen shot could be how it routes to your guys server or servers and off YOUR ISP network so it could be a problem on a route.
Anyhow PM me or email me when you will be on and I'll jump on as well to your server and see if we have the same issues, we would typically have the same route and hops since we come off the same ISP in the same area
Catch you in game
-
09-19-2009, 03:28 AM #8
- Join Date
- Sep 2009
- Posts
- 10
Re: Server ping unstable/need analysis of test results
Zhohar this can't be compared because you route a entirely different way then AB does. Tou may go from Vancouver to Ohio, etc Originally Posted by Zhohar
Ab could go from SD, to AZ, to TEX to Florida, etc
So you could have a good route with no issues inbetween, but once it gets of the ISP's network that is another story
-
09-19-2009, 04:18 AM #9
Re: Server ping unstable/need analysis of test results
Which is why MTRs are so good. They give you the route as well as the per-hop stats along that route. So 2 people both running MTR might both show ping spike. If both show it on the same host along the route (IE, after their paths have converged) then you know it the issue really is there. However if both show problems early on (first 2-3 hops) then you know its localized and just coincidence.
"...the rules aren't there to enumerate what is always correct but what is always wrong..."
Reply With Quote
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Bookmarks