Basic Internet Connectivity And Modem Help

turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Reply
Topic Options
Visitor
Visitor
Posts: 2
Registered: ‎11-19-2009

Continuous short disconnects in Broomfield, CO

‎11-19-2009 11:41 PM

For the past month or so I've been getting an increasing number of short disconnects.  They are short enough that the modem lights seldom turn off but long enough to have my connections to programs dropped.  Last week it became enough of an issue that a Comcast tech was out on Sunday.  He replaced the modem but said everything else was fine.  That didn't resolve the issue.  In fact it's gotten worse.

 

The disconnects happen to all 4 computers in the house.  They happen to my primary computer when I take the router out of the equation.  Power cycling the modem doesn't stop the problem.  I've inspected the coxial from the splitter to the modem and there are no obvious problems.  I've replaced the ethernet lines between the modem and the router/my computer.

 

The following numbers are with my primary computer connected straight to the modem.

 


C:\Users\Home>tracert www.comcast.net

Tracing route to a1526.g.akamai.net [208.49.52.8]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     8 ms    10 ms    12 ms  ge-2-3-ur01.wheatridge.co.denver.comcast.net
.86.105.129]
  3    11 ms    13 ms    11 ms  68.86.179.133
  4    10 ms    11 ms    11 ms  te-0-8-0-1-ar02.denver.co.denver.comcast.net
.86.103.69]
  5    11 ms    13 ms    13 ms  68.86.91.169
  6    25 ms    26 ms    42 ms  pos-0-2-0-0-cr01.santateresa.tx.ibone.comcas
t [68.86.86.170]
  7    43 ms    42 ms    42 ms  pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast
 [68.86.86.13]
  8    55 ms    44 ms    42 ms  TenGigabitEthernet9-1.ar2.LAX2.gblx.net [64.
88.29]
  9    44 ms    44 ms    43 ms  te2-3-10G.ar4.LAX1.gblx.net [67.17.107.42]
 10    42 ms    44 ms    54 ms  208.49.52.8

Trace complete.

C:\Users\Home>tracert www.yahoo.com

Tracing route to www-real.wa1.b.yahoo.com [209.131.36.158]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    40 ms    12 ms     8 ms  ge-2-3-ur01.wheatridge.co.denver.comcast.net
.86.105.129]
  3     9 ms    33 ms    12 ms  68.86.179.133
  4     9 ms    26 ms    26 ms  te-0-8-0-1-ar02.denver.co.denver.comcast.net
.86.103.69]
  5    23 ms    12 ms    10 ms  68.86.91.169
  6    25 ms    24 ms    26 ms  pos-0-3-0-0-cr01.santateresa.tx.ibone.comcas
t [68.86.86.174]
  7    42 ms    42 ms    46 ms  pos-1-7-0-0-cr01.losangeles.ca.ibone.comcast
 [68.86.86.17]
  8     *        *        *     Request timed out.
  9    44 ms    46 ms    56 ms  if-14-0-0-1128.mcore5.LAA-LosAngeles.as6453.
[209.58.33.13]
 10    58 ms    58 ms    70 ms  if-5-0.mcore4.PDI-PaloAlto.as6453.net [216.6
9]
 11    56 ms    56 ms    56 ms  ix-11-0-3.mcore4.PDI-PaloAlto.as6453.net [20
.196.90]
 12    57 ms    56 ms    99 ms  ae1-p151.msr2.sp1.yahoo.com [216.115.107.79]
 13    77 ms    72 ms    73 ms  te-8-1.bas-a1.sp1.yahoo.com [209.131.32.17]
 14    58 ms    60 ms    56 ms  f1.www.vip.sp1.yahoo.com [209.131.36.158]

Trace complete.

C:\Users\Home>tracert www.google.com

Tracing route to www.l.google.com [74.125.53.103]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    31 ms     9 ms    11 ms  ge-2-3-ur01.wheatridge.co.denver.comcast.net
.86.105.129]
  3    35 ms    23 ms    11 ms  68.86.179.133
  4    10 ms     9 ms    21 ms  te-0-8-0-1-ar02.denver.co.denver.comcast.net
.86.103.69]
  5    17 ms    10 ms    12 ms  pos-0-4-0-0-cr01.denverqwest.co.ibone.comcas
t [68.86.91.17]
  6    26 ms    25 ms    25 ms  pos-0-3-0-0-cr01.santateresa.tx.ibone.comcas
t [68.86.86.174]
  7    66 ms    43 ms    53 ms  pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast
 [68.86.86.13]
  8    60 ms    73 ms    54 ms  pos-1-14-0-0-cr01.sanjose.ca.ibone.comcast.n
68.86.85.185]
  9    63 ms    58 ms    55 ms  pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.
[68.86.86.122]
 10    64 ms    56 ms   101 ms  75.149.230.190
 11   125 ms    67 ms    82 ms  216.239.49.168
 12    56 ms    62 ms    55 ms  216.239.47.186
 13    58 ms    62 ms    61 ms  216.239.48.32
 14    60 ms    71 ms    69 ms  216.239.48.137
 15    82 ms    68 ms    71 ms  72.14.232.10
 16    59 ms    65 ms    57 ms  pw-in-f103.1e100.net [74.125.53.103]

Trace complete.

C:\Users\Home>ping -t www.comcast.net

Pinging a1526.g.akamai.net [8.14.216.17] with 32 bytes of data:
Reply from 8.14.216.17: bytes=32 time=46ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=53ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=58ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=42ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=41ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=45ms TTL=56
Reply from 8.14.216.17: bytes=32 time=62ms TTL=56
Reply from 8.14.216.17: bytes=32 time=41ms TTL=56
Reply from 8.14.216.17: bytes=32 time=51ms TTL=56
Reply from 8.14.216.17: bytes=32 time=61ms TTL=56
Reply from 8.14.216.17: bytes=32 time=44ms TTL=56
Reply from 8.14.216.17: bytes=32 time=49ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=74ms TTL=56
Reply from 8.14.216.17: bytes=32 time=52ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=46ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=42ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=51ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=54ms TTL=56
Reply from 8.14.216.17: bytes=32 time=55ms TTL=56
Reply from 8.14.216.17: bytes=32 time=36ms TTL=56
Reply from 8.14.216.17: bytes=32 time=59ms TTL=56
Reply from 8.14.216.17: bytes=32 time=48ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=54ms TTL=56
Reply from 8.14.216.17: bytes=32 time=52ms TTL=56
Reply from 8.14.216.17: bytes=32 time=43ms TTL=56
Reply from 8.14.216.17: bytes=32 time=56ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=36ms TTL=56
Reply from 8.14.216.17: bytes=32 time=44ms TTL=56
Reply from 8.14.216.17: bytes=32 time=43ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=40ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=48ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=41ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=43ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=48ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=39ms TTL=56
Reply from 8.14.216.17: bytes=32 time=36ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=38ms TTL=56
Reply from 8.14.216.17: bytes=32 time=37ms TTL=56
Reply from 8.14.216.17: bytes=32 time=55ms TTL=56
Reply from 8.14.216.17: bytes=32 time=44ms TTL=56

Ping statistics for 8.14.216.17:
    Packets: Sent = 76, Received = 76, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 74ms, Average = 43ms

 

 

For modem signal stats I have the following..

 

Down Stream Power Level:                    1 dBmV  

Down Stream Signal to Noise Ratio:         34 dB 

Upstream Power Level:                         50 dBmV

 

 

Does anyone have any ideas?

 

 

Thanks

Message 1 of 9 (143 Views)
Reply
Connection Expert
JamesR
Posts: 5,755
Registered: ‎09-29-2007

Re: Continuous short disconnects in Broomfield, CO

‎11-20-2009 09:21 AM

Welcome to the Forum.  Sorry you are having trouble.

Looks like you have done a pretty thorough job of troubleshooting your issue.

The only thing I see from the data you posted is that the upstream power is on the high edge.  It might be bouncing up and out of spec.

Would you please copy and ppaste the Log from this new modem back here in your thread.

Message 2 of 9 (139 Views)
Reply
0 Kudos
Regular Contributor
Regular Contributor
Posts: 27
Registered: ‎11-15-2009

Re: Continuous short disconnects in Broomfield, CO

‎11-20-2009 01:42 PM

Seeing the same issue here on this side of town, Castle Pines North.. I have a program ping plotter that is set up to ping comcast.com and log issues.. Even with the documentation , I get the same story as you from Comcast (hear no evil see no evil.. I have had some lip service from a feedback to comcast link where you send corportate an email. Your trace looks cleaner then mine with some unexplained hops in mine.

This makes VOIP no a viable option if you get intermittant drops.

 

   11/19/2009 3:03:06 PM,3053,3016,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,2792,2754,2714,2676,2634

Trace Session Started at: 11/17/2009 8:14:36 PM

Trace to: comcast.com 68.87.60.144
Repeated every 2.5 seconds

Hop  IPAddress         DNSName
2   68.85.221.221   te-8-2-ur01.englewood.co.denver.comcast.net
3   68.86.179.166    --------------
4   68.86.103.45    te-0-0-0-4-ar02.aurora.co.denver.comcast.net
5   -              
6   -              
7   -              
8   -              
9   -              
10  68.86.72.162    te-4-2-ar01.newcastle.de.bo.comcast.net
11  68.86.228.102   te-1-1-ar02.ndceast.pa.bo.comcast.net
12  68.86.134.49    te-4-1-ur02.ndceast.pa.bo.comcast.net
13  68.87.98.12      --------------
14  68.87.60.144    eloa.comcast.com

Date/Time                             2    3    4    5    6    7    8    9    10   11   12   13   14 
   11/20/2009 6:49:04 AM,9   ,12  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,68  ,70  ,70  ,73  ,  *

Trace Session Started at: 11/17/2009 8:14:36 PM

Trace to: comcast.com 68.87.60.144
Repeated every 2.5 seconds

Hop  IPAddress         DNSName
2   68.85.221.221   te-8-2-ur01.englewood.co.denver.comcast.net
3   68.86.179.166    --------------
4   68.86.103.45    te-0-0-0-4-ar02.aurora.co.denver.comcast.net
5   -              
6   -              
7   -              
8   -              
9   -              
10  68.86.72.162    te-4-2-ar01.newcastle.de.bo.comcast.net
11  68.86.228.102   te-1-1-ar02.ndceast.pa.bo.comcast.net
12  68.86.134.49    te-4-1-ur02.ndceast.pa.bo.comcast.net
13  68.87.98.12      --------------
14  68.87.60.144    eloa.comcast.com

Date/Time                          2    3    4    5    6    7    8    9    10   11   12   13   14 
   11/20/2009 6:49:04 AM,9   ,12  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,68  ,70  ,70  ,73  ,  *
   11/20/2009 7:33:04 AM,10  ,11  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,71  ,71  ,73  ,  * ,1490
   11/20/2009 7:33:04 AM,10  ,11  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,71  ,71  ,73  ,  * ,1490
  11/20/2009 10:09:04 AM,11  ,12  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,69  ,71  ,72  ,  * ,2617
  11/20/2009 10:09:04 AM,11  ,12  ,  * ,N/A ,N/A ,N/A ,N/A ,N/A ,69  ,71  ,72  ,  * ,2617

 

Message 3 of 9 (133 Views)
Reply
0 Kudos
Regular Contributor
Regular Contributor
Posts: 27
Registered: ‎11-15-2009

Re: Continuous short disconnects in Broomfield, CO

‎11-20-2009 01:48 PM

sorry my log didnt come out more readable, guess I'll have to try the preview from now on.
Message 4 of 9 (132 Views)
Reply
0 Kudos
Connection Expert
EG
Posts: 34,286
Registered: ‎12-24-2003

Re: Continuous short disconnects in Broomfield, CO

[ Edited ]

‎11-20-2009 02:20 PM - edited ‎11-20-2009 02:21 PM

What do random traces to other sites look like ?

 

Try using www.google.com instead of the Comcast site.

 

And if you are using a flavor of Windows. Please use the built in tracert tool.

Message Edited by EG on 11-20-2009 02:21 PM
Message 5 of 9 (128 Views)
Reply
0 Kudos
Visitor
Visitor
Posts: 2
Registered: ‎11-19-2009

Re: Continuous short disconnects in Broomfield, CO

‎11-20-2009 03:31 PM

Thanks for the reply JMCS.  Here's the log from the modem.

 

2009-11-20 07:51:453-CriticalR02.0No Ranging Response received - T3 time-out
2009-11-19 22:38:537-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2009-11-19 22:38:517-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2009-11-19 22:38:517-Information PROG: SW Download File name the same as currently run.
2009-11-19 22:38:517-Information SEC: Co-Signer CVC from configuration file was verified
2009-11-19 22:38:507-InformationB401.0Authorized
2009-11-19 22:38:507-Information REGISTRATION COMPLETE - Waiting for Operational status
2009-11-19 22:38:507-Information Registration file - downloaded
2009-11-19 22:38:487-Information Trying to download Configuration file ...
2009-11-19 22:38:487-Information Time of day - retrieved
1970-01-01 00:00:147-Information DHCP - parameters acquired
1970-01-01 00:00:147-Information DHCP: ACK: Setting (*) CM TFTP Boot file: d11_m_sb5120_silver_c01.cm
1970-01-01 00:00:147-Information DHCP: Setting CM IP address to: 73.85.15.125
1970-01-01 00:00:147-Information DHCP: Setting (*) CM Syslog Server address to: 0.0.0.0
1970-01-01 00:00:147-Information DHCP: Setting (*) CM Time Server address to: 68.87.66.15
1970-01-01 00:00:147-Information DHCP: Setting (*) CM Subnet mask to: 255.255.240.0
1970-01-01 00:00:147-Information DHCP: Setting (*) CM Gateway address to: 73.85.0.1
1970-01-01 00:00:147-Information DHCP: OFFER: Setting (*) CM TFTP Boot file: d11_m_sb5120_silver_c01.cm
1970-01-01 00:00:147-Information DHCP select: Setting (*) CM TFTP Server address to: 68.87.66.15
1970-01-01 00:00:147-Information DHCP: Offered (*) CM IP address to: 73.85.15.125

Message 6 of 9 (121 Views)
Reply
0 Kudos
Contributor
Contributor
Posts: 5
Registered: ‎02-08-2007

Re: Continuous short disconnects in Broomfield, CO

‎11-23-2009 04:04 PM

I'm in the same area (Westminster) and have been seeing the same behavior.  It has gotten worse in the past week.

 

When I lose connection I'm noticing packet loss to my Comcast gateway as well as random high echo responses.

 

I understand some packet loss can be expected on a network but it shouldn't be occuring to the subnet gateway (first hop).

 

 

<snip>

64 bytes from 98.245.0.1: icmp_seq=93 ttl=255 time=7.1 ms
64 bytes from 98.245.0.1: icmp_seq=94 ttl=255 time=8.1 ms
64 bytes from 98.245.0.1: icmp_seq=95 ttl=255 time=9.1 ms
64 bytes from 98.245.0.1: icmp_seq=96 ttl=255 time=9.5 ms
64 bytes from 98.245.0.1: icmp_seq=97 ttl=255 time=8.0 ms
64 bytes from 98.245.0.1: icmp_seq=98 ttl=255 time=8.9 ms
64 bytes from 98.245.0.1: icmp_seq=105 ttl=255 time=1346.8 ms
64 bytes from 98.245.0.1: icmp_seq=106 ttl=255 time=347.1 ms
64 bytes from 98.245.0.1: icmp_seq=107 ttl=255 time=9.0 ms
64 bytes from 98.245.0.1: icmp_seq=108 ttl=255 time=7.5 ms
64 bytes from 98.245.0.1: icmp_seq=109 ttl=255 time=8.5 ms
64 bytes from 98.245.0.1: icmp_seq=110 ttl=255 time=6.9 ms
64 bytes from 98.245.0.1: icmp_seq=111 ttl=255 time=7.9 ms

</snip>

 

 

I have reset the modem numerous times with no change.

 

 

TimePriorityCodeMessage
2009-11-23 13:44:173-CriticalR02.0No Ranging Response received - T3 time-out
2009-11-23 13:25:307-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2009-11-23 13:25:287-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2009-11-23 13:25:287-Information PROG: SW Download File name the same as currently run.
2009-11-23 13:25:287-Information SEC: Co-Signer CVC from configuration file was verified
2009-11-23 13:25:267-InformationB401.0Authorized
2009-11-23 13:25:267-Information REGISTRATION COMPLETE - Waiting for Operational status
2009-11-23 13:25:267-Information Registration file - downloaded
2009-11-23 13:25:247-Information Trying to download Configuration file ...
2009-11-23 13:25:247-Information Time of day - retrieved
1970-01-01 00:00:187-Information DHCP - parameters acquired
1970-01-01 00:00:187-Information DHCP: ACK: Setting (*) CM TFTP Boot file: d11_m_sb5120_speedtier_c01.cm
1970-01-01 00:00:187-Information DHCP: Setting CM IP address to: 96.169.31.28
1970-01-01 00:00:187-Information DHCP: Setting (*) CM Syslog Server address to: 0.0.0.0
1970-01-01 00:00:187-Information DHCP: Setting (*) CM Time Server address to: 68.87.66.14
1970-01-01 00:00:187-Information DHCP: Setting (*) CM Subnet mask to: 255.255.248.0
1970-01-01 00:00:187-Information DHCP: Setting (*) CM Gateway address to: 96.169.24.1
1970-01-01 00:00:187-Information DHCP: OFFER: Setting (*) CM TFTP Boot file: d11_m_sb5120_speedtier_c01.cm
1970-01-01 00:00:187-Information DHCP select: Setting (*) CM TFTP Server address to: 68.87.66.14
1970-01-01 00:00:187-Information DHCP: Offered (*) CM IP address to: 96.169.31.28

 

 

Signals:

 

Downstream Value
Frequency603000000 Hz 
Signal to Noise Ratio33 dB 
QAMQAM256
Network Access Control ObjectON
Power Level6 dBmV  
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream Value
Channel ID12
Frequency35800000 Hz
Ranging Service ID2518
Symbol Rate5.120 Msym/s
Power Level34 dBmV

 

 

Message 7 of 9 (94 Views)
Reply
0 Kudos
Contributor
Contributor
Posts: 5
Registered: ‎02-08-2007

Re: Continuous short disconnects in Broomfield, CO

‎11-23-2009 04:09 PM

Just after posting the last post I had the disconnect again and did a ping to the gateway..

 

~ # ping 98.245.0.1
PING 98.245.0.1 (98.245.0.1): 56 data bytes
64 bytes from 98.245.0.1: icmp_seq=5 ttl=255 time=24.6 ms
64 bytes from 98.245.0.1: icmp_seq=6 ttl=255 time=8.0 ms
64 bytes from 98.245.0.1: icmp_seq=7 ttl=255 time=8.9 ms
64 bytes from 98.245.0.1: icmp_seq=8 ttl=255 time=7.8 ms
64 bytes from 98.245.0.1: icmp_seq=9 ttl=255 time=8.4 ms
64 bytes from 98.245.0.1: icmp_seq=10 ttl=255 time=9.3 ms
64 bytes from 98.245.0.1: icmp_seq=13 ttl=255 time=9.2 ms
64 bytes from 98.245.0.1: icmp_seq=26 ttl=255 time=7.7 ms
64 bytes from 98.245.0.1: icmp_seq=27 ttl=255 time=8.7 ms
64 bytes from 98.245.0.1: icmp_seq=28 ttl=255 time=194.4 ms
64 bytes from 98.245.0.1: icmp_seq=29 ttl=255 time=7.6 ms
64 bytes from 98.245.0.1: icmp_seq=30 ttl=255 time=9.1 ms
64 bytes from 98.245.0.1: icmp_seq=43 ttl=255 time=7.2 ms
64 bytes from 98.245.0.1: icmp_seq=44 ttl=255 time=8.1 ms

--- 98.245.0.1 ping statistics ---
45 packets transmitted, 14 packets received, 68% packet loss
round-trip min/avg/max = 7.2/22.7/194.4 ms

 

I'll look at getting the modem replaced.. again.   Though it seems that there may be something in a larger area going on.

Message 8 of 9 (92 Views)
Reply
0 Kudos
Contributor
Contributor
Posts: 5
Registered: ‎02-08-2007

Re: Continuous short disconnects in Broomfield, CO

‎11-23-2009 05:04 PM

I saw this thread http://forums.comcast.net/comcastsupport/board/message?board.id=5&thread.id=113943 and wonder if it's related..

 

I have the same modem and firmware.

 

Software Version: SB5120-2.19.0.14-SCM01-NOSH
Hardware Version: 4
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Message 9 of 9 (89 Views)
Reply
0 Kudos