Do I have a problem?

[UncleBooBoo]

Do I have a problem?

This is taken from my NTL 250 modems logs:

First Time Last Time Counts Level ID Text
Time Not Established Time Not Established 2 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Wed Nov 09 02:09:56 2005 Wed Nov 09 02:09:56 2005 5 Critical(3) 82000200 No Ranging Response received - T3 time-out
Wed Nov 09 02:09:49 2005 Wed Nov 09 02:09:49 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Wed Nov 09 01:47:24 2005 Wed Nov 09 01:47:24 2005 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Wed Nov 09 01:47:18 2005 Wed Nov 09 01:47:18 2005 5 Critical(3) 82000200 No Ranging Response received - T3 time-out
Wed Nov 09 01:47:12 2005 Wed Nov 09 01:47:12 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Wed Nov 09 01:41:29 2005 Wed Nov 09 01:41:29 2005 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Wed Nov 09 01:27:14 2005 Wed Nov 09 01:27:14 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Tue Nov 08 19:39:23 2005 Tue Nov 08 19:39:23 2005 5 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Sat Nov 05 15:44:06 2005 Sat Nov 05 15:44:06 2005 40 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Wed Nov 02 18:51:09 2005 Wed Nov 02 18:51:09 2005 25 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Time Not Established 4 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Mon Oct 10 13:41:22 2005 Mon Oct 10 13:41:22 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Mon Oct 10 13:38:49 2005 Mon Oct 10 13:38:49 2005 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Mon Oct 10 13:38:41 2005 Mon Oct 10 13:38:41 2005 2 Critical(3) 82000200 No Ranging Response received - T3 time-out
Mon Oct 10 13:38:34 2005 Mon Oct 10 13:38:34 2005 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Mon Oct 10 13:38:34 2005 Mon Oct 10 13:38:34 2005 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Mon Oct 10 13:38:22 2005 Mon Oct 10 13:38:22 2005 1 Critical(3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
Mon Oct 10 13:38:22 2005 Mon Oct 10 13:38:22 2005 17 Critical(3) 82000200 No Ranging Response received - T3 time-out
Mon Oct 10 13:36:48 2005 Mon Oct 10 13:36:48 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Mon Oct 10 12:35:44 2005 Mon Oct 10 12:35:44 2005 11 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Wed Oct 05 00:12:16 2005 Wed Oct 05 00:12:16 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Sat Oct 01 17:24:33 2005 Sat Oct 01 17:24:33 2005 2 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Thu Sep 22 15:49:33 2005 Thu Sep 22 15:49:33 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Sun Sep 18 19:11:34 2005 Sun Sep 18 19:11:34 2005 7 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Sat Sep 17 20:51:45 2005 Sat Sep 17 20:51:45 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Tue Sep 13 15:53:17 2005 Tue Sep 13 15:53:17 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Time Not Established 3 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Sun Sep 11 13:03:31 2005 Sun Sep 11 13:03:31 2005 1 Critical(3) 82000200 No Ranging Response received - T3 time-out
Wed Nov 09 01:40:54 2005 Wed Nov 09 01:40:54 2005 324063 Critical(3) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Sun Sep 11 03:40:02 2005 Sun Sep 11 03:40:02 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Download Failed (1)
Should I have this many errors?

[jrhnewark]

Is your service working OK? If it is, there's nothing to worry about. 'Error' doesn't always mean "oh, no, the connection won't work!!". :)

[fluff]

I also have similar messages to this in my 250 log but the service is running perfectly (apart from not running at 10mbit yet ;))

[UncleBooBoo]

yea it seems to be working ok.

I noticed from the day I had it installed that when I click on internet explorer it can be slow to load the initial page. it's not a speed issue on my pc as internet explorer loads quick I just get a white page and the loading simbol at the bottom of the page that indicates how much of that page is loaded is slow although my lights on my modem are flashing like mad. I have tried changing the home page same thing.

Speed tests indicat im running at 2mb which is good as thats what im paying for!

Never had that with adsl, however once internet explorer is up and running with the home page everything seems ok!

[jrhnewark]

Then I seriously wouldn't worry about it - they mean something to someone, somewhere. If it works, it works. :)

[swapshop1]

1. I'm guessing that the errors relate to the modem attempting to check in for an update - no response could mean the service is down - maybe because it doesn't need to be availiable 24h or maybe to revise the downloads......


Anyway from the first no answer you would expect multiple error due to persistant failed attempts until the service was resumed..

2. the Sync error is more important but this again means that the modem temperary lost tracking of the carrier signal. Electronics are far from perfect - thats why error protection is often employed, but anyway the modem did its job by re-aquiring the carrier and re sync'd. The log doesn't show successful attempts just failed attempts. This may have been for perhaps just 1/2 second - maybe un-noticable.