Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
10-27-2015 12:31 AM - last edited on 10-27-2015 08:35 AM by RogersPrasana
Hello I am on the rogers ignite 250u package and the internet has been very unstable lately over the past month. There are many disconnects daily on average. Most of the disconnects occur in the evenings from about 8 PM to 2AM but the timing is very sporadic. Sometimes the CGN3ACSMR will take 2 minutes to reset and provide internet again but other times it takes an hour or more to reset properly. Oddly enough the desktop computer that is connected via ethernet to the CGN3ACSMR has a higher amount of connectivity issues than laptops that connect via wi-fi. The ethernet port on the router flashes green during periods of poor connectivity and it is usually orange when the connection is stable. It might also be worth mentioning that the motherboard I use uses realtek drivers to connect to the internet. I have also ordered a separate NIC to see if this was a possible source of error. I think that another problem may lie with an old ethernet cable and have since ordered a new one but the router routinely has overall connectivity problems wirelessly as well. I was wondering what was the best way to proceed with this issue?
I have seen in past threads relating to this issue that it is useful to provide the signal logs and event logs from the gateway. There are many t3 and t4 timeouts in the event logs. These are copied and pasted below:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 651000000 | 256QAM | -1.200 | 130 | 36.387 |
2 | 591000000 | 256QAM | -0.800 | 121 | 37.636 |
3 | 597000000 | 256QAM | -0.500 | 122 | 37.356 |
4 | 603000000 | 256QAM | -0.900 | 123 | 37.636 |
5 | 609000000 | 256QAM | -1.100 | 124 | 37.356 |
6 | 615000000 | 256QAM | -1.500 | 125 | 36.610 |
7 | 621000000 | 256QAM | -1.800 | 126 | 36.610 |
8 | 633000000 | 256QAM | -1.400 | 127 | 36.610 |
9 | 639000000 | 256QAM | -1.000 | 128 | 36.610 |
10 | 645000000 | 256QAM | -1.000 | 129 | 36.844 |
11 | 657000000 | 256QAM | -1.700 | 131 | 36.387 |
12 | 663000000 | 256QAM | -2.100 | 132 | 36.610 |
13 | 669000000 | 256QAM | -2.800 | 133 | 35.780 |
14 | 675000000 | 256QAM | -3.000 | 134 | 35.780 |
15 | 681000000 | 256QAM | -0.900 | 135 | 37.356 |
16 | 687000000 | 256QAM | -0.400 | 136 | 37.636 |
17 | 693000000 | 256QAM | -0.100 | 137 | 37.636 |
18 | 699000000 | 256QAM | 0.000 | 138 | 37.356 |
19 | 705000000 | 256QAM | -0.200 | 139 | 37.356 |
20 | 711000000 | 256QAM | -0.200 | 140 | 37.356 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | BandWidth |
1 | 38596000 | ATDMA - 64QAM | 39.750 | 5 | 3200000 |
2 | 23700000 | ATDMA - 64QAM | 38.250 | 7 | 6400000 |
3 | 30596000 | ATDMA - 64QAM | 38.250 | 6 | 6400000 |
The DOCSIS event logs is shown here. The dates and times seems to be incorrect.
No. | Time | type | Priority | Event |
1 | 10/27/15 00:16:50 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
2 | 10/27/15 00:16:53 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
3 | 10/27/15 00:19:50 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
4 | 10/27/15 00:20:31 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
5 | 10/27/15 00:21:36 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
6 | 10/27/15 00:24:35 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
7 | 10/27/15 00:28:07 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
8 | 10/27/15 00:28:11 | 67070100 | error | DBC-ACK not received;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
9 | 10/27/15 00:42:35 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
10 | 10/27/15 00:42:49 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
11 | 10/27/15 00:43:40 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
12 | 10/27/15 00:46:37 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
13 | 10/27/15 00:49:22 | 68000100 | critical | DHCP FAILED - Discover sent, no offer received;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
14 | 10/27/15 00:50:16 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
15 | 10/27/15 00:50:24 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
16 | 10/27/15 00:51:21 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
17 | 10/27/15 00:56:35 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
18 | 10/27/15 00:57:40 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
19 | 10/27/15 01:00:37 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
20 | 10/27/15 01:02:49 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=bc:4d:fb:73:60:f0;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
- Labels:
-
CGN3
-
Connection Issue
-
Slow Speeds
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-08-2015 07:12 PM
I only messaged them today, right now its happening every 5 minutes, internet is useless at the moment.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-08-2015 08:30 PM
Hi @cgould1985-2,
We have not recieved any PM from you. I just checked the inbox for @CommunityHelps. I’m going to send you a private message from @CommunityHelps, when you receive it please check our messages via the envelope icon which appears in the top right hand side of your screen when you are logged into the forums.
Thanks,
RogersHassam
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-11-2015 10:59 PM
So there has been a technician who came and changed the splitters outside the house. This did improve the signal slightly for gateway however this was not succesful in fixing the disconnect problem. This was followed up by the replacement of the cgn3acsmr gateway by the request from a person at rogers tech support. Unfortunately, neither of these things seemed to do much in fixing the problem. Once again tonight there was a 2 hour outage where the new router was unable to proving an internet signal via ethernet and wifi.
I will once again post the event logs this time from the new cgn3acsmr gateway. Unfortunately the time and date settings are incorrect.
1 | 11/12/15 03:37:00 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
2 | 11/12/15 03:37:04 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
3 | 11/12/15 03:37:04 | 82000800 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 6;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
4 | 11/12/15 03:37:04 | 85010200 | warning | TCS Partial Service;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
5 | 11/12/15 03:37:26 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
6 | 11/12/15 03:40:22 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
7 | 11/12/15 03:40:57 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
8 | 11/12/15 03:40:57 | 82000700 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
9 | 11/12/15 03:41:23 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
10 | 11/12/15 03:41:24 | 82000700 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
11 | 11/12/15 03:41:49 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
12 | 11/12/15 03:41:49 | 82000700 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
13 | 11/12/15 03:42:11 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
14 | 11/12/15 03:42:12 | 82000700 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
15 | 11/12/15 03:42:35 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
16 | 11/12/15 03:42:50 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
17 | 11/12/15 03:43:55 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
18 | 11/12/15 03:46:50 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
19 | 11/12/15 03:50:05 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
20 | 11/12/15 03:51:10 | 73050200 | notice | Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:fc:8d:86:fb:40;CMTS-MAC=00:14:f1:e9:3c:4e;CM-QOS=1.1;CM-VER=3.0; |
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-11-2015 11:06 PM - edited 11-11-2015 11:11 PM
Can you repost the signal levels for both downstream and upstream. The previous signal levels weren't bad, so its a bit perplexing as to why you are having problems. Those tables are in the STATUS..... DOCSIS WAN page of the modem's user controls / inteface. Did you have any success with a new network card and swapping the ethernet cable?
Just as a side note, the best time to call tech support is when there is a service outage. The question at that point is whether or not the CSR can communicate with the modem, and if not, whats the source of the problem, the modem or neighborhood node?
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-11-2015 11:20 PM - edited 11-11-2015 11:21 PM
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 645000000 | 256QAM | -0.300 | 129 | 36.610 |
2 | 591000000 | 256QAM | 0.100 | 121 | 37.356 |
3 | 597000000 | 256QAM | 0.000 | 122 | 37.356 |
4 | 603000000 | 256QAM | -0.200 | 123 | 37.356 |
5 | 609000000 | 256QAM | -0.500 | 124 | 37.356 |
6 | 615000000 | 256QAM | -0.900 | 125 | 36.610 |
7 | 621000000 | 256QAM | -1.100 | 126 | 36.610 |
8 | 633000000 | 256QAM | -0.600 | 127 | 36.610 |
9 | 639000000 | 256QAM | -0.200 | 128 | 36.610 |
10 | 651000000 | 256QAM | -0.700 | 130 | 36.387 |
11 | 657000000 | 256QAM | -1.100 | 131 | 36.387 |
12 | 663000000 | 256QAM | -1.500 | 132 | 36.387 |
13 | 669000000 | 256QAM | -2.200 | 133 | 36.387 |
14 | 675000000 | 256QAM | -2.200 | 134 | 35.780 |
15 | 681000000 | 256QAM | -0.100 | 135 | 37.636 |
16 | 687000000 | 256QAM | 0.400 | 136 | 37.356 |
17 | 693000000 | 256QAM | 0.600 | 137 | 37.636 |
18 | 699000000 | 256QAM | 0.700 | 138 | 37.636 |
19 | 705000000 | 256QAM | 0.600 | 139 | 37.356 |
20 | 711000000 | 256QAM | 0.500 | 140 | 37.356 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | BandWidth |
1 | 38596000 | ATDMA - 64QAM | 39.750 | 5 | 3200000 |
2 | 23700000 | ATDMA - 64QAM | 38.250 | 7 | 6400000 |
3 | 30596000 | ATDMA - 64QAM | 39.750 | 6 | 6400000 |
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-11-2015 11:22 PM - edited 11-11-2015 11:36 PM
Those levels should be ok. Is your internet working thru the modem at this time, or are you experiencing an outage and posting via smartphone?
When you called in during the outage, was the CSR able to communicate with the modem at all, or was the modem not available to him or her?
If this is the second CGN3ACSMR, can you check the firmware version listed on the STATUS page. I'm wondering if you're on the base firmware version which is 4.4.8.14, or if you happen to have 4.5.8.16 loaded yet. 4.4.8.14 is very problematic and will complicate any troubleshooting.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-12-2015 05:46 PM - edited 11-12-2015 06:18 PM
the one time the internet was down and a person was contacted they were not able to communicate with the modem
the problems are usually not long lasting as well so by the time a person is actually contacted usually the internet is up again
the firmware for both routers has been the most current one 4.5.8.16 as the first one got updated when I was unable to play league of legends due to the old firmware and the new router came with 4.5.8.16
is this problem just what is mentioned in this thread and theres nothing can be done untill rogers improves their infrastructure in my area?
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
11-17-2015 06:37 AM - edited 11-17-2015 06:38 AM
same problem here in my area... keeps happening far too frequently... issue not just with internet but with cable TV as well... black screens on some channels and two way com fails regarding all on demand channels... approaching 20 area failures/outages since begininning of october
tech support claims that there has been one visit for repairs in my area each month since august this year (2015)... there have been many more outages... each time i call, the contact person checks other modems in the area and advises that none can be reached by him/her which means its an area outage
rogers is hiding something... what i do know is that toronto hydro has been replacing all the poles in the area and it is starting to look like its some bogus uncoordinated effort... toronto hydro has been working on the poles since late summer... no one is talking, no one seems to know anything
all i can say is either toronto hydro is messing up or rogers is hiding something, namely the networks are overloaded
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
01-02-2016 09:28 PM - last edited on 01-02-2016 10:15 PM by RogersMoin
speed/connection issues
The speed / connection stability issues back in Toronto. we should get discounts with these ongoing issues.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 10:44 PM - last edited on 06-13-2016 11:41 PM by RogersMaude
Hey guys,
I signed up for the 100u package about a month ago and I've been having nothing but issue with the interent.
Basically the Modem loses internet at least once a day and needs to be restarted to get internet again. The rogers technician came out and replaced the modem but the problem persists.
My setup is the Rogers Modem, connected in bridge mode to my Asus AC66u router that I've had for a few years now. Only the modem needs to be restarted to reconnect, the router operates properly and I maintain local network access.
I've set the DHCP query frequency to normal mode as suggested. I've also run the Hitron in router mode and still experienced the same problem.
Rogers is sending someone out to check the lines tomorrow but I was wondering if there was anything else I should try to resolve the problem
Thanks
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 10:56 PM - last edited on 06-13-2016 11:41 PM by RogersMaude
First question, please have a look at the product sticker at the back of the modem and let me know which modem you have, CGN3, CGN3ACR, CGN3ACSMR, CGN2, DPC-3825.
2. If its a CGN3 series modem, please log into the modem and confirm which Software (firmware) version is loaded, as seen on the Status page that comes up when you log in. If you have the modem in Bridge mode with your router running, use 192.168.100.1 to log into the modem, thru your router. You don't have to rip apart your network by using that address. If you are running the modem in Gateway mode, ie as a modem and router, you can use either 192.168.0.1, or 192.168.100.1.
3. Navigate to the STATUS ...... DOCSIS EVENT page and have a look for one of the following sequences:
a. CMTS-MAC=00:17:10 which indicates that you are connected to a Casa Systems Cable Modem Termination System (CMTS), or;
b. any of the following which indicates that you are connected to a Cisco Systems CMTS.
1. CMTS-MAC=00:05:00
2. CMTS-MAC=00:12:43
3. CMTS-MAC=00:14:f1
4. CMTS-MAC=00:1f:ca
5. CMTS-MAC=e0:2f:6d Note: there may be other Cicso MAC addresses
as well which are not on this list yet.
Please let me know if you have the CMTS-MAC=00:17:10 sequence in your DOCSIS EVENTS log. You may need to request the trial version 4.5.8.21 if you are connected to the Casa Systems CMTS, which that sequence indicates and you have a CGN3ACSMR. If that is the case, please see the following linked page and follow the @CommunityHelps link to their public page. On the right hand side is another link to "Send this user a private message" Fill out the topic line as indicated in this thread and your HFC MAC address from the Status page in the text area along with your update request. Its already addressed, so when ready, hit SEND.
If it is the case that you have a CGN3ACSMR connected to a Casa Systems CMTS, request the updated firmware version and don't swap the modem. Most likely this combination is what is causing the current problem. This is a new issue where the Casa CMTS equipment is replacing the current Cisco CMTS equipment in order to run gigabit service. Some incompatibility has come up, requiring the updated firmware version to resolve the issue.
I run an Asus RT-AC68U, so, I believe that your router should also be able to enable or disable IPV6. If you have IPV6 enabled and have any issues with address resolution or web pages that won't load, consider disabling IPV6 for a period of time until all of the network IPV6 issues are worked out.
Hope this helps.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 11:12 PM - last edited on 06-13-2016 11:41 PM by RogersMaude
Hi,
1. It is a CGN3ACSMR.
2. So this modem has firmware 4.4.8.14, howerver the previous one had 4.5.8.20 both did the same thing.
3. I am connecting to MAC=00:17:10, will send a message for the test firmware.
4. I do have IPv6 enabled however everything on that end has been operating properly, no issues connecting to webpages.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 11:24 PM - last edited on 06-13-2016 11:42 PM by RogersMaude
Ok, the problem is the combination of the Casa CMTS which supports gigabit service and the CGN3ACSMR. Firmware version 4.5.8.21 will resolve that.
4.4.8.14 is the original firmware for that modem and its terrible for gaming, VOIP phones, VPNs and any other latency intolerant application or device. 4.5.8.16 resolved those issues.
As a quick check, you could navigate to the STATUS ..... DOCSIS WAN page, copy the downstream and upstream tables and paste them into a post so that I can have a quick look at them. The copy and paste process will paste in the text contents of the tables. Those are the cable signal levels. If they are ok, then you shouldn't need a tech.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 11:38 PM - last edited on 06-13-2016 11:42 PM by RogersMaude
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 693000000 | 256QAM | -3.900 | 23 | 37.636 |
2 | 561000000 | 256QAM | -3.700 | 2 | 37.356 |
3 | 567000000 | 256QAM | -3.500 | 3 | 37.636 |
4 | 573000000 | 256QAM | -3.400 | 4 | 38.605 |
5 | 579000000 | 256QAM | -3.000 | 5 | 37.636 |
6 | 585000000 | 256QAM | -3.100 | 6 | 37.636 |
7 | 591000000 | 256QAM | -3.100 | 7 | 37.356 |
8 | 597000000 | 256QAM | -3.100 | 8 | 38.605 |
9 | 603000000 | 256QAM | -3.300 | 9 | 37.636 |
10 | 609000000 | 256QAM | -3.400 | 10 | 37.356 |
11 | 615000000 | 256QAM | -3.600 | 11 | 37.636 |
12 | 621000000 | 256QAM | -3.800 | 12 | 37.636 |
13 | 633000000 | 256QAM | -3.900 | 13 | 37.636 |
14 | 639000000 | 256QAM | -3.900 | 14 | 37.356 |
15 | 645000000 | 256QAM | -4.400 | 15 | 37.356 |
16 | 651000000 | 256QAM | -4.700 | 16 | 36.387 |
17 | 657000000 | 256QAM | -4.300 | 17 | 36.387 |
18 | 663000000 | 256QAM | -4.500 | 18 | 36.387 |
19 | 669000000 | 256QAM | -4.500 | 19 | 36.387 |
20 | 675000000 | 256QAM | -4.000 | 20 | 36.387 |
21 | 681000000 | 256QAM | -3.800 | 21 | 37.356 |
22 | 687000000 | 256QAM | -3.800 | 22 | 37.636 |
23 | 555000000 | 256QAM | -3.700 | 1 | 37.636 |
24 | 699000000 | 256QAM | -4.000 | 24 | 37.356 |
Port ID | Frequency (MHz) | Modulation | Signal Strength (dBmV) | Channel ID | BandWidth |
1 | 23700000 | ATDMA - 64QAM | 39.750 | 2 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 41.250 | 3 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 39.500 | 1 | 6400000 |
They are a little lower than what I get at my other location but still isn't terrible.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 11:45 PM - last edited on 06-14-2016 12:03 AM by RogersMaude
I would say you're good. The downstream are a little low, but tightly grouped, Signal to Noise is good as are the upstream levels. The downstream ideal level is 0 dBmV, so at -3/-4, you're good.
The only thing that could happen is that there is a very fast transient on the cable, which drops the levels and then comes back up immediately. That could be water ingress into an underground cable, or maybe the wind blowing around a cracked cable running overhead to a utility pole. If that was the case, especially with an overhead cable, the tech should be able to recognize the overall condition of the cable and decide if it needs replacing or not. My bet is the Casa CMTS and CGN3ACSMR at this time.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-13-2016 11:57 PM - last edited on 06-14-2016 12:04 AM by RogersMaude
I'll let the tech take a look at it. I think all cable in my area are underground. I had cable internet previously with distributel and didn't have any major issues like this.
Thanks for your help
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-14-2016 11:33 PM
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Signal noise
ratio (dB) Channel ID
1 693000000 256QAM 2.700 40.366 23
2 561000000 256QAM 3.300 40.366 2
3 567000000 256QAM 3.500 40.366 3
4 573000000 256QAM 3.100 40.366 4
5 579000000 256QAM 3.200 40.366 5
6 585000000 256QAM 3.100 40.366 6
7 591000000 256QAM 3.200 40.366 7
8 597000000 256QAM 3.300 40.366 8
9 603000000 256QAM 3.300 40.946 9
10 609000000 256QAM 3.200 40.366 10
11 615000000 256QAM 3.300 40.946 11
12 621000000 256QAM 3.200 40.946 12
13 633000000 256QAM 3.200 38.983 13
14 639000000 256QAM 3.400 40.366 14
15 645000000 256QAM 3.600 40.946 15
16 651000000 256QAM 3.400 40.366 16
17 657000000 256QAM 3.600 40.366 17
18 663000000 256QAM 3.400 40.366 18
19 669000000 256QAM 3.300 38.605 19
20 675000000 256QAM 3.200 38.605 20
21 681000000 256QAM 3.200 38.983 21
22 687000000 256QAM 3.000 40.366 22
23 555000000 256QAM 3.400 40.366 1
24 699000000 256QAM 2.200 40.366 24
Upstream Overview
Port ID Frequency (MHz) BandWidth Modulation Type Signal Strength
(dBmV) Channel ID
1 23699843 6400000 ATDMA 50.250 2
2 30596000 6400000 ATDMA 51.500 1
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-14-2016 11:55 PM - edited 06-15-2016 12:25 AM
The downstream signal levels and signal to noise ratios are good. The upstream is a disaster. You only have two channels instead of three, so you must be seeing slower than usual data rates, and the remaining two channels are very near the failure points. Did the third channel data not paste into the post?
Call tech support and have the CSR run a signal check. With only two channels running, the check should return an automatic failure and you should see a tech out to your home tomorrow, or as you arrange that with the CSR.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-14-2016 11:57 PM
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-15-2016 12:43 AM
Tech came ouf said everything looks fine. Had to restart once today. But tonigh ive been getting very slow speeds, max 20Mbps. No idea whats going on. Still waiting on thw test firmware, hopefully that helps.
Re: Terrible Connection Issues
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content
06-15-2016 01:01 AM - edited 06-15-2016 01:10 AM
How are you running that speedtest, ethernet or wifi? And, what browser and test server are you using. I've seen some strange results posted recently which included both http://speedcheck.rogers.com/en.html and speedtest.net. Speedtest has recently started a beta test for those users who are not running Flash on their pc. I've been directed to servers in Ontario and the first speedtest has usually been terrible. If I rerun the speedtest at the same site right away, it will turn out much improved.
So, to get around that I use Chrome to run a test using the speedtest.net Toronto Telus server. I force the use of the Toronto Telus server so that speedtest doesn't choose a server for me that has a lower capacity, in terms of high data rates.
Looking back at the posts, I see that you're running the router with IPV6 enabled. Just for the heck of it, try disabling IPV6 in the router, reboot the router, then the pc or laptop and then try an ethernet connected test with the Speedtest.net Toronto Telus server using Firefox if you have Flash loaded, or use Chrome. For the pc or laptop, if its running windows, after the router reboot is complete, you can simply bring up a command prompt and type:
ipconfig/release
ipconfig/renew
Run that instead of rebooting the pc or laptop to save time.
The updated firmware will solve the reboots required to restart dead LAN ports.