Modem fails to connect with ISP

Toggle sidebar Toggle sidebar
D

DC4747

Prominent
Feb 20, 2017
2
0
510
I have a Dell laptop running win 8.1 and a Netgear CM400 modem. The ISP is Comcast.

Typically it takes 10 to 60 minutes to make a connection to the ISP. During this time the modem displays the power light, and then runs through a sequence of flashing and then solid green lights for downstream, then the same for upstream, and then flashing green for internet -- before recycling to the downstream light flashing and repeating the cycle. Eventually a connection is made, which runs around 80 Mps which is what the ISP supposedly provides.

The modem provides an event log. I'll post the last one below.

I'd like advice as to how to return to the prior condition where a connection occurred within a few seconds after power-cycling. I'd also like to know if there are any settings I should try changing. And finally if the problem is with the modem, the computer, or the ISP. Thanks in advance.

The modem event log:

Time Priority Description
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:47 2017 Warning (5) Lost MDD Timeout
Feb 20 22:00:58 2017 Error (4) T6 Timeout and retries exceeded
Feb 20 22:00:58 2017 Critical (3) REG RSP not received
Feb 20 22:01:03 2017 Warning (5) Lost MDD Timeout
Feb 20 22:01:30 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:01:37 2017 Warning (5) Lost MDD Timeout
Feb 20 22:01:54 2017 Warning (5) ToD request sent - No Response received
Time Not Established Warning (5) Lost MDD Timeout
Time Not Established Warning (5) ToD request sent - No Response received
Feb 20 22:02:08 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:02:14 2017 Warning (5) Lost MDD Timeout
Feb 20 22:02:22 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 20 22:02:23 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:02:34 2017 Error (4) T6 Timeout and retries exceeded
Feb 20 22:02:34 2017 Critical (3) REG RSP not received
Feb 20 22:02:40 2017 Warning (5) Lost MDD Timeout
Feb 20 22:02:49 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:03:00 2017 Warning (5) MDD message timeout
Feb 20 22:03:00 2017 Warning (5) Lost MDD Timeout
Feb 20 22:03:15 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:03:32 2017 Warning (5) Lost MDD Timeout
Feb 20 22:03:45 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:03:52 2017 Warning (5) Lost MDD Timeout
Feb 20 22:03:57 2017 Warning (5) ToD request sent - No Response received
Time Not Established Warning (5) Lost MDD Timeout
Time Not Established Warning (5) ToD request sent - No Response received
Feb 20 22:04:25 2017 Warning (5) Lost MDD Timeout
Feb 20 22:05:24 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:05:45 2017 Warning (5) Lost MDD Timeout
Feb 20 22:05:50 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:06:07 2017 Warning (5) Lost MDD Timeout
Feb 20 22:07:07 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:07:09 2017 Warning (5) Lost MDD Timeout
Feb 20 22:07:31 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:07:41 2017 Warning (5) Lost MDD Timeout
Feb 20 22:08:20 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:08:24 2017 Critical (3) TFTP failed - Request sent - No Response
Feb 20 22:08:24 2017 Critical (3) TFTP Request Retries exceeded, CM unable to register
Feb 20 22:08:34 2017 Critical (3) No Ranging Response received - T3 time-out
Feb 20 22:09:02 2017 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
 
Solution
kanewolf
They will come check the signal at the side of your house for no charge (I believe). Since you own your modem, they won't exchange it.
Sort by date Sort by votes
Start with a brand new coax (across the floor) to the outside of your house direct to the modem. If that improves it you will have to investigate your in-house wiring. if not, call Comcast to check the signal level at the outside of your house.
 
Upvote 0 Downvote
I understand that this would isolate the factor of the in-house wiring. However it would be a time-consuming and expensive trial. Is there something in the modem event log or the description of the problem that suggests in-house wiring as a likely problem?
Would having Comcast come out to evaluate service up to the exterior wall of the house cost me money? I own the modem, but would they be willing to swap it out for one they carry in order to see if this is the problem?
Note again that the problem isn't that I'm consistently getting no signal or a weak signal. Rather, I often am running at the max per my deal. Right now, 85 Mbps shows on the Comcast online test meter.
To clarify, the problem is that quite often when I power cycle the modem, for a long time the connection is between 0 and 1 Mbps and the modem display shows only one locked download channel rather than the typical 8.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom