|
Re: Modem stopped responding 4 times tonight playing WoW
It was me who was telling him what the IP was not vice versa, I was only looking at the network adapter status while it was set to DHCP with the modem being plugged directly into the machine.
Basically at regular intervals the modem will stop working, the ready light will start flashing and if I check either my network adapter status or my router (when it's connected) I can see the modem's for some reason started using 192.168.100.10.
When it works it's using a conventional address beginning with 82 like you said.
// For the sake of science I'm going to post the event log of the modem, I obviously have no idea what significance any of it has.
First Time Last Time Priority Description
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) The s/w filename specified in the config file is the same as ...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) A software upgrade filename was specified in the config file.
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Authorized
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Registration complete!
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) We registered with a DOCSIS 1.1 config file!
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Received a REG-RSP message from the CMTS...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Sending a REG-REQ to the CMTS...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) CableModem SNMP configure complete
Sun Aug 22 14:33:39 2010 Sun Aug 22 14:33:39 2010 Information (7) IP init completed ok
Sun Aug 22 14:33:39 2010 Sun Aug 22 14:33:39 2010 Information (7) CableModem TFTP init ok
Time Not Established Time Not Established Information (7) CableModem DHCP client init ok
Time Not Established Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Sun Aug 22 12:35:45 2010 Sun Aug 22 12:35:45 2010 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Aug 22 12:34:29 2010 Sun Aug 22 12:34:29 2010 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sun Aug 22 12:34:26 2010 Sun Aug 22 12:34:26 2010 Critical (3) DHCP FAILED - Discover sent, no offer received
Sun Aug 22 12:34:12 2010 Sun Aug 22 12:34:12 2010 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Sun Aug 22 12:33:57 2010 Sun Aug 22 12:33:57 2010 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Sun Aug 22 12:32:35 2010 Sun Aug 22 12:32:35 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:29 2010 Sun Aug 22 12:32:29 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:27 2010 Sun Aug 22 12:32:27 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:22 2010 Sun Aug 22 12:32:22 2010 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Sun Aug 22 12:32:22 2010 Sun Aug 22 12:32:22 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:21 2010 Sun Aug 22 12:32:21 2010 Critical (3) No Ranging Response received - T3 time-out
|