Sign in with
Sign up | Sign in
Your question

Having Internet Disconnect issues randomly

Last response: in Networking
Share
November 5, 2012 10:25:23 AM

I have attempted to fix this issue on my own and have decided I definitely need help. I have a sb 6120 modem and a wireless router that have been randomly dropping and resetting. I thought it was happening with increased bandwidth usage, but it doesn't appear to be linked to when I'm downloading or gaming. Just in case, I set up port forwarding for my games but no change. I have swapped out wireless routers and directly connected to my modem and it still happens. I have spoken with my ISP and they can't see that I have lost connection even while I am currently disconnected. My stats look good with my downstream power stable around 4 or 5 and up around 38. Also, I have pinged my modem and each computer connected wirelessly and show no packet loss. I'm pretty much out of ideas here and I have scheduled an appointment for a tech to come out but I don't want to burn the money if I'm just going to have to replace my modem anyway. Any ideas on ways to test/fix what's going on? I have posted the logs below if anyone knows how to interpret. Thanks in advance!

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;

5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
November 7, 2012 8:39:29 PM

As I recall vaguely, a bunch of folks had issues last year with SB6120 after a firmware update, and many seemed to have fixed it by rolling the firmware back to an earlier version. I don't think that the SB6121 had these issues, so my guess is that it is a problem with your SB6120 modem. I would hunt down an older firmware version and try flashing it to that earlier version to see if it fixes the issues.
m
0
l
!