NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WAX214 stops accepting management connections
I have three WAX214s installed at my premises, and two of them manifest a symptom whereby after a relatively short period of time, maybe 15-20 mins, they stop accepting connections for management. ...
Just installed mine and am hitting the same issue. I wrote an expect script to change the password daily on a guest SSID.
basically does this:
wax214>ssidp 4 apsecu 6 passp <passphrase>
wax214>ssidp 4 apsecu 6 accept
wax214>reboot
I left it using WPA2/WPA3 security, the rest of my manually configured SSIDs use WPA2 only. I lost my management connections via ssh and http. I was only able to get to the GUI via the config SSID.
When I saw your post, I spotted you used WPA2/WPA3 - I thought I'd set it to WPA2 via the config SSID gui and management started working again on the LAN.
Yes, the conclusion I have come to is that there is something wrong with Netgear's WPA3 implementation. I also have a couple of EAX12s (which also have other significant flaws in the current version of their firmware), and if I try and use WPA3 on these the wireless clients continually disconnect, whereas with WPA2 there is no problem.
Although Netgear get some things right (hardware is decent and support website is pretty good), their firmware is unacceptably poor and buggy.
- Connecting to the management Web UI from clients associated wireless or does the same.issue exist on the world network?
IPv4 or IPv6 local link or static IPv6 ?- Status IPv4.
- It's amazing how people walk ways off the product documented and intended usage.
At no point Netgear does promote using any kind of shell access (AFAIK there is none out of the box).*bump*
I have the same problem as the OP, where I have a Netgear AX1800 WAX214 which stopped responding on the web UI.
The AP is powered through PoE (connected to a Netgear GS324TP), successfully obtains its IP via DHCP from my router, and allows clients to connect via WIFI and passes on traffic.
A ping of the IP is successful with ping times of 3-4ms.
There are no firewall rules preventing the access of the AP.
The issue is that I want to be able to access the web UI to configure the AP, but typing the IP into the browser results in a timeout error:
* Firefox: "The connection has timed out. The server at [192.168.5.123] is taking too long to respond."
* Chrome: "This site can’t be reached. [192.168.5.123] took too long to respond. ERR_CONNECTION_TIMED_OUT"
* Edge: "Hmmm… can't reach this page. [192.168.5.123] took too long to respond. ERR_CONNECTION_TIMED_OUT"
Is there a solution to this problem, or should I consider the AP faulty and request a replacement?
Thanks
Mike
- Mike, If you reboot it can you get to the config-only ssid? If so, try disabling any WPA3 and set back to WPA2 only.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
