NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
cm400 modem sees router, won't provide internet connectivity
Modem: CM400 (also CMD31T) Routers: Airport Extreme, Netgear RP614, Linksys BEFSR41 Mac: MacbookPro 10.10.5 While using a CMD31T modem, a firmware upgrade failure on a DLink DSR-250 left it unb...
This afternoon I finally found the answer. I'd power cycled everything many times, and factory-reset and firware-upgraded all three of the routers being tried. However, for what it's worth to anyone else who runs into this kind of hassle, here are the considerations that just this afternoon resolved the situation:
1. A modem (cable modem, at least) requires that every time a different device is connected to its internet port, it must be rebooted. I didn't do that when I was trying to debug the situation by first connecting the computer and then switching to the router. The modem rebooting that I DID do apparently didn't coincide exactly with the switching I was doing.
2. The Apple Thunderbolt/Ethernet adapter has its own device address and is seen as a different device from the modem's point of view, which explains why when I tried to share the connection with another machine, by plugging first one and then the other into the modem, the other machine wouldn't connect unless I also transferred the adapter, making me think the second adapter was faulty (and prompting an expensive order of an extra one from Amazon, which won't be needed now).
3. Probably also necessary was a complete connection reset of the modem by disconnecting it from the coax cable and powering it off for 20 minutes. That seemed to be the magic bullet in this case, though #1 above may have been sufficient (I didn't try it before taking this step). I remember arguing with a Time-Warner representative a while back when he told me to disconnect the cable -- I didn't see how it would make any difference. It turns out a modem looks different to the Time-Warner server when it's simply powered off and when it's totally disconnected. In the latter case, when shows up again to T-W, the whole T-W/modem connection relationship is reset, and it DOES make a difference.
FWIW, these insights resolved ALL the endless little crazinesses I've been dealing with for the past four days.
Hello Datlee
Have you tried to factory reset the router?
DarrenM
This afternoon I finally found the answer. I'd power cycled everything many times, and factory-reset and firware-upgraded all three of the routers being tried. However, for what it's worth to anyone else who runs into this kind of hassle, here are the considerations that just this afternoon resolved the situation:
1. A modem (cable modem, at least) requires that every time a different device is connected to its internet port, it must be rebooted. I didn't do that when I was trying to debug the situation by first connecting the computer and then switching to the router. The modem rebooting that I DID do apparently didn't coincide exactly with the switching I was doing.
2. The Apple Thunderbolt/Ethernet adapter has its own device address and is seen as a different device from the modem's point of view, which explains why when I tried to share the connection with another machine, by plugging first one and then the other into the modem, the other machine wouldn't connect unless I also transferred the adapter, making me think the second adapter was faulty (and prompting an expensive order of an extra one from Amazon, which won't be needed now).
3. Probably also necessary was a complete connection reset of the modem by disconnecting it from the coax cable and powering it off for 20 minutes. That seemed to be the magic bullet in this case, though #1 above may have been sufficient (I didn't try it before taking this step). I remember arguing with a Time-Warner representative a while back when he told me to disconnect the cable -- I didn't see how it would make any difference. It turns out a modem looks different to the Time-Warner server when it's simply powered off and when it's totally disconnected. In the latter case, when shows up again to T-W, the whole T-W/modem connection relationship is reset, and it DOES make a difference.
FWIW, these insights resolved ALL the endless little crazinesses I've been dealing with for the past four days.