Intermittent connection - DOCSIS Event log displaying critical errors

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I'm a Reliable Contributor
Posts: 112

Re: Intermittent connection - DOCSIS Event log displaying critical errors

 

All machines are conceted the same way...all go through the same gigabit switch (no settings) to the CGN3

All machines have IPv6 off (popualr tip to address "resolving host" issues)

 

Point taken re flakey Realtek cards!

 

I tried another approach...

 

On one of the 'bad' machines, I forced the network card DNS entries on the IPv4 properties to the Google settings ( 8.8.8.8 and 8.8.4.4). It WORKED! - Ie no delays or DNS issues. Of course doing this, I had no UnBlockUS service!

 

So, using this approach. I forced the network card DNS entries for iPv4t o the UnBlock US settings ( 208.122.23.22; 208.122.23.23) . These did NOT work- many URLs continue to have resolving host issues.

 

So now I am stumped. It would be easy enought to assume the UnblockUS DNS server were simply bad...but they work fine on PC02 ( with no forced DNS entires on the PC and only on the router). One explanation could simply be flakey Realtek network cards on 3 machines. but that sounds a bit much as well

 

Will dig further .. and try your suggestion ablove. 

Highlighted
Resident Expert
Resident Expert
Posts: 6,600

Re: Intermittent connection - DOCSIS Event log displaying critical errors

I wouldn't say flakey, just different.  There is something unique about Realtek controllers that is causing problems for a good number of people, and it seems that no one has found the answer to the riddle.  I think it would take a passive tap between two devices to see the traffic going both ways which would allow someone to see or detemine what the problem is.  My bet is that its something basic, but you would need to see the traffic flow to figure it out.



Highlighted
I'm a Reliable Contributor
Posts: 112

Re: Intermittent connection - DOCSIS Event log displaying critical errors

 

Updates/Recap

 

In general, the last few days have been better than usual, with fewer critical errors. Things now "appear" more normal 🙂

 

Theprimary reason was the fix made for DNS entries. Web sites popped in as soon as I used the google DNS entries whereas many were dead slow when running my prior DNS settings.

 

When I was using only the UnBlockUS DNS entries (set in the router) the pc with an Intel NIC was fine with it, but the pc's with a Realtek NICs (like my main machine) were choking on it, even when specified in the IPv4 properties on the card. As soon as I put the Google DNS entries, everything was normal. I still need those UnblockUS entries on the router for now, for my Roku3, but can overrwide their impact my specifying the Google DNS values on the card (and dont need the service on most of those pcs anyway). I wrote tech support at UnBlockUS, and they gave me a temporary set of DNS entries to try, and indeed they worked, even on Realtek, but  tehy dont know why (!), and am not going to rely on them as they are temporary and not guarateed to work. So there is defnitely something not sociable between UnBlockUS DNS entries and some Realtek NIC cards.

 

To sumamrize the short list of things that help me dealing with intermiittent connections:

Network Card:

-use of  Goodle DNS for IPv4 poperites

-disabling IPv6

-disabling off-load and side-scalling features

-disabling power saving feature to turn network card to to save power

-compare with other network cards on other pc'd

Router

-set time to default  with TOD enabled and set to GMT 🙂 ; sntp disabled

Cabling

-check all cable connections

-consider swapping internet and home phone feeds ( but didnt need to do that)

 

I still get the odd critical error (one is the last three days). The message is of the form : 

No Ranging Response received - T3 time-out;CM-MAC=router_mac_adress;CMTS-MAC=macaddress2;CM-QOS=1.1;CM-VER=3.0;

I recognized the first MAC address as the one from the CGN3, Did not recognize the second one, but I think that is normal ; a google search said "CMTS refers to cable modem termination service. normally owned by the ISP"

 

There might still be an issue there, re external cabling or the router,  but I dont have the time over the next few weeks to address it. Very happy with the progress made to date!

 

Thanks

Highlighted
Resident Expert
Resident Expert
Posts: 6,600

Re: Intermittent connection - DOCSIS Event log displaying critical errors

Nice to see that you are making progress.  The only other thing I can think of at the moment is to load an older driver for the Realtek cards.  If you have the CDs that have the original install files for example, load the driver from the CD, regardless of whether you are running Windows 7 or 8.  The only hiccup in that plan is the driver update that will always appear in the Windows optional update files.  I don't think it will load on its own. 

 

Also consider the fact that the CGN3 will apparently supply two IP addresses when it runs in Bridge mode.  With that and a couple of routers, you could run two nets, one that uses UnBlockUS and one that doesn't.

 

And, you could always go the last mile so to speak and install gigabit Intel NICs on those pc's and disable the Realtek controller.



Highlighted
Resident Expert
Resident Expert
Posts: 6,600

Re: Intermittent connection - DOCSIS Event log displaying critical errors

I wonder what you would see if you loaded Wireshark on the pc's, both Intel and Realtek and then ran data captures on both, once going to the real UnBlockUS address, and then once more going to the temp address.  You wouldn't have to capture much data, just enough to capture the initial few seconds going to the UnBlockUS address.  Maybe you might see something that stands out when you compare the Intel to Realtek data captures.  Ideally you might see something flagged as erroneous which would give you some hint of what the problem is.



I've Been Here Awhile
Posts: 2

Re: Intermittent connection - DOCSIS Event log displaying critical errors

OK, soo i have been getting quick drops on my net every 4-5 min. It started a few weeks ago but happened once a day, now a week later it happens so much that just to say got onto google i have to keep hitting stop then refresh. Its as well cutting out on my XBONE, and games such as Mechwarrior Online. (keep getting lost server connection). Youtube plays a vid for 1-3 min then buffers till i click on the bar at the bottom of the vid to jump back a few seconds in the vid and it buffers and plays fine for a bit again.

 

So, i have retoobted the PC, the XBONE, still getting the error, rebooted the cgn3 router rogers provided...nothing did a factory reset, still got the issue. Firmware is upto date....

 

 What i have seen is the following 5 things in the DOCSIS section of the UI.....

 

 

 

1 04/17/15 05:08:08 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=0c:47:3d:e5:14:20;CMTS-MAC=00:05:00:e1:b5:49;CM-QOS=1.1;CM-VER=3.0;

 

2 04/17/15 05:19:14 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=0c:47:3d:e5:14:20;CMTS-MAC=00:05:00:e1:b5:49;CM-QOS=1.1;CM-VER=3.0;

 

3 04/17/15 00:47:56 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=0c:47:3d:e5:14:20;CMTS-MAC=00:05:00:e1:b5:49;CM-QOS=1.1;CM-VER=3.0;

 

4 01/01/70 01:01:11 68000401 warning ToD request sent - No Response received;CM-MAC=0c:47:3d:e5:14:20;CMTS-MAC=00:05:00:e1:b5:49;CM-QOS=1.1;CM-VER=3.0;

 

5 04/17/15 04:23:43 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=0c:47:3d:e5:14:20;CMTS-MAC=00:05:00:e1:b5:49;CM-QOS=1.1;CM-VER=3.0;

 

AS well the WAN doesnt restart just keeps counting....

 

here is the up and down stream info..

 

1 603000000 256QAM 6.400 37.636 99

2 591000000 256QAM 6.400 37.636 97

3 597000000 256QAM 6.300 37.636 98

4 609000000 256QAM 6.500 37.356 100

5 615000000 256QAM 6.100 37.356 101

6 621000000 256QAM 6.000 37.356 102

7 633000000 256QAM 5.100 37.636 103

8 639000000 256QAM 4.300 37.356 104

9 645000000 256QAM 3.900 36.610 105

10 651000000 256QAM 3.600 36.387 106

11 657000000 256QAM 3.600 36.610 107

12 663000000 256QAM 4.100 36.387 108

13 669000000 256QAM 4.700 36.610 109

14 675000000 256QAM 5.200 36.610 110

15 681000000 256QAM 6.500 37.356 111

16 687000000 256QAM 7.300 37.356 112

17 693000000 256QAM 7.500 37.356 113

18 699000000 256QAM 6.700 36.610 114

19 705000000 256QAM 5.700 36.610 115

20 711000000 256QAM 5.000 36.610 116

 

1 30596000 6400000 ATDMA 35.000 2

2 23700000 6400000 ATDMA 35.000 3

3 38596000 3200000 ATDMA 36.500 1

 

Highlighted
Resident Expert
Resident Expert
Posts: 6,600

Re: Intermittent connection - DOCSIS Event log displaying critical errors

We're only seeing this now?  Is this still an issue?  If so, call tech support and advise the CSR that you're seeing quick drop outs occur in your internet service.  Looks like they are probably too fast for the modem to react from the numbers in the post.  The signal levels on the downstream side are all high, which might be part of it, but it looks more like a cable issue I think.



Highlighted
I've Been Around
Posts: 1

Re: Intermittent connection - DOCSIS Event log displaying critical errors

I have been having the same issues and it was a frayed line.  The supervisor who came out did replace my line with RG11 (thicker) cable for the ignite 500 service  had installed.  Internet keeps dropping since, and I have the same setup (Apple Time Capsule).  Tech support indicated that they do not support modems in bridge mode, however the supervisor who arrived on site indicated that it is supported and they help customers set it up.  So i removed the Apple Time Capsule.  Internet still dropping and my wifi range has diminished significantly. So, what to do now?  I have been having this issue for months, and no credit has been offered to me.  So I think we take this matter to either senior execs or the BBB.