how-to block ads
|
LPZ
@rcn.com
| reply to LPZ
Re: [Connectivity] Ongoing problems in the Lehigh Valley
Well, my problems continue. Modem is dropping offline, maybe twice daily. I suppose I could buy a new modem and see if that resolves the issue, but I'd prefer to know that this isn't an RCN problem before I do that.
Was hoping for some expert help, but I guess the RCN engineers no longer monitor this site. | |
lilhurricane
Crunchin' For Cures
Premium,Mod
join:2003-01-11
Purple Zone
clubs: 
 ·Comcast
Host:
TV over IP
Software
RCN
Inside Insight
Team Discovery
| said by LPZ :
Was hoping for some expert help, but I guess the RCN engineers no longer monitor this site.
They're still around
Our members here offer fairly expert help too
The majority of them are quite knowledgeable and their suggestions usually come from personal experience.
--
~Safe Hex~ Team Discovery ~ Project Hope ~ Like A Hurricane~ | |
alanisrox69
join:2005-03-29
LHV, PA | reply to LPZ
I'm betting 10 to 1 it's your modem.
-Derek- | |
LPZ
@rcn.com
| said by alanisrox69  :I'm betting 10 to 1 it's your modem. -Derek- I'm not into gambling! 
Can I access the modem online and have it run a self-diagnostic or something? It seems strange to me that a failing modem would behave in this way, but I have no expertise in such matters.
I wish I could rule out RCN-related issues---without buying a new modem and testing. | |
LPZ
@rcn.com
| OK, I've discovered how to obtain my modem's log file. Here is the portion that leads up to my having to reboot the modem early this morning. Can anyone explain what it means?
2009-06-28,04:50:52 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,04:50:55 No Ranging Response received - T3 time-out
2009-06-28,04:51:02 last event repeated 7 times, up to this date/time
2009-06-28,04:51:07 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:51:14 last event repeated 17 times, up to this date/time
2009-06-28,04:51:14 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,04:51:14 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:51:22 last event repeated 22 times, up to this date/time
2009-06-28,04:51:32 No UCD's Received - Timeout
2009-06-28,04:51:33 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:51:40 last event repeated 19 times, up to this date/time
2009-06-28,04:51:45 No Ranging Response received - T3 time-out
2009-06-28,04:51:54 last event repeated 11 times, up to this date/time
2009-06-28,04:52:02 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,04:52:18 last event repeated 6 times, up to this date/time
2009-06-28,04:52:19 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,04:52:22 No Ranging Response received - T3 time-out
2009-06-28,04:52:30 last event repeated 7 times, up to this date/time
2009-06-28,04:52:35 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:52:52 last event repeated 45 times, up to this date/time
2009-06-28,04:52:53 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,04:52:53 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:52:59 last event repeated 15 times, up to this date/time
2009-06-28,04:53:03 No Ranging Response received - T3 time-out
2009-06-28,04:53:05 last event repeated 3 times, up to this date/time
2009-06-28,04:53:09 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,04:53:27 last event repeated 7 times, up to this date/time
2009-06-28,04:53:30 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,04:53:34 No Ranging Response received - T3 time-out
2009-06-28,04:53:53 last event repeated 19 times, up to this date/time
2009-06-28,04:53:57 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:53:58 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,04:54:08 No UCD's Received - Timeout
2009-06-28,04:56:59 last event repeated 16 times, up to this date/time
2009-06-28,04:57:02 No Ranging Response received - T3 time-out
2009-06-28,04:57:05 last event repeated 7 times, up to this date/time
2009-06-28,04:57:09 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,04:57:29 last event repeated 9 times, up to this date/time
2009-06-28,04:57:33 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,04:57:36 No Ranging Response received - T3 time-out
2009-06-28,04:57:50 last event repeated 11 times, up to this date/time
2009-06-28,04:57:54 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:57:55 last event repeated 1 times, up to this date/time
2009-06-28,04:58:05 No UCD's Received - Timeout
2009-06-28,04:58:37 last event repeated 3 times, up to this date/time
2009-06-28,04:58:38 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:58:38 last event repeated 3 times, up to this date/time
2009-06-28,04:58:38 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,04:58:42 last event repeated 9 times, up to this date/time
2009-06-28,04:58:42 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:58:43 last event repeated 2 times, up to this date/time
2009-06-28,04:58:44 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,04:58:44 last event repeated 1 times, up to this date/time
2009-06-28,04:58:44 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,04:58:55 No UCD's Received - Timeout
2009-06-28,05:00:09 last event repeated 7 times, up to this date/time
2009-06-28,05:00:10 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:00:11 last event repeated 3 times, up to this date/time
2009-06-28,05:00:22 No UCD's Received - Timeout
2009-06-28,05:00:32 last event repeated 1 times, up to this date/time
2009-06-28,05:00:33 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:00:43 No UCD's Received - Timeout
2009-06-28,05:00:54 last event repeated 1 times, up to this date/time
2009-06-28,05:01:00 No Ranging Response received - T3 time-out
2009-06-28,05:01:12 last event repeated 11 times, up to this date/time
2009-06-28,05:01:14 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,05:01:21 last event repeated 3 times, up to this date/time
2009-06-28,05:01:34 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,05:01:37 No Ranging Response received - T3 time-out
2009-06-28,05:01:49 last event repeated 11 times, up to this date/time
2009-06-28,05:01:54 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:01:54 last event repeated 1 times, up to this date/time
2009-06-28,05:01:54 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:01:55 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:01:58 last event repeated 10 times, up to this date/time
2009-06-28,05:01:59 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:01:59 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:02:02 last event repeated 6 times, up to this date/time
2009-06-28,05:02:02 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:02:02 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:02:03 last event repeated 2 times, up to this date/time
2009-06-28,05:02:13 No UCD's Received - Timeout
2009-06-28,05:02:14 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:02:18 last event repeated 12 times, up to this date/time
2009-06-28,05:02:29 No UCD's Received - Timeout
2009-06-28,05:03:12 last event repeated 4 times, up to this date/time
2009-06-28,05:03:13 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:03:19 last event repeated 17 times, up to this date/time
2009-06-28,05:03:23 No Ranging Response received - T3 time-out
2009-06-28,05:03:31 last event repeated 5 times, up to this date/time
2009-06-28,05:03:36 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,05:03:39 last event repeated 2 times, up to this date/time
2009-06-28,05:03:53 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,05:03:55 No Ranging Response received - T3 time-out
2009-06-28,05:04:03 last event repeated 7 times, up to this date/time
2009-06-28,05:04:07 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:04:29 last event repeated 62 times, up to this date/time
2009-06-28,05:04:33 No Ranging Response received - T3 time-out
2009-06-28,05:04:42 last event repeated 7 times, up to this date/time
2009-06-28,05:04:43 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,05:05:01 last event repeated 5 times, up to this date/time
2009-06-28,05:05:05 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,05:05:09 No Ranging Response received - T3 time-out
2009-06-28,05:05:24 last event repeated 16 times, up to this date/time
2009-06-28,05:05:27 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:05:29 last event repeated 5 times, up to this date/time
2009-06-28,05:05:29 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:05:30 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:05:46 last event repeated 42 times, up to this date/time
2009-06-28,05:05:46 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:05:47 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:05:48 last event repeated 3 times, up to this date/time
2009-06-28,05:05:48 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:05:48 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:05:51 last event repeated 6 times, up to this date/time
2009-06-28,05:05:55 No Ranging Response received - T3 time-out
2009-06-28,05:06:03 last event repeated 7 times, up to this date/time
2009-06-28,05:06:04 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-06-28,05:06:15 last event repeated 2 times, up to this date/time
2009-06-28,05:06:23 Unicast Ranging Received Abort Response - Re- initializing MAC
2009-06-28,05:06:27 No Ranging Response received - T3 time-out
2009-06-28,05:06:34 last event repeated 7 times, up to this date/time
2009-06-28,05:06:39 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:06:41 last event repeated 5 times, up to this date/time
2009-06-28,05:06:41 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:06:48 last event repeated 19 times, up to this date/time
2009-06-28,05:06:49 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:06:49 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:06:50 last event repeated 6 times, up to this date/time
2009-06-28,05:06:50 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:06:51 last event repeated 3 times, up to this date/time
2009-06-28,05:06:52 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:06:53 last event repeated 5 times, up to this date/time
2009-06-28,05:06:54 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:06:55 last event repeated 3 times, up to this date/time
2009-06-28,05:06:55 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:06:56 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:06:56 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:06:58 last event repeated 6 times, up to this date/time
2009-06-28,05:06:58 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-06-28,05:07:00 last event repeated 3 times, up to this date/time
2009-06-28,05:07:00 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-06-28,05:07:01 last event repeated 1 times, up to this date/time | |
alanisrox69
join:2005-03-29
LHV, PA | The tuner on your current modem went. Get new modem and stop whining :P
-Derek-
--
CHECK YOUR FSLC TAXES!!! | |
LPZ
@rcn.com
| said by alanisrox69 :The tuner on your current modem went. Get new modem and stop whining :P -Derek- I don't believe I'm whining. I'm trying to determine where a problem lies.
Please explain how you reached your conclusion about the tuner. Is that indicated by the log file? Are there other possibilities? Thanks. | |
daveinpoway
Premium
join:2006-07-03
Poway, CA
| My, what a busy log you have! In contrast, here's the log on my Motorola SB5101 since June 15 (the second line is the final step of the initialization procedure; everything below the second line has been omitted, since it is all initialization reporting):
2009-06-29 03:28:29 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:02:44 3-Critical D003.0 DHCP WARNING - Non-critical
field invalid in response. | |
LPZ
@rcn.com
| said by daveinpoway :My, what a busy log you have! Lucky me! Any idea what it means? Thanks.
I've been Googling, but it's hard to process all the random bits of information (and misinformation). It seems that the problem is probably not the modem, but rather a line problem or an RCN issue further upstream. Guess I'll just have to call RCN and have them send someone here. | |
Coyotered
Rcn Rules
Premium
join:2002-06-02
Prospect Park, PA
1 edit | reply to LPZ
The modem you have is almost obsolete. RCN should swap it free of charge no questions asked.
You didn't mention what speed plan you have but I know for a fact the PCX2600 does not work on the higher speed plans.
Call and ask if they will swap it out for you.
--
c3-0.rdl-ubr1.trpr-rdl.pa.cable.rcn.com
Sorry meant to reply to the person with the PCX2600 | |
alanisrox69
join:2005-03-29
LHV, PA
·RCN CABLE
1 edit | said by Coyotered :The modem you have is almost obsolete. RCN should swap it free of charge no questions asked. You didn't mention what speed plan you have but I know for a fact the PCX2600 does not work on the higher speed plans. Call and ask if they will swap it out for you. He/she said he owns his modem, so RCN will not supply a new one.
I've told him/her multiple times to replace the modem and watch the problem disappear, but alas, he/she won't listen. What more can one do?
-Derek-
--
CHECK YOUR FSLC TAXES!!! | |
daveinpoway
Premium
join:2006-07-03
Poway, CA | reply to Coyotered
The Motorola SB5101 (which "LPZ" has) is still a current model, and is hardly obsolete. Perhaps you meant to reply to "john43", who has a Toshiba modem. | |
daveinpoway
Premium
join:2006-07-03
Poway, CA | reply to LPZ
Yes, having a tech (equipped with the proper measuring equipment) come out would be a very good course of action. | |
LPZ
@rcn.com
| reply to alanisrox69
said by alanisrox69 :I've told him/her multiple times to replace the modem and watch the problem disappear, but alas, he/she won't listen. What more can one do? -Derek- I listened (or, read), but I decided not to act on your opinion, which now appears to have been wrong.
The problem seems to be solved---no lost connections and an empty modem log file for the last twelve hours. Apparently my router was to blame, which still seems strange to me. But after rebooting the router, followed by rebooting the modem, my system seems fine again. Fingers crossed here, and apologies to RCN for suggesting the problem was theirs. | |
alanisrox69
join:2005-03-29
LHV, PA | Those loss of syncs in the modem log would have nothing to do with your router.
-Derek- | |
LPZ
@rcn.com
| said by alanisrox69 :Those loss of syncs in the modem log would have nothing to do with your router. -Derek- That's what I thought, and I think I may owe you an apology. The situation here is getting stranger and stranger. Here's the latest:
Modem went offline again, so I took the router out of the picture completely. After rebooting the modem, it went out again, and I was not able to get it back on line by rebooting. Called RCN and they're sending a truck on Thursday to check lines and modem.
Here's where it gets weird. After failing to get the modem back online, I decided to try the "broken" SB5120 I have in reserve. This one lost the ability to come online about three years ago, and RCN told me that it was shot. Well, that one came online just fine, and after re-provisioning I'm using it now.
So I either have two broken modems, two working modems, or something in between.
Anyway, apologies. Is it possible that both my modems are fine and that the failures to come online are RCN issues?
I'm totally lost right now. | |
alanisrox69
join:2005-03-29
LHV, PA
·RCN CABLE
| Usually when the tuner goes, it will stop working after it gets really heated up.
So it may have worked for a few hours just fine since it wasn't fully warmed up, but then once you started doing xfers and it was really working hard, then it started cutting out again.
Now, it may be an RCN issue, but if they don't find anything wrong, I think you'll get socked a $50 charge for truck roll fee, a new modem costs less than that.
-Derek-
--
CHECK YOUR FSLC TAXES!!! | |
LPZ
@rcn.com
|
While RCN was re-provisioning my resurrected modem (the one they insisted was dead several years ago, and which would not come online then) the representative mentioned that he saw a lot of packet loss, and he said that that issue is usually coming from outside the house.
As I said, I have no idea what the situation is right now. I have two modems, a "dead" SB5120 that is currently working just fine, and an SB5101 which now won't come online (actually the "receive" light comes on solid green, but the "send" light flashes). I'd be willing to think the 5101 is dead, but that's what RCN told me about the 5120.
I wish there were some easy way to determine if a modem is operational, without having to rely on RCN in any way. I really don't want to buy another modem, and it's hard to believe that they die so easily. | |
lilhurricane
Crunchin' For Cures
Premium,Mod
join:2003-01-11
Purple Zone
clubs: | said by LPZ :
...it's hard to believe that they die so easily.
I agree | |
LPZ
@rcn.com
| said by lilhurricane :said by LPZ :
...it's hard to believe that they die so easily.
I agree Well, my SB 5120 that was declared dead by RCN three years ago continues to function, seemingly well. The only data in the modem log is "No Ranging Response received - T3 time-out", although this entry is repeated very often.
I haven't tried to reconnect the SB 5101 that I have been using for several years, which wouldn't come online yesterday and which may or may not be dead.
My download speed dropped to about 2Mbs for a bit last evening, but is back to normal today. I've decided to go ahead with tomorrow's scheduled visit from RCN. Enough has been happening that I suspect there are issues that RCN needs to identify and resolve. | |
-
|
