Ok I have been told constantly to ignore the Ambit modem logs but today I had an early start for an appointment leaving no time to check emails or I would have perhaps noticed the internet had been down. It had been down long enough to give me a different IP number leaving me with a problem with a ,htaccess file leaving me to contact a friend who is working on this with me to get me back in. When I checked the modems logs there is no way you can say ignore the amount on it for today.
Quote:
- Wed Nov 23 02:13:59 2005 Wed Nov 23 02:13:59 2005
1
Warning(5)
68010300
DHCP RENEW WARNING - Field invalid in response
- Wed Nov 23 01:39:12 2005 Wed Nov 23 01:39:12 2005
1
Critical(3)
68000300
DHCP WARNING - Non-critical field invalid in response.
- Wed Nov 23 01:38:33 2005 Wed Nov 23 01:38:33 2005
44
Critical(3)
84000100
SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
- Wed Nov 23 01:36:39 2005 Wed Nov 23 01:36:39 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:36:39 2005 Wed Nov 23 01:36:39 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:35:51 2005 Wed Nov 23 01:35:51 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:35:51 2005 Wed Nov 23 01:35:51 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:35:14 2005 Wed Nov 23 01:35:14 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:35:14 2005 Wed Nov 23 01:35:14 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:34:34 2005 Wed Nov 23 01:34:34 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:34:34 2005 Wed Nov 23 01:34:34 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:33:56 2005 Wed Nov 23 01:33:56 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:33:56 2005 Wed Nov 23 01:33:56 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:33:19 2005 Wed Nov 23 01:33:19 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:33:19 2005 Wed Nov 23 01:33:19 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:32:41 2005 Wed Nov 23 01:32:41 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:32:41 2005 Wed Nov 23 01:32:41 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:32:06 2005 Wed Nov 23 01:32:06 2005
1
Critical(3)
82000300
Init RANGING Critical Ranging Request Retries exhausted
- Wed Nov 23 01:32:06 2005 Wed Nov 23 01:32:06 2005
17
Critical(3)
82000200
No Ranging Response received - T3 time-out
- Wed Nov 23 01:31:25 2005 Wed Nov 23 01:31:25 2005
1
Critical(3)
82000400
Received Response to Broadcast Maintenance Request, But no Un...
- Wed Nov 23 01:39:00 2005 Wed Nov 23 01:39:00 2005
83
Critical(3)
84000200
SYNC Timing Synchronization failure - Failed to acquire FEC f...
|
With all those errors around the same time its no wonder my internet dropped then and continued to try and reconnect until 2.17am when it shut down.
Could someone from the NTL staff please explain these logs and what caused the outage today?