how-to block ads
|
MichiganMania
| reply to MoviePhreak9
Re: Comcast in Swartz Creek
Ping Results:
Pinging yahoo.com [64.58.79.230] with 32 bytes of data:
Request timed out.
Reply from 64.58.79.230: bytes=32 time=32ms TTL=242
Reply from 64.58.79.230: bytes=32 time=32ms TTL=242
Reply from 64.58.79.230: bytes=32 time=32ms TTL=242
Ping statistics for 64.58.79.230:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 24ms
TraceRoute Results: (I've always gotten request timed out from hops 2-4 for as long as I've had comcast, even when the service was fine.)
Tracing route to yahoo.com [64.58.79.230]
over a maximum of 30 hops:
1 10 ms 15 ms 10 ms 10.64.248.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 10 ms * 10 ms 68.60.32.250
6 31 ms * * sl-gw33-chi-4-0.sprintlink.net [144.228.151.217]
7 16 ms 16 ms 31 ms sl-bb22-chi-4-0.sprintlink.net [144.232.26.21]
8 15 ms 16 ms 16 ms 144.232.9.50
9 * 16 ms 16 ms agr3-loopback.Chicago.cw.net [208.172.2.103]
10 15 ms 16 ms 15 ms dcr1-so-0-2-0.Chicago.cw.net [208.175.10.9]
11 31 ms 47 ms 47 ms dcr2-loopback.Washington.cw.net [206.24.226.100]
12 32 ms 47 ms 47 ms bhr1-pos-10-0.Sterling1dc2.cw.net [206.24.238.16
6]
13 32 ms 47 ms 46 ms csr04-ve240.stng01.exodus.net [216.33.98.203]
14 * 32 ms 109 ms 216.35.210.126
15 * * * Request timed out.
16 32 ms 46 ms 47 ms w1.rc.vip.dcx.yahoo.com [64.58.79.230]
Signal Levels
Frequency 591000000 Hz Locked
Signal to Noise Ratio 35 dB
QAM 64
Network Access Control Object ON
Power Level 0 dBmV The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 5
Frequency 19984000 Hz Ranged
Ranging Service ID 1511
Symbol Rate 1.280 Msym/s
Power Level 34 dBmV | |
Spector42
Forty-Two
Premium
join:2002-01-07
Owings Mills, MD
| 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. | |
|
