Internet connection ping time rockets on win7?

[tinytomlogan]

Anyone else having this problem? My XP machines have a ping of about 42ms each but my win7 machine seemed slow so I tested it and its 556ms!!!!

Thought it might be something daft like Commodo but its not that, please tell me this is common and there is a fix?

 

[Pyr0]

hi tom,

what are you pinging?

i just use a cmd window in Win7 7127 to ping google.co.uk and got:

Minimum = 21ms, Maximum = 22ms, Average = 21ms

 

[Rastalovich]

Maybe more down to the network.

The google link is a recognized good pinger - AND I personally find the oc3d homepage a good banker.

 

[llwyd]

If it goes up again, run a netstat and a pathping to see what / where it's happening

 

[JN]

If it goes up again, run a netstat and a pathping to see what / where it's happening

^ what llwyd said tbh.

tracert www.overclock3d.net from command prompt should show you exactly where its choking. Paste the output in here.

 

[tinytomlogan]

Microsoft Windows [Version 6.1.7100]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Time To Live Customs>tracert www.overclock3d.net

Tracing route to www.overclock3d.net [212.69.36.81]

over a maximum of 30 hops:

1 13 ms 1 ms <1 ms 192.168.2.1

2 2 ms 1 ms 1 ms voyager.home [192.168.1.1]

3 42 ms 41 ms 43 ms 217.47.89.186

4 41 ms 41 ms 75 ms 217.47.88.161

5 43 ms 41 ms 41 ms 217.47.159.170

6 43 ms 41 ms 41 ms 217.41.217.9

7 43 ms 41 ms 41 ms 217.41.171.122

8 43 ms 41 ms 41 ms 217.41.171.50

9 42 ms 41 ms 41 ms 217.47.88.241

10 42 ms 41 ms 41 ms core1-pos1-0.kingston.ukcore.bt.net [194.72.3.57

]

11 44 ms 43 ms 43 ms core1-pos0-7-0-0.ilford.ukcore.bt.net [62.6.201.

109]

12 43 ms 55 ms 49 ms transit2-gig7/0/0.ilford.ukcore.bt.net [194.74.7

7.174]

13 43 ms 41 ms 43 ms t2c2-ge14-0-0.uk-ilf.eu.bt.net [166.49.168.121]

14 43 ms 43 ms 43 ms t2c1-p3-3.uk-lon1.eu.bt.net [166.49.164.97]

15 44 ms 43 ms 43 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.102]

16 45 ms 44 ms 42 ms 166-49-211-34.eu.bt.net [166.49.211.34]

17 45 ms 43 ms 43 ms e2-2.cx3.lon2.idnet-gw1.arbinet.net [213.232.65.

101]

18 45 ms 45 ms 45 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]

19 47 ms 47 ms 43 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]

20 62 ms 45 ms 45 ms www.overclock3d.net [212.69.36.81]

Trace complete.

C:\Users\Time To Live Customs>

Ill ping the other machine in a sec

 

[Ham]

I had massive pings on win7 a while ago, turned out that a process called 'system' was hogging a lot of my bandwidth and thusly killing the connection.

Theres a very nifty bandwidth monitor built in, not sure if its new to 7 or was in vista, but might be work checking.

 

[Rastalovich]

I had massive pings on win7 a while ago, turned out that a process called 'system' was hogging a lot of my bandwidth and thusly killing the connection.

Theres a very nifty bandwidth monitor built in, not sure if its new to 7 or was in vista, but might be work checking.

Look out for mediaplayer and a cfg exe doing network stuff. What it attempts to do is keep part of the network for media playing. Hammers filecopying over a network.

(shouldn't effect pinging over the internet tho)

 

[tinytomlogan]

Great seeing as Ive just put a file server in the shed

 

[tinytomlogan]

after changes - for jim

Microsoft Windows [Version 6.1.7100]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Time To Live Customs>tracert www.overclock3d.net

Tracing route to www.overclock3d.net [212.69.36.82]

over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.2.1

2 3 ms 1 ms 1 ms voyager.home [192.168.1.1]

3 44 ms 43 ms 43 ms 217.47.89.186

4 43 ms 43 ms 41 ms 217.47.89.161

5 45 ms 43 ms 41 ms 217.47.159.174

6 90 ms 49 ms 43 ms 217.41.217.13

7 44 ms 43 ms 43 ms 217.41.171.65

8 46 ms 43 ms 43 ms 217.41.171.122

9 43 ms 43 ms 45 ms 217.41.217.34

10 47 ms 43 ms 43 ms 217.47.66.35

11 44 ms 45 ms 43 ms core2-pos13-2.kingston.ukcore.bt.net [62.6.40.21

3]

12 44 ms * 44 ms core2-pos0-0-0-7.ilford.ukcore.bt.net [62.6.204.

238]

13 58 ms 69 ms 47 ms transit2-gig11/0/0.ilford.ukcore.bt.net [194.72.

20.154]

14 48 ms 45 ms 51 ms t2c2-ge8-0-0.uk-ilf.eu.bt.net [166.49.168.113]

15 45 ms 45 ms 43 ms t2c1-p3-2.uk-lon1.eu.bt.net [166.49.164.93]

16 46 ms 47 ms 43 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.102]

17 56 ms 59 ms 45 ms 166-49-211-34.eu.bt.net [166.49.211.34]

18 70 ms 47 ms 47 ms e2-2.cx3.lon2.idnet-gw1.arbinet.net [213.232.65.

101]

19 46 ms 47 ms 45 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]

20 69 ms 55 ms 47 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]

21 47 ms 45 ms 45 ms www.overclock3d.net [212.69.36.82]

Trace complete.

PING-----

C:\Users\Time To Live Customs>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.82] with 32 bytes of data:

Request timed out.

Reply from 212.69.36.82: bytes=32 time=46ms TTL=43

Reply from 212.69.36.82: bytes=32 time=44ms TTL=43

Reply from 212.69.36.82: bytes=32 time=44ms TTL=43

Ping statistics for 212.69.36.82:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 44ms, Maximum = 46ms, Average = 44ms

C:\Users\Time To Live Customs>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.82] with 32 bytes of data:

Request timed out.

Request timed out.

Reply from 212.69.36.82: bytes=32 time=51ms TTL=43

Reply from 212.69.36.82: bytes=32 time=45ms TTL=43

Ping statistics for 212.69.36.82:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

Minimum = 45ms, Maximum = 51ms, Average = 48ms

C:\Users\Time To Live Customs>ping www.overclock3d.net

Pinging www.overclock3d.net [212.69.36.82] with 32 bytes of data:

Reply from 212.69.36.82: bytes=32 time=47ms TTL=43

Request timed out.

Reply from 212.69.36.82: bytes=32 time=81ms TTL=43

Reply from 212.69.36.82: bytes=32 time=45ms TTL=43

Ping statistics for 212.69.36.82:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 45ms, Maximum = 81ms, Average = 57ms

C:\Users\Time To Live Customs>

 

[llwyd]

Mate run the command netstat -a when its bad, will give you all the apps using your connection. Then run the command pathping -4 which will give you the ping between hops, as opposed to on the way there, the -4 dictates use of only ipv4. Poor mans badwidth monitor haha

What rast said is a good comment too, vista had a few daft things that hogged the network, like the MP network process. Open task manager and check the tab for network useage (if there is one there in win7, may have been replaced with what ham mentioned) If there is anything going on while it shouldnt be, kill off processes untill it goes to 0% (if it doesnt drop all the way, something is being sneaky) when its at 0, check your ping and if its still happening its network related.

Are there other PCs on the network with other OS's that are fine? Is the PC on ethernet?

 

[tinytomlogan]

All rigs are on the net, all the others load fine its just the win 7 rig thats doing it.

Stopped the WMP networking service doesnt seem to have changed anything though, is there anything I can screenie/copy to try and help you guys see whats going on?