New Contributor II
•
3 Messages
Brand New Motorola Surfboard SB6141 Behind Netgear WNDR344 In Constant Need of Power Recycle
I was so proud of myself yesterday when my shiny new SB6141 DOCSIS3.0 modem was delivered to me. Had I known then what I know now, having spent most of the hours in between reading forum post after forum post and troubleshooting every which way but loose, I would have asked the kind UPS man to take that box and put it "where the sun don't shine". Mere hours after I installed the thing and verified with a Cox Support Rep via Live Chat, the modem simply started losing its grip on the internet and could only be temporarily revived via cycling the power. That seems to work very well for about 10 minutes at best.
Having read so many posts specifically about my particular model of modem in the last 18 hours, I have yet to see a single definitive answer to any of the very commonly worded cries for help on this very same user experience. I've seen every suggestion from surge protectors draining/spiking the power levels beyond spec to Netgear routers being overpowered by the sheer gloriousness of the SB6141 modem. There were moderators from Time Warner Cable suggesting that there could be too much noise in the copper and a customer of Comcast's claiming that installing a reverse path gain amplifier did the trick. Most of the posts put the blame on the modem itself, but quite a few pointed the finger at the ISP's area infrastructure and the poor quality of signal flowing down the streets.
I live in New Orleans. I don't know if the forum moderators have ever seen the condition of the outdoor cabling and wiring in New Orleans, but I can assure you we are only different from the hillside slums and cardboard shanties of Rio de Janeiro in that we at least manage to have working air conditioners sticking out of every window in our homes. The wiring from the pole to these old historic houses looks like something a child would draw to illustrate a nightmare about the Flying Spaghetti Monster. Back when I actually subscribed to Cox Cable TV, my television had a pretty constant 90 hertz feedback stripe on it for the whole year and a half that I kept cable. I have to use powerstrips/surge protectors in every room, because there is usually only one outlet remotely close to where power is needed.
When I was forced to upgrade my internet service from Premier to Ultimate in December 2013 after receiving notifications about exceeding my data cap, I did so over the phone without any technician being dispatched to my address to inspect my wiring for its suitability to deliver higher speeds. Nothing was said to me about the need to replace my Cisco DOCSIS2.0 modem at the time. So I am quite certain that everything I've read tonight - all of it - is very likely true of my own case. My electricity fluctuates like crazy, my cable line is probably split in 4 different places and respliced in another 16 knowing the quality of New Orleans workmanship. And there is no getting around the fact that I have more things to plug in than holes in which to plug them.
So. Here we are. I'm going to provide all of the reports from the monitor that you will undoubtedly need, but short of having Cox restring copper from one end of New Orleans to the other or getting a little more aggressive with their delivery of gigabit service to the area, I'm already doubtful that we are going to be able to resolve my intermittent connection issues without some amount of exasperation. Bon chance, mes amis!
Speed Test 5/30 - Before the Issues:
Then when the celebrating stopped, and the headache began, here's the result for this morning's Speed Test. Keep in mind that nothing in my configuration, connections, or settings has changed other than the earth's position relative to the sun.
I should mention that this loss of internet connection happened back-to-back, again and again for several hours in the late evening, throughout most of the wee hours before dawn. For the last few hours or so, though, it's behaved itself and has not dropped me once. Of course, it started to rain pretty heavily around 2AM, so perhaps we can chalk the improved staying power up to the extra humidity in the air bridging circuits, sort of the opposite of what was done to help in Cox_Support_SB6141_Error_Log_05312014. In either case, I sure wouldn't mind getting that speed back!
Thank you, and let me know if you need any other information.
Accepted Solution
NOLA_bear
New Contributor II
•
3 Messages
11 years ago
Thanks for following up, Health Edge & chanmiro. After I composed my magnum opus here, I decided a sanity check and gadget-free time out were in order, so I stepped away from the frustration that was my office and came back at it this afternoon with a fresh set of eyes.
The first thing I tried was running the statistics report off of the Netgear Router. I wanted to see what the router was detecting while my PC was showing no connection to the internet. It didn't look good, because LAN1 was connected to the modem. (Mistake #1)
I pulled every ethernet cable out of all the modems, routers, repeaters, and computers to tackle it from scratch instead of trusting that the new modem could just plug and play into the same spot that the Cisco modem held. That obviously wasn't working. EUREKA! Tucked away under one of the risers on my desk was an old D-Link switch that I had added to the footprint years ago for reasons I can't even remember. (Mistake #2) I found that a couple of my cables were hooked in there in some weird kind of loop between the new modem and the router. I'm not even sure the thing was powered on. That had to go.
So, I ran the cables again reconnecting everything the way a sane person would have done it, restarted all the devices including my computers, reset the LAN and WAN adapters on the PC's, and ran another diagnostic from the router.
Since the D-Link switch was no longer plugged into LAN2, this was like a chorus of angels singing from the Cloud.
Everything *seems* to be working correctly. I haven't lost my connection to the internet so far, and I haven't had to unplug and replug the modem to reset the connection (yes, that's what that log was showing above.) at all. For the time being, I think the issue is solved, and I'm a little embarrassed at how much forum fodder I typed up during my hours of exasperation and despair.
As for the XBone being connected so unforgivably to that Wi-Fi repeater in my living room, I agree. Something has to be done about that. Maybe I'll see about putting the old Cisco modem in there for now with the gaming systems and entertainment stuff. You know, because my home network isn't complicated enough. There's always room for more, right?
Thank you again for taking the time to review this thread. I guess the advice I'll leave here for the next know-it-all customer whose thorough research of the SB6141's reboot issue leads him or her straight to an ego party for 1 is to walk away from it for a while and check your work again. You might have a hidden 5-port switch you didn't know about. Wouldn't THAT be embarrassing?
0
0
NOLA_bear
New Contributor II
•
3 Messages
11 years ago
Also, just in case you need it, here's the system info for my home PC, an Alienware X51 desktop running Windows 8.1 Pro.
My system configuration is going to be fun to explain. </sarcasm>
My home PC is connected to the Netgear WNDR3400 Wi-Fi Router, which gets its juice from the Surfboard SB6141 modem. Out of that Netgear router, I have an ethernet connection to my Work PC, a Latitude E6410 running Windows 7 SP4 in a docking station. Also out of the back of that router is another ethernet connection to a wireless repeater (1 of 2) plugged into the wall that uses the house's wiring to boost the Wi-Fi into a second repeater in the front of the house (2 of 2). From repeater 2, I have ethernet out to my Xbox One and to my Amazon Fire TV box. My Surface Pro connects via Wi-Fi to the network, as does my cell phone and a few Belkin WeMo electrical outlets to power my lamps and such. A Roku connects via Wi-Fi for the bedroom TV, as well as my XBox 360. And I believe that complete's this virtual tour of my humble abode. Make yourselves at home.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
Wow, thats a heck of a post. Let me get a drink.
It sounds like you already know the likely causes of the problem, probably a mixture of intermittent noise thanks to the "spaghetti monster" XD and the power fluctuations. The good news is, at least at the time of the snapshot, your signal levels look good. Here is a FAQ explaining the particulars, notice DOCSIS 3.0 vs 2.0 signal level requirements.
I guess my first question would be what kind of solution were you looking for? You made it clear any change inside is difficult due to the complexity of your setup and sheer size of it. The main issue I see in the logs are resets due to power loss. Is that you rebooting the modem or possibly the result of the power fluctuations you mentioned? Were you looking for opinions from others in your area? Options on how to document and track the problems? I don't want to start spouting off copy pasta before I understand your expectations. Seeing a Xbox One hooked up to a dual repeater does make the nerd in me cry a little though. BTW, welcome to the forums!
0
0
chanmiro
Contributor
•
73 Messages
11 years ago
I agree with Health Egde in that your signals look great. But those constant reboots are pretty odd to see, especially if they are going on automatically (are they?).
Speaking of those log entries, I'm not sure what the "ToD request sent - No response received" comments mean, is it the time of day? Could it be that although the modem has great connectivity to the Cox infrastructure, for some reason the modem cannot actually communicate properly with it?
This is all speculation in my part and I apologize because I'm no expert.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
The more eyes on, the better I always say. Awesome to see someone else having a interest in helping others!
Pretty sure this is standard procedure for a modem reboot. ToD stands for Time of Day. This occurs during a reboot because the modem is trying to phone home to get the date and time before it's fully connecting to Cox. Thats also why you see the 1970 date in the logs. For some reason it defaults to that when it can't get a date.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
11 years ago
Such a delightful read. Thank you for taking the time to both fix your problem, and document it in a way where others can possibly learn from it. Good call using the Netgears statistics to find the connection issue, which brought you to the dlink switch. I was way off pointing you towards power fluctuations. If you do ever have problems with that though, a UPS might help. I use a Cyberpower CP1350AVRLCD for power, and a Tripp-lite Isotel6Ultra for everything else. But I have also heard of some people getting free power conditioners if they bug their electric company enough.
Thanks again for the greats posts. It was a breath of fresh air to theforum. Feel free to pop in any time you want. I sometime feel I post too much here and like when others join in on the conversations.
0
0