Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » Cox HSI » [VA] Losing connection without desync
Search Topic:
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
[NEWS] Cox Raising Broadband Prices In Several States »
« Internet Disconnect  
AuthorAll Replies

Joonp

join:2008-06-02

reply to Joonp
Re: [VA] Losing connection without desync

oh come on, i'm out of option on what to do, it's been great til 2 months ago

July 07 5:00 AM
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=11ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=11ms TTL=248
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=12ms TTL=248
Reply from 64.233.169.103: bytes=32 time=21ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=13ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=9ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248

July 07 7:22 AM
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=10ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=10ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=15ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248

July 07 8:30 AM
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=16ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=9ms TTL=248
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=29ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=11ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248

this is quite unbearable

Joonp

join:2008-06-02


edit:
July 7th, @08:56AM

July 07 8:54 AM
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=9ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=13ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=13ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248

4 07/03/08 10:04:27 R02.0 critical No Ranging Response received - T3 time-out
5 07/03/08 10:04:28 R03.0 critical Ranging Requests Retries exhausted
6 07/03/08 10:05:16 R02.0 critical No Ranging Response received - T3 time-out
7 07/03/08 10:05:20 R03.0 critical Ranging Request Retries exhausted
8 07/03/08 10:05:58 R02.0 critical No Ranging Response received - T3 time-out
9 07/03/08 10:05:59 R03.0 critical Ranging Request Retries exhausted
10 07/03/08 10:05:59 U02.0 critical UCD invalid or channel unusable
11 07/03/08 10:06:00 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
12 07/03/08 10:06:09 T04.0 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
13 07/03/08 10:06:10 T01.0 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
14 07/03/08 10:06:49 R02.0 critical No Ranging Response received - T3 time-out
15 07/03/08 10:06:53 R03.0 critical Ranging Request Retries exhausted
16 07/05/08 02:29:47 R02.0 critical No Ranging Response received - T3 time-out
17 07/05/08 02:29:48 R03.0 critical Ranging Requests Retries exhausted
18 07/05/08 02:30:33 R02.0 critical No Ranging Response received - T3 time-out
19 07/05/08 02:30:38 R03.0 critical Ranging Request Retries exhausted
20 07/07/08 06:21:36 R02.0 critical No Ranging Response received - T3 time-out
21 07/06/08 20:38:21 D04.1 warning ToD request sent - No Response received
22 07/06/08 20:38:24 I401.0 notice TLV-11 - unrecognized OID
23 07/07/08 06:45:17 R02.0 critical No Ranging Response received - T3 time-out

Joonp

join:2008-06-02



^^
July 07 9:18 AM
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=6ms TTL=248
Reply from 64.233.169.103: bytes=32 time=13ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=13ms TTL=248
Reply from 64.233.169.103: bytes=32 time=14ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248
Reply from 64.233.169.103: bytes=32 time=8ms TTL=248
Reply from 64.233.169.103: bytes=32 time=7ms TTL=248


jsimmons
Premium,MVM
join:2000-04-24
Falls Church, VA
·Cox HSI

While your round-trip ping time looks very good, it appears that the packet loss is mostly being introduced at your first hop.. Indicating a possible problem with the upstream path. I doub't we'll be able to help you directly, so as long as you have Cox techs looking at it, they should hopefully come up with a fix. keep us posted on your progress.
--
"Everything should be made as simple as possible, but not one bit simpler."- Albert Einstein

Joonp

join:2008-06-02




Time log of PL burst today
July 07 5:00 AM
July 07 7:22 AM
July 07 8:30 AM
July 07 8:54 AM
July 07 9:18 AM
July 07 9:42 AM
July 07 10:05 AM

*** stopped monitoring 'til evening ***

July 07 9:19 PM
July 07 10:02 PM
July 07 11:31 PM
July 07 11:58 PM
July 08 12:58 AM
July 08 1:25 AM
July 08 1:53 AM

on the other hand, I haven't noticed »[VA] Intermittent Internet Issues??? for several days.
Forums » US Cable Support » Cox HSI[NEWS] Cox Raising Broadband Prices In Several States »
« Internet Disconnect  


Tuesday, 02-Dec 15:32:13 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 9 years online! © 1999-2008 dslreports.com.
page compression OFF
Most commented news this week
· [107] AT&T Metered Billing Trial Hits Second Market
· [82] UDP BitTorrent Will Destroy The Interwebs!
· [59] Comcast Tries To Slow Verizon's Philly Entry
· [58] EFF Challenges Telecom Immunity
· [32] Cablevision Bumps HD Count To 68
· [22] Mega-ISPs, Consumer Advocates Demand Broadband Plan
· [17] FCC To Vote On Free National Wireless Broadband
· [17] Hawaii Telecom Files For Bankruptcy
· [15] Clearwire May Slow WiMax Build
· [14] Verizon Tops Consumer Reports Wireless Satisfaction Ratings
Most people now reading
· [Rant] Bestbuy receipt checker [Rants, Raves, & Praise]
· Is this a good thing for the net? [news,99366]
· Coalition Government Possible? [TekSavvy]
· Ted Rogers passed away [Rogers]
· Routing problem? [OptimumOnline]
· Notice, new uTorrent Alpha may be able to evade throttling [TekSavvy]
· Upverting DVD players vs Blue ray DVD players. [General Questions]
· Basic 500 Price Increase! [Vonage]
· [WotLK] New Hunter Macros [World of Warcraft]
· Java SE Runtime Environment (JRE) 6 Update 11 [Security]