- Comcast in PA Every Now and Then it Quits
- Posted by Harry Edwards on October 9th, 2004
I would say not much more than once a month the cable modem seems to
loose contact with the server. I included the logand the signal
strength from the cable modem's information page.
Is thre anything blaring that could be wrong?
Downstream Channel
The data shown in the table below provides information about the
signal coming from the
network to your cable modem.
Lock Status Locked Modulation QAM64
Channel ID 1 Symbol rate 5056941 sym/sec
Downstream Frequency 723000000 Hz Max Bit Rate 3300000 bps
Downstream Power -0.73 dBmV SNR 33 dB
Upstream Channel
The data shown in the table below provides information about the
signal being transmitted to
the network from your cable modem.
Lock Status Locked Modulation QPSK
Channel ID 2 Symbol rate 2560 ksym/sec
Upstream Frequency 30992000 Hz Max Bit Rate 256000 bps
Upstream Power 34.00 dBmV
Cable Modem
The data shown in the table below provides information about the
operational status of your
cable modem.
System Up Time 26Days 14hr:1min:31sec
Network Access Allowed
Cable Modem IP Address **.**.**.**
CPE Connections
The data shown in the table below provides information about the
customer premise equipment
(CPE) connected to your cable modem.
CPE MAC Address IP Address Connect To
PC-1 00:**:**:**:**:** **.**.**.** Ethernet
2004-10-09 09:21:49 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-08 20:23:47 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-08 20:09:52 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-08 20:02:49 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-08 02:42:51 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-07 20:38:36 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-07 16:39:26 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-07 05:54:16 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-07 03:10:06 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-07 01:48:43 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 19:57:42 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 19:42:19 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 18:03:53 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 18:03:52 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 12:37:41 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-06 00:44:40 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 19:15:57 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 19:14:17 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 17:20:16 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 01:46:06 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 01:04:48 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-05 00:01:14 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-04 20:19:23 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-04 13:53:17 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-04 04:29:29 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-03 21:11:17 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-03 20:49:16 information DHCP: Syslog server not specified
2004-10-03 20:15:58 information Auth Comp MAC addr:** ** ** ** ** **
2004-10-03 13:31:20 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-02 19:40:31 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-01 15:35:31 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-10-01 13:27:52 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-30 22:25:44 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-30 20:21:59 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-30 13:28:28 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 14:03:31 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 12:54:19 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 09:37:28 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 08:43:03 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 06:43:29 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 06:20:39 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 05:57:07 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 03:25:40 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 02:45:39 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-29 01:11:10 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-28 22:47:32 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-28 21:07:36 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-28 17:11:10 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-28 13:05:37 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2004-09-27 15:55:39 critical Started Unicast Maintenance Ranging - No
Response received - T3 time-out
- Posted by BigJIm on October 9th, 2004
yea I lose mine about once a week for a few minutes about 1 am.
guess they are doing maintenance, if you loose it more than me, you might
have a problem.
btw I live in western pa
"Harry Edwards" <Nobody@nowherebecauseihatespam.com> wrote in message
news:rr1gm0p4dsf49liuuhugifbpdt6kdb358u@4ax.com...
- Posted by Harry Edwards on October 9th, 2004
On Sat, 09 Oct 2004 16:32:10 GMT, "BigJIm" <Jim10277@hotmail.com>
wrote:
Its a lot less than once a week. Once every three weeks at the most.
I know once time when we changed our cable TV sybscription, we lost
cablt TV and internet for about 30 minutes while they reset the
billing, again at 1am.
It interrupted my p0rn downloading...
