Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Packet loss average about 5%
I've been getting some packet loss for a month or so, but it's been tolerable until the last week; today is especially horrible. I work at home and today it's so bad I can't keep an SSH connection open consistently. It comes and goes so I might be good for an hour and then get disconnected every 5 minutes for the next hour.
This happens on all devices regardless of wired or wireless. Rebooting computers and/or network gear does not help. Here is an example of my ping for today when it gets bad (http://s27.postimg.org/mjs95a9v7/ping.jpg) - image is too big to fit into post.
Modem is a Surfboard SB6120 and I noticed quite a few of the following logs:
No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:18:41;CMTS-MAC=00:1b:54:c9:87:75;CM-QOS=1.1;CM-VER=3.0;
The connection doesn't drop, ping response is good when it's working, and speed is fine. It's just some random packet loss that causes my SSH connections to drop (luckily I use screen so no loss of work, but it interrupts the flow of coding). It also affects Netflix a bit in that the words and mouth movements start to not match like I'm watching some 80s kung fu movie. Web sites only partially load. etc. I've been dealing with it by reconnecting my SSH or refreshing web pages, but it's now to the point where I can't work consistently.
I've done a ping out from my computers (the above image), but also back into my modem's public IP and see the same results. Is there anything that can be checked via tools Cox might have?
ChrisL
Former Moderator
•
0
0
foobar1538
New Contributor
•
Internal problem with the modem?
I was watching it closely yesterday since it was particularly bad between 10am and 12pm and every time it would stutter, I would see the following logs:
Sep 25 2014 01:02:25 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 25 2014 01:02:25 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Unfortunately my modem logs don't show every single instance. I watched them get combined when the same message happens within minutes of each other. Here is the full log shown:
Sep 25 2014 01:02:25 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 25 2014 01:02:25 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 25 2014 00:29:17 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 25 2014 00:29:17 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 23:05:49 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 23:05:48 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 22:33:40 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 22:33:40 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 22:17:58 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 22:17:58 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 20:49:01 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 20:49:01 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 20:45:32 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 20:45:32 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 20:29:20 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 20:29:20 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 20:14:54 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 18:49:40 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
Sep 24 2014 18:49:25 3-Critical R02.0 No Ranging Response received - T3 time-out;
Sep 24 2014 18:49:25 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;
It's been fine so far today since 5am anyway. I'm watching it to see if it happens around the same times each day as well. Unfortunately, with so few log entries it's hard to get a true feeling of the issue.
Yeah, unless you are pinging it all day you will likely not see the loss since it just happens and then disappears. It was bad yesterday for about 2 hours and then I didn't see the issue again for about 4 more hours, then it stuttered and was fine again. Between 10am and 12pm yesterday it averaged about 5% loss; if I did it across 24 hours I'd guess less, but it seems to happen more during the morning when I am working which is why I noticed it. If it happened between 1am and 4am I wouldn't care :)
There's some box outside my house that has a bunch of wires that has had the cover off for months now. Not sure if that's one of yours, but thought I'd mention it if it matters. It's maybe 3 feet tall and somewhat cylindrical.
0
0
Health_Edge
+5 more
Valued Contributor III
•
A T3 shouldn't make the modem non responsive to ping as far as I know. Only non responsive passing traffic over it. When you're getting packet loss to the modem, try to ping the gateway IP of your router. If you don't see packet loss there then there is a connection problem between modem and router.That would either be a ethernet issue or a port issue.
0
0
foobar1538
New Contributor
•
Was going well, with no problems all morning, but starting around 10:30am, I see my pings to the Internet timing out; usually clusters of them and then it goes back to normal. Sometimes it's enough to kick my SSH sessions offline. At the same time in the modem log I see the "No Ranging Response received - T3 time-out" errors. This was about the same time yesterday this started. It's been happening for 1.5 hours now and I've seen around 15 clusters of the timeouts - they happen every few minutes. Sometimes it's a single timeout (no big deal) and sometimes 10 timeouts (boots my SSH).
I set up 5 pings early this morning:
1. From desktop to router internal IP
2. From desktop to modem internal IP
3. From desktop to Internet (google.com)
4. From desktop to router's gateway public IP
5. From remote server to the router public IP
When the timeouts occur the pings affected are #3 and #4. The packet loss IN I saw the other day had to have been for some other reason since I've been watching this for a bit now and the remote ping never misses a beat even though the Internet pings time out.
Given those T3 timeouts happen at the same time, I can only think it's related. According to the T3 definition it causes the cable interface to reset and the modem to re-register. I'm not a network guru (I know enough to be dangerous) but it sounds like for that brief moment of re-registration, data going out is suspended, but I'm not certain as I don't know what they mean exactly by "cable interface reset". The pings to the internal IP of the cable modem are getting there with no interruption, but going past the modem times out.
The only hiccup I noticed on internal IP pings is sometimes, if the public pings timeout several times consecutively, the ping to the modem internal IP has a long round trip time (220+ ms) where normally it's <1ms.
Any advice given all these observations? Thanks.
0
0
foobar1538
New Contributor
•
Same packet loss today except it has been between 2pm and 4pm (going on now). Was fine all day until then. Here's a ping screenshot when it goes bad:
http://s13.postimg.org/ammph829z/ping2.jpg
Pretty much does that off and on for 2 hours each day so far. This is the first day it hasn't been between 10am and 12pm though.
0
0
foobar1538
New Contributor
•
I don't have cable TV so nothing to split to; goes from modem to wall only. Cable is solid - tight connections and no physical damage that I can see.
I also checked the cables in the box outside my garage and tightened any that were loose - 3 splitters in there but no idea what goes to what.
0
0
Health_Edge
+5 more
Valued Contributor III
•
As in 3 separate splitters? And you don't have cable service? I assume at some point you or someone else living there did if they put in that many outlets. I say get a technician out there to clean that up and make it direct from pole to modem, with ground of course.
0
0
foobar1538
New Contributor
•
We used to have cable service years ago when we first moved in back in 1999 (only owners of this house). We eventually moved to DirectTV, but haven't had that in at least the last 7 years.
There is:
5-1000 MHz 2 way splitter (SV-2G)
Holland Electronics DPD2 (5-2150MHz) (28 VDC, 2A Max) splitter
- This one has VHF/UHF and SAT inputs - DirectTV maybe?
and another one that is just chrome in color with no other labeling that I could see.
0
0
Health_Edge
+5 more
Valued Contributor III
•
All that should be replaced with a coupler with ground like this. Sounds like atleast 1 splitter and 1 amp you don't need. If its all in the house box, it should be Cox territory, as in they should fix it for free, but if you want to fix it yourself feel free. Just leave the other splitters and stuff in there in case you ever need to use it again, just make the Cox connection direct. I hope that should fix most of your problems.
0
0