nl
@comcast.net
| my comcast got slow
we had 8 down and then they bumped us up to 16 down 1 up and i did get those speeds. lately not even half that. i browsed my sb5100 modem and the power and snr are within the ranges discussed here. this xp computer has been tuned with drtcp. the wan port on my router is set at 100 Mbs. same with router or directly to the modem.
comcast says i am fine.
suggestions please? |
|
Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
clubs: | Post your modem's log entries. |
|
nl
@comcast.net
| Downstream Value
Frequency 651000000 Hz Locked
Signal to Noise Ratio 37 dB
Power Level -5 dBmV
Upstream Value
Channel ID 5
Frequency 32400000 Hz Ranged
Power Level 45 dBmV
2008-07-10 17:35:04 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:35:02 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:34:52 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:34:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-07-10 17:34:38 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-07-10 17:34:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-07-10 17:34:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-07-10 17:34:23 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:34:13 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:34:07 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:33:57 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:33:49 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:33:39 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:33:18 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:33:08 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:32:46 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-10 17:32:36 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-10 17:32:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-07-10 17:32:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-07-10 17:32:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-07-11 01:39:24 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-07-11 01:39:15 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:38:57 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2008-07-11 01:38:57 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:38:48 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2008-07-11 01:38:48 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:38:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-07-11 01:38:33 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-11 01:38:23 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:38:16 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-11 01:38:06 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:37:54 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-11 01:37:44 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:37:38 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-07-11 01:37:28 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-07-11 01:37:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-07-11 01:37:16 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-07-11 01:37:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:31:42 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-16 18:31:36 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-06-16 18:31:26 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-16 18:31:09 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:31:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:31:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:31:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:31:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:31:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:30:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:30:54 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-06-16 18:30:54 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:26:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:26:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:26:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:26:24 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:26:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:26:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:26:05 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-16 18:26:03 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-06-16 18:25:53 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-16 18:25:41 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-06-16 18:25:31 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-16 18:25:09 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:25:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:56 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:53 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:52 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:47 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:47 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:40 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:09 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:01 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:24:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:24:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:23:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:23:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:23:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:23:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:23:53 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-06-16 18:23:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-06-16 18:23:51 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing |
|
JahsDisciple
Living my life like it's golden
Premium
join:2007-07-07
Baltimore, MD | reply to nl
can you post a speedtest result and possibly your config file?
»www.speedtest.net |
|
tshirt
Premium,MVM
join:2004-07-11
Snohomish, WA
1 edit | reply to nl
Do a Tweak Test »/tweaks
and an LQ test too. »/linequality
and post the links back here.
Please make yourself "pingable" for the tests, if you are not already. |
|
Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
clubs:
 ·Comcast Digital Vo..
 ·Comcast
·Vonage
| reply to JahsDisciple
said by JahsDisciple  :can you post a speedtest result and possibly your config file? » www.speedtest.net The config didn't show in the log entries above.
--
Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/ |
|
Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
clubs: | reply to nl
Haven't you rebooted the modem since 7/10? |
|
nl
@comcast.net
| reply to Johkal
i haven't seen a config file, even after booting to get the other data.
said by Johkal :said by JahsDisciple :can you post a speedtest result and possibly your config file? » www.speedtest.net The config didn't show in the log entries above. |
|
nlehrer
join:2004-06-11
Arlington, VA
| reply to tshirt
»/linequality/nil/2409293
»/tweakr/block:···a=normal
said by tshirt :Do a Tweak Test » /tweaksand an LQ test too. » /linequalityand post the links back here. Please make yourself "pingable" for the tests, if you are not already. |
|
tshirt
Premium,MVM
join:2004-07-11
Snohomish, WA
·Comcast
| Both those test results look good. i would consider cutting your rwin from 400040 to 200020, even though no packet loss occured during that test( High RWIN can cause delays if/when packets are lost/must be resent, and some occasional packet loss is normal) you want to find a middle ground, neither too high nor too low. |
|
tshirt
Premium,MVM
join:2004-07-11
Snohomish, WA
·Comcast
| reply to Johkal
said by Johkal : The config didn't show in the log entries above. It's a Moto 5100, it won't show the config file. (unfortunately!!!) |
|
nlehrer
join:2004-06-11
Arlington, VA
| reply to tshirt
i played with the rwin values and got the download speed up to about 10.5 Mbs. that's a lot better, thanks. but i still want to get closer to 16Mbs. any further suggestions?
said by tshirt :Both those test results look good. i would consider cutting your rwin from 400040 to 200020, even though no packet loss occured during that test( High RWIN can cause delays if/when packets are lost/must be resent, and some occasional packet loss is normal) you want to find a middle ground, neither too high nor too low. |
|
tshirt
Premium,MVM
join:2004-07-11
Snohomish, WA | rerun and post the tests again so we can see what changed |
|
