View Single Post
Old 21-08-2010, 03:15   #1
TommyTomTom
Inactive
 
Join Date: Jun 2010
Posts: 19
TommyTomTom is an unknown quantity at this point
Modem stopped responding 4 times tonight playing WoW

Hi, I've been playing WoW tonight and my modem's stopped working 4 times. I've cycled the power to bring it back every time. When it happens I can't access 192.168.100.1. I live in the Staffordshire area (ST17), using an NTL: 250 modem. Here's my log just in case.

First Time Last Time Priority Description
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) The s/w filename specified in the config file is the same as ...
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) A software upgrade filename was specified in the config file.
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) Authorized
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Registration complete!
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) We registered with a DOCSIS 1.1 config file!
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Received a REG-RSP message from the CMTS...
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Sending a REG-REQ to the CMTS...
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) CableModem SNMP configure complete
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) IP init completed ok
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 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
Sat Aug 21 03:09:03 2010 Sat Aug 21 03:09:03 2010 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Sat Aug 21 03:09:03 2010 Sat Aug 21 03:09:03 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:53 2010 Sat Aug 21 03:08:53 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:52 2010 Sat Aug 21 03:08:52 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:49 2010 Sat Aug 21 03:08:49 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:44 2010 Sat Aug 21 03:08:44 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:37 2010 Sat Aug 21 03:08:37 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:28 2010 Sat Aug 21 03:08:28 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:16 2010 Sat Aug 21 03:08:16 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:10 2010 Sat Aug 21 03:08:10 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:01 2010 Sat Aug 21 03:08:01 2010 Critical (3) No Ranging Response received - T3 time-out
TommyTomTom is offline   Reply With Quote