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 issue
First the statistics and equipment. Ultimate Internet, Cox issued CG3000-RG Netgear gateway connected directly with ethernet to laptop and wirelessly to second laptop and Ps3.
Now the issue.
I've had issue after issue with my internet for all of 2013. Replaced the modem multiple times, replaced ethernet cable, the wall wiring was redone, and a few other things that I probably forgot as of the moment. My CURRENT issue is packet loss and ping response time. I've been experiencing intermittent packet loss when testing using the old school command technique as well as pingtest.net and www.hostmycalls.com tests. The latest round of tests I've run are via hostmycalls which tests the routing over a specific timeframe. It's showing packet loss on multiple hops as well as high delay. I have a general understanding of what this info means but I need to find out if this latest test pinpoints and exact cause of my issues. Something has been wrong for nearly the past year whether it's random modem resets, intermittent connection, slow connection or now this latest issue of packet loss and delay problems. Every tech that comes out has either A) not experienced the problem while they were here B) was not trained well enough to even know how to find the problem or C) all of the above. Links to the info from the hostmycalls tests are provided below. Any feedback would be great. Thanks
http://pinger.hostmycalls.com/netdet/netdetresults.html?Project=PRO000000520131223151000&PName=98.164.10.162
Current gateway statistics:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Current System Time:Fri Dec 27 13:50:43 2013 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
http://www.pingtest.net/result/90853807.png
http://www.pingtest.net/result/90853611.png
http://www.pingtest.net/result/90972000.png
ChrisL
Former Moderator
•
0
0
Sl4ck3r
New Contributor
•
do I have to do anything for this to take affect? Reboot modem etc?
0
0
Sl4ck3r
New Contributor
•
couldn't tell you if it's a direct result of the firmware upgrade push but now I'm getting 1/2 my speeds prior to the update. And I don't see how that upload speed can even be accurate.
http://www.speedtest.net/my-result/3191532387
http://www.speedtest.net/my-result/3191536142
http://www.speedtest.net/my-result/3191541703
I've rebooted the PC and modem and nothing resolves the issue. Haven't retested the packetloss issue as of yet.
0
0
Health_Edge
+5 more
Valued Contributor III
•
My guess is it's two problems. First, a peering issue between Cox and XO. Are you in AZ or West coast? I know within the last two weeks Cox has been working on the issue. It was causing alot of issues with Google services (Youtube, Google Voice, Google Play, etc). That would explain some of the packet loss and latency at Hop 12 of the provided tracert.
However, I think the main issue is the gateway itself. Notice that the highest packet loss comes at the last hop, which is the public IP of your gateway. I think you would be much better off trading in the gateway for a stand alone modem and investing in a good router. Especially if your trying to run business grade services through it. Thats like entering Nascar with a Go-cart.
Perhaps it would help to see the traffic from the computer out. Can you run a basic Tracert to cox.net from the computer hardwired to the gateway?
0
0
Sl4ck3r
New Contributor
•
I'm in Kansas. I've had this gateway for maybe a month issued to me brand new. I rent it after trying numerous modems with numerous different routers and experienced some kind of issue with all of them so this was the next thing I could try without actually buying more equipment that ends up laying around.
Tracert www.cox.net
Tracing route to www.cox.net [68.99.123.161]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.32.128.1
3 8 ms 8 ms 6 ms 70.183.70.193
4 15 ms 15 ms 16 ms 70.183.69.6
5 15 ms 15 ms 15 ms 70.183.71.16
6 88 ms 47 ms 47 ms dukedsrj01-ge-210.0.rd.at.cox.net [68.1.1.121]
7 48 ms 47 ms 47 ms 68.1.15.234
8 48 ms 47 ms 49 ms 68.99.123.4
9 48 ms 48 ms 46 ms ww2.cox.com [68.99.123.161]
Trace complete.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Looks like the tracert isn't picking up the problem. Try Pathping cox.net and pathping cr2.attga.ip.att.net. Here is one I did for comparison;
Tracing route to cr2.attga.ip.att.net [12.122.8.16]
over a maximum of 30 hops:
0 PC [192.168.1.136]
1 router.asus.com [192.168.1.1]
2 10.2.x.x
3 wwcksysc01-gex0103000.ri.ri.cox.net [68.9.8.13]
4 ip98-190-33-32.ri.ri.cox.net [98.190.33.32]
5 provdsrj01-ae3.0.rd.ri.cox.net [98.190.33.20]
6 68.1.5.157
7 xe-11-2-1.edge1.NewYork1.Level3.net [4.78.132.29]
8 ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC [192.168.1.136]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 10.2.x.x
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% wwcksysc01-gex0103000.ri.ri.cox.ne
t [68.9.8.13]
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% ip98-190-33-32.ri.ri.cox.net [98.1
90.33.32]
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% provdsrj01-ae3.0.rd.ri.cox.net [98
.190.33.20]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 68.1.5.157
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% xe-11-2-1.edge1.NewYork1.Level3.ne
t [4.78.132.29]
0/ 100 = 0% |
8 17ms 0/ 100 = 0% 0/ 100 = 0% ae-1-60.edge3.NewYork1.Level3.net
[4.69.155.17]
Trace complete.
0
0
Sl4ck3r
New Contributor
•
Pathping cox.net
Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:
0 Tyler-PC [192.168.0.3]
1 192.168.0.1
2 10.32.128.1
3 70.183.70.193
4 70.183.69.6
5 70.183.71.16
6 dukedsrj01-ge-210.0.rd.at.cox.net [68.1.1.121]
7 68.1.15.234
8 68.99.123.4
9 ww2.cox.com [68.99.123.161]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Tyler-PC [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.32.128.1
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% 70.183.70.193
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0% 70.183.69.6
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% 70.183.71.16
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% dukedsrj01-ge-210.0.rd.at.cox.net
[68.1.1.121]
0/ 100 = 0% |
7 47ms 0/ 100 = 0% 0/ 100 = 0% 68.1.15.234
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% 68.99.123.4
0/ 100 = 0% |
9 48ms 0/ 100 = 0% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
Trace complete.
pathping cr2.attga.ip.att.net
Tracing route to cr2.attga.ip.att.net [12.122.8.16]
over a maximum of 30 hops:
0 Tyler-PC [192.168.0.3]
1 192.168.0.1
2 10.32.128.1
3 70.183.70.189
4 70.183.66.74
5 70.183.69.6
6 70.183.71.16
7 207.86.210.9
8 207.88.15.50.ptr.us.xo.net [207.88.15.50]
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Tyler-PC [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% 10.32.128.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 70.183.70.189
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 70.183.66.74
0/ 100 = 0% |
5 7ms 0/ 100 = 0% 0/ 100 = 0% 70.183.69.6
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% 70.183.71.16
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% 207.86.210.9
0/ 100 = 0% |
8 26ms 0/ 100 = 0% 0/ 100 = 0% 207.88.15.50.ptr.us.xo.net [207.88
.15.50]
Trace complete.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Darn, doesn't look like that caught it either. Looking over the data again it looks like the packet loss is pretty small, and mostly occurs inside the XO backbone. If thats the case, there really isn't much you can do. You may be able to contact XO direct but they are unlikely to act if its a isolated issue.
Also, you might be able to route around the problem. Do you have any other offices you can VPN or Proxy through? You might also want to consider getting a Cox Business connection. Not only do they offer more dependable solutions (Fiber, Metro-E, etc) which can get you a dedicated route, but you would be able to work out a agreement with one of the Sales admin (Half sales, half tech) to see if maybe they can approach XO on your behalf.
0
0
EdwardH
Valued Contributor
•
0
0