NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't login to WAC124 any more
Hi, Today, I realized I couldn't log into the WAC124 any more, even though I've been able to do that for the past 3 years. I'm still able to use it as WiFi Internet access point, though. The ...
PC (static IP) 192.168.0.123 255.255.255.0 gateway 192.168.0.1 <-> WAC124 (DHCP) 192.168.0.100
-or-
Alternate approach block the WAC124 LAN IP on your router from the Internet access. This won't impact the Wi-Fi / WLAN access to the LAN
Essentially what I explained above already - operate the WAC124 offline!
Tom_G wrote:
When I try to login, the login/password are correct and accepted, I get the "Checking the Internet connection; please wait …", then it goes back to the login page.
I tried to connect a laptop directly to one of the LAN ports after disconnecting the router from the Internet (the yellow port), and opened the browser on www.routerlogin.net, but it can't connect (which is logical). I also tried to connect with the browser to 192.168.0.100, but it can't connect either. A ping to that address doesn't work, either. All that is normal since it's not on the network any more, and the modem is the device managing the network with DHCP.
Almost everything here is "logical" dear Tom_G - as this is about networking and computers, which commonly exactly behave as designed and implemented.
The routerlogin.net DNS query can be captured on the AP when the request does pass the device - it will return the device LAN IP.
The default 192.168.0.100 IP address is only in place in case there is no DHCP server returning a valid IP for your LAN IP subnet.
When operating the WAC124 offline - so no connection to your LAN with DHCP server - the DHCP client (permitting there is no static LAN IP defined) is likely fall-back to the default LAN IP 192.168.0.100 (/24, 255.255.255.0 subnet mask). This does require an Ethernet LAN config in that subnet, so 192.168.0.x (.1 ... .254) on your computer Ethernet adapter. At that point is no Internet connection, so the outdated Netgear Single Sign-on feature won't be active, but was defines obsolete and removed almost three years ago. Said this, with a correct network adapter config, and only a direct connection PC <-> WAC124, a login is certainly possible, without "Checking the Internet connection ...". At that point you can install https://kb.netgear.com/000065060/WAC124-Firmware-Version-1-0-4-9
Regards,
-Kurt.
schumaku wrote:The routerlogin.net DNS query can be captured on the AP when the request does pass the device - it will return the device LAN IP.
The default 192.168.0.100 IP address is only in place in case there is no DHCP server returning a valid IP for your LAN IP subnet.
I know its assigned IP, but it's apparently not possible to log into the WAC124 without using Netgear's remote server while it's connected to the Internet, so I have to disconnect it first before I can use the local admin login.
I'm using a modem/router, which is imposed by my provider, so the only way to remove Internet is to unplug the cable between the modem and the DSL filter, which would disconnect the Internet for everyone else. The other solution would be to isolate the WAC124 from Internet with the modem/router, but I doubt it can do that.
When operating the WAC124 offline - so no connection to your LAN with DHCP server - the DHCP client (permitting there is no static LAN IP defined) is likely fall-back to the default LAN IP 192.168.0.100 (/24, 255.255.255.0 subnet mask). This does require an Ethernet LAN config in that subnet, so 192.168.0.x (.1 ... .254) on your computer Ethernet adapter. At that point is no Internet connection, so the outdated Netgear Single Sign-on feature won't be active, but was defines obsolete and removed almost three years ago.
Ah, so that explains it. Netgear's basically sawn off the branch on which its product was sitting, not very smart (unless it's on purpose).
Said this, with a correct network adapter config, and only a direct connection PC <-> WAC124, a login is certainly possible, without "Checking the Internet connection ...". At that point you can install https://kb.netgear.com/000065060/WAC124-Firmware-Version-1-0-4-9
Yes, that's exactly what I'm asking. That's what I've been trying to do, but without any success (and I understand why it didn't work, since I explained the current DHCP configuration).
What are the owners of that device supposed to do after they shut down their server?
I suppose my only option is to temporarily disable Internet for everyone, or start messing with a local router and just a laptop and this WAC124, which I really would like to avoid. They could just have added a checkbox "local connection", but no, it would have been too user-friendly. An overall lazy design with a very limited guarantee.
Thanks for the link to the new firmware! I'll make sure to install that if I can get past the login.
PC (static IP) 192.168.0.123 255.255.255.0 gateway 192.168.0.1 <-> WAC124 (DHCP) 192.168.0.100
-or-
Alternate approach block the WAC124 LAN IP on your router from the Internet access. This won't impact the Wi-Fi / WLAN access to the LAN
Essentially what I explained above already - operate the WAC124 offline!
schumaku wrote:PC (static IP) 192.168.0.123 255.255.255.0 gateway 192.168.0.1 <-> WAC124 (DHCP) 192.168.0.100
I'm not sure what you mean by that. Nothing replies on 192.168.0.123.
Alternate approach block the WAC124 LAN IP on your router from the Internet access.Yes, that's what I said. I found out that I could use the parental control on my modem/router to exclude the WAC124 from the Internet access. So I could *finally* login locally.
Once I was logged in, of course it said there was a firmware update—but couldn't download it because it was offline. Another thing they didn't design properly (why propose a download in offline mode?).
Anyway, I'm upgrading it now and I'll see how it goes.
It's easily the most amateur job I've ever seen. My next network hardware won't be Netgear, for sure.
PS: I also tried to plug an USB key in and boot on it, no luck. I also tried to connect the WAC124 on another port than the yellow one, but it doesn't change anything. If it can't connect to the login server because it's not online anymore, why not give a correct status? Why not offer a local login?! It's just bad design.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
