For the past few weeks my net connection has been up and down a lot. Had a few engineers out to look at it, but they usually replace a connector and/or tighten some bits and then say that was the problem. Its a bit annoying going through the tech support because its so time consuming and because I have a set top box and a cable modem they usually ignore the problems im having and instead they try to update my account details (been through the same thing 7 or 8 times so far).
im not sure it will help when the cable is down, im using an ntl 200 cable modem, it has the ENET LED on solid and the D/S LED flashing, all others are out.
i can access the modem through 192.168.100.1 and here are some other bits of info.
Quote:
Downstream Status
Downstream Lock : Not Locked
Downstream Frequency : 818750000 Hz
Downstream Modulation : unknown
Downstream Interleave Depth : ???
Downstream Receive Power Level : 0.3 dBmV
Downstream SNR : 0.0 dB
|
Quote:
Upstream Status
Upstream Channel ID : 0
Upstream Transmit Power Level : 52.50 dBmV
Upstream Symbol Rate : 0 Ksym/sec
Upstream Frequency : 0 Hz
Upstream Mini-Slot Size : 0
|
Quote:
Event Log
Index First Time Last Time Counts Level ID Text
1 Time Not Established MON APR 17 16:31:44 2006 45095 Critical (3) 82000200 No Ranging Response received - T3 time-out
2 WED SEP 15 04:22:43 2004 TUE APR 18 11:01:18 2006 100 Critical (3) 84000500 SYNC Timing Synchronization failure - Loss of Sync
3 WED SEP 15 04:23:08 2004 TUE APR 18 11:01:29 2006 123 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
4 WED SEP 15 04:23:19 2004 TUE APR 18 11:01:40 2006 47 Critical (3) 85000100 No UCD's Received - Timeout
5 WED SEP 15 04:45:49 2004 TUE APR 18 00:53:16 2006 4044 Critical (3) 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out
6 WED SEP 15 05:20:17 2004 SUN APR 16 18:30:56 2006 106 Critical (3) 68000100 DHCP FAILED - Discover sent, no offer received
7 Time Not Established Time Not Established 463 Critical (3) 82000300 Init RANGING Critical Ranging Request Retries exhausted
8 WED SEP 15 08:05:51 2004 Time Not Established 96 Critical (3) 82000100 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
9 Time Not Established MON APR 17 16:31:49 2006 509 Critical (3) 68000300 DHCP WARNING - Non-critical field invalid in response.
10 FRI OCT 22 13:36:22 2004 MON APR 17 16:28:49 2006 15467 Critical (3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
11 Time Not Established MON APR 10 20:48:58 2006 5 Critical (3) 68000200 DHCP FAILED - Request sent, No response
12 Time Not Established WED JAN 25 05:07:27 2006 5 Critical (3) 68000500 TFTP failed - request sent - No Response
13 Time Not Established Time Not Established 1 Notice (6) 2454454281 Link up--Ethernet interface
14 Time Not Established TUE APR 18 12:19:54 2006 51736 Notice (6) 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
15 Time Not Established TUE APR 18 12:15:52 2006 319 Notice (6) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing
16 SUN APR 16 19:14:02 2006 SUN APR 16 19:14:02 2006 1 Notice (6) 2454454273 coldStart
17 SUN APR 16 19:14:02 2006 MON APR 17 16:31:52 2006 5 Notice (6) 2454454282 Link up--Cable interface
18 SUN APR 16 19:14:02 2006 MON APR 17 16:31:52 2006 5 Notice (6) 2454454279 Link down--USB interface
19 SUN APR 16 23:39:11 2006 TUE APR 18 10:41:04 2006 3 Notice (6) 2454454287 SNMP authentication-Failure
20 MON APR 17 16:25:12 2006 TUE APR 18 11:01:30 2006 3 Notice (6) 2454454276 Link down--Cable interface
21 MON APR 17 16:26:12 2006 MON APR 17 16:31:49 2006 2 Notice (6) 2454454274 warmStart
|
does anything here indicate where the problem might be? The engineers never seem to check the log, they just do a signal strength check.
Thanks for any advice, ill give more info as well if needed.