NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAC124 not able to login when it is connected to internet
Hello everyone,
Last december I installed the WAC124 (Firmware Version V1.0.4.6) in a relatively simple setup, the goal was to boast Wifi signal for the 1st and 2nd floor.
I left it as it's own network, so it has it's DHCP enabled (running two networks 192.168.0.x downstairs and wired - 192.168.1.x on the netgear).
I decided that I wanted to let the Netgear take full controll of the entire network with DHCP and its extra functions that are not on my main router - trying to log in on the netgear got me to all the different pages where it says: "Page not working" "Connection timed out" "Secure Connection Failed" etc depending on the browser. I already had "External management" enabled, but that gives the same errors.
Things I tried:
different browsers
different devices
turing it off and on again
factory reset
Offline login - WORKS!
so, i managed to get in the console, reconfigured everything after the factory reset, plugged the internet cable back in - locked out again.
took the internet cable out, and I was able to login again with the local admin account again, but I am not able to get it to work while it is connected to the internet.
To make sure it's not something in my network, I turned of my Domain controller (testing purposes) and the Pi Hole (also testing purposes) even though both of them shouldn't interfere.
I am stumped..... help?
You are messing around in dangerous territory with two routers and all that this can entail:
What is Double NAT? | Answer | NETGEAR Support
When it comes to the WAC124, you might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here:
Business Wireless - NETGEAR Communities
In the meantime you could visit the support pages:
Support | NETGEAR
Feed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.
You may have done this already. I can't tell from your message.
I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.It may be some time before the images land. To ensure that you aren't posting anything naughty, a Netgear moderator has to approve the pictures.
You can attach images to messages without any delay.
4 Replies
New day, new attempt trying the external management login, same result:
You are messing around in dangerous territory with two routers and all that this can entail:
What is Double NAT? | Answer | NETGEAR Support
When it comes to the WAC124, you might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here:
Business Wireless - NETGEAR Communities
In the meantime you could visit the support pages:
Support | NETGEAR
Feed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.
You may have done this already. I can't tell from your message.
I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.It may be some time before the images land. To ensure that you aren't posting anything naughty, a Netgear moderator has to approve the pictures.
You can attach images to messages without any delay.
Thank you for the reply!
The Double NAT was precicely the subject I am trying to change, but halted because of this issue (if I can't login when it's connected, it's not usefull to use it for my main DHCP server).
This weekend I should have some time where I can tinker and take the entire network offline (which is needed for this) - so I will see if that will make a difference.
Keep in mind that during the setup fase in December I was able to login on the Router, so this issue started somewhere in between (I believe i've last logged in around March on the configuration interface).
I have indeed browsed through the manual to see if I can find anything that could cause this issue, as of yet to no succes.