Welcome to Comcast Help & Support Forums
Find solutions, share knowledge, and get answers from customers and experts

New to the Community? Start here.

5,785,868

members

28

online now

1,936,536

discussions

Top

Having Issues with CDV and Internet service

Regular Visitor

Having Issues with CDV and Internet service

Hi all,

 

I have been lately having issues with my CDV service. I will still have internet service but no phone. My phone is directly connected to the emta and not to the house wiring. the modem is an Arris TM402. I am posting my numbers below to see if you see something I don't. This seems to be happeneing whenever but seems to happen more at night or early morning.a splitter is not being used so I don't know whats going on.

 

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

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    42 ms   111 ms    88 ms  te-5-4-ur07.saltlakecity.ut.utah.comcast.net [68.85.39.113]
  4    14 ms    10 ms    11 ms  te-9-4-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.9]
  5    33 ms    35 ms    40 ms  te-0-1-0-1-cr01.seattle.wa.ibone.comcast.net [68.86.90.205]
  6    33 ms   124 ms    30 ms  pos-0-11-0-0-cr01.portland.or.ibone.comcast.net[68.86.85.110]
  7    44 ms    44 ms    42 ms  pos-1-12-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.86.229]
  8    57 ms    57 ms    57 ms  pos-0-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.46]
  9    60 ms    59 ms   108 ms  68.86.87.2
 10    61 ms   163 ms   121 ms  a184-84-222-66.deploy.akamaitechnologies.com [184.84.222.66]

Trace complete.

 

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

  1     1 ms     1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    11 ms    74 ms     8 ms  te-5-4-ur07.saltlakecity.ut.utah.comcast.net [68.85.39.113]
  4     9 ms    13 ms     8 ms  te-9-4-ar01.saltlakecity.ut.utah.comcast.net [68.87.170.9]
  5    27 ms   119 ms    26 ms  te-0-1-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.249]
  6    31 ms    27 ms    41 ms  pos-0-0-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.86.138]
  7    58 ms    83 ms    59 ms  75.149.231.90
  8    59 ms   206 ms    59 ms  209.85.249.34
  9    60 ms   163 ms    60 ms  209.85.250.126
 10    62 ms   153 ms   123 ms  216.239.43.228
 11     *       66 ms   154 ms  64.233.174.125
 12    64 ms   155 ms   124 ms  pv-in-f106.1e100.net [72.14.213.106]

Trace complete.

 

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

Pinging a1526.g.akamai.net [184.84.222.66] with 32 bytes of data:
Reply from 184.84.222.66: bytes=32 time=146ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=59ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=136ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=59ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=98ms TTL=57
Reply from 184.84.222.66: bytes=32 time=83ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=62ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=60ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=69ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=61ms TTL=57
Reply from 184.84.222.66: bytes=32 time=55ms TTL=57
Reply from 184.84.222.66: bytes=32 time=64ms TTL=57
Reply from 184.84.222.66: bytes=32 time=63ms TTL=57
Reply from 184.84.222.66: bytes=32 time=59ms TTL=57
Reply from 184.84.222.66: bytes=32 time=67ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=55ms TTL=57
Reply from 184.84.222.66: bytes=32 time=59ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=79ms TTL=57
Reply from 184.84.222.66: bytes=32 time=63ms TTL=57
Reply from 184.84.222.66: bytes=32 time=56ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=60ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=58ms TTL=57
Reply from 184.84.222.66: bytes=32 time=57ms TTL=57
Reply from 184.84.222.66: bytes=32 time=55ms TTL=57

Ping statistics for 184.84.222.66:
    Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 55ms, Maximum = 146ms, Average = 63ms

 

Modem error page

6/18/2010 15:04 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 6/18/2010 15:05 8000800 3 TFTP file complete - but failed Message Integrity check MIC

 6/18/2010 15:05 20000200 3 No Ranging Response received - T3 time-out

6/18/2010 15:05 8000800 3 TFTP file complete - but failed Message Integrity check MIC

6/18/2010 15:05 18000200 3 UCD invalid or channel unusable

6/18/2010 15:06 8000800 3 TFTP file complete - but failed Message Integrity check MIC

6/18/2010 18:03 20000200 3 No Ranging Response received - T3 time-out

6/19/2010 8:19 20000400 3 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout

6/20/2010 5:46 20000200 3 No Ranging Response received - T3 time-out

 6/20/2010 6:14 20000400 3 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout

6/21/2010 6:06 20000200 3 No Ranging Response received - T3 time-out

 6/21/2010 8:06 20000400 3 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout

6/21/2010 8:06 20000200 3 No Ranging Response received - T3 time-out

6/21/2010 9:54 20000400 3 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout

6/22/2010 10:58 20000200 3 No Ranging Response received - T3 time-out

6/22/2010 10:58 20000300 3 Ranging Request Retries exhausted

 6/22/2010 10:58 18000200 3 UCD invalid or channel unusable

6/22/2010 10:58 14020600 3 DCC aborted unable to communicate on new upstream channel

6/22/2010 10:58 20000500 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out

6/25/2010 5:07 20000200 3 No Ranging Response received - T3 time-out

 

 

 

Downstream   Freq/Power: 531.000 MHz 6 dBmV     Signal to Noise Ratio:  36 dB     Modulation: QAM256

 

Upstream   Freq/Power: 24.000 MHz 43 dBmV     Channel Type: DOCSIS 1.x (TDMA)     Symbol Rate: 2560 kSym/sec     Modulation: QAM16    Status

 System Uptime: 0 days 0h:58m:40s

Computers Detected: 1

CM Status: Telephony-AC Power Iso OFF

 Reg Complete WAN Isolation: OFF-Access to WAN is allowed

Time and Date: FRI JUN 25 13:35:22 2010

 

Connection Expert

Re: Having Issues with CDV and Internet service

W.I.W. here, and this doesn't provide help or a solution for your CDV issue, but posting traces doesn't help you as the the CDV and HSI services traverse different routing paths. You should call in to tech support about your phone service issue.




Community Icon
I am not a Comcast employee, I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help. For information on the program click here.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee. I am a paying customer just like you!
I am an XFINITY Forum Expert and I am here to help.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am not a Comcast employee.

Was your question answered?
Mark it as a solution!solution Icon