NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
C6300 and Cable signal drops
Hello. Trying to resolve recurring issues with Medicom and my C6300, firmware version v1.02.21. My cable connection and internet access randomly drops. Here are the symptoms. 1) Modem connectio...
Hi,
Can you please post the power values? and full event log?
How do I obtain the event logs from a NETGEAR cable modem/modem router?
Link: http://kb.netgear.com/app/answers/detail/a_id/30008
How do I obtain the cable connection information from a NETGEAR cable modem/modem router?
Link: http://kb.netgear.com/app/answers/detail/a_id/30007
as soon as I see this message "Unicast Ranging Received Abort Response" , I see that reset was initiated from ISP side (Mediacom). also, if you have lot of uncorretables, that is another sign of RF issue from ISP.
We had a another community user from the same ISP with similar issue. he resolved the issue by removing unnecessary splitter(s) in his home.
DoS attack info is ok as it is an internal packet. You can ignore it.
Event Log Part 2
| Nov 30 01:14:01 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:01 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:02 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:02 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:02 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:02 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:03 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:03 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:03 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:03 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:04 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:04 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:04 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:04 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:05 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:05 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:06 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:06 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:06 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:06 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:07 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:07 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:07 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:07 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:08 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:08 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:09 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:09 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:09 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:09 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:10 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:10 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:10 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:10 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:14:38 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:52 2015 | Critical (3) | No Ranging Response received - T3 time-out |
| Nov 30 01:15:38 2015 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Nov 30 01:15:38 2015 | Notice (6) | TLV-11 - unrecognized OID |
| Nov 30 15:40:18 2015 | Critical (3) | No Ranging Response received - T3 time-out |
there are so many timeouts and ranging abort messages request coming from ISP makes me believe this is an ISP issue rather than device issue.
which device were you using before?
This is the 1st cable modem with Mediacom. I was using VDSL from CenturyLink but their best offering was only 25Mbps down/0.8kbps up in my area. Need the higher cable modem speed (150Mbps down/25Mbps up) from Mediacom. IF it can become reliable.
ah ok. Looks like there may some issue with RF. you should not be seeing so many timeouts and so many MAC Re-inits.
can you please call them fix the line?