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 connect to router after switching to AP mode mode.
I know the IP but I can't connect... Netgear RAXE300 (AXE7800). No matter what I do (wired, static IP with it disconnected from the network, or connected to the network trying to visit from PC on the same network... timeout.)
First time I put it in AP mode while its IP was 192.168.1.1 and after reset, my (wired in) laptop wouldn't reconnect. I tried setting a static IP (e.g. 192.168.1.5) and still it wouldn't let me connect. Since my subnet at home is 192.168.0.x, I was afraid that hooking it in wouldn't work so I just started over with a factory reset, the set the router IP to 192.168.0.4. Everything still worked fine after that and I could access via web broswer.
Then, I put it in AP mode again. And, I can't access it, at all. To be clear, the IP is no longer 192.168.0.4 and I know that and that's fine. I can see it it my main router - it was assigned an IP of 192.168.0.221 by main router DHCP. But, trying to go to that IP doesn't do anything. Just a "This site can't be reached" message. Tried multiple browsers etc. Confirmed it's not my main router blocking or isolating IPs or whatever, as I can access a different AP (an AX73 router in AP mode) at 192.168.0.5 no problem.
Is it impossible to do anything with your routers after I put them in AP mode? Is the only way to get out of AP mode to factory reset? Please advise.
If your home subnet is 192.168.0.x, then you need to set a static IP address on the RAXE for a IP address on this same subnet. 192.168.0.30 would work in AP mode then access it's web page there. If you do this, the host routers Default IP address pool range should be set to .100 thru .200. Any static IP addressed devices needs to be outside of the host routers default DHCP IP address pool range.
https://kb.netgear.com/20927/How-do-I-change-my-NETGEAR-router-to-AP-mode
7 Replies
I'm having the same issue. It's like it won't let you connect at all once it's in AP mode? First time I put it in AP mode while its IP was 192.168.1.1 and after reset, my (wired in) laptop wouldn't reconnect. I tried setting a static IP (e.g. 192.168.1.5) and still it wouldn't let me connect. Since my subnet at home is 192.168.0.x, I was afraid that hooking it in wouldn't work so I just started over with a factory reset, the set the router IP to 192.168.0.4. Everything still worked fine after that and I could access via web broswer.
Then, I put it in AP mode again. And, I can't access it, at all. To be clear, the IP is no longer 192.168.0.4 and I know that and that's fine. I can see it it my main router - it was assigned an IP of 192.168.0.221. But, trying to go to that IP doesn't do anything. Just a "This site can't be reached" message. Tried multiple browsers etc. Confirmed it's not my main router, as I can access a different AP (an AX73 router in AP mode) at 192.168.0.5 no problem.So... what the eff Netgear? Is it impossible to do anything with your routers after I put them in AP mode? Is the only way to get out of AP mode to factory reset? Seriously stupid.
If your home subnet is 192.168.0.x, then you need to set a static IP address on the RAXE for a IP address on this same subnet. 192.168.0.30 would work in AP mode then access it's web page there. If you do this, the host routers Default IP address pool range should be set to .100 thru .200. Any static IP addressed devices needs to be outside of the host routers default DHCP IP address pool range.
https://kb.netgear.com/20927/How-do-I-change-my-NETGEAR-router-to-AP-mode
Is 192.168.0.221 not considered to be on the 192.168.0.x subnet? I'm confused. I was able to get into the web interface after setting a static IP on my main router and forcing the AXE300 to get 192.168.0.4 - no magically I can connect. I don't understand why 192.168.0.221 wasn't working (wasn't letting me connect to it) but doesn't matter I suppose.
I'm not sure I agree / understand why DHCP pool range must not include any reserved (static) addresses within it, but yes, my router is configured to start handing out dynamically at x.x.x.100...
I don't know how this reply ended up here - it was meant to be a reply to an older thread where someone was having the same issue. Sorry it looks weird. Any help or advice is appreciated.