site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
2625
Share Topic
Posting?
Post a:
Post a:
Links: ·Forum Rules ·Motorola FAQs ·Support and Downloads
AuthorAll Replies


SadFace

@att.net

SB 5101 constantly loses connection... End of my rope.

Hello!
First off, please excuse me for being a bit of a novice when it comes to the technical workings of a cable internet connection. All of my knowledge comes from google.

Last week, I had cable broadband installed in my home. It worked incredibly well for the first day. Since then, I've been plagued with connection issues.

My connection to the internet seems to just hang at random, sometimes as often as every ten minutes or so. I even had 15 hour period of no connectivity. Both my modem and computer claim to be connected, but I can't access any pages. There are even some rare occasions where I'm unable to look at my modem's diagnostics page!

When I am able to look, I see messages in the logs page about "Unicast Maintenance Ranging Started...No response received." These entries directly correspond with my loss of connectivity. I also see some that involve "DHCP Warning" and "DHCP Failed."

The only thing I can do that seems to help a little bit is power cycling, sometimes 4 or 5 times in a row... What do you think? Is this a modem issue?


sashwa
Pixie Cat Crunchin' n Foldin'
Premium,Mod
join:2001-01-29
Alcatraz
kudos:15

Who is your ISP? We may have a forum that can help with this.



SadFace

@att.net

I subscribe to an ISP called MICOM in the northern Michigan area... They might be pretty local though.



sashwa
Pixie Cat Crunchin' n Foldin'
Premium,Mod
join:2001-01-29
Alcatraz
kudos:15

No forum for them here. Sorry.

Hopefully someone around here might be able to give you some help with this.

Have you talked to your ISP about this?



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:5

reply to SadFace
Could you please post:

1) Signal levels
2) Entire log entries

Thanks!
--
In God we trust; all others bring data!



SadFace

@att.net

970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:53 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:45 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:45 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:31 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:31 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:15 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-14 02:25:25 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2011-11-14 02:19:52 3-Critical I002.0 REG RSP not received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:11 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-11 20:38:26 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:02:49 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:02:48 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:39 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:14 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:32 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:31 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:17 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:13 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-11 17:37:14 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-11 16:13:52 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-11 15:05:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-11 13:28:11 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:19 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:16 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-08 10:08:55 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2011-11-08 04:02:36 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2011-11-06 10:51:34 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:18 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:10 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:12 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2011-11-04 10:05:43 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:55 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:51 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:43 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:40 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:40 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:09 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:09 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:05 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:28 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:27 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-03 15:16:33 4-Error D004.3 ToD request sent- No Response received
1970-01-03 15:16:31 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-03 15:16:22 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-03 15:16:22 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-03 15:16:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-03 15:16:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-03 15:16:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-03 15:16:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-03 15:16:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-03 15:16:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-03 15:16:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-12 20:45:07 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-12 20:45:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-12 20:44:03 4-Error D004.3 ToD request sent- No Response received
1970-01-12 12:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-12 11:59:03 4-Error D004.3 ToD request sent- No Response received
1970-01-12 00:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-11 23:59:03 4-Error D004.3 ToD request sent- No Response received
1970-01-11 12:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-11 11:59:03 4-Error D004.3 ToD request sent- No Response received
1970-01-11 00:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-10 23:59:03 4-Error D004.3 ToD request sent- No Response received
1970-01-10 12:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-10 11:59:03 4-Error D004.3 ToD request sent- No Response received
1970-01-10 00:03:57 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-09 23:59:03 4-Error D004.3 ToD request sent- No Response received

Downstream Value
Frequency 111000000 Hz
Signal To Noise Ratio 39.8 dB
Power Level -2.0 dBmV

Upstream Value
Channel ID 3
Frequency 29584000 Hz
Power 45.3 dBmV



SadFace

@att.net

Sorry about the lengthy post.... thought it best to report the whole log. I've been reluctant to contact the ISP so far just because I've wanted to believe the problem would just go away (looking like I'm dead wrong), and they have a policy about charging for service calls that I'd like to avoid....



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:5

Your signal levels are within specs.

Is the modem yours or do you rent it?



SadFace

@att.net

I rent. I have seen the signal to noise ratio in the 20's once or twice though...



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:5
Reviews:
·Comcast

Good info about the signal level fluctuation.
Since this was a new install & you rent, I don't see why it would cost for your ISP to address this issue. It's either pointing to an intermittent splitter/cable, etc issue or possible bad modem; neither which should be considered a chargeable service call.



SadFace

@att.net

I'll have to give them a call after the weekend... I'm really hoping a new modem will be my magic fix. My connection hanged last night and I decided to just let it go overnight to see if it would snap back. It didn't. And a restart of my modem didn't work in the morning either. A restart after I got home from work did the trick. Frustrating!



Nick
Purveyor of common sense
Premium,VIP,MVM
join:2000-10-29
Smithtown, NY

reply to SadFace
Sounds like impulse noise issues causing fluctuation in levels when you lose your connection. Can you get the modem firmware from your modem?



SadFace

@att.net

Not sure about firmware.... how would I go about it?



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:5
Reviews:
·Comcast

You can find the firmware version under the "Help" tab in the diagnostic pages.

Not sure what we will gain with the info., considering it's your ISP's responsibility to correct your issue with their install & their modem.



SadFace

@att.net

Software Version: SB5101-2.4.1.3-SCM00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

I'll take what I can get lol.... I'm definitely still going to call them though. I don't think I'm even getting the performance I should when I AM connected..



Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
kudos:5
Reviews:
·Comcast

2.4.1.3-SCM00-NOSH is an old firmware version, but is only known for degrading transfer rates; not disconnections.
The version before it was known for lock-ups & disconnects (ref: 2.4.1.1-SCM14-NOSH )

You can ask for a firmware upgrade if they are willing.



SadFace

@att.net

I hope they're willing... I have this huge fear that they're actually grossly incompetent lol. Like when I called to first inquire about the service itself I asked about possibly making it wireless, and the receptionist's answer was "Uhhhh... YOU can make it that way, but we don't really DO that..."



SadFace

@att.net

I did notice the day after installation that the modem itself looked a little worn... And I've noticed the ethernet connection on the modem itself is really loose... But I assumed that would give me "a network cable is unplugged" rather than weird stall-outs.


agenthndyman

join:2011-12-12
Castroville, TX

reply to SadFace

Re: SB 5101 constantly loses connection... End of my rope.

I recently converted from AT&T DSL 1.5mb to AT&T U-verse 6MB. I had a similar problem after they installed a new network interface on the side of the house. It would work great for a good while (6-8 hours) then just drop and be out for hours! Local tech left a 2nd modem to try the next time it went down. No luck! Anyway, it ended up being a defective "module" in the network interface. He replaced it and service is back to the phenomenal quality which I am used to having with AT&T DSL! Total troubleshooting... 1 week! He even left the 2nd modem and said keep it!

Sunday, 26-May 01:46:27 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics