PDA

View Full Version : What's this? (modem log)


DarkFX
24-03-2005, 16:25
After recent issues with my broadband ( here (http://www.cableforum.co.uk/board/showthread.php?t=25993) ) NTL came out and gave me the new ntl:250 modem.

Anyway, since getting it i've been suffering similar problems to before.... however now I can view the log... and this is what it's like:

First Time Last Time Counts Level ID Text
Thu Mar 24 16:02:33 2005 Thu Mar 24 16:02:33 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Thu Mar 24 13:12:05 2005 Thu Mar 24 13:12:05 2005 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Thu Mar 24 13:11:56 2005 Thu Mar 24 13:11:56 2005 5 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Thu Mar 24 13:11:43 2005 Thu Mar 24 13:11:43 2005 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Thu Mar 24 13:11:35 2005 Thu Mar 24 13:11:35 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Thu Mar 24 13:11:03 2005 Thu Mar 24 13:11:03 2005 21 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...


This is just a tiny chunk of the log that shows this going on a LOT, same thing over and over and every time it does happen my connection drops.

I've searched the forum and found similar messages but no clear answer on what causes them and the resolution (although i'm gonna guess the latter involves an engineer) - Can anyone shed some light on what's happening to my modem? NTL Tech decided they'd blame my router for it, so I took the router out of the equation and it continues...

Anyway... anyone know anything about this? :Yikes:

carlingman
25-03-2005, 02:38
After recent issues with my broadband ( here (http://www.cableforum.co.uk/board/showthread.php?t=25993) ) NTL came out and gave me the new ntl:250 modem.

Anyway, since getting it i've been suffering similar problems to before.... however now I can view the log... and this is what it's like:

First Time Last Time Counts Level ID Text
Thu Mar 24 16:02:33 2005 Thu Mar 24 16:02:33 2005 1 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Thu Mar 24 13:12:05 2005 Thu Mar 24 13:12:05 2005 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Thu Mar 24 13:11:56 2005 Thu Mar 24 13:11:56 2005 5 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...
Thu Mar 24 13:11:43 2005 Thu Mar 24 13:11:43 2005 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Thu Mar 24 13:11:35 2005 Thu Mar 24 13:11:35 2005 1 Critical(3) 82000400 Received Response to Broadcast Maintenance Request, But no Un...
Thu Mar 24 13:11:03 2005 Thu Mar 24 13:11:03 2005 21 Critical(3) 82000500 Started Unicast Maintenance Ranging - No Response received - ...


This is just a tiny chunk of the log that shows this going on a LOT, same thing over and over and every time it does happen my connection drops.

I've searched the forum and found similar messages but no clear answer on what causes them and the resolution (although i'm gonna guess the latter involves an engineer) - Can anyone shed some light on what's happening to my modem? NTL Tech decided they'd blame my router for it, so I took the router out of the equation and it continues...

Anyway... anyone know anything about this? :Yikes:

What are the power levels like if it shows that option as T3 errors usually relate to an upstream problem.

:D

DarkFX
25-03-2005, 14:44
What are the power levels like if it shows that option as T3 errors usually relate to an upstream problem.

:D

usually between 35-49dBmV - Though it does sometimes spike to 60... which I guess, is bad? :monkey:

Ignition
25-03-2005, 15:23
usually between 35-49dBmV - Though it does sometimes spike to 60... which I guess, is bad? :monkey:

Well the spiking isn't the issue the huge variation is. Definitely network or modem problems.

Tighten up those connectors, and if that doesn't help engineer time.

DarkFX
25-03-2005, 22:18
Thanks for the replies.

Cables/Connectors checked, absolutely fine but problems persist. Another engineer visit ahoy... such a pain in the backside, having to take time off work for an engineer visit :(