Charter Cable Internet keeps cutting out...

kellyismetal · 21-07-2008, 05:36

Hi, this is my first post. I was wondering if anyone can interpret my log that I got from http://192.168.100.1/

This was from earlier in the day. Any suggestions or help would really be helpful. I just want to figure out whats wrong before I have to sit on the phone for 4 hours with tech support.

1 Time Not Established SUN JUL 20 03:11:43 2008 590 Critical (3) 82000200 No Ranging Response received - T3 time-out

2 SUN JUL 13 15:15:08 2008 SUN JUL 20 11:58:52 2008 278 Critical (3) 84000500 SYNC Timing Synchronization failure - Loss of Sync

3 Time Not Established Time Not Established 34 Critical (3) 85000100 No UCD's Received - Timeout

4 Time Not Established SUN JUL 20 13:04:05 2008 1573 Critical (3) 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out

5 SUN JUL 13 15:36:41 2008 SUN JUL 20 02:09:45 2008 23 Critical (3) 68000500 TFTP failed - request sent - No Response

6 SUN JUL 13 15:37:47 2008 SUN JUL 20 03:22:09 2008 23 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

7 SUN JUL 13 17:22:53 2008 SAT JUL 19 21:59:22 2008 164 Critical (3) 68000100 DHCP FAILED - Discover sent, no offer received

8 Time Not Established SAT JUL 19 21:54:09 2008 8 Critical (3) 68000200 DHCP FAILED - Request sent, No response

9 SUN JUL 13 18:20:02 2008 FRI JUL 18 22:57:50 2008 6 Critical (3) 68000700 TFTP Failed - OUT OF ORDER packets

10 SUN JUL 13 20:22:57 2008 Time Not Established 28 Critical (3) 82000100 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out

11 TUE JUL 15 06:05:39 2008 SAT JUL 19 21:13:53 2008 10 Critical (3) 73000200 REG RSP not received

12 Time Not Established SUN JUL 20 02:19:19 2008 2304 Notice (6) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

13 Time Not Established SUN JUL 20 02:19:17 2008 624 Notice (6) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing

14 Time Not Established SUN JUL 20 02:19:50 2008 564 Notice (6) 84000400 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period

15 Time Not Established Time Not Established 1 Notice (6) 2454454281 Link up--Ethernet interface

16 Time Not Established SUN JUL 20 03:22:32 2008 52 Error (4) 68000403 ToD request sent- No Response received

17 SAT JUL 19 23:00:54 2008 SAT JUL 19 23:00:54 2008 1 Notice (6) 2454454273 coldStart

18 SAT JUL 19 23:00:54 2008 SUN JUL 20 03:22:39 2008 20 Notice (6) 2454454282 Link up--Cable interface

19 SAT JUL 19 23:00:54 2008 SUN JUL 20 03:22:39 2008 20 Notice (6) 2454454279 Link down--USB interface

20 SAT JUL 19 23:11:13 2008 SUN JUL 20 03:22:09 2008 14 Notice (6) 2454454276 Link down--Cable interface

21 SAT JUL 19 23:11:37 2008 SUN JUL 20 03:22:28 2008 14 Notice (6) 2454454274 warmStart

Cobbydaler · 21-07-2008, 08:01

to the forum.

This is primarily a forum for UK residents, but the log you've posted may prompt help from one of the Virgin Media personnel who frequent it.

I've moved this to a more appropriate forum where you may get an answer to your problem.

21-07-2008, 20:21

Quote:

Originally Posted by kellyismetal

Hi, this is my first post. I was wondering if anyone can interpret my log that I got from http://192.168.100.1/

This was from earlier in the day. Any suggestions or help would really be helpful. I just want to figure out whats wrong before I have to sit on the phone for 4 hours with tech support.

1 Time Not Established SUN JUL 20 03:11:43 2008 590 Critical (3) 82000200 No Ranging Response received - T3 time-out

2 SUN JUL 13 15:15:08 2008 SUN JUL 20 11:58:52 2008 278 Critical (3) 84000500 SYNC Timing Synchronization failure - Loss of Sync

3 Time Not Established Time Not Established 34 Critical (3) 85000100 No UCD's Received - Timeout

4 Time Not Established SUN JUL 20 13:04:05 2008 1573 Critical (3) 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out

5 SUN JUL 13 15:36:41 2008 SUN JUL 20 02:09:45 2008 23 Critical (3) 68000500 TFTP failed - request sent - No Response

6 SUN JUL 13 15:37:47 2008 SUN JUL 20 03:22:09 2008 23 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

7 SUN JUL 13 17:22:53 2008 SAT JUL 19 21:59:22 2008 164 Critical (3) 68000100 DHCP FAILED - Discover sent, no offer received

8 Time Not Established SAT JUL 19 21:54:09 2008 8 Critical (3) 68000200 DHCP FAILED - Request sent, No response

9 SUN JUL 13 18:20:02 2008 FRI JUL 18 22:57:50 2008 6 Critical (3) 68000700 TFTP Failed - OUT OF ORDER packets

10 SUN JUL 13 20:22:57 2008 Time Not Established 28 Critical (3) 82000100 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out

11 TUE JUL 15 06:05:39 2008 SAT JUL 19 21:13:53 2008 10 Critical (3) 73000200 REG RSP not received

12 Time Not Established SUN JUL 20 02:19:19 2008 2304 Notice (6) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

13 Time Not Established SUN JUL 20 02:19:17 2008 624 Notice (6) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing

14 Time Not Established SUN JUL 20 02:19:50 2008 564 Notice (6) 84000400 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period

15 Time Not Established Time Not Established 1 Notice (6) 2454454281 Link up--Ethernet interface

16 Time Not Established SUN JUL 20 03:22:32 2008 52 Error (4) 68000403 ToD request sent- No Response received

17 SAT JUL 19 23:00:54 2008 SAT JUL 19 23:00:54 2008 1 Notice (6) 2454454273 coldStart

18 SAT JUL 19 23:00:54 2008 SUN JUL 20 03:22:39 2008 20 Notice (6) 2454454282 Link up--Cable interface

19 SAT JUL 19 23:00:54 2008 SUN JUL 20 03:22:39 2008 20 Notice (6) 2454454279 Link down--USB interface

20 SAT JUL 19 23:11:13 2008 SUN JUL 20 03:22:09 2008 14 Notice (6) 2454454276 Link down--Cable interface

21 SAT JUL 19 23:11:37 2008 SUN JUL 20 03:22:28 2008 14 Notice (6) 2454454274 warmStart

Be careful of reading modem logs, because what happens when you reboot your modem is that every single update for that modem is received at the same time giving you those worrying logs.

kellyismetal · 23-07-2008, 22:14

Thanks for the help.
I posted a more recent one on a different forum where I didn't reboot the modem for a few days and everyone says that it's time for a new one.

Cobbydaler · 23-07-2008, 22:20

Hope you get one & it sorts out the problem...