New Contributor II
•
4 Messages
Roanoke Internet issues?
Wall o' text incoming.
Started having some issues on Oct 14th. Lost all connectivity to anything not on my LAN. Tracert to a server showed the following:
Tracing route to http01.rev.net [209.170.177.145]
over a maximum of 30 hops:
1 6 ms 10 ms 7 ms 10.64.96.1
2 6 ms 7 ms 8 ms 98.172.172.186
3 19 ms 15 ms 18 ms ashbbprj01-ae3.0.rd.as.cox.net [68.1.0.214]
4 * * * Request timed out
5-9 all time out as well.
Normally these all plot fine. Same issue regardless of what I ping. Always dies after ashbbprj01*.cox. Rebooted router, same issue. Rebooted modem, same issue. Started working again afer 20-30 minutes.
Over the next 5 days, random packet loss, full on connection drops and connectivity losses have sporadically popped up. Sometimes I'm lucky enough to catch them and be able to run a trace that shows me something similar, other times I am not able to catch it in time. Once it even acted as if I had no WAN IP on my router. Had to reboot the router to regain connectivity. ( D-Link DIR 880L ). Modem is a Cisco DPC3010.
Modem shows the following:
| About | ||||||||||||||||||||
|
| Cable Modem State | ||||||||||||||
|
| Downstream Channels | |||||||||||||||||||||||||||||
|
| Upstream Channels | ||||||||||||
|
Now, I am aware of the fact that 95% of the time, everything works fine so when someone from Cox looks at the modem from their end, all appears to be well. However, something is up. I've been using Cox HSI since '97 and this has been the most problematic time period yet. ( Which is still pretty good ). Speeds are great at ~60Mbps down/ 8-10 up.
I'm only seeing about 1% packet loss overall if I let a ping run all night, but that can be enough to trip up my work VPN at times. I seem to notice that my upstream power levels are higher when I see packet loss. Normally they are around 46-47dBmv, but at times they spike to the values above.
Bad modem? Outside wiring issue? No splitters on modem line aside from the one outside that comes off the pedestal.
Accepted Solution
ENCOMCEO
New Contributor II
•
4 Messages
This is the result of a tracert to Google's public DNS servers while bypassing the D-Link router. Note the first two hops stay the same as when I am connected to the D-Link, so this shows the router is doing anything funky with those hops.
>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 7 ms 6 ms 7 ms 10.64.96.1
2 11 ms 7 ms 6 ms 98.172.172.184
3 17 ms 17 ms 17 ms ashbbprj01-ae2.rd.as.cox.net [68.1.0.242]
4 19 ms 16 ms 15 ms 68.105.30.118
5 18 ms 20 ms 18 ms 209.85.252.46
6 20 ms 17 ms 16 ms 72.14.236.148
7 24 ms 24 ms 24 ms 64.233.174.9
8 32 ms 32 ms 34 ms 216.239.48.40
9 31 ms 30 ms 30 ms 209.85.253.90
10 * * * Request timed out.
11 31 ms 31 ms 30 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
I say "fried" as in my old RT-N66U simply would not power on one morning. Smelled a little cooked. I have everything running through an APC Back-UPS ES 750. Could have been a death from natural causes, or it could have gotten hit. No way for me to tell. We had a TON of rain in the area a few weeks back, and the issues seemed to start then. Our pedestal by the road does not close completely, either. It's on of these : http://stopthecap.com/wp-content/uploads/2012/09/pedestal.jpg The cap is loose and has been for years. There is a 3 inch gap at the bottom.
Having said all of this, I've not had any issues that I know of for 24 hours, but we'll see how that lasts. Thanks to everyone for the replies. I'll keep an eye on it and likely call a tech out if it crops up again.
0
0
ENCOMCEO
New Contributor II
•
4 Messages
Not even a few minutes later, levels look like this:
0
0
ChrisL
Former Moderator
•
7.1K Messages
From this end everything appears to be as it should with the modem. Can you try testing with a direct connection to the modem and see if there is any change?
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Looks like a bad tap, or something in the area. But just in case, any splitters in the room or house that you can bypass?
Also, are you using a 10.x.x.x IP scheme for your network? Or was your Dlink bypassed at the time of the trace? If your connected to your Dlink, then it's not normal to have a 7-9ms from PC to router. 1+ to bypass Dlink and test again.
Last, are you aware that http://http01.rev.net/ looks down? When I go there I get the message:
"If you are the website/domain holder and expected to see your website, there may be a billing issue"
0
0
ENCOMCEO
New Contributor II
•
4 Messages
I am not using a 10.x scheme. Some digging tells me that 10.64.96.1 is a CMTS = Cable MODEM Termination System (also called the UBR by Cisco).
I'll bypass the Dlink tonight and see what I get. I did get a reply from Cox Support on Twitter that my modem showed some T3 errors and high upstream power values last night . Could be a modem or line issue at home I suppose. Starting to wonder if my modem is going out. The previous router got fried 3 weeks back, wondering if the modem took a hit as well. I already had to replace the patch cable from the router to the modem.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Yup. More specifically its the HFC(Hybrid Fiber Coaxial) interface of the CMTS. I was just making sure because hop 2 was also a private IP scheme, so making sure THAT wasn't the CMTS.
Maybe, but my gut still thinks its a bad tap. The tap is the device on the pole that connects the cable that goes from pole to pole to the cable that goes to your house. Here is a picture of some of what may be on your pole, including the tap. It doesn't sound like a modem issue.
Can you define "fried"? I don't think it's a modem issue, but if you had electrical problems severe enough to damage your router, then it's quite possible that issue damaged Cox equipment out on the poles too.
0
0
Becky
Moderator
•
4.3K Messages
Please keep us posted! We're happy to set up a service call if needed.
0
0