• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SB 5100 problems

Sead0nkey

Senior member
SB 5100 problems

First off this modem worked fine for 6 months.....Then about 1 month ago my connection started to drop intermittently. Almost once an hr for no longer then 2 mins. I have had the cable company out twice. Both times they have remarked on how high my signal is. They added some splitters to knock down the signal but I still get dropped....help!


Here is the signal snapshot:

Downstream Value
Frequency 117000000 Hz Locked
Signal to Noise Ratio 28 dB
Power Level -7 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 26992000 Hz Ranged
Power Level 51 dBmV

Here are the logs from the 5100:

1970-01-04 23:21:00 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-04 01:15:13 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-04 01:11:00 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-04 00:00:55 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-04 00:00:50 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-04 00:00:47 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 22:01:23 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-03 22:00:54 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 17:41:57 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-03 17:40:54 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 03:52:26 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-03 03:50:54 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 02:16:38 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-03 02:15:54 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 00:00:49 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-03 00:00:38 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 06:28:51 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-02 06:25:44 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 02:42:01 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-02 02:40:44 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 00:00:40 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-02 00:00:29 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-02 00:00:24 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 23:50:23 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 23:45:30 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 06:54:01 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
 
I had a similar problem once, but it happened when they had the DC Tap hooked up backwards and then added Digital Telephone in my area. If you're wired with a DC tap, try reversing the "tap" and "out" legs. You're looking for a little 2-way splitter type looking thing. Fixed my problems after half a dozen techs and a month later. Still going strong.
 
Back
Top