Inzax
New Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: intermittent cable modem resets caused by signal drop
I also have SBG6580 with Firmware, 3.5.8.4-GA-00-505-NOSH. It is not setting back to earlier version and has been at 3.5.8.4 for some time. My earlier post in this thread (I think it was this thread) indicate I have been with 3.5 for weeks.0Views0likes0CommentsRe: intermittent cable modem resets caused by signal drop
The firmware version is still the same on my modem as posted by others late in this thread. I have noticed the "hardware version" is now 2 instead of 1. Hmmm....Is the new hardware version indicative of a "patch." Information Standard Specification Compliant DOCSIS 3.0 Hardware Version 2 Software Version SBG6580-3.5.8.4-GA-00-505-NOSH0Views0likes0CommentsRe: intermittent cable modem resets caused by signal drop
Inzax said: The only advice I have is to keep at them, Call tech support. Don't settle. Move on to another service if you can. The SBG6580 seemed to be the common denominator. That appears not to be the case. To prove my case and monitor my internet connection I downloaded this http://code.google.com/p/internetconnectivitymonitor/ It pings two websites of your choice every five seconds. If your connection goes down it keeps track of missed connections. You can save the log and show it to Cox. This won't tell you where the problem is but will justify adjusting your bill or escalating your case. Post back hereyour results. I am curious. Mine missed all sorts of connections until I had them re-provision the modem. After that, I was good to go. That fix has not worked for others. also....if you don't want to download the above from google. You can download other type of programs. Pingdom is one. Also there are dos shell commands (ping) you can use. Google search will produce results you need. Edit: you would have to allow pings for pingdom. Use the free version for your IP. I have never used it but others have spoken of it.0Views0likes0CommentsRe: intermittent cable modem resets caused by signal drop
The only advice I have is to keep at them, Call tech support. Don't settle. Move on to another service if you can. The SBG6580 seemed to be the common denominator. That appears not to be the case. To prove my case and monitor my internet connection I downloaded this http://code.google.com/p/internetconnectivitymonitor/ It pings two websites of your choice every five seconds. If your connection goes down it keeps track of missed connections. You can save the log and show it to Cox. This won't tell you where the problem is but will justify adjusting your bill or escalating your case. Post back hereyour results. I am curious. Mine missed all sorts of connections until I had them re-provision the modem. After that, I was good to go. That fix has not worked for others.0Views0likes0CommentsRe: intermittent cable modem resets caused by signal drop
Although this solution solved your problem, be aware this is not the best solution for the reason's you pointed out. Your other PC's will continue to have issues since they are not in the DMZ. It sounds like your router and/or its settings are the root of your issues. Good luck.0Views0likes0CommentsRe: Need firmware update for SBG6580 modem - current firmware kills VOIP
Agreed. Two separate devices seems to be the answer. I see what you are saying about the firmware. I assumed since the router worked as intended when factory reset then would stop shortly after being hooked up to the network it was being "updated." Thanks.0Views0likes0CommentsRe: Need firmware update for SBG6580 modem - current firmware kills VOIP
Not trying to argue with you. I do appreciate you responding. It is very frustrating when I am getting onepiece of information from Motorola and another from Cox. I think what I am seeing is part of a bigger issue. Motorola says one thing. Cox says another. In the end, I get bounced around between the two. Motorola claims the modem was NOT shipped with the latest firmware. I could reset it and see what version it is but I don't want to do that since the modem is at least holding an internet connection now. Either way I do know the modem was not working for port forwarding and triggering a problem Motorola says is caused by Cox. Cox says it's Motorola's problem. I sit in the middle. Tier 2 advises there is a new firmware in the works. They can't push it to me because the network will reset the modem to only the approved firmware for the cox network. I am hopeful the new firmware will address the problem. Take care. Thanks again for your efforts.0Views0likes0Comments