NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR1000v2 running V1.1.0.22
Hi our home network was working well around 09:00 we all went out, on returning we had no WIFI signal, but use devices attached by CT5, no strange entries in the log, so we restarted the router, WIFI...
Is there a router and wifi at the ONT or this Grandstream box at all?
Be sure your using a good quality LAN cable between the modem and router. CAT6 UTP is recommended.
Try setting wifi channels to 1 and 40.
Try disabling 20/40Mhz Coexistence.
Be sure to disable any MAC Address randomizers on phones and pads while at home:
https://community.netgear.com/t5/Nighthawk-App/NETGEAR-Mobile-Applications-and-Apple-Devices-FAQ/td-p/2220015/jump-to/first-unread-message
Maybe try another factory reset as well.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
The Grandstream box only has a cat5 cable socket and a phone socket ( as we have Voice over IP telephone service as well and the cable between the Grandstream and the router is the cable supplied by Negear which arrived with the router. and the phone line was still up and working at the time of the problem but then again the phone can reset itself if there is a problem at the ISP end so one never knows what happened earlier in the day.
- If you're using the MAC access control then if you have private/random addresses on for the WiFi on individual devices then that will prevent them connecting as the MAC addresses will change each time they connect. Disable MAC access control, then disable the private/random addresses in the specific devices wifi settings, reboot the router then you can set MAC access control again
- Our phones are set to use the physical MAC number fixed in the phone so they do not change so always get provided with same IP address
- Without anything in the logs to indicate why it happened it'll be really hard to determine the cause. Monitor it, see if it happens again/how often it happens and see if there is any pattern you can determine e.g. time/day, when a particular service/application is used etc
