Ping problems on ECGN

[Jim0322 Profile]

I seem to be having intermittant ping problems on BF2 #1 server. I ran several trace routes and I might have found a/one of the problems. See below:

12 624 ms 129 ms 782 ms pos4-2.colo01.ash01.pccwbtn.net [63.218.44.165]

The whole thing is below.
1 13 ms 14 ms 13 ms iub-vnp2-6.uits.indiana.edu [156.56.245.6]
2 13 ms 14 ms 13 ms 156.56.245.254
3 14 ms 14 ms 15 ms ibr-ibs1-pb.noc.iu.edu [149.166.2.52]
4 75 ms 14 ms 15 ms 149.165.254.229
5 15 ms 14 ms 14 ms sd-ul.indiana.gigapop.net [192.12.206.245]
6 19 ms 18 ms 19 ms so-2-3-0-0.gar2.Chicago1.Level3.net [67.72.124.9
]
7 19 ms 19 ms 20 ms so-0-3-0.bbr2.Chicago1.Level3.net [4.68.96.45]
8 19 ms 22 ms 19 ms so-7-0-0.edge1.Chicago1.Level3.net [209.244.8.14
]
9 18 ms 19 ms 21 ms bpr1-ge-2-3-0.ChicagoEquinix.savvis.net [208.174
.226.57]
10 20 ms 19 ms 19 ms bpr2-ae2.ChicagoEquinix.savvis.net [208.175.9.13
8]
11 19 ms 20 ms 19 ms beyond-the-network.ChicagoEquinix.savvis.net [20
8.174.224.6]
12 624 ms 129 ms 782 ms pos4-2.colo01.ash01.pccwbtn.net [63.218.44.165]

13 46 ms 45 ms 45 ms ecgn20.ecgnetwork.com [205.177.13.8]


Is there anything I should do? I e-mailed my ISP. However, the problem is just one hop away from ECGN.

Jim

[Spirit of Me Profile]

That appears to be an oc48 hub. Hummm is ECGN.com on a oc48? wow you guys impress me.

Anyways there may be issues on that hub. how long has that been an issue for you?

[Jim0322 Profile]

It has been this way for 1-2 weeks. I end up getting a lot of sling shotting when I play. Sometimes it is hard to run in a straight line because I keep warping back. At times it is just an annoyance but many times it makes it unplayable. Packet loss is almost nil but my ping varies between 40-700. (It used to be 40-50 almost all the time) I can just watch it (from the screen that lists both teams players and their pings) cycle up to 600-700 and then drop back down. It is very unstable. It just goes up and down all the time.

Jim

[Jim0322 Profile]

One more sample. I pinged the IP one hop away.

Pinging 63.218.44.165 with 32 bytes of data:


Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=71ms TTL=244
Reply from 63.218.44.165: bytes=32 time=45ms TTL=244
Reply from 63.218.44.165: bytes=32 time=66ms TTL=244
Reply from 63.218.44.165: bytes=32 time=116ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=57ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=51ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=72ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=136ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=45ms TTL=244
Reply from 63.218.44.165: bytes=32 time=216ms TTL=244
Reply from 63.218.44.165: bytes=32 time=215ms TTL=244
Reply from 63.218.44.165: bytes=32 time=254ms TTL=244
Reply from 63.218.44.165: bytes=32 time=774ms TTL=244
Reply from 63.218.44.165: bytes=32 time=552ms TTL=244
Reply from 63.218.44.165: bytes=32 time=700ms TTL=244
Reply from 63.218.44.165: bytes=32 time=901ms TTL=244
Reply from 63.218.44.165: bytes=32 time=95ms TTL=244
Reply from 63.218.44.165: bytes=32 time=609ms TTL=244
Reply from 63.218.44.165: bytes=32 time=641ms TTL=244
Reply from 63.218.44.165: bytes=32 time=425ms TTL=244
Reply from 63.218.44.165: bytes=32 time=512ms TTL=244
Reply from 63.218.44.165: bytes=32 time=652ms TTL=244
Reply from 63.218.44.165: bytes=32 time=907ms TTL=244
Reply from 63.218.44.165: bytes=32 time=821ms TTL=244
Reply from 63.218.44.165: bytes=32 time=374ms TTL=244
Reply from 63.218.44.165: bytes=32 time=168ms TTL=244
Reply from 63.218.44.165: bytes=32 time=78ms TTL=244
Reply from 63.218.44.165: bytes=32 time=93ms TTL=244
Reply from 63.218.44.165: bytes=32 time=46ms TTL=244
Reply from 63.218.44.165: bytes=32 time=46ms TTL=244
Reply from 63.218.44.165: bytes=32 time=51ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=83ms TTL=244
Reply from 63.218.44.165: bytes=32 time=46ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=43ms TTL=244
Reply from 63.218.44.165: bytes=32 time=47ms TTL=244
Reply from 63.218.44.165: bytes=32 time=50ms TTL=244
Reply from 63.218.44.165: bytes=32 time=43ms TTL=244
Reply from 63.218.44.165: bytes=32 time=51ms TTL=244
Reply from 63.218.44.165: bytes=32 time=93ms TTL=244
Reply from 63.218.44.165: bytes=32 time=47ms TTL=244
Reply from 63.218.44.165: bytes=32 time=46ms TTL=244
Reply from 63.218.44.165: bytes=32 time=45ms TTL=244
Reply from 63.218.44.165: bytes=32 time=43ms TTL=244
Reply from 63.218.44.165: bytes=32 time=45ms TTL=244
Reply from 63.218.44.165: bytes=32 time=44ms TTL=244
Reply from 63.218.44.165: bytes=32 time=47ms TTL=244

Ping statistics for 63.218.44.165:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 907ms, Average = 131ms

[Spirit of Me Profile]

Jim this may be a workaround for you, maybe. The following instructions will talk you trough changing your DNS. Do it if you feel comtable. It may work you around the stalled hub.

Give it a try and check your pings again.

FOR WINDOWS XP, 2000, and 2003 ONLY

To change dns servers:

o Right click on the My Network Places icon on the desktop and select Properties. (If the icon is not available, go to Start menu | My Computer | My Network Places | View Network Connections.)

o Locate the network connection that is associated with your Internet connection. This is typically labeled something like "Local Area Connection." If you have more than one connection to choose from, be sure you determine the right one before proceeding.

o Right click on the appropriate connection and select Properties.

o In the list that appears under the General tab, double click on Internet Protocol (TCP/IP).

o In the window that appears, you want to select the option to Use the following dns server addresses...

At this point you will want to enter at least one of your personal preferred dns servers. There are a number of public servers suggested by members of the Comcast forum; simply do a search for 'dns' and you should get adequate results.

o Press Ok out of all windows until you are back to the Network Connections window. You can now open your web browser and browse to a website to see if it connects faster.

ALWAYS USE PUBLIC SERVERS FIRST!!!! ... then as soon as the outage is resolved, flush your dns, and go back into your settings and reset it to Obtain dns Automatically. It will get you back on your Comcast server.

Windows XP caches successful AND failed dns lookups for 24hrs by default, so you want
TO FLUSH YOUR dns
- Go to Start -> Run
- Type cmd ... click OK
- In the box that comes up, type ipconfig /flushdns ...press Enter key

Other Windows systems, simply rebooting should do the trick.

If you are using a router, power cycling it will usually clear out it's cache.

Here is a small list of servers to try:

Public (Level3) Nameservers (these are NOT Verizon servers)
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6

ORSC Public Access dns Nameservers
199.166.24.253
199.166.27.253
199.166.28.10
199.166.29.3
199.166.31.3
195.117.6.25
204.57.55.100

SpeakEasy Nameservers
66.93.87.2
216.231.41.2
216.254.95.2
64.81.45.2
64.81.111.2
64.81.127.2
64.81.79.2
64.81.159.2
66.92.64.2
66.92.224.2
66.92.159.2
64.81.79.2
64.81.159.2
64.81.127.2
64.81.45.2
216.27.175.2
66.92.159.2
66.93.87.2

Sprintlink General dns
204.117.214.10
199.2.252.10
204.97.212.10

Cisco
128.107.241.185
192.135.250.69