Ping and tracert (trace route) a two useful tools. A description of how to do them and examples below.
To open a command window, hold down the key with Windows logo and hit r. The Run box will come up. Type cmd in the box and click ok button. A window with a black screen will come up called C:\windows\system32\cmd.exe. At the top of the black screen will be something like this. (I need to learn to do screenshots)
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\SayrePC>
To do a ping: after > type ping(space) name or IP of the target. enter
To do a traceroute: after > type tracert(space) name or IP of target
To copy the results to a post: Right click the cmd screen and select all. Press ctrl and c to copy to your clipboard. Right click the post message screnn and paste.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
Pings: first to
www.yahoo.com, second to my modem 192.168.0.1
C:\Users\SayrePC>Ping
www.yahoo.com
Pinging
www.yahoo-ht3.akadns.net [209.191.93.52] with 32 bytes of data:
Reply from 209.191.93.52: bytes=32 time=65ms TTL=52
Reply from 209.191.93.52: bytes=32 time=63ms TTL=52
Reply from 209.191.93.52: bytes=32 time=63ms TTL=52
Reply from 209.191.93.52: bytes=32 time=63ms TTL=53
Ping statistics for 209.191.93.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 65ms, Average = 63ms
C:\Users\SayrePC>Ping 192.168.0.1
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
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Ping sends a small packet to the target and gets a response. Problem indicaters are packet losses, inconsistant times, and high time values. Total time is primarily affected by distance and quality of the equipment. If you live in the US and ping a US target time should be under 100 ms. A target outside the US will usually be over 100 ms.
65 ms to Yahoo in Dallas from Minneapolis is about average.
Anything over 1 ms to your router and/or modem would indicate a possible problem. Usually something like a bad cable, cables coiled, modem/router sittng to close to strong EMF source.
Tracert to
www.yahoo.com
C:\Users\SayrePC>tracert
www.yahoo.com
Tracing route to
www.yahoo-ht3.akadns.net [209.191.93.52]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms home [192.168.0.1]
2 34 ms 33 ms 35 ms mpls-dsl-gw07-199.mpls.qwest.net [207.225.140.199]
3 34 ms 34 ms 33 ms mpls-agw1.inet.qwest.net [65.103.30.49]
4 34 ms 35 ms 35 ms min-core-01.inet.qwest.net [205.171.128.129]
5 * 43 ms 44 ms cer-core-01.inet.qwest.net [67.14.8.202]
6 44 ms 44 ms 43 ms chp-brdr-02.inet.qwest.net [205.171.139.114]
7 44 ms 50 ms 52 ms 63.146.26.250
8 64 ms 68 ms 72 ms Vlan5.icore2.DTX-Dallas.as6453.net [206.82.141.30]
9 63 ms 64 ms 62 ms if-5-0-0-31.core2.DTX-Dallas.as6453.net [66.198.2.37]
10 63 ms 64 ms 64 ms ix-4-2.core2.DTX-Dallas.as6453.net [66.198.2.14]
11 64 ms 62 ms 66 ms ae1-p101.msr1.mud.yahoo.com [216.115.104.99]
12 65 ms 66 ms 66 ms te-9-1.bas-c2.mud.yahoo.com [68.142.193.11]
13 64 ms 64 ms 64 ms f1.
www.vip.mud.yahoo.com [209.191.93.52]
Trace complete.
Three larger packets are sent. Each switching station is identified. The times between each station and any packet (*) loss is listed. The only "problems" are the packet loss at hop 5 and the inconsistant times in hop 7; and those are not really bad.
Hop 1 is from my computer to my modem.Hop2 is modem to Qwest DSLAM.
If I had a route,r hop1 would be computer to router, hop 2 router to modem, hop 3 modem to ISP.
Long, but hope it helps.