Unconfigured Ad Widget

Collapse

cable issues ... help ....

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Iknownot
    replied
    To the OP, we had similar issues several times. Drops, outages for periods of time (30 mins to all night) and speed issues.

    One time it was the drop line from the pole to the house.

    One time, it was the whole cable line running through the backyard of the neighborhood. It had cracks and I had to wait a bit before the crew came out to replace it (other people had issues in the neighborhood).

    One time, it was some issue at a switch in the neighborhood. That one took the longest to fix. I was the only one experiencing issues for some reason and it would only happen around midnight. So they had to send around some guy to come check specifically then. Took forever for the cable co to get around to figuring it out.

    Generally, if you are having issues with the lines somewhere, you will be having issues with all 3 of the services. You'll get ghosting, static, or channel drops on the cable side. You'll lose phone service. And your internet will have outages or speed issues or synch issues.

    If you are experiencing all three, keep calling the cable co until they send someone out that actually knows what they are doing and will trouble shoot where the issue with the line.

    At one point, I was literally calling every day. Or every time I had an outage. They'll eventually get the crew out there that actually fixes stuff, rather than the tech that comes out and hooks up the sensor to your line an goes, "Er'Yup..."

    Leave a comment:


  • catmman
    replied
    They can throttle speeds on any modem

    Leave a comment:


  • GlockGuy
    replied
    And with 3.0 they can throttle down speeds.

    Originally posted by Darto
    Jeepers, had same problem, even worse than yours, this solved it completely:


    We tried a new router first, did not help.
    New modem did the trick.
    New Modem is DOCIS 3.0, old one DOCIS 2.0.

    Comcast had been phoning recommending a new modem because their new systems installed a few months ago slow down modems with old protocols to the point of loosing connection. I finally took their advice. Worked.

    Leave a comment:


  • Darto
    replied
    Jeepers, had same problem, even worse than yours, this solved it completely:


    We tried a new router first, did not help.
    New modem did the trick.
    New Modem is DOCIS 3.0, old one DOCIS 2.0.

    Comcast had been phoning recommending a new modem because their new systems installed a few months ago slow down modems with old protocols to the point of loosing connection. I finally took their advice. Worked.

    Leave a comment:


  • Satex
    replied
    How is your cable TV service, any issues?
    Probably worth checking with your neighbors to see if they are having issues.

    If the answer to both is no, then you have a bad modem.

    Leave a comment:


  • Jeepers
    replied
    Still arguing with charter,i have been running a monitor and Iam losing internet and phone 35-45 times a day for about 3-5 min at a time ....

    Have disconnected the modem fron the router and homeplugs and makes no difference, it is also dropping alot while everyine is asleep and zero useage .... thinkin it may be time to switch isp again

    Leave a comment:


  • Satex
    replied
    The link quality is pretty good, so it doesn't appear to be a bad coax.

    Leave a comment:


  • Rivers
    replied
    What happens when you connect your computer directly to the modem, taking your router totally out of the equation? Do you still have connection issues or is it working properly. That will help you to isolate the problem.

    A side note: when power cycling (restarting) devices, power on from the outside in. Power the modem up first and wait for its lights to stabilize. Then the router, same thing. If there are any switches or hubs, they get turned back on now. Last to get booted is the computer. Often it's best that all devices are powered off for at least a full minute to dump any memory caches.
    __________________
    Apple Certified Technical Consultant (ACTC)
    Last edited by Rivers; 03-01-2015, 7:58 AM.

    Leave a comment:


  • catmman
    replied
    Sorry I meant if the phone goes down unless you are using vonage or something.

    Leave a comment:


  • catmman
    replied
    Can't be your router if they want you to change the router channel. Having downstream channel bonding makes it pretty bulletproof. Interesting that it looks like one upstream atdma channel.

    Leave a comment:


  • catmman
    replied
    It is only using one upstream?

    Leave a comment:


  • Jeepers
    started a topic cable issues ... help ....

    cable issues ... help ....

    Ok so i called out charter once again for the constant internet and phone loss many many times a day, they came out replaced a bit of cable in the wall and wanted me to change my WiFi router channel(not sure why they want it changed) and since he left yesterday its been even worse

    here are some logs if they help
    Code:
     DOCSIS(CM) Events
    
    Date Time 	Event ID 	Event Level 	Description
    2/24/2015 13:17 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 13:18 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 14:54 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 14:54 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 14:55 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 15:53 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 15:53 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 15:54 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 17:59 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 17:59 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:00 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:06 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:06 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:07 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:35 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:35 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:36 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:40 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:40 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 18:40 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    Code:
    PacketCable(MTA) Events
    
    Date Time 	Event ID 	Description
    2/24/2015 13:19 	26 	MTA PROV: Successful!
    2/24/2015 13:19 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 14:54 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 14:56 	65517 	ConfigFile - BadParam
    2/24/2015 14:56 	16 	MTA TFTP: Successful
    2/24/2015 14:56 	26 	MTA PROV: Successful!
    2/24/2015 14:56 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 15:53 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 15:55 	65517 	ConfigFile - BadParam
    2/24/2015 15:55 	16 	MTA TFTP: Successful
    2/24/2015 15:55 	26 	MTA PROV: Successful!
    2/24/2015 15:55 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 17:59 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 18:01 	65517 	ConfigFile - BadParam
    2/24/2015 18:01 	16 	MTA TFTP: Successful
    2/24/2015 18:01 	26 	MTA PROV: Successful!
    2/24/2015 18:01 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 18:06 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 18:08 	65517 	ConfigFile - BadParam
    2/24/2015 18:08 	16 	MTA TFTP: Successful
    2/24/2015 18:08 	26 	MTA PROV: Successful!
    2/24/2015 18:08 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 18:35 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 18:37 	65517 	ConfigFile - BadParam
    2/24/2015 18:37 	16 	MTA TFTP: Successful
    2/24/2015 18:37 	26 	MTA PROV: Successful!
    2/24/2015 18:37 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    2/24/2015 18:40 	3 	Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
    2/24/2015 18:41 	65517 	ConfigFile - BadParam
    2/24/2015 18:41 	16 	MTA TFTP: Successful
    2/24/2015 18:41 	26 	MTA PROV: Successful!
    2/24/2015 18:41 	3 	Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
    Code:
     Hardware Information
    System: 	ARRIS DOCSIS 3.0 / PacketCable 1.5 Touchstone Telephony Modem
    HW_REV: 1
    VENDOR: Arris Interactive, L.L.C.
    BOOTR: 1.2.1.61
    SW_REV: 7.5.93
    MODEL: TM822A
    Serial Number: 	XXXXXXXX
    	
    Options: 	
     Firmware Build and Revisions
    Firmware Name:	TS070593_060313_MODEL_7_8
    Firmware Build Time: 	Mon Jun 3 11:26:20 EDT 2013
    Code:
     RF Parameters
    Downstream
    	DCID 	Freq 	Power 	SNR 	Modulation 	Octets 	Correcteds 	Uncorrectables
    Downstream 1	15	687.00 MHz	-5.83 dBmV	34.93 dB	256QAM	3711346	0	0
    Downstream 2	6	633.00 MHz	-5.67 dBmV	35.25 dB	256QAM	1782933	7	0
    Downstream 3	7	639.00 MHz	-5.93 dBmV	34.93 dB	256QAM	1865198	0	0
    Downstream 4	8	645.00 MHz	-5.67 dBmV	34.93 dB	256QAM	1755413	6	0
    Downstream 5	9	651.00 MHz	-6.13 dBmV	35.25 dB	256QAM	3676027	0	0
    Downstream 6	10	657.00 MHz	-6.01 dBmV	35.08 dB	256QAM	2936116	0	0
    Downstream 7	11	663.00 MHz	-5.95 dBmV	35.08 dB	256QAM	3446061	0	0
    Downstream 8	12	669.00 MHz	-5.61 dBmV	35.42 dB	256QAM	3816037	0	0
    Reset FEC Counters
    Upstream
    	UCID 	Freq 	Power 	Channel Type 	Symbol Rate 	Modulation
    Upstream 1	63	23.00 MHz	45.50 dBmV	DOCSIS2.0 (ATDMA)	5120 kSym/s	64QAM

    grrrr went out again while typing this, here is the log

    Code:
    2/24/2015 19:06 	82000300 	3 	Ranging Request Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 19:06 	82000600 	3 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
    2/24/2015 19:06 	82000200 	3 	No Ranging Response received - T3 time-out;CM-MAC=00:1d:d5:5e:41:aa;CMTS-MAC=00:01:5c:67:b6:4d;CM-QOS=1.1;CM-VER=3.0;
Working...
UA-8071174-1