how-to block ads
|
shadowrose64
Premium
join:2003-11-02
Pittsburg, KS
 ·Cox HSI
4 edits | [KS] Over 1000ms At 4th Hop! Help, Please!
As stated in another thread, I've been a Cox HSI customer since March of this year. My trouble began in April, with random disconnects occurring six+ times a day. I called tech support, and spoke to someone in Wichita who said that while the signal looked great, there was packet loss of 60% or better occurring. He ordered a truck roll. During the first visit, the splitter was changed. This seemed to initially make some difference, but as soon as the service truck turned the corner (bet I'm not the only one with this luck!), the packet loss was back. I called tech support again, the next day the cable modem and cable outside the house was replaced. The poor guy did everything he could, troubleshooting every possible lead. Finally it was determined that they would just have to check things on down the line. I was encouraged to call back if I experienced problems again. Well, the problems with random disconnects and packet loss have fluctuated since, but are beginning to reoccur with more frequency. Here is some (hopefully) useful info.
Computers:
#1 Dell Dimension 8400, running Windows XP SP2, connected via internal wireless card
#2 Dell Inspiron 2650 (yes, old!), running Windows XP SP2, connected via wireless notebook card.
Modem: Surfboard SB 5120
Wireless Router: Linksys/WRT54GL
Modem Signal Levels via »192.168.100.1
Downstream:
Frequency: 651000000 Hz
Signal to Noise Ratio: 35 dB
QAM: QAM256
Network Access Control Object: ON
Power Level: -1 dBmV
Upstream:
Channel ID: 2
Frequency: 25150000 Hz
Ranging Service ID: 649
Symbol Rate: 2.560 Msym/s
Power Level: 34 dBmV
Here are traceroutes to www.cox.net and www.google.com:
Tracing route to www.cox.net [68.99.123.155]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 24 ms 24 ms 44 ms ip24-255-132-1.ks.ks.cox.net [24.255.132.1]
3 35 ms 31 ms 49 ms ip68-103-151-21.ks.ks.cox.net [68.103.151.21]
4 21 ms 452 ms 35 ms ip70-183-65-85.ks.ks.cox.net [70.183.65.85]
5 41 ms 39 ms 32 ms ip70-183-65-53.ks.ks.cox.net [70.183.65.53]
6 118 ms 34 ms 41 ms wichdsrj02gex070003.rd.ks.cox.net [70.183.71.1
7 60 ms 75 ms 51 ms wichbbrj01-so013.rd.ks.cox.net [68.1.1.190]
8 41 ms 147 ms 43 ms mtc3bbrj01-so010.rd.ok.cox.net [68.1.1.193]
9 67 ms 67 ms 53 ms mtc3bbrj02-ae0.rd.ok.cox.net [68.1.0.121]
10 82 ms 72 ms 76 ms dukebbrj01-so000.tc.at.cox.net [68.1.1.116]
11 170 ms 87 ms 77 ms dukedsrj01-ge610.tc.at.cox.net [68.1.1.121]
12 90 ms 78 ms 80 ms dukedsrj02-so010.tc.at.cox.net [68.1.15.37]
13 78 ms 67 ms 76 ms 68.1.15.238
14 84 ms 107 ms 74 ms 68.99.123.13
15 304 ms 122 ms 132 ms www.cox.net [68.99.123.155]
Trace complete.
Tracing route to www.l.google.com [72.14.203.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 73 ms 35 ms 28 ms ip24-255-132-1.ks.ks.cox.net [24.255.132.1]
3 35 ms 31 ms 54 ms ip68-103-151-21.ks.ks.cox.net [68.103.151.21]
4 43 ms 29 ms 40 ms ip70-183-65-85.ks.ks.cox.net [70.183.65.85]
5 42 ms 36 ms 43 ms ip70-183-65-53.ks.ks.cox.net [70.183.65.53]
6 65 ms 84 ms 32 ms wichdsrj02gex070004.rd.ks.cox.net [70.183.71.33]
7 35 ms 84 ms 56 ms wichbbrc02-pos0101.rd.ks.cox.net [68.1.1.182]
8 92 ms 129 ms 63 ms mtc1bbrc01-pos0200.rd.om.cox.net [68.1.1.177]
9 48 ms 43 ms 43 ms mtc1bbrc02-pos0100.rd.om.cox.net [68.1.0.123]
10 83 ms 66 ms 64 ms langbbrj01.r2.la.cox.net [68.1.0.225]
11 76 ms 68 ms 69 ms 72.14.197.54
12 73 ms 77 ms 69 ms 66.249.95.253
13 63 ms 70 ms 68 ms 72.14.238.89
14 75 ms 73 ms 74 ms 64.233.175.94
15 59 ms 72 ms 67 ms 72.14.203.104
Trace complete.
Last but hopefully not least, I am including a 24 hour ping plot. I'm frustrated, but am very willing to help troubleshoot this problem. If any other info is needed, please don't hesitate to ask.
Note: This morning am seeing pings over 600 ms from second hop on. See second ping plot.
Here are the results of a couple more tracerts. As you can see, things are not going well at all.
Tracing route to www.l.google.com [64.233.167.147]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 105 ms 54 ms 440 ms ip24-255-132-1.ks.ks.cox.net [24.255.132.1]
3 120 ms 41 ms 375 ms ip68-103-151-21.ks.ks.cox.net [68.103.151.21]
4 241 ms 1116 ms 398 ms ip70-183-65-85.ks.ks.cox.net [70.183.65.85]
5 372 ms 629 ms 84 ms ip70-183-65-53.ks.ks.cox.net [70.183.65.53]
6 705 ms 34 ms 125 ms wichdsrj02gex070004.rd.ks.cox.net [70.183.71.33
7 229 ms 112 ms 48 ms wichbbrc02-pos0101.rd.ks.cox.net [68.1.1.182]
8 141 ms 904 ms 148 ms mtc1bbrc01-pos0200.rd.om.cox.net [68.1.1.177]
9 92 ms 50 ms 78 ms mtc1bbrc02-pos0100.rd.om.cox.net [68.1.0.123]
10 108 ms 55 ms 219 ms mtc1bbrc02-pos0300.rd.om.cox.net [68.1.0.225]
11 77 ms 192 ms 682 ms 72.14.197.54
Tracing route to www.cox.net [68.99.123.155]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 71 ms 43 ms 72 ms ip24-255-132-1.ks.ks.cox.net [24.255.132.1]
3 347 ms 18 ms 103 ms ip68-103-151-21.ks.ks.cox.net [68.103.151.21]
4 1936 ms 20 ms 84 ms ip70-183-65-85.ks.ks.cox.net [70.183.65.85]
5 161 ms 416 ms 141 ms ip70-183-65-53.ks.ks.cox.net [70.183.65.53]
6 430 ms 144 ms 278 ms wichdsrj02gex070003.rd.ks.cox.net [70.183.71.11]
7 33 ms 277 ms 75 ms wichbbrj01-so013.rd.ks.cox.net [68.1.1.190]
8 191 ms 734 ms 86 ms mtc3bbrj01-so010.rd.ok.cox.net [68.1.1.193]
9 72 ms 49 ms 140 ms mtc3bbrj02-ae0.rd.ok.cox.net [68.1.0.121]
10 1008 ms 124 ms 199 ms dukebbrj01-so000.tc.at.cox.net [68.1.1.116]
11 229 ms 322 ms 91 ms dukedsrj01-ge610.tc.at.cox.net [68.1.1.121]
12 122 ms 127 ms 125 ms dukedsrj02-so010.tc.at.cox.net [68.1.15.37]
13 586 ms 111 ms 561 ms 68.1.15.238
14 200 ms 2721 ms 783 ms 68.99.123.13
15 117 ms 182 ms 192 ms www.cox.net [68.99.123.155]
Trace complete.
Ideas? Speculations? Lucky guesses? At this point I'm sure open to suggestions. | |
Tsume
join:2004-02-23
Johnson City, TN | I had this same exact problem, and it was a bad modem. The modem that went bad was different though, a Linksys BEFCMU10 v2. | |
robertfl
Premium
join:2005-10-10
Mary Esther, FL
 ·Cox VOIP
| reply to shadowrose64
Try pinging your modem and see what happens if the pings go beyond 1ms then thats your problem.
Also, it woudln't hurt to private message level 2
»/useremail/u/621911
give him your modem's mac address and a description of the problem (give him this thread)
-Rob | |
shadowrose64
Premium
join:2003-11-02
Pittsburg, KS
·Cox HSI
| reply to Tsume
Thanks for the responses.  I was beginning to feel lost in the wilderness, lol! Well, Tsume, we've replaced the modem three times, and the router twice with no real difference when we've switched them out. Also gone directly to the modem by hooking the desktop via usb (yes, I have updated usb files for the surfboard, one of the first things I checked), and then tried a direct hookup to the modem via ethernet cable. Ping times/packet loss/disconnects were the same. Robert, pinging the modem results in 1ms, every time. Pinging the router when adding it into the mix produces the same result. Monday morning I'll run up to my local Cox office and see if a face to face meeting with the good folks there, plots and stats in hand, will result in any new ideas. I hate bugging folks close to the weekend. Living in a college town (Pittsburg State University, go Gorillas, woot! ) I'd think the additional service saturation would have a small part to play. Odd thing though, the troubles occur no matter how many students are in town. *shrugs* I do appreciate the responses, guys. Have a good weekend. | |
|
