NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
RS700 pinging Google DND every 4-5 secs on AP Mode
I am currently using my RS700S in AP mode behind a pfSense firewall. I noticed the router is pinging 8.8.8.8 and 8.8.4.4 every 4-5 secs showing up in block alerts, more of nuisance than anything with it flooding the logs rather than any connectivity. I assume it's trying to check for an internet connection, but there needs to be a way to block/stop the RS700S when in AP mode. I assume this is not just the RS700 but other models probably doing the same as a lot of them share similar core firmware.RS700 - Firmware problems ongoing
Firmware version is currently v1.0.9.16 because the updated version v1.0.9.6 basically nuked the router and nothing would connect to the internet. I reverted it back to the v1.0.7.96 version and still had trouble getting that to work correctly. there is apparently a trial version firmware out there but I cannot seen to locate a legit download for it without contacting user: "BH_C NETGEAR Expert" Trial firmware v1.0.9.101_25.7.19 which is supposed to be for the RS700 fixes the issues described in multiple threads in this RS700 forum. I have discussed the issues for the better part of 4 hours with netgear support, being promised a call back, which never happened either time, and I had to call them back to try to fix the problems with the router. Then after being on the phone with them until 3:00am trying to fix the problem, they closed my case and the problems are still not fixed. Problems: #1. As others have stated, router is online and then loses connectivity (orange internet light) around 3 am and never regains stability until a reboot. Once the reboot is performed, not all devices will auto-reconnect to the network. #2. Netgear support in general is less than helpful and gives inaccurate information as to when a callback is going to happen, if it even does. When the router is being used for work-from-home functionality and is malfunctioning, that causes a serious problem, which was explained to their support reps as well. For some reason, this router went from being solid, to being a complete pillar of garbage after the firmware was auto-updated. Yes i do have a case number (closed by netgear without resolution) and yes I appear to be among the many people beyond frustrated and fed-up with the quality and service of Netgear products. If there is anything that will fix this problem, trial version or tested and proven, i am willing to try it at this point as setting up yet another multi-hundred dollar router is not an option for me and this router is less than a year old. Thank you in advance for any help anyone is able to offer on getting this fixed.RS700 DHCP Issues with newest firmware
I purchased an RS700 back in February and on the previous firmware I had the slow Wi-Fi issue and once I would login to the web UI and re-apply the Wi-Fi settings it fixed everything and seemed to be pretty solid. I upgraded a few weeks back to the newest 1.0.11.6 firmware and I have had issues with DHCP and devices showing no internet/IP configuration failure after a reboot. I reloaded the newest firmware from the web UI in Edge and completely factory reset the router and set it up from scratch and the issue remains. Anytime I reboot the router it takes me at least an hour to get it stabilized. When the router reboots I get an IP configuration failure on my Google Pixel when trying to connect and my desktop PC connects, but shows no internet. After waiting around 30 minutes I am able to get my desktop PC connected and when I log into the Web UI and go to attached devices I see many with either 169.x.x.x invalid IPs or else just 0.0.0.0 as the IP address. The fix I have found so far is to go into setup/wireless setup and re-apply the wireless settings and once I do that everything stabilizes usually within 15 minutes and all of my devices connect. I don't use the default DHCP pool so I define my own, but I did try using the default pool after the factory reset and saw the same issue. Is this the DHCP issue I saw in another thread or has that issue been fixed? Any help anyone could provide would be appreciated. Thanks!
