NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
driver8
Nov 12, 2022Aspirant
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. ...
schumaku
Dec 21, 2022Guru - Experienced User
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).
At no point Netgear does promote using any kind of shell access (AFAIK there is none out of the box).
Mike0000
Dec 29, 2022Aspirant
*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
- olly_thomasDec 30, 2022AspirantMike, If you reboot it can you get to the config-only ssid? If so, try disabling any WPA3 and set back to WPA2 only.
- n0t_gearJan 28, 2023Aspirant
Same issue here. I have 3 WAX214s. POE, IPv4,WPA2. I've tried static addresses and DHCP. I can ping all 3 successfully. WebUI works for a while then doesn't. Occasionally, repeated refreshs on the browser will bring up the WebUI but usually quicker to just reboot the device.
nmap also shows the ports (80/443) as filtered.
Not shown: 992 closed ports
PORT STATE SERVICE VERSION
53/tcp open domain (generic dns response: NOTIMP)
| fingerprint-strings:
| DNSVersionBindReqTCP:
| version
|_ bind
80/tcp filtered http
443/tcp filtered https
554/tcp filtered rtsp
1935/tcp filtered rtmp
5000/tcp open upnp MiniUPnP 1.9 (UPnP 1.1)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!