Spector42
Forty-Two
Premium
join:2002-01-07
Owings Mills, MD
| reply to MichiganMania
Re: Comcast in Swartz Creek
Your snr, up and down power all look great. For better accuracy ping more than 4 times and use a larger packet size. Here is a ping to the first router in your tracert that shows packet loss. Note the use of -n and -l in the ping command.
H:\>ping -t 68.60.32.250 -n 50 -l 1000
Pinging 68.60.32.250 with 1000 bytes of data:
Reply from 68.60.32.250: bytes=1000 time=31ms TTL=246
Reply from 68.60.32.250: bytes=1000 time=31ms TTL=246
Request timed out.
.
.
.
Reply from 68.60.32.250: bytes=1000 time=32ms TTL=246
Reply from 68.60.32.250: bytes=1000 time=32ms TTL=246
Ping statistics for 68.60.32.250:
Packets: Sent = 50, Received = 48, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 30ms
It is also beneficial to run a reverse tracert. A search on google should yield a handful of these. Since I do not know your IP, here is a trace to the above router:
H:\>tracert 68.60.32.250
Tracing route to 68.60.32.250 over a maximum of 30 hops
1 10 ms 10 ms 10 ms 10.10.4.50
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 10 ms 10 ms 68.34.76.50
5 10 ms 10 ms 10 ms sl-gw26-rly-2-0.sprintlink.net [144.232.238.233]
6 10 ms 10 10 ms sl-bb20-rly-3-3.sprintlink.net [144.232.14.33]
7 10 ms 16 ms 10 ms sl-bb25-nyc-14-1.sprintlink.net [144.232.18.254]
8 16 ms 31 ms 31 ms sl-bb25-chi-6-3.sprintlink.net [144.232.20.58]
9 15 ms 31 ms 32 ms sl-bb21-chi-13-0.sprintlink.net [144.232.26.89]
10 16 ms 31 ms 32 ms sl-gw22-chi-9-0.sprintlink.net [144.232.10.14]
11 32 ms 31 ms 31 ms 68.60.32.250
Trace complete.
From these tests, it is not very conclusive where you are dropping packets. |
