NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot access router configuration page after configuring WAX206 as AP with static IP
I have tried many things, but I couldn't manage to get back access, so here I am. I have configured my Essentials WiFi 6 (WAX206) as an Access Point and with a static IP address setting. I cannot re...
Head to the Network Connections ...
Image credit: Tom's Hardware
I am not sure how this helps. I currently cannot access the router configuration interface, and I would like to regain that access.
- Think about doing a factory reset? And become clear if you need the WAX206 as a router or as an access point 8-). Figuring out if the intended IP address is available on your network is another task.
Factory reset shall be the last resort. I had went through several hoops to change the router's region (locked to the location of purchase, Japan) to match my actual region (Europe). I also had fine-tuned many of the settings which I do not remember in full.
I'm curious why I cannot simply access the router configuration page by:
1) Connecting the router via Wi-Fi on my computer
2) Setting my computer's IP to 192.168.1.15, subnet mask to 255.255.255.0, and gateway IP to 192.168.1.1 on the network settings
3) Typing https://192.168.1.1 on my browser
I suppose it is because I configured the router to assume the IP address 192.168.0.100; the router probably doesn't recognize itself as 192.168.1.1... But then:
1) Setting my computer's IP to 192.168.0.15, subnet mask to 255.255.0.0, and gateway IP to 192.168.0.100 on the network settings
2) Typing https://192.168.0.100 on my browser
should work, right? But that doesn't work either...
I thought I knew enough about networking, but that's not true, it seems.
I really would appreciate and enjoy a solution other than resetting.
ThoAppelsin wrote:
1) Setting my computer's IP to 192.168.0.15, subnet mask to 255.255.0.0, and gateway IP to 192.168.0.100 on the network settings
2) Typing https://192.168.0.100 on my browser
should work, right? But that doesn't work either...
Your earlier assumption was this before:
IP Address: 192.168.0.100
Subnet Mask: 255.255.255.0
Gateway Address: 192.168.0.1Yes, some 192.168.0.15/24 (255.255.255.0) for example should allow the access - permitting the Ethernet adapter is really in this subnet, no other devices are on 192.168.0.100 and on 192.168.0.15 and on 0.1 ... what should be easy to be configured as a native IP subnet on this adapter. Certainly better than new guessing and trying .1.1 Avoid any crazy experiments with this clunky Windows ICS which can be cumbersome if the wrong KB patches are in place. Unless I'm very wrong, ICS is always routing, rarely pure bridging. So correct subnet masks are key. Don't forget both your Wi-Fi and your Ethernet is supposed to be in the very same IP subnet.
Starting from a region locked device - for whatever reason (because it was cheap?) isn't a good advise and start for experimenting.
In case you are concerned about the usability or reliability of ICS, consider to configure a bridge between your Ethernet adapter and the the Wi-Fi adapter instead.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
