Skip to main content
ChrisLe's profile
ChrisLe

New Contributor

 • 

1 Message

Monday, August 1st, 2016

Closed

DNS server not responding

Over the past 5 days or so, i have been having intermittent internet drop outs affecting all my devices (desktop PC, laptop, phone) multiple times a day. There is no pattern to the problem that I can see as it happens  at various times, and when i am doing various online activities (surfing, playing games, watching Netflix etc.) It has also happened several times when I have been idle. When I run the network troubleshooting, it comes back 'Your computer appears to correctly configured but the device or resource (DNS server) it is connected to is not responding'. 90% of the time, I can correct the problem with a hard reset of my wireless modem (Netgear CG3000DV2 recently replaced), but the remaining 10% requires either multiple hard resets or for me to just wait up to 45 minutes for the modem to 'magically' reset itself. Is this a common problem that can be easily fixed, or do i need to call and have a service order placed on this issue. 

Here is a recent event log with multiple issues.
Time Priority Description
 Mon Aug 01 13:45:50 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:38:51 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:38:51 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:38:51 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:20:55 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:20:55 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:20:55 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:02:59 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:02:59 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 13:02:59 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:45:02 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:45:02 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:45:02 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:27:06 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:27:06 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:27:06 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:09:09 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:09:09 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 12:09:09 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:51:13 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:51:13 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:51:13 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:33:16 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:33:16 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:33:16 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:15:20 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:15:20 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 11:15:20 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 10:57:24 2016    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 10:57:24 2016    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 10:57:24 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 01 10:39:27 2016    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=a4:2b:8c:dd:4d:30;CMTS-MAC=a4:4c:11:8b:3a:64;CM-QOS=1.1;CM-VER=3.0; 
 

Discussions

 • 

Updated 

9 years ago

9.4K

5

0

0

Harleymama

New Contributor

 • 

3 Messages

9 years ago

I am having the exact same problem! I can't get any work done...have to reboot several times per day. Ugh

0

0

AllenP

Valued Contributor

 • 

1.7K Messages

9 years ago

Your log is loaded with T3 errors, that may indicate ingress, noise on the cable line.  I would check all cable, make sure it's free of cracks and make sure all connectors are secure and tight.  Also, if possible, remove any splitters in the line.  If this continues you may need a service tech to come out and check the lines.  The DNS server error you get is just a symptom of the modem resetting itself because of the T3 errors.

0

0

AllenP

Valued Contributor

 • 

1.7K Messages

9 years ago

Harleymama said:
I am having the exact same problem! I can't get any work done...have to reboot several times per day. Ugh

Harleymama, are you seeing the same multiple T3 timeouts in your modem's log?  If not, you may have similar symptoms but a different cause.  Please post logs and signal levels, thanks.

0

0

DerrickW

Valued Contributor

 • 

1.2K Messages

9 years ago

Hi ChrisLe,

I pulled up the modem information using the MAC address in the modem log. I am seeing some signal issues to your modem, do you use any splitters to connect a cable box and modem to the same outlet? If so, we could remove that to see if the signal improves. We may need to schedule a tech to come out and do some troubleshooting.

0

0

DerrickW

Valued Contributor

 • 

1.2K Messages

9 years ago

@Harleymama,

We can investigate your connection issues as well, please send an email with the name and address listed on the account to cox.help at cox.com. You can also include the link to this forum post as a reference point, thanks!

0

0

Related Content

Loading...

Recent Discussions

View More

Loading...