| [Windows] What might cause slower ping times? I am having a minor problem with my new computer's ping times. My ping-to-router times are a steady 2ms, about double that of my other two computers. My ping-to-Website times are also measurably longer, anywhere from 15ms to double that of the other computers.
1) New computer is a Win 7 x64 desktop with onboard Intel LAN. Also tried an Intel PCIe NIC.
....Motherboard is an ASUS Sabertooth Z77.
2) Old computer is an XP Pro desktop with onboard Marvell LAN.
3) Third computer is a laptop running Win 7 x64 and WLAN.
I have run numerous tests to confirm the problem (trace routes, ping tests, speedtest.net, pingtest.net) and tried all of the normal solutions. It's not the Cat 5 cables, the router, or the cable modem. It is also not the network adapter itself as I have used both the onboard LAN and a new Intel PCIe LAN card with identical results. My conclusion is either the motherboard is somehow at fault or my Windows settings or LAN adapter settings are at fault.
On pingtest.net for instance, the new computer gets results that are pretty consistently double the ping results of the other two computers e.g. New comp= 82 ping-11 jitter; Old comp= 39 ping-2 jitter. This new computer runs great in all other areas.
To the best of my knowledge, both the Windows and the adapter settings are in stock, default condition except that I have tried un-checking the QoS Packet Scheduler and switching from my ISP's DNS to the Google DNS. Both of those changes are also in effect in the other two computers.
I really don't think either my 3 year old wireless laptop or 5 year old desktop should be pinging faster than the new computer. So...........
Are there any settings for Windows, NIC, LAN, TCP/IP, anywhere, that I may have overlooked which may have an affect on these ping times?
or............
Is there any change I might have made to my settings, either accidentally or in error, that could have actually slowed down ping times? I did experiment a little when I first got the machine up and running a few months ago, but I believe everything got put back to the defaults. |
|
| Same OS and different NICs produces the same results... have you tried changing the cables with either
the XP PRO or the laptop?
Regards |
|
|
|
Reviews:
 ·Comcast Business..
 ·AT&T Midwest
| reply to Jake
I assume the new computer is a clean build with a fresh install of win7? If this is a new computer with a pre-installed OS I would run the restore DVD and go back to stock windows only.
Also, try resetting the TCP stack: »support.microsoft.com/kb/299357 |
|
| reply to HELLFIRE
said by HELLFIRE:Same OS and different NICs produces the same results... have you tried changing the cables with either
the XP PRO or the laptop?
Yar, tried swapping the cables, no help. The laptop is connecting wirelessly and still pings faster than the machine in question. |
|
| reply to cmslick3
said by cmslick3:I assume the new computer is a clean build with a fresh install of win7? If this is a new computer with a pre-installed OS I would run the restore DVD and go back to stock windows only.
Also, try resetting the TCP stack: »support.microsoft.com/kb/299357
Ah ha, that is the type of possible suggestion I was looking for so I tried resetting the TCP/IP stack and rebooted. Then I ran the ping command (to the router) at the command prompt for a test. After a 20-ping series I saw improved results. Instead of the usual 2ms times I got an average of 1ms which got my hopes up. A visit to pingtest.net was a reality check, I got the same ol, same ol results there (82 ping, 12 jitter). After a while I tried local ping to the router again and it was back to its usual 2ms.
This may sound odd but a similar thing happened last week when I started this little adventure. I uninstalled, rebooted, then reinstalled the drivers/software for the onboard Intel LAN, after which ping times seemed to be improved but upon booting next day pings were slowed down again.
Well, it's nothing I can't live with. My connection is a pretty snappy 25Mb/5Mb and I get that very consistently, and though I can measure the slightly longer pings I can't actually feel them.
But I'd still like to get the same ping times as my other computers so let me know if you have any other ideas.
Thanks to both of you. |
|
| reply to Jake
When you ping the local loopback address 127.0.0.1, how's the result look?
For chuckles, look into swapping your home router, just to rule it out
If cabling, OS and NIC hardware have been ruled out, may be time to look at the NIC driver.
My 00000010bits
Regards |
|
 shdesignsPowered By Infinite Improbabilty DrivePremium
join:2000-12-01
Stone Mountain, GA | reply to Jake
I have seen antivirus software slow things down like this. |
|
| reply to HELLFIRE
said by HELLFIRE:When you ping the local loopback address 127.0.0.1, how's the result look?
For chuckles, look into swapping your home router, just to rule it out
If cabling, OS and NIC hardware have been ruled out, may be time to look at the NIC driver. I have tested with 2 different routers as well as straight into the cable modem.
Localhost ping does not appear good to me. First 4 pings were all 4ms. Then a group of 20 pings flashed a first ping of 15ms, 3rd ping was 7ms, and the rest were mostly 4ms with a couple of 3ms' mixed in. Another group of 20 pings was a mix of 3ms and 4ms times, average = 3ms.
My old XP box returns sub-1ms ping times 100% of the time when pinging 127.0.0.1 which is what I might expect. Ditto for the laptop, all localhost pings are sub-1ms.
--------------------------
"I have seen antivirus software slow things down like this."
Actually, all 3 of my computers here are running the same AV program though I have not tried any testing with the AV disabled. Two of the computers seems to produce normal pings. |
|
 Samir
join:2010-02-06
Madison, AL | That laggy localhost ping time definitely confirms it's not the hardware, but somewhere in the OS or other software.
Is it possible to boot from something that's a live cd of some sort with a ping capability? Then you can try the ping again and see what happens.
--
Huntsville's Premiere Car and Bike Enthusiast website: www.huntsvillecarscene.com |
|
| said by Samir:That laggy localhost ping time definitely confirms it's not the hardware, but somewhere in the OS or other software.
Is it possible to boot from something that's a live cd of some sort with a ping capability? Then you can try the ping again and see what happens.
No, I don't have any alternate booting ability. But tell me if this qualifies as a new clue:
Just now I tried something a little different, at the command prompt I used "localhost" instead of the home IP 'ping -n 20 localhost' and got all sub-1ms pings. Then I went back to 'ping -n 20 127.0.0.1' and the first ping was 17 ms and the rest were all 4ms. I was able to duplicate those results several times.
Why wouldn't those results be the same? |
|
Reviews:
·Comcast Business..
·AT&T Midwest
| The only other reason I could think of for the difference between the XP and windows 7 results are the TCP/IP tuning functions which run in the background on windows 7. That's why you saw faster ping responses after the uninstall/reinstall and TCP reset tests.
Doing that to windows 7 causes the TCP/IP tuning parameters to reset. I can't recall the specific commands but I think this should help you out some: »www.speedguide.net/articles/wind···aks-2574
forgive me for posting a link to a competing site...
Windows 7 is detecting something in your connection which XP is simply ignoring. Could be an issue with the UL side of your cable connection. I would also suggest that you setup a smokeping test, found on DSLR under tools, to your detected public IP. Assuming it doesn't change too often you should be able to see what your line looks like.
I would also say that if you were to post the line stats from your modem we may be able to diagnose further. |
|
| Partial solution found!
The laggy ping times to both 127.0.0.1 and to my router are being caused by something in Malwarebytes Pro. I tried ping tests in safe mode and got normal times and the only notable difference was that MBAM was not running. Back in regular Windows I tested with MBAM both on and then off to confirm the problem.
Oddly, the problem only seems to appear with Win 7 (possibly only with the x64 version). My XP Pro desktop also runs MBAM Pro but does not suffer from this issue. The tech people at MBAM report they are aware of the issue and they are working on it.
This still does not explain why my newest desktop still gets worse ping scores when pinging external Web sites. Testing on pingtest.net, the new machine consistently gets scores roughly double those of the XP machine or the Win 7 x64 laptop (with or without Malwarebytes running). |
|
