+ Reply to Thread
Results 1 to 10 of 10

Thread: Windows 7 random ping spikes every few seconds

  1. 30-07-10 00:46 #1
    331Andy
    331Andy is offline
    Junior Member 331Andy is on a distinguished road
    Join Date
    May 2009
    Posts
    13

    Exclamation Windows 7 random ping spikes every few seconds

    Hey guys,

    Not sure if it's been posted before, but I'm getting a continuous ping spikes on my Nexus running on Windows 7, and it's making gaming online impossible! I'm on wireless, and the router is a Netgear (although I think it's a problem with windows itself, since I had the same problem on a Thomson router). I think I've isolated the problem to Windows 7, as I've pinged the same router on a different XP machine, and its latency was perfectly consistent, unlike my Nexus.

    Since the spikes are so frequent, I have a feeling it's not due to the notorious Wireless Zero Config (winxp). The equivalent is WLAN AutoConfig in Windows 7, and as soon as I stop the service I get no internet, so I can't even find out whether or not Windows is indeed regularly scanning for networks.

    And I've tried this WLAN Optimizer program some people suggested, but it doesn't seem to work (no difference).

    Below is the data collected after pinging the router - you can clearly see the ping spikes & irregularities. (Sorry to have to make this post so long)

    C:\Windows\system32>ping 192.168.0.1 -t

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=11ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=35ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=37ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=10ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=196ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=80ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=7ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255

    Ping statistics for 192.168.0.1:
    Packets: Sent = 213, Received = 204, Lost = 9 (4% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 196ms, Average = 3ms


    Any help is appreciated!
    Andy

    (just realised, wrong forum section.. could a mod please move it? Cheers!)
    Last edited by 331Andy; 30-07-10 at 00:47. Reason: Wrong forum section!
    Reply With Quote Reply With Quote  
  2. 30-07-10 07:03 #2
    Andy
    Andy is offline
    Senior Member Andy is on a distinguished road
    Join Date
    Apr 2009
    Location
    Manchester
    Posts
    911

    Default

    Do you have the latest drivers onstalled on your laptop? Especially the network card drivers? Also when did this problem start? As soon as you installed win 7?
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Quote Originally Posted by neil@kobalt View Post
    Andy (our resident SSD expert )
    Kobalt Nexus | P9600 | 4GB 1066MHz DDR3 RAM | GTX 260M | 250GB Vertex SSD + SSD tweaks applied | Windows 7 Home Premium - 64bit

    FAQ - PLEASE READ BEFORE POSTING
    Reply With Quote Reply With Quote  
  3. 30-07-10 16:01 #3
    331Andy
    331Andy is offline
    Junior Member 331Andy is on a distinguished road
    Join Date
    May 2009
    Posts
    13

    Default

    Quote Originally Posted by Andy View Post
    Do you have the latest drivers onstalled on your laptop? Especially the network card drivers? Also when did this problem start? As soon as you installed win 7?
    I think the problem started when I installed windows 7 (but very mild. I remember some random ping spikes in cmd, and the rare occurences in-game don't even bother me), but I recently had a gaming session full of severe spikes - about once every 3-5 seconds.

    I've just updated the Realtek network driver (I let windows check for driver updates, and it automatically installed a new one), and restarted. Pinged router once more:

    C:\Users\Andy>ping 192.168.0.1 -t

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=6ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=28ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=9ms TTL=255
    .
    .
    .
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=227ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=118ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=130ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=14ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=227ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=19ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=12ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=4ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255

    Ping statistics for 192.168.0.1:
    Packets: Sent = 167, Received = 167, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 227ms, Average = 8ms


    Wow! No time outs! Cheers Andy!

    However, I'm still concerned about the spikes... I suspect it's not normal, am I right? Shouldn't the ping times be more consistent, i.e. around 1ms almost always?

    I'll try going online and see if I get any spikes while gaming.

    Any further help greatly appreciated!
    Last edited by 331Andy; 30-07-10 at 17:37.
    Reply With Quote Reply With Quote  
  4. 30-07-10 17:34 #4
    331Andy
    331Andy is offline
    Junior Member 331Andy is on a distinguished road
    Join Date
    May 2009
    Posts
    13

    Default

    Seems like I spoke too soon:

    C:\Windows\system32>ping 192.168.0.1 -t

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=5ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=179ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=71ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=191ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=8ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=13ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=255

    Ping statistics for 192.168.0.1:
    Packets: Sent = 50, Received = 48, Lost = 2 (4% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 191ms, Average = 10ms



    So.. what could it be?
    Reply With Quote Reply With Quote  
  5. 30-07-10 17:48 #5
    Les
    Les is offline
    Junior Member Les is on a distinguished road
    Join Date
    Jul 2010
    Location
    Livingston, Scotland
    Posts
    2

    Default

    Hi
    Just tried it on my system (old Evesham laptop running Vista Ultimate)
    1/2 hour running - every ping <1ms
    Had a quick game of Joint Operations and during game, all pings still <1ms

    regards, Les Hay, Livingston, Scotland
    Reply With Quote Reply With Quote  
  6. 30-07-10 18:31 #6
    alexrose1uk
    alexrose1uk is offline
    Senior Member alexrose1uk is on a distinguished road
    Join Date
    Oct 2009
    Location
    Outside Milton Keynes
    Posts
    575
    Send a message via Skype™ to alexrose1uk

    Default

    I know this is going to sound obvious, but have you tried downloading the latest driver for your network card, completely uninstalling the current driver then installing the up to date driver, incase its a driver related issue.

    El Diablo Kobalt G890/w 940XM, 4GB DDR3, Intel G2 80GB SSD, WD Black 640GB RAID0, Blu-ray Burner, 5870M Crossfire
    Ex-AW owner - Alienware treat you like a resource, not a customer. Do not buy Alienware Europe!
    Vertical Horizons Team Member, 'X32I: Redemption' in Development - http://www.x32i.org & http://www.moddb.com/games/x32i-redemption
    Previous machines: - Alienware M17, Fujitsu-Siemens Amilo Xi 1546
    Reply With Quote Reply With Quote  
  7. 30-07-10 19:20 #7
    331Andy
    331Andy is offline
    Junior Member 331Andy is on a distinguished road
    Join Date
    May 2009
    Posts
    13

    Default

    Yep, just rebooted after uninstalling & reinstalling the intel wifi drivers. Pinged with same results as my 4pm post - thankfully no time outs. There's still the ping spikes.
    Reply With Quote Reply With Quote  
  8. 31-07-10 12:14 #8
    Blue-Baboon
    Blue-Baboon is offline
    Senior Member Blue-Baboon is on a distinguished road Blue-Baboon's Avatar
    Join Date
    Mar 2010
    Location
    Gloucestershire, UK
    Posts
    223

    Default

    mine does the same, seems to be a regular timed event

    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=97ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=46ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=166ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=59ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Steve the Blue-Baboon
    G860 + 920XM + ATI 5870 + 8GB Ram + 60GB SSD + 500GB HDD (in optical bay)
    Cooler Master Notepal U2 + Razer Copperhead, eXactMat, Lycosa + SB X-FI
    Reply With Quote Reply With Quote  
  9. 31-07-10 12:25 #9
    alexrose1uk
    alexrose1uk is offline
    Senior Member alexrose1uk is on a distinguished road
    Join Date
    Oct 2009
    Location
    Outside Milton Keynes
    Posts
    575
    Send a message via Skype™ to alexrose1uk

    Default

    I don't use wireless very often, but is there an Intel wireless configuration utility? If so it may be possible to disable Win7 autopolling and use the Intel app.
    Alternatively, if you root through the options it MAY be possible to disable the scanning with a registry key or even a simple box somewhere, unfortunately I dont have a wireless Win7 machine to test with right now.

    El Diablo Kobalt G890/w 940XM, 4GB DDR3, Intel G2 80GB SSD, WD Black 640GB RAID0, Blu-ray Burner, 5870M Crossfire
    Ex-AW owner - Alienware treat you like a resource, not a customer. Do not buy Alienware Europe!
    Vertical Horizons Team Member, 'X32I: Redemption' in Development - http://www.x32i.org & http://www.moddb.com/games/x32i-redemption
    Previous machines: - Alienware M17, Fujitsu-Siemens Amilo Xi 1546
    Reply With Quote Reply With Quote  
  10. 01-08-10 11:16 #10
    331Andy
    331Andy is offline
    Junior Member 331Andy is on a distinguished road
    Join Date
    May 2009
    Posts
    13

    Default

    Quote Originally Posted by alexrose1uk View Post
    I don't use wireless very often, but is there an Intel wireless configuration utility? If so it may be possible to disable Win7 autopolling and use the Intel app.
    I'm not entirely sure I even have it running.. It's definitely installed, because I see a list of WiFi tools in my Intel PROSet Wireless folder, but there doesn't seem to be an application/config utility.

    I remember there being one when I was using WinXP, but now there's not even the Intel icon which replaced the generic Windows 'connected' icon. I'll try Googling to find a solution. And hopefully the guys at Kobalt may be able to fix it when I send my Nexus off to them soon, if I can't myself.

    Thanks for all the help!
    Reply With Quote Reply With Quote  
+ Reply to Thread
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Forum Rules