Originally posted by jerry atrik:"unplug the pc and turn the modem off plug lappy in and turn the modem back on."
A.) Turn off PC/laptop first.
B.) Then, routers/firewalling "NAT" routers (if you use one like a LinkSys or Netgear for instance).
C.) Lastly, power out/reboot/bounce cablemodem.
* WAIT UP TO 1 MINUTE BEFORE TURNING THEM ON AGAIN, SO THEY LOSE THEIR CONFIGURATIONS ONCE POWERED OFF/UNPLUGGED.
Then?
1.) Turn on cablemodem, wait for "link" light to show as powered on & sync'd w/ BSP... this varies by modem type, e.g.-> Top 4 lights on Motorola Surfboards etc.
2.) Then, turn on routers (if any), & wait for link light here...
3.) Turn on PC/laptop & logon.
* This is std. operating procedure step #1 for any cable internet support tech... & it fixes a good 90% of the hassles that go on (mainly, loss of sync between cablemodem & BSP, or sync of router to PC, or direct cablemodem to PC's & IP stack).
(The only REAL diff. afaik, is if they do it from cablemodem BSP side (reboot of modem), is that also clears the cablemodem's ARP cache)
Originally posted by jerry atrik:"cox establishes a trust when the modem is turned on so it must be rebooted to create a trust account with a new computer."
Some "FYI" for folks:
All cablemodem ISP's do that during the "DORA" (discover, offer, realize, acknowledge) cycle!
Via TFTP to your cablemodem (really a router if you think about it, that is how you configure many routers... either telnet, or tftp).
* They send a config file that writes into the EEPROM of the cablemodem, creating the private network (10.x.x.x) they operate privately on.
APK