Looked in event log, is this bad news???

[Efour]

Cable Modem Event Log First Time Last Time Counts Level ID Text Thu May 25 00:30:24 2006 Thu May 25 00:30:24 2006 1 Warning(5) 68010300 DHCP RENEW WARNING - Field invalid in response Tue May 23 21:21:05 2006 Tue May 23 21:21:05 2006 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ... Time Not Established Time Not Established 10 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Time Not Established Time Not Established 1 Critical(3) 82000200 No Ranging Response received - T3 time-out Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response. Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out Time Not Established Time Not Established 2 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f... Time Not Established Time Not Established 82 Critical(3) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...

THe last entry in particular with 82 counts....... Is that something to be concerned about ? Its an NTL250 modem on a 10mbit service that runs pretty damn slowely. Has anyone done a walk through/explantion thread about all these error codes and stuff? If so could somone link me towards it.

I do hope this is a technical problem at least there is hope it will/can be fixed.

[EvilRix]

Try Google:"No Ranging Response received" as there are loads of pages discussing the kind of event log messages you are seeing.

[Stuart W]

TBH, unless you have a problem, it's best not to look in the logs.

Lots of people spend hours looking through anti-virus and firewall logs only to make themselves paranoid about all the failed atempts.
Same goes for the CM logs, they arn't there to tell you to fix / change something, they are just there as a log. Should anything go wrong, they can be called up to aid fault finding.