@Datalink apparently I spoke too soon. After 4 days of no issues at all, today my internet dropped twice again just like the old time before we made any changes. Event log:
|9||07/11/16 21:09:57||82000200||critical||No Ranging Response received - T3 time-out;|
|10||07/11/16 21:09:57||82000300||critical||Ranging Request Retries exhausted;|
|11||07/11/16 21:09:57||82000600||critical||Unicast Maintenance Ranging attempted - No response - Retries exhausted;|
|12||07/11/16 21:10:00||82000200||critical||No Ranging Response received - T3 time-out;|
|13||07/11/16 21:10:01||82000300||critical||Ranging Request Retries exhausted;|
|14||07/11/16 21:10:01||82000600||critical||Unicast Maintenance Ranging attempted - No response - Retries exhausted;|
|15||07/11/16 21:10:02||82000200||critical||No Ranging Response received - T3 time-out;|
|16||07/11/16 21:10:02||82000300||critical||Ranging Request Retries exhausted;|
|17||07/11/16 21:10:02||82000600||critical||Unicast Maintenance Ranging attempted - No response - Retries exhausted;|
|18||07/11/16 21:11:24||82000200||critical||No Ranging Response received - T3 time-out;|
|19||07/11/16 21:11:54||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;|
|20||07/11/16 21:11:55||73040100||notice||TLV-11 - unrecognized OID;|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||BandWidth|
|1||38596000||ATDMA - 16QAM||38.210||3||3200000|
|2||30596000||ATDMA - 16QAM||38.250||1||6400000|
|3||23700000||ATDMA - 16QAM||38.250||2||6400000|
At this point I have no idea what to do. I think we've tried everything...
Your signal levels are good at this point, but, its definitely possible to see fast drops in levels if there is an intermittent cable fault. It would be much easier to troubleshoot if the cable simply died once and for all. Would you happen to know if the tech replaced the cable on his or her last visit, and if not, what was done? If the cable wasn't replaced that should be the next step as you have already replaced the modem.
Are the interruptions long enough that you would have time to call tech support or does the modem go down and then reestablish comms with the neighbourhood node on its own? If its dead, don't touch the modem. Leave it as is while you're on the phone to tech support. Ask the CSR to run a signal check to determine if the problem is with your cable or if its a bigger issue that would affect your neighbors as well.
One other check is to look at the modem to node performance. You can test that by using pingplotter, or WinMTR. Pingplotter is available from pingplotter.com. It will run in pro mode for about 14 days and then downgrade to free version if you don't buy a licence for it. There are free, standard and pro modes available, so you can go freebie version or buy a licence for one of the other two modes. Running pingplotter will allow you to determine if there are any issues from the modem to the neighborhood node or beyond, to your selected target, which could be a gaming server, google, or any other server of your choice. There is a File ... Save Image function that will save the current image, which can then be inserted into a post so that we can see if there any any problems between the modem and neighborhood node or beyond.
WinMTR is a text version of a network test and will show the trace to the target and times to the target. Same idea as pingplotter though, it can be used to look at intermediate hops, such as modem to next node to determine if there are any problems just reaching the neighborhood node. This can be downloaded from https://winmtrnet.codeplex.com This is an updated version that can be used for IPV4 or IPV6 traces.
In either case, if you run the program at various times of the day, morning, noon, early evening, late evening, you will soon see if there are patterns to the problem times, such as in the evening when people are home and the load on the neighborhood node increases. This can result in poor download rates, high ping times and out of spec signal levels.
So, in either case, you can post the results in the forum, text or image for us to have a look at. The image will require moderator approval to make it avaialable to the public but that isn't a problem. If you use either pingplotter or WinMTR, look for IPV6 addresses in the trace. If you do have IPV6 IP addresses, save the image and then open it with something like MS Paint. Wipe out the IP address on the first line which will be your modem's IPV6 address. I prefer not to leave those out in the open, for your own online security.
If you happen to load pingplotter and use it, input a server address of your choosing, and let the test run for 200 pings or more. When its running, right click on the top title bar that shows the column headings and select MAX from the popup menu. Drag that column over and park it next to the MIN column so we can compare the two fields. At the top there is a Focus drop down selection menu. Select that and choose "All" to use all the data in the average ping time calculation. On the bottom, right click and select something like 10 minutes for the bottom time display.
@Datalink I agree it would be easier if it went down and stayed down, but it will not.
The technician replaced the entire cable length from the pole across the street to the pole on my side of the street, and then the wire from that pole to my house (it's currently going through my neighbour's tree, but he said they'd come within a month to re-bury the cable).
The wire in the house was run when I moved in 5 years ago, directly from the side of the house through the drop ceiling in the baesment to the modem. I helped the tech trace the old cables and run the new one.
I never touch the modem when it happens, as it always solves itself within 5 minutes (whether I'm home or not). So unfortunately there's no way I can make it stay in that state that I can think of.
Ok, then there might be something going on further upstream. I understand what you're saying about the length of time that the modem goes down. If you're around when that happens, see if you can get in touch with tech support before the modem springs back into action. Hopefully that might resolve the issue, or at least get the field techs looking in the right direction. You should ask your neighbors if they're on Rogers cable as well and are seeing the same problems.
@Datalink thanks for all the help but I plan to move within the next few months so I'm just going to leave it alone.
The internet was down in my area for over 12 hours, and is once again down. In general, my area has absolutely horrible service from Rogers; it goes down a minimum of once a month, but typically more.
Compound that with my modem issues (which have indeed improved since you helped me, but still occur about once a week), and I think it's just a full failure of Roger's infrastructure in that area. I'm not convinced they have the ability to solve it within the next few years either, since it's been like this for the last 5 years that I've been there.
If anyone ever stumbles across my old post, moving solved the issue.
I've been using the same identical setup as my old house in my new house for the last 9 months, and I haven't had this issue once (internet dropping randomly).
I've had other issues though which I will post about. So this specific issue is undoubtedly a local infrastructure problem in that area. I'm not sure if Rogers will ever fix that.