Re: [VA] Losing connection without desync in Cox HSI

Re: [VA] Losing connection without desync in Cox HSI http://www.dslreports.com/forum/r20732468 en Mon, 14 Dec 2009 20:34:18 EDT Mon, 14 Dec 2009 20:34:18 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20774155 lambition : Your packet loss problem and losing connection once or twice a day many not be related at all.

I think you have two different problem since you had packet loss problem before changing the modem and losing connection issue started after changing the modem.]]> http://www.dslreports.com/forum/remark,20774155 Fri, 11 Jul 2008 09:25:42 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20773485 Joonp : this is a problem i had before dcm-202, i was using linksys wcg200

the problem mainly concerning the first post is similar problem as yours but it's been better lately, my another problem is the later posted ones which is a lot older and continueing]]> http://www.dslreports.com/forum/remark,20773485 Fri, 11 Jul 2008 02:02:16 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20773454 lambition : Looks like you are having problem very similar to to the problem I had.
I too had DCM-202 and was loosing connection once or twice (most of the time every 12 or 24 hours) and I had to reset the modem to get back on the net.
The cable modem showed it was getting good signal even when I wasn't able to connect interenet just like in your case.

This problem was fixed when I changed my modem to Scientific Atlanta WebSTAR DPC2100 (the one that COX issues).

I did not have packet loses while internet connection was working though.

Following was my case.
»[VA] Anyone experiencing intermittent connection loss?

COX must have done something to their network which is not compatible with DCM-202.
I heard they were upgrading to DOCSIS 3.0. It must have something to do with that. ]]> http://www.dslreports.com/forum/remark,20773454 Fri, 11 Jul 2008 01:41:30 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20773025 Joonp :

trace during following:

July 10 11:15 PM
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=17ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=12ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=26ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=14ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=21ms TTL=248
Reply from 64.233.169.104: bytes=32 time=18ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=15ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.104: bytes=32 time=8ms TTL=248
Reply from 64.233.169.104: bytes=32 time=9ms TTL=248]]> http://www.dslreports.com/forum/remark,20773025 Thu, 10 Jul 2008 23:23:49 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20759346 Joonp : yeah, hopefully it works out soon]]> http://www.dslreports.com/forum/remark,20759346 Tue, 08 Jul 2008 14:59:24 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20757604 jsimmons : No doubt there is a signal path issue between your modem and the CMTS. So is Cox working on it for you?
--
"Everything should be made as simple as possible, but not one bit simpler." - Albert Einstein ]]> http://www.dslreports.com/forum/remark,20757604 Tue, 08 Jul 2008 09:24:29 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20756951 Joonp :

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.]]> http://www.dslreports.com/forum/remark,20756951 Tue, 08 Jul 2008 02:06:41 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20752663 jsimmons : 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 ]]> http://www.dslreports.com/forum/remark,20752663 Mon, 07 Jul 2008 10:40:44 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20752321 Joonp :

^^
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]]> http://www.dslreports.com/forum/remark,20752321 Mon, 07 Jul 2008 09:22:41 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20752235 Joonp : 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 ]]> http://www.dslreports.com/forum/remark,20752235 Mon, 07 Jul 2008 08:55:10 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20752178 Joonp : 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]]> http://www.dslreports.com/forum/remark,20752178 Mon, 07 Jul 2008 08:32:34 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20742647 Joonp : thanks, been tracing since last night

15 global packet losses from tracing is due to same issue as »[VA] Intermittent Internet Issues??? as I could not get back online until I reset the modem.]]> http://www.dslreports.com/forum/remark,20742647 Fri, 04 Jul 2008 17:28:14 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20737238 jsimmons : Do yourself a favor and get a copy of this (it free): »www.pingplotter.com/freeware.html

It'll make your life easier in tracking down connectivity issues. :D
--
"Everything should be made as simple as possible, but not one bit simpler." - Albert Einstein ]]> http://www.dslreports.com/forum/remark,20737238 Thu, 03 Jul 2008 14:02:35 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20736368 Joonp : sent you a PM

meanwhile...

July 02 5:27 PM
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=10ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=13ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=11ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=10ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=10ms TTL=24
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=10ms TTL=24
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Request timed out.
Reply from 64.233.169.147: bytes=32 time=21ms TTL=24
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=15ms TTL=24
Request timed out.
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248

July 02 8:58 PM
Reply from 64.233.169.147: bytes=32 time=13ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=10ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Reply from 64.233.169.147: bytes=32 time=15ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=16ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Reply from 64.233.169.147: bytes=32 time=23ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248

July 02 9:59 PM
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=13ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=17ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248

July 03 10:22 AM
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=24
Request timed out.
Reply from 64.233.169.147: bytes=32 time=22ms TTL=24
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248

July 03 11:04 AM
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=16ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=15ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=11ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=16ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.]]> http://www.dslreports.com/forum/remark,20736368 Thu, 03 Jul 2008 11:09:07 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20735515 CoxTOC1 : If you could send me you modem MAC I would like to take a look at it.]]> http://www.dslreports.com/forum/remark,20735515 Thu, 03 Jul 2008 05:16:45 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20734560 Joonp : »[VA] Intermittent Internet Issues???

seems like it's not just me, not sure if they are also experiencing no problem with light signals on the modem itself when you are not connected (it says you are synced but you are not)

I also have periodic burst of packet loss since, uh two months ago? for example:

July 02 9:59 PM
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=13ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=17ms TTL=248
Reply from 64.233.169.147: bytes=32 time=8ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=6ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Reply from 64.233.169.147: bytes=32 time=14ms TTL=248
Request timed out.
Request timed out.
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Request timed out.
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=9ms TTL=248
Reply from 64.233.169.147: bytes=32 time=7ms TTL=248

this has happen at least 5 times today already...

this is getting old, techs who came couldn't figure out]]> http://www.dslreports.com/forum/remark,20734560 Wed, 02 Jul 2008 22:17:52 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20733029 jsimmons : FYI, the error log messages are fairly normal. You don't want to see tons of T3 errors in a short period, but a few a day are nothing to be concerned about. The other two generally occur when the modem resets or is rebooted, and while it would be nice not to see them in the log, they don't seem to cause issues. I see them too in my logs but don't have any connectivity issues.
--
"Everything should be made as simple as possible, but not one bit simpler." - Albert Einstein ]]> http://www.dslreports.com/forum/remark,20733029 Wed, 02 Jul 2008 17:16:14 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20732468 Joonp : NOVA]]> http://www.dslreports.com/forum/remark,20732468 Wed, 02 Jul 2008 15:33:35 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20730054 jfoj : Where are you located?

jfoj]]> http://www.dslreports.com/forum/remark,20730054 Wed, 02 Jul 2008 05:59:40 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20729773 Joonp : no router]]> http://www.dslreports.com/forum/remark,20729773 Wed, 02 Jul 2008 01:48:03 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20724610 daveinpoway : Based on my experience, my DLink DCM-202 reports a downstream S/N ratio that is a dB or so lower than my Motorola SB5120, so the posted number (almost 34) would probably be 35-36 with a Motorola. Here, after a recent tech visit that resulted in several things being swapped out and my connection being given a clean bill of health, it is impossible for my DCM-202 to report 35 dB or higher.

From what I know, the S/N ratio is not directly measured by the modem, but it is calculated from the bit error rate. It seems reasonable that different modems might perform this calculation a little differently. ]]> http://www.dslreports.com/forum/remark,20724610 Tue, 01 Jul 2008 06:14:23 EDT Re: [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20724476 dvd536 : signals look good although that SNR is lower than cox likes to see it at.
do you have a router?
--
When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee]]> http://www.dslreports.com/forum/remark,20724476 Tue, 01 Jul 2008 03:29:38 EDT [VA] Losing connection without desync http://www.dslreports.com/forum/remark,20722000 Joonp : Previously, I had problem with periodic burst of packet loss but it disappeared after a week of new modem. However now I have a new problem with complete connection loss at least once or twice a day without going out of sync and it doesn't seem to recover itself unless I restart the modem. Please help.

Model Name: DCM-202

Downstream Signal
Frequency: 393000000 Hz
QAM Mode: 256 QAM
Channel Power: 1.6 dBmV
SNR: 33.967 dB

Upstream Signal
Channel Id: 1
Frequency: 28496000 Hz
Channel Width: 3200000 Hz
Channel Power: 41.3 dBmV

System Event Log

1 06/30/08 14:55:27 R02.0 critical No Ranging Response received - T3 time-out
2 06/30/08 03:47:40 D04.1 warning ToD request sent - No Response received
3 06/30/08 03:47:43 I401.0 notice TLV-11 - unrecognized OID
]]> http://www.dslreports.com/forum/remark,20722000 Mon, 30 Jun 2008 17:10:54 EDT