Hello @Raps_in_4,
It's great to hear that you've gotten this issue resolved!
Thank you for posting a potential solution, keep us posted if you notice any issues going forward.
Cheers,
RogersTony
Hello @Raps_in_4,
It's quite strange that this issue keeps happening. I personally have not experienced this issue in the past but luckily you've reached the right place!
We've got several Resident Experts: @Datalink, @gp-se, & @Gdkitty who may be able to shine some light on what is causing this issue and possible solutions.
If anyone in the Community has run into similar issues feel free to chime in!
RogersTony
@RogersTony, @Raps_in_4, I would look at the downstream and upstream signal levels as indicated on the STATUS .... DOCSIS WAN tab in the modem. Unfortunately the DOCSIS 3.1 OFDM channel data which in included on that page is not correctly displayed and as a result a call to tech support is required as they have access to the correct data.
An overloaded node can result in strange indications at the modem, including unusual data transfer times and signal levels. So, when the problem starts and continues for a period of time, thats the first item I would look at.
@Raps_in_4 are these slow load periods long enough for you to attempt contacting tech support?
If so, you would have to hurry the online tech thru the initial inquisition of proving who you and ask him or her to run a signal check on the modem. The question at this point is, can he or she query the modem, and, is this a modem only problem, or is there some issue further upstream.
Edit: Those signal levels aren't bad. I wouldn't think that you would have any issues due to where they are.
Do you happen to have another device on hand so that when your pc or laptop appears to lockup, you can have a quick look at the modem or attempt to cruise the net? I'm wondering if there is any possibility of a cryptocurrency mining program running? That might happen if you happen to be on a web page that is loading the mining application without notifying you, which is pretty common these days.
Running a quick check with another device would confirm or deny that theory. Seeing the same issue on another device would definitely confirm a modem issue.
Is this occurring on an ethernet connected device, wifi connected device, or both?
Ok, can you have a look at the additional Edit section above. One way to demo this would be to run pingplotter to capture the events. If you're up to it, have a read thru the following post and give it a go. You don't have to buy a licence for pingplotter unless you want to, and, you can always unload it.
http://communityforums.rogers.com/t5/Internet/Intermittent-disconnects/m-p/364602#M35528
This would be useful to run as it can be used to display ongoing events. If you arrive at a point in time where this starts, stops, starts, stops, you could call tech support and ask the CSR to ping the modem from the CMTS or ping the CMTS from the modem. When you see packet loss occur due to the problem, the CSR should see the same event. Hopefully that will cue the tech to look at other modems connected to the same tap, and look further afield to see if this is more of a widespread issue.
In cases like these, persistence is important to seeing that this is resolved. There's something that isn't right but, whatever it is, it hasn't failed completely, which would make it much easier to find. So, at this point in time, its going to be a complete pain, but, don't stop calling it to report the problem as it will build a history of poor performance.
@Raps_in_4 beyond pingplotter, you can run a DNS Monitor program to watch for UDP issues. From my testing, the 4582 does not have UDP DNS issues and I've run more testing than the DNS Monitor program does, unless you run it for weeks.
The DNSMonitor program can be found here:
http://www.tallsoft.com/dnsmonitor.htm
Hit the download link on that page to go to the download and then hit the download link for the .exe or .zip file. The middle link that indicates DNSMonitor actually points to a ping test program, so, use the .exe or .zip link.
The program is a little old and only does IPV4, but, you can run multiple DNS queries to Rogers, Google, OpenDNS, etc, etc. It only runs each query at 1 query per second, although the company claims that it will run queries at 0.5 second intervals. I've tried that and couldn't get it to run at 0.5 second intervals.
So, first step would be to use Pingplotter to look for disconnects and packet loss. If those are evident, then thats the first items to address.
If there is no disconnects and you have a UDP problem that affects DNS lookups, then that should be evident in these results.
When you start the program, navigate to OPTION ..... ADD DNS. On that pop up panel, the bottom section marked "Dns" is the only part that really counts. In there you add the domain name that you want to query, www.google.com for example, leave the DNS Record type at "A" and add the Rogers DNS server in the bottom entry panel. You could add an Item name so that you know what name is being queried or what Domain Name Server is being queried.
Rogers has two IPV4 DNS ip addresses:
64.71.255.204
64.71.255.198
I just tried both with DNSMonitor and the first one failed with a response that the request was refused for policy reasons. Huh??? Thats the first that I've ever seen that. The second one runs fine. So, if you happen to have the both listed as a DNS source, with the first one being 64.71.255.204, maybe the query from the pc is being refused, in which case the second one should be used. This is a little odd to say the least. I don't use Rogers DNS, so if there is anything odd going on with those servers I wouldn't normally be aware of any issues.
If you run a config/all command at a command prompt that will show if you are using IPV4 or IPV6 for the primary address and what the DNS IP addresses are. If you're running IPV4 only, and have 64.71.255.204 as the primary address, consider changing both addresses to Google or OpenDNS for test purposes.
Watching the results as I type this up, using Google DNS to lookup up www.google.com, 1800 responses, no failures, as expected. Using Rogers secondary DNS, 1650 response, no failures, as expected. I personally find the secondary Rogers DNS to be slow, averaging 37 ms for a response time while google averages 18 ms. That could be caused by the physical location of Rogers secondary server in relation to Ottawa. I don't know where its located but its always been slower than the primary Rogers DNS.
- last edited on by
RogersTony
So looking at PingPlotter, I've noticed that I experience huge ping spikes (500-800+) whenever the loading issues surface. I'm not sure how to read the packet loss data (I've saved the reports).
Here are some screenshots: 
*** Images not approved due to personal IP addresses visible ***
You would have to contact someone at rogers, you can try messaging @CommunityHelps
But any offers for replacement of services, were offered a LONG time ago when Shomi was canceled... they may not be offered anymore.
- last edited on by
RogersTony
@Jmckinnon, only if you have a filter set up in the modem to block that website. Other than that, only reason that comes to mind is the DNS that you're using, which can be set in the modem or in the device. Its possible that the DNS isn't resolving the address.
Hey @Shafeen,
Considering you upgraded your service and equipment, I can certainly understand your frustration. I wouldn't be pleased either in the same scenario.
With that said, which modem were you upgraded to, the CODA-4582? Were you able to review some of the solutions provided on this thread? Particularly, the one provided by our Res Expert @Datalink? If not, have a look at post #54. Give it a try and let us know if it resolves your issue!
Kind regards,
RogersCilio
-
52363 views
-
16 Likes
-
-
