Talk > Rants, Raves, and Praise > COX HSI problems, NOVA Only pease,

reply to COXnightmare

Re: COX HSI problems, NOVA Only pease,

reply to COXnightmare
BTW, this is at 1:30 in the morning, so this eliminates quite a few possible causes for this latency issue.

reply to COXnightmare
1 * * * Request timed out.
2 * 19 ms 11 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 23 ms 13 ms 24 ms ip68-100-0-149.nv.nv.cox.net [68.100.0.149]
4 75 ms 12 ms 35 ms 68.1.1.6
5 21 ms 65 ms 18 ms 68.1.1.17
6 27 ms 18 ms 37 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
7 52 ms 48 ms 70 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
8 332 ms 357 ms 376 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
69.5]
9 338 ms 459 ms 406 ms ge-6-2-0.mp2.Atlanta1.level3.net [64.159.3.77]
10 * * * Request timed out.
11 393 ms 376 ms 368 ms gigabitethernet2-1.core1.NewYork1.Level3.net [64
159.17.69]
12 374 ms 394 ms 416 ms unknown.wcg.net [209.244.160.138]
13 437 ms 388 ms 384 ms nycmnyhlce1-oc12.wcg.net [64.200.87.114]
14 395 ms 372 ms 376 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150

15 372 ms 379 ms 444 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
16 412 ms 407 ms 405 ms dslreports.com [209.123.109.175]

Now the problem seems to be with that first level3 server. One problem onto the next.

reply to COXnightmare
*
[text was edited by author 2002-07-02 14:41:30]

reply to COXnightmare
1 * * * Request timed out.
2 * 291 ms 156 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 124 ms 158 ms 162 ms ip68-100-0-149.nv.nv.cox.net [68.100.0.149]
4 115 ms 98 ms 144 ms 68.1.1.6
5 96 ms 97 ms 104 ms 68.1.1.17
6 80 ms 137 ms 95 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
7 142 ms 238 ms 117 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
8 701 ms 769 ms 674 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
9 751 ms 690 ms 731 ms ge-6-2-0.mp2.Atlanta1.level3.net [64.159.3.77]
10 * * * Request timed out.
11 728 ms 683 ms 720 ms gigabitethernet2-1.core1.NewYork1.Level3.net [64
.159.17.69]
12 680 ms 695 ms 693 ms unknown.wcg.net [209.244.160.138]
13 737 ms 723 ms 730 ms nycmnyhlce1-oc12.wcg.net [64.200.87.114]
14 731 ms 724 ms 820 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150
]
15 757 ms 1005 ms 714 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
16 743 ms 756 ms 758 ms dslreports.com [209.123.109.175]

Trace complete.

Brilliant. Just brilliant.

reply to COXnightmare
GeneStarwind,

I'm pretty sure your problem is on your cable node in your neighborhood. And try to download Ping Plotter (like most of folks posting here) instead of using Tracert as Tracert only use very small amount of data to get the results which in most case underestimates the poor line quality you have. And if anytime the ping to your first hop is over 20 ms a lot, that means you have a bad cable node. And don't count on Cox to fix your problem anytime soon because as far as Cox concerns, as long as you have connection, there is nothing more they can do. Read my post on the first page of this thread to see if that can help you or not. I've enjoy very good latency ever since I fixed the problem by myself. I play Counter-Stike almost every day in 30 to 60 ping to my favorite servers.

Foxbat

reply to COXnightmare
You stated that Toshiba modems are less susceptible to this problem. I own a Toshiba PCX1000, and these problems are have been practically never-ending. So essentially what you're saying is, just ask them to switch me over to channel 2? But if a bad node is the case, why am I able to receive flawless service for days at a time, then get something like the above traceroute?

reply to COXnightmare
Plus I do use ping plotter quite often, if you've viewed my previous posts. I just haven't gotten around to wiping it from the registry, and reinstalling it yet (it gets rather difficult to use after the 30-day trial period expires). Plus I think there's a way to increase the bit-size of the ping packet in the DOS traceroute program, I'm just not sure how to do it.

reply to COXnightmare
1 * * * Request timed out.
2 16 ms 10 ms 8 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 16 ms 17 ms 22 ms ip68-100-0-149.nv.nv.cox.net [68.100.0.149]
4 16 ms 31 ms 15 ms 68.1.1.6
5 1446 ms 1448 ms 1439 ms 68.1.1.17
6 1433 ms 1435 ms 1440 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
7 1474 ms 1452 ms 1445 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
8 1444 ms 1450 ms 1445 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
9 1453 ms 1449 ms 1446 ms ge-6-2-0.mp2.Atlanta1.level3.net [64.159.3.77]
10 * * * Request timed out.
11 1449 ms 1460 ms 1465 ms gigabitethernet2-1.core1.NewYork1.Level3.net [64
.159.17.69]
12 1448 ms 1450 ms 1451 ms unknown.wcg.net [209.244.160.138]
13 1449 ms 1471 ms 1453 ms nycmnyhlce1-oc12.wcg.net [64.200.87.114]
14 1455 ms 1454 ms 1450 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150
]
15 1453 ms 1449 ms 1453 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
16 1461 ms 1471 ms 1454 ms dslreports.com [209.123.109.175]

It's like single-circuit christmas lights, one of them goes out, and all the ones after it go out along with it. And the more there are, the greater the chance that one of them burn out.

reply to GeneStarwind
Why would all these problems have magically started when Cox switch to their own network?

Strong possibility that Cox did not scale the network properly.

reply to GeneStarwind

said by GeneStarwind:

---

You stated that Toshiba modems are less susceptible to this problem. I own a Toshiba PCX1000, and these problems are have been practically never-ending. So essentially what you're saying is, just ask them to switch me over to channel 2? But if a bad node is the case, why am I able to receive flawless service for days at a time, then get something like the above traceroute?

---

reply to COXnightmare
They could fix it, but as Foxbat said, "fine" for them is if your first 3 cable lights are solid. I think it's about time they had some competition.

reply to COXnightmare

nm

reply to COXnightmare

Re: COX HSI problems, NOVA Only pease,

reply to COXnightmare

reply to COXnightmare

Well the Cox person was just here, he says these problems are due to the digital upgrade and that I will have them for the next 2 months when they upgrade my neighborhood. He said he had 27 calls today for the same problem. :eek: I showed him my pingplotter graphs and he was VERY interested. He said he would show it to the other 9 network troubleshooters who cover this area. I gave him a copy on a floppy.

The good thing is I he said I can get credit for the next two months

EDIT BTW I'm at the intersection of the parkway and 29, near the Price Club.
[text was edited by author 2002-07-03 19:31:22]

MikeS, The conversion and update in the city of Fairfax and some of its surrounding area SHOULD HAVE BEEN COMPLETED BY FIRST WEEK OF JUNE. Don't be "satisfied" by their words. Get FULL credit and if possible go to Cox office and try to get free special offer for their lack of quality service and false information on their website regarding transition/digital upgrade completion date.

Plus file with Fairfax County at the above link.