Speedtest Ping issues

D

Dragonsmight

Member
Speedtest Ping issues (Solved)

For some reason two different computers on the same ISP/router are getting very different results on speedtest.

Computer A is a desktop





Firewall is comodo, Anti-virus is nod32, same results with them on or off. Browser is Firefox or IE.



A ping to google.com looks like this

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jeremy>ping google.com

Pinging google.com [66.102.7.99] with 32 bytes of data:
Reply from 66.102.7.99: bytes=32 time=80ms TTL=51
Reply from 66.102.7.99: bytes=32 time=85ms TTL=51
Reply from 66.102.7.99: bytes=32 time=80ms TTL=51
Reply from 66.102.7.99: bytes=32 time=80ms TTL=51

Ping statistics for 66.102.7.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 85ms, Average = 81ms



Computer B is a laptop





This uses Symantec for firewall/anti-virus, also using Firefox

Ping to google looks the same.


Any help with this is much appreciated thanks a lot.
 
Last edited:
Strange, if you got to www.whatismyip.com on both Computer A & B are the connected IP addresses the same?

Also how are both the computers connected to your Router? Wireless or via a Ethernet/USB cable.
 
Okay, the first thing I would try before anything else (if you haven't already done this) is to replace the current Ethernet/USB cable you have got connected from the Router to the problem computer (Computer A) then re-run testing.
 
Computer A

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jeremy>tracert google.com

Tracing route to google.com [66.102.7.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 10 ms cm-76-45-200-1.sw.rr.com [76.45.200.1]
3 10 ms 9 ms 9 ms CPE-65-28-220-133.kc.res.rr.com [65.28.220.133]

4 14 ms 9 ms 10 ms CPE-65-28-220-38.kc.res.rr.com [65.28.220.38]
5 12 ms 8 ms 25 ms CPE-65-28-220-29.kc.res.rr.com [65.28.220.29]
6 24 ms 27 ms 23 ms CPE-65-28-220-5.kc.res.rr.com [65.28.220.5]
7 38 ms 23 ms 33 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
8 23 ms 23 ms 25 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
9 22 ms 19 ms 33 ms 72.14.219.56
10 37 ms 25 ms 35 ms 72.14.233.54
11 84 ms 78 ms 79 ms 216.239.43.124
12 82 ms 90 ms 80 ms 64.233.174.70
13 80 ms 79 ms 79 ms lax04s01-in-f104.1e100.net [66.102.7.104]

Trace complete.


Computer B

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Hallie>tracert google.com

Tracing route to google.com [66.102.7.99]
over a maximum of 30 hops:

1 27 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 8 ms cm-76-45-200-1.sw.rr.com [76.45.200.1]
3 39 ms 9 ms 10 ms CPE-65-28-220-133.kc.res.rr.com [65.28.220.133]

4 23 ms 13 ms 9 ms CPE-65-28-220-38.kc.res.rr.com [65.28.220.38]
5 9 ms 9 ms 16 ms CPE-65-28-220-29.kc.res.rr.com [65.28.220.29]
6 28 ms 33 ms 26 ms CPE-65-28-220-5.kc.res.rr.com [65.28.220.5]
7 23 ms 27 ms 55 ms ge-2-3-0.cr0.atl20.tbone.rr.com [66.109.6.172]
8 24 ms 23 ms 28 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
9 26 ms 26 ms 23 ms 66.109.9.90
10 31 ms 23 ms 20 ms 64.233.174.2
11 84 ms 83 ms 79 ms 216.239.43.124
12 81 ms 106 ms 89 ms 72.14.239.246
13 80 ms 80 ms 82 ms lax04s01-in-f99.1e100.net [66.102.7.99]

Trace complete.

C:\Users\Hallie>
 
Solution found

Finally came across something that worked for me. It was a nod32 issue. Went to advanced settings, Antivirus and antispyware > Web access protection > HTTP, HTTPS > uncheck Enable HTTP checking.

Before


After



Before


After



Thanks for the help and fast responses though Ambushed, I appreciate it
 
Last edited:
Dragonsmight said:
Finally came across something that worked for me. It was a nod32 issue. Went to advanced settings, Antivirus and antispyware > Web access protection > HTTP, HTTPS > uncheck Enable HTTP checking.

Before


After





Thanks for the help and fast responses though Ambushed, I appreciate it
Click to expand...

Wow! I thought this was the same result with NOD32 off or on. Anyway thanks for letting me know what the problem was. :D
 
You must log in or register to reply here.
Back
Top