Random disconnects, is my modem dying?

Sirkusphreak · Post by **Sirkusphreak** » Mon Jun 04, 2007 6:05 pm

Lately for the past several weeks i've noticed my latency shoot up while I play my World of Warcraft, and sometimes it would actually disconnect.

I've tried contacting Comcast about it (comcast chicago btw) but the guy I was talking too was more concerned with why my Mac adress wasn't either displaying or wasn't the same or something (mind you when he was checking the Mac Adress, my internet was actually working again).

I've been using the same modem for well over 3 or 4 years now, with the exception of 1 day when i tried to change out modems to see if that fixed a connection issue, but it turns out a squirelle actually ate through some of the cable line, but I called them up and had the modems switched back.

Anways, i noticed lately that whenever the internet goes out, I just log into my modem via my computer and do a simple reset and its usually fine again, sometimes for the rest of the day, some times for 2 days, sometimes for 20 minutes...

I checked the logs and this is the error i'm getting:

Code: Select all

070604123253 8-Debug M571.7 CM Cert Upgrade Enabled. Initiate after Registration  
070604123253 8-Debug I503.0 Cable Modem is OPERATIONAL  
070604123253 7-Information B401.0 Authorized  
070604123252 8-Debug F502.1 Bridge Forwarding Enabled.  
070604123252 8-Debug F502.3 Bridge Learning Enabled.  
070604123252 7-Information B0.0 Baseline Privacy  
070604123250 7-Information X518.9 Configuration - MMFMMD - Unit Update Enabled by CVC  
070604123250 8-Debug I500.1 DOCSIS 1.0 Registration Completed  
070604123250 7-Information I500.4 Attempting DOCSIS 1.0 Registration  
070604123250 7-Information D509.0 Retrieved TFTP Config File SUCCESS  
070604123250 7-Information D507.0 Retrieved Time....... SUCCESS  
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS  
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response  
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.  
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 5s Tot DSC:1 OFF:1 REQ:1 ACK:1  
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day  
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS  
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 54, tempSid 153  
************ 8-Debug T505.0 Acquired Upstream with status OK  
************ 7-Information T501.0 Acquired Downstream (711000000 Hz)........ SUCCESS  
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 711000000, US Id 1  
************ 7-Information I510.0 *** BOOTING *** SB4100-1.4.9.0-SCM00-NOSH  
070604121923 8-Debug M570.2 Motorola CM certificate present  
070604121923 8-Debug M571.7 CM Cert Upgrade Enabled. Initiate after Registration  
070604121923 8-Debug I503.0 Cable Modem is OPERATIONAL  
070604121923 7-Information B401.0 Authorized  
070604121921 8-Debug F502.1 Bridge Forwarding Enabled.  
070604121921 8-Debug F502.3 Bridge Learning Enabled.  
070604121921 7-Information B0.0 Baseline Privacy  
070604121921 7-Information X518.9 Configuration - MMFMMD - Unit Update Enabled by CVC  
070604121921 8-Debug I500.1 DOCSIS 1.0 Registration Completed  
070604121921 7-Information I500.4 Attempting DOCSIS 1.0 Registration  
070604121921 7-Information D509.0 Retrieved TFTP Config File SUCCESS  
070604121921 7-Information D507.0 Retrieved Time....... SUCCESS  
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS  
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response  
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.  
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 5s Tot DSC:1 OFF:1 REQ:1 ACK:1  
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day  
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS  
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 45, tempSid 153  
************ 8-Debug T505.0 Acquired Upstream with status OK  
************ 7-Information T501.0 Acquired Downstream (711000000 Hz)........ SUCCESS  
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 711000000, US Id 1  
************ 7-Information I510.0 *** BOOTING *** SB4100-1.4.9.0-SCM00-NOSH  
070604005717 8-Debug M570.2 Motorola CM certificate present  
070604005717 8-Debug M571.7 CM Cert Upgrade Enabled. Initiate after Registration  
070604005717 8-Debug I503.0 Cable Modem is OPERATIONAL  
070604005717 7-Information B401.0 Authorized  
070604005715 8-Debug F502.1 Bridge Forwarding Enabled.  
070604005715 8-Debug F502.3 Bridge Learning Enabled.  
070604005715 7-Information B0.0 Baseline Privacy  
070604005715 7-Information X518.9 Configuration - MMFMMD - Unit Update Enabled by CVC  
070604005715 8-Debug I500.1 DOCSIS 1.0 Registration Completed  
070604005715 7-Information I500.4 Attempting DOCSIS 1.0 Registration  
070604005715 7-Information D509.0 Retrieved TFTP Config File SUCCESS  
070604005715 7-Information D507.0 Retrieved Time....... SUCCESS  
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS  
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response  
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.  
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 5s Tot DSC:1 OFF:1 REQ:1 ACK:1  
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day  
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS  
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 45, tempSid 153  
************ 8-Debug T505.0 Acquired Upstream with status OK  
************ 7-Information T501.0 Acquired Downstream (711000000 Hz)........ SUCCESS  
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 711000000, US Id 1  
************ 7-Information I510.0 *** BOOTING *** SB4100-1.4.9.0-SCM00-NOSH  
070604005644 7-Information H501.2 HFC: Shutting Downstream Down  
070604005644 2-Alert T507.0 Received Async Error Range Failed  
070604005644 3-Critical R4.0 Received Response to Broadcast Maintenance Request, but no Unicast Maint  
070604005644 3-Critical H501.8 HFC: T4 Timer Expired  
070604003844 8-Debug M570.2 Motorola CM certificate present  
070604003844 8-Debug M571.7 CM Cert Upgrade Enabled. Initiate after Registration  
070604003844 8-Debug I503.0 Cable Modem is OPERATIONAL  
070604003844 7-Information B401.0 Authorized  
070604003843 8-Debug F502.1 Bridge Forwarding Enabled.  
070604003843 8-Debug F502.3 Bridge Learning Enabled.  
070604003843 7-Information B0.0 Baseline Privacy  
070604003841 7-Information X518.9 Configuration - MMFMMD - Unit Update Enabled by CVC  
070604003841 8-Debug I500.1 DOCSIS 1.0 Registration Completed  
070604003841 7-Information I500.4 Attempting DOCSIS 1.0 Registration  
070604003841 7-Information D509.0 Retrieved TFTP Config File SUCCESS  
070604003821 7-Information D507.0 Retrieved Time....... SUCCESS  
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS  
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response  
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.  
************ 5-Warning D520.2 DHCP Attempt# 5 BkOff: 5s Tot DSC:5 OFF:2 REQ:2 ACK:1  
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received  
************ 5-Warning D520.2 DHCP Attempt# 3 BkOff: 4s Tot DSC:3 OFF:1 REQ:1 ACK:0  
************ 3-Critical D2.0 DHCP FAILED - Request sent, No response  
************ 5-Warning D520.2 DHCP Attempt# 2 BkOff: 7s Tot DSC:2 OFF:0 REQ:0 ACK:0  
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received  
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 4s Tot DSC:1 OFF:0 REQ:0 ACK:0  
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received  
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day  
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS  
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 45, tempSid 153  
************ 8-Debug T505.0 Acquired Upstream with status OK  
************ 7-Information T501.0 Acquired Downstream (711000000 Hz)........ SUCCESS  
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 711000000, US Id 1  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 127756300, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 133756600, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 139756900, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 145757200, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 151757500, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 157757800, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 163758100, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 169758400, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 175758700, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 181759000, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 187759300, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 193759600, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 199759900, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 205760200, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 211760500, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 217760800, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 223761100, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 229761400, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 235761700, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 241762000, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 247762300, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 253762600, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 259762900, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 265763200, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 271763500, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 277763800, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 283764100, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 289764400, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 295764700, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 301765000, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 307765300, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 313765600, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 319765900, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 325766200, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 331766500, US Id 0  
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing  
070604123253 8-Debug M570.2 Motorola CM certificate present

The only thing that leads me to believe that it might be a problem with a wire of some sort is that I notice this happens more often when it rains. Not that when it rains i'm screwed, but today has been on and off rainy and according to my roomate its DCed a few times, where as i've actually been able to play through a storm we had a few days ago no problem.

Other times there isn't a cloud in the sky and i'll just get DCed or whatever, so i've no idea what could be causing the problem.

Sorry for all of the text; i just want to be as clear as possible and give as much information about the problem I can, you know?

What else can I do to help give you guys more info (if need be) to help diagnose this problem even further?

Sirkusphreak · Post by **Sirkusphreak** » Mon Jun 04, 2007 6:12 pm

Oh yeah, sorry:

Modem: Motorola Surfboard SB4100

Signal at the time of this post with the internet running well (well, not fantastic):

Code: Select all

Downstream  Value 
Frequency 711000000 Hz Locked 
Signal to Noise Ratio 37 dB 
Power Level -4 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 1 
Frequency 24000000 Hz Ranged 

Power Level 53 dBmV

Router:
Linksys WRT300N, wireless router: Please note that i'm connected to this router via your standard ethernet wire, NOT wirelessly.

legumo · Post by **legumo** » Tue Jun 12, 2007 3:51 am

3-4 years for a modem is a long time.

yes modem is dying ......OR.........ISP problem.

Sava700 · Post by **Sava700** » Tue Jun 12, 2007 9:05 am

legumo wrote:3-4 years for a modem is a long time.

yes modem is dying ......OR.........ISP problem.

jesus... decided to hit every thread? LOL

I don't think his modem is dying..but it does sound like line noise making him drop.

Looks to me his upstream level is right on the upper edge and thus when it peaks over 56 it will cause him to drop too..but noise can push this up.

Sirkusphreak · Post by **Sirkusphreak** » Tue Jun 12, 2007 5:21 pm

Thanks for the responses guys, but I think it was a combo of the modem being crappy and my line giving out. I guess the other techs did more of a quick fix whenever they did something with my line as opposed to a long term fix. The tech that came out yesterday looked at my line and said screw it, he was gonna replace the whole thing.

I haven't gotten a disconnect since he went ahead and did that, and he told me the signals were OK, so I guess that's good.

Code: Select all

Downstream Value  
Frequency 711000000 Hz 

Signal To Noise Ratio 38.7 dB 

Power Level -1.4 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 1 
Frequency 24000000 Hz 
Power 50.0 dBmV

The upstream power hasn't moved at all. When he replaced the wire it went down to 50.0 dBmV and stayed there.

I hope that's the end of my troubles. Thank you all for your help.

scarlet · Post by **scarlet** » Tue Jun 19, 2007 2:24 pm

Hey Sirkusphreak!

I was just wondering how you did those tests on your internet to check the downstream and upstream info.

For the past month or so, perhaps a little more, I've been having intermittant disconnects as well. Not only does WoW DC, but also vent. With some fiddling and turning off the power and resetting the modem or router, I can usually get it to come back up, but needing to do that every few days is getting to be a pain.

The comcast modem I have is an RCA modem I got from comcast 2 years ago. I connect directly to a Linkys Wireless router.

alex_barringer · Post by **alex_barringer** » Tue Jun 19, 2007 8:14 pm

Ok, I will bite again...

It is very rare that a modem fails in Cable and xDSL. You modem is not failing from the information I just read. As I have said in other posts, if you have trouble during a storm and you don't have power glitches, your problem is outside the house.

I have mentioned that many service providers use amplifiers to boost the SNR of a line condition so that your speed of your connection stays up there. These amplifiers are suseptible that of lightning and rain. If you have poor grounding on the cable connector and shielding or bad chassis ground on the amplifiers the ionization of the air from lightning will cause spikes or surges to occur on the amplifier power path which in turn will affect your connection and other people's as well. You should find out if other people are having trouble with their connection in your immediate area, this would help me a great deal.

Also if it is happening to you and is an amp problem, more than likely at least 4 to 8 other people will have the same trouble. Not all cable / xDSL telephone network enclosures are created equal, some are not grounded by default and this is a very bad thing.

jer0miah · Post by **jer0miah** » Sun Apr 13, 2008 5:00 am

look... it is really important to understand how the upload and download signal works. the Motorola modem sb 4100 or 4200 has an optimal operating range (cable signal to the modem) for the download of +12 to -12 for the up load the optimal "sweet spot" is 45. the upload should be between 35 and 50 if it goes lower than that it runs too "hot" meaning it doesn't think its online. If it goes above 50 it might have connection problems because it cannot communicate with the isp's head end. NOTE The only time an amplifier should be used if if all of the wiring including to the pole or underground is in good condition free of defects because it will amplify both good and bad signals(garbage in garbage out). It appears from the log that your modem is "ranging" which means that it is not getting a response from the isp so it will change the frequency in an attempt to communicate with the host. Normally I would start by telling you to check all your connections for "loose" fittings(causes packet loss). A return of 53 is much too high and the modem might be having an issue connecting to the host server. I highly doubt it is the modem.