NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear WAX218 login page inaccessible
I hadn't tried to log in to my WAX218 for a while, but when I tried to this morning, I get sent to the default page on netgear.com. My DNS is set up to redirect aplogin.net to the correct address, and trying to access it with openssl's s_client feature gets me a "400 Bad Request" result. Has there been a recent firmware update? Anyone else see this problem?
10 Replies
rjmx wrote:
My DNS is set up to redirect aplogin.net to the correct address, ...
While using a wireless device connected to the WAX218, without encrypted DNS, the device does automatically resolve tp the AP LAN IP address.
rjmx wrote:
--- and trying to access it with openssl's s_client feature gets me a "400 Bad Request" result.
Impossible to answer, lack of any insight what fancy DNS tricks you have configured there.
Already tried to power-reboot the WAX218?
rjmx wrote:
Has there been a recent firmware update?
https://www.netgear.com/support/product/wax218#download shows v2.1.1.3 is current, since about July 2022.
Similar situation here.
Except the AP refuses to respond at all. I can power cycle the AP and can login and adjust settings for about 3 minutes. Then it stops responding.
WiFi continues to function, and otherwise you'd never know.
On the latest firmware last I checked a few months ago, and nothing new there from Netgear on the support page.
Ideas?
VW_Factor wrote:
Except the AP refuses to respond at all. I can power cycle the AP and can login and adjust settings for about 3 minutes. Then it stops responding.
...regardless of using the fancy names (prone to various DNS system and browser caching issues) or the known IP address? No fancy wireless or whatever bridge involved?
Double check you have no other device on your LAN sharing the same IP address, being DHCP, being static IP.
From the computer shell (cmd on Windows) what shows a
ping aplogin.com
Nothing fancy, simple network. pfSense router, TPLink switch and WAX218 on the switch.
Only notable changes was the switch was upgraded about 18 months ago, haven't attempted login to the AP since. The IP set in the AP does respond to ping, just the admin login webpage doesn't respond. Bypassing the switch to the AP (using another switch) allows login.
Pointing to the TPLink switch is doing something funny.
This likely has nothing to do with the AP at all, however I still need to find the time to investigate further.
Thanks.
To be honest, I'd completely forgotten about this. I don't try to log in to the device very often -- it just keeps working fine, and I rarely have to change anything. In any case, I just checked again, and I managed to log in fine (apart from the usual arguments with my password manager).
I'd guess it was some kind of transient problem.
I had a few minutes when I got home from work tonight.
As a test, I plugged the AP into my nearby PoE Switch (IP cam power/data from Mokerlink, it will not handle our WiFi load). Simply removed the ethernet cable from the TPLink switch and plugged into the PoE switch.
Immediately able to access the web login.
Switched it back to the TPLink, had about 3 minutes of access, then stopped responding.
Continues to function appropriately otherwise.
I must dig deeper.
So, no solution yet but at least I have a direction.
Early this morning, while the family unit isn't needing WiFi. I've done some preliminary testing.
I again moved the ethernet from the TPLink switch to the PoE switch. No response this time.
Factory reset the AP, config'd through the ConfigWiFi (only changed SSID and static IP to a different IP this time and set ConfigWiFi to perm).
Put it back on the LAN, through a Netgear GS105 switch.
Again, had a few minutes of response on the WebUI, then dead again. WiFi still functioning.
SSH responds and connects to the CLI. Can ping the IP of the AP.
Overall, I'm not sure I want to put in the effort of mirroring some ports and sniffing traffic. This AP has worked flawlessly for years now and I'm pleased with it otherwise. Shouldn't this just work as intended?
Not that I often require to login to the WebUI to make any changes, but it just bothers me that this basic feature simply refuses to function appropriately.Sidenote - I did leave the ConfigWiFi on perm, and I can use my notebook to connect to that WiFi interface and the WebUI responds here. This shouldn't be a work-around to this issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
