NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk X6 - Model R8000 INTERNET repetitive disconnects with no log
Hi my router worked well after the last firmware update some months ago. Firmware V1.0.4.12_10.1.46 . Then about 10 days ago it has started disconnecting very frequently and repetitively, and reconnecting and disconnecting etc.... I see no log about the disconnect /reconnect in the router log . Only Genie shows no internet connection. I thought it was attacks but the logs don't show attacks at the same time. Internet frequently comes back after few minutes and falls ago few minutes later. My provider says it sees nothing. But has a visit scheduled this weekend. Earlier this afternoon internet did completely go off for a while and would not come back by itself for many minutes. The modem (provided y the provider ) then had the online led off. I resetted(turned off and on) the modem and it worked after many / multiple resets. The provider also resetted it. as I was on the phone with it. When restarting the router the internet reconnection appeared on the log. Could it appear every time I get disconnected? What could the problem be? how to fix it? Thanks!
Hi, thanks James. I did install it earlier today.
I imagine that it must be related to the security issues in the news.
supposed to allow auto update of the firmware too.
Hopefully all goes well and keeps hackers at bay.....
But also this morning I had the visit of my 3rd technician and I am hopeful it is going to be finally working well.
First technician did some connections tightening and changes and changed my modem to another thomson. Not better five minutes after he left
I went to mediacom shop the next day to get another modem, arris, better.
2 days later second technician was helpful finding out and telling me there was a capacity problem sometimes (that appears in logs at the provider) and that he was going to ask to be looked at.
Then nothing happened during 2 weeks and still internet often bad.
No news about capacity increase when I was asking and it did look like problem was still too present to be only that.
Called and complained last week and Surprise: Third technician rings at the door this morning today.
I think he did a good job, very methodical, replaced some cables that were dammaged from ?rabbits, checked every connection and splitter. changed several. Noticed also I was using a ethernet cable from modem to wifi that was maybe a limiting factor in the speeds and not related to the drop we think
Very happy with him. Very hopeful. No issue for the last 12 hours and I saw the firmware and updated.
So modems might be more or less performant with a bad signal but I think 2 main factors to my problems have been
-coax dammaged and connections loose or deficient (hopefully all fixed for the moment)
-maybe capaicity
To have an increased capacity provider must do increase of capacity and it might not happen soon but I will be challenging them if problem
Also I have a 8 channel modem, might go and buy a 16 channel one. Hearing it could help.
If I think about the technicians I have had,I have seen others and none was as professional as the one today I think and I had given up on a TV problem (frozen frames) on TV for the last 2 years, getting worse last 2 moths while internet also underwent issues leading to this post.
Will check whether it improved or still happens.
Pretty thankful to the technician of this morning also I have learned a lot thanks to talking to them and this chat. Thankful to this chat too.
53 Replies
NGbaby wrote:
I resetted(turned off and on) the modem and it worked after many / multiple resets.
Power cycling, the process you described, is not the same thing as a full factory reset.
New firmware sometimes introduces changes that are not compatible with the old configuration.
So while it isn't guaranteed to fix problems a factory reset is the first thing to try if you have issues with new firmware.There is a manual for the R8000 somewhere at the end of this link:
>>>>> R8000 | Product | Support | NETGEAR <<<<<
See pages 11 and 189.
This is nuisance because you then have to reconfigure the device all over again. (Trying to restore a backup configuration can just bring the bug back from the grave.) But it has rescue many a victim from the symptoms you describe.
Thank you. I am going to have the factory reset as last alternatve. I did it in March when having internet completely disconnected and doing firmware update . After that it worked for several weeks well. Why suddenly it would not work? Maybe some provider issues that I would like to pinpoint. But factory reset is an alternative to try at some point. Thanks.
If you do have Internet up, most Modems can be accessed at 192.168.100.1 and do not seem to have access controls or if the do use ADMIN and PASSWORD for entry to view the modem status and logs. You might find some info there at to who is going down or causing the router to lose connection. If that doesn't work, Google "xxx modem 192.168.100.1 username and password" and change 'xxx' to the make of your ISP modem.
As in most of these things, when talking about routers it would help if we knew what the modem is. Simply saying "provided by the provider" could be anything.
In my case, 192.168.100.1 gets me nowhere. Nor would I expect it to. (It is a modem-router on modem only mode.)
Would a modem show up on the router's map of attached devices?
michaelkenward, I've got an Arris TG1672G from my ISP. It is a bridged modem/router/eMTA unit. It does work for me... see JPG attached.
No, the MODEM does NOT show on the router or as an attached device.
My router is at 192.168.1.1, and I can PING both it and the modem:
C:\>ping 192.168.100.1
Pinging 192.168.100.1 with 32 bytes of data
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms
