site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
5502
Share Topic
Posting?
Post a:
Post a:
Links: ·800RINGRCN ·RCN FAQ ·Monitors ·RCN Portal
page: 1 · 2 · 3
AuthorAll Replies


LPZ

@rcn.com

[Connectivity] Ongoing problems in the Lehigh Valley

After many month of sustained excellent service, I have been experiencing persistent connectivity issues for several weeks. I am posting here in the hope that an RCN engineer will investigate and perhaps offer suggestions. I have called 1-800-RING-RCN several times, and have not been satisfied. The representatives to whom I have spoken have almost immediately suggested that my cable modem is to blame, which seems unlikely to me.

My modem (a Motorola SB 5101 that I own) has been dropping off-line almost daily, sometimes several times per day. Typically the POWER and RECEIVE lights on the modem remain solid green, while the SEND light becomes flashing green or goes off. Almost always a modem reboot temporarily restores service.

Even when I have service, my upload speeds have been variable and often very slow. See below, for example. Download speeds seem fine.
Web page loading has been inconsistent, often with long pauses.

Perhaps someone from RCN will read this and look into this matter, which is becoming quite annoying. Thanks.

+++++++++++++++++++++++++++++++++++++++++

Your Modem Mac 00:19:5e:f5:7a:7e Your IP
Forward Frequency 735000000 Return Frequency 24816000
Forward Modulation qam256(4) Modem TX Power 45 dBmV
Foward Signal to Noise 35.4 dB Downstream Ratelimit 11000000
Forward Power Level -7.8 dBmV Upstream Ratelimit 800000

Download #1
------------------------------------------------------------------
File size transferred : 3.02 MB (3167484 bytes)
Total time taken : 2.58 seconds (2581 milliseconds)
Throughput : 1227.0 KB/sec [Kilobyte-per-second]
= 1.23 MB/sec [Megabyte-per-second]
= 9816.0 Kbps [Kilobit-per-second]
= 9.82 Mbps [Megabit-per-second]

Upload #1
------------------------------------------------------------------
File size transferred : 3.02 MB (3167484 bytes)
Total time taken : 66.66 seconds (66658 milliseconds)
Throughput : 47.0 KB/sec [Kilobyte-per-second]
= 0.05 MB/sec [Megabyte-per-second]
= 376.0 Kbps [Kilobit-per-second]
= 0.38 Mbps [Megabit-per-second]


shadyman777
The Hero of Time
Premium
join:2009-03-02
Allentown, PA
Reviews:
·RCN CABLE

I've noticed the problems are ongoing to. The problem is, whenever a tech takes a look at the modem, the modem is working properly. I don't think it has anything to do directly with the gateway to the internet. Since i've switched my DNS servers to two opendns addresses, the issue has gone away. I was getting VERY long pauses with service. I feel the DNS cache is to high on their DNS servers and they need to be flushed, but hey, what do i know? I only have a degree in Computer Networking. The techs in the NOC don't believe me when I was able to get a hold of them about the issue. So I just switched to an opendns address... and bam, no issues with websites.


wbertram
Premium
join:2005-08-19
Allentown, PA

3 edits

reply to LPZ
I have had similar problems where the modem stops working; you cannot access it with the browser (192.168.0.1), the 4 green lights are solid green, and the orange light is also solid orange (not blinking, as in normal operation).

The problem started to be seen about the time I reconfigured the equipment closet so that the modem and the wireless router were physically very close together. I had read somewhere that if a modem and router are too close to each other, they may interfere with each other.

Several days ago I moved the two units so that they are a little over a foot apart. I have not had the problem since. Did that solve the problem? Time will tell. But you may want to look into it.



LPZ

@rcn.com

reply to shadyman777
I have been using OpenDNS for a long time already. The issue I reported seems to have nothing to do with DNSs.


quattrog

join:2009-03-20
Northampton, PA

1 edit

reply to LPZ
Well, all I can say is that each time I had a similar issue, it really was the modem. My first modem lasted a few years. It was a Toshiba model. When it started to go, it would run very very slow, and drop many times. I would power cycle and it would work for a short time, but then back to the slow behavior. RCN then gave me a used Moto modem. That one was a problem from day one. They then gave me a brand new Scientific Atlantic modem. That's been rock solid since. When the modems go, it's not like they just power off and that's it. If you are renting the modem from RCN, then just request a new, and I mean NEW, modem.


john43

join:2009-05-27

2 edits

reply to LPZ
Having this problem here in the LV also, gonna go with the suggestion of getting a new modem. My connection is very slow and many pages won't load all the way. It happens periodically- the connection would be fine for 12-24 hours, and then afterwards another 12-24 hours of slowness. No matter how many times I powercycle it, the problem doesn't go away.

I'm currently using the Toshiba PCX2600 supplied by RCN, had it since 2004.

Can I just buy a new modem myself and return my old modem to RCN?

I think I will get the D-Link DCM-202 modem, which was recommended by another post.



LPZ

@rcn.com

reply to LPZ
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
kudos:51
Reviews:
·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
kudos:2

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

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
kudos:2

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
kudos:2

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.
page: 1 · 2 · 3

Saturday, 02-Jun 23:58:22 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics