JeremyS

For the record..Cableone is an awful ISP.

I've contacted them many times about my problems, they always say it's a problem on my side. I just recently moved this past weekend, and had to get the same ISP. Before, while playing games, I would get a lot of ping spikes while playing games. It would spike from 30, to 200 or so, and sometimes just stay around 120+.

Now that I moved I was thinking "great, maybe I'll be able to play with no problems!" because all the time, I thought it had something to do with the cablelines in my old house or something. So NOW, my internet is wors e than it has ever been. In ventrilo ( VoIP program for people who dont know ) I'll ping around 40,000. I'll play Counter-Strike, and my ping will go up to 600, and just freeze for about 5 seconds, then go back to normal. Occasionally my internet will slow down to dialup speeds.

I just went to my cable modem status page, and to logs and saw this.

1970-01-01 03:32:40 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:00 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:24 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response
1970-01-01 00:02:12 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:00 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:06 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:00 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-02 09:25:21 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-02 09:25:09 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-02 09:25:09 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-02 09:24:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:24:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:24:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:23:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:23:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:22:51 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:22:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:22:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:22:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:22:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 09:22:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 09:22:26 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-02 09:22:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 15:52:22 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 15:39:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 08:37:13 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:00 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:06 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:00 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:27 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:16 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:10 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:00:10 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-07-01 17:37:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-01 17:36:11 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-01 17:36:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing


I'm not sure what that means, maybe someone here does? It doesn't look good though.

Heres the signal page

Downstream Value
Frequency 555000000 Hz Locked
Signal to Noise Ratio 39 dB
Power Level -5 dB
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream Value
Channel ID 1
Frequency 27568000 Hz Ranged
Power Level 54 dBmV

Which I think is normal. Downstream powerlevel can be anywhere between -8/+8.


I've reformatted my computer just a few days ago, somy question is finally - Does anyone know anyway I can fix these problems myself? Anything that would help would be great, thanks.

StanT

Framing errors and timing errors strongly point to a crappy circuit (technical term). The other errors could be other things, but are consistant with with circuit issues. Paste them into a note and ask your circuit provider (probably ISP) what they are going to do about it.

bendsley

I'm suspecting your modem is bad. I'm also assuming here that you have not "uncapped" your cable modem.

If your cable modem is in the same condition is was when you first purchased it, then its bad. What I would tell you to do is go buy another one from some place like Best Buy, take it home and try it. You may have to call the cable company and give them the new MAC address, depends on the cable provider. If it works, good deal, keep the modem. If it doesn't work, take the modem back to Best Buy with all the packaging and your receipt. They will take it back within 30 days whether the box is open or not. Trust me on that one.

__________________
"You hear the one about the fella who died, went to the pearly gates? St. Peter let him in. Sees a guy in a suit making a closing argument. Says, "Who's that?" St. Peter says, "Oh, that's God. Thinks he's Denny Crane."

cyrnel

Do you see the same problems with the cable modem as the only device connected? (television and all splitters removed)

Cable and DSL install issues are dependent on the systems used in a region so I'll avoid being the stupid armchair expert. If nobody else here can help, and even if they can, I'd post your question on http://www.broadbandreports.com/. Many current and former ISP reps help out on the forums and with more freedom than they enjoy when you call the official helpdesks.

__________________
There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195

cyrnel

StanT - Is cable framing directly dependent on signal level, such as would be affected by taps, or is it riding at another layer? How do those SNR & power levels look? Never worked with cable beyond plugging it in.

__________________
There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195

JeremyS

I believe it's a brand new modem. Before I moved I had a really old surfboard that I had gotten 3 years ago or something when I had first gotten cable, but when I moved I had to get a new modem, and I got the newest surfboard model. I guess since you guys say it has something to do with the circuit issuses, i'll ATTEMPT to call my ISP, and ask them about it, and hope they actually try and do something about it this time. Wish me luck !

BulletCatcher

Sorry to hear you are having problems with Cableone. I've been using their service for 5 years now and have no major complaints. Everytime I've had a problem they've been quick to resolve it and on one occasion they even sent a tech out to re-wire a direct connection to my modem at no cost. My only real complaint is their email servers. I often go through 1 -2 hour stretches where I'm unable to connect to retrieve email.

I live in a smaller city than some of their markets so maybe location has something to do with the level of service received.