High ping

firebat · Post by **firebat** » Sun Dec 13, 2009 4:04 pm

I'm getting ridiculously high ping, like ~5000ms. At time of post, it's gotten a little better ~3600ms. I am on cable and the speed is around 1Mbps. One computer is wired to the router and two others are connected wirelessly. I'm wondering why the ping is so high and what can I do to correct this?

The test at http://miranda.ctd.anl.gov:7123/ says that there's packet queuing. What is that?

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 6.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.02Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_15

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 402.5 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 7.41% of the time
S2C throughput test: Packet queuing detected: 10.94%
This connection is receiver limited 25.22% of the time.
Increasing the the client's receive buffer (63.0 KB) will improve performance
This connection is sender limited 48.77% of the time.
This connection is network limited 26.00% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON

Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [24.207.xxx.xxx] but Client says [192.168.1.3]

TCP analyzer shows:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 12.13.2009 15:37
IP address: 24.207.xxx.xx
Client OS: Windows XP

TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 65535 (NOT multiple of MSS)
RWIN Scaling: 0 bits
Unscaled RWIN : 65535
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 113
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

Tracert results:

Tracing route to http://www.l.google.com [74.125.67.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 3157 ms 3103 ms 3144 ms 10.162.0.1
3 3180 ms 2817 ms 2707 ms 96-34-52-118.static.unas.mo.charter.com [96.34.52.118]
4 1675 ms 1365 ms 1025 ms bbr01olvemo-tge-0-3-0-0.olve.mo.charter.com [96.34.2.18]
5 1906 ms 1936 ms 1696 ms bbr02chcgil-tge-0-0-0-4.chcg.il.charter.com [96.34.0.12]
6 2235 ms 2696 ms 2195 ms prr01chcgil-tge-2-2.chcg.il.charter.com [96.34.3.39]
7 2455 ms 2888 ms 2840 ms 74.125.51.253
8 1587 ms 1247 ms 1910 ms 209.85.254.128
9 2207 ms 2484 ms 2484 ms 72.14.239.90
10 2638 ms 2806 ms 3276 ms 209.85.254.249
11 3118 ms 2664 ms 3937 ms 209.85.255.194
12 * 3017 ms 3618 ms gw-in-f99.1e100.net [74.125.67.99]

I have no idea what these test mean, but maybe somebody out there will find it useful.

Post by **Philip** » Sun Dec 13, 2009 5:01 pm

There is defiitely a problem with your line if you're getting such high latency on the first hop, I'd contact your provider to correct the issues.

What you can do on your end is to physically separate the cable modem and any routers at least one foot apart, and away from any possible sources of EMI interference (power supplies, fluorescent lamps, etc.)

You should also determine whether there is any difference in latency between the wired and wireless clients.

I hope this helps some.

Sava700 · Post by **Sava700** » Sun Dec 13, 2009 6:50 pm

yeah a major issue at hop 1... call them ASAP cause it may take em a few days to repair it.

firebat · Post by **firebat** » Sun Dec 13, 2009 9:52 pm

I called the ISP and they pinged me back at 6ms!??? How is that possible when I'm getting ~3000ms? Woudn't it be the same?
But anyways, they told me it was because my modem was old. The model is Ambit U10C018. Would just an old modem cause such a large ping? or are they lying to me? I didn't find many people online ranting about their slow Ambit U10C018.

Sava700 · Post by **Sava700** » Sun Dec 13, 2009 10:27 pm

hmm.... ok can you take the router out and plug directly into the modem then try pinging?

firebat · Post by **firebat** » Wed Dec 16, 2009 7:27 pm

New modem, new ISP. Speed is much better at ~7 Mbps. Thanks for the tips!!

Sava700 · Post by **Sava700** » Wed Dec 16, 2009 9:31 pm

firebat wrote:New modem, new ISP. Speed is much better at ~7 Mbps. Thanks for the tips!!

new ISP?? lol ok

RPitch · Post by **RPitch** » Thu Dec 17, 2009 12:07 am

Hope you got it reconfiged fb, see you online halo..

Icenum