I returned the first WAX206 thinking it was faulty, but the replacement has the same issue. When I configure it in 'router' mode, it works fine. However, when I change the mode to 'access point', it 1. loses internet connection, 2. can't be accessed via administrator menu, 3. must be reset to restore 'router' mode. The router is connected to a Netgear Cable Modem CM1200. I have Cox coaxial cable ISP.
I beleive puting it in "access point" mode is essentially making it act as a bridge. Have you tried connecting it to your router via a LAN port rather than the WAN port? The WAN port is typically only used when in router mode.
Great suggestion! But unfortunately that didn't work. The router just loses internet when in access point mode. The modem shows internet is good. I've tried turning the modem and router off and on. I also reset my modem. What am I missing...
1. Is the DHCP server running on your cable modem (CM1200) as that will become the primary router once WAX206 is in access point mode?
2. Are you attempting to access the WAX206 over WiFi or cable? When troubleshooting, it is sometimes better to reduce the variables so going cable helps.
My next steps would be to cable in to the CM1200:
1. See if the DHCP server on CM1200 has allocated the WAX206 an IP address.
2. Try to connect to connect to the WAX206 from the CM1200 (remember to use https).
3. Check that DHCP server on the WAX206 is disabled, otherwise all it's clients won't have internet access as the gateway (WAX206) has no WAN to route to.
I was not seeking help but wanted to assist the person that logged the original ticket. I also own a WAX206 and been doing some troubleshooting with device in AP Mode and believe I have found a solution.
Not sure what made you think I was queue jumping - just wanted to help and wanted to make sure the person was still around before wasting time entering the steps I had taken.
But nevermind - you have already scared me off this forum.
Netgear... great products - but lousy Forum monitoring.
I admit I thought you were kind of "thread jumping" a little because you used the phrase "I'm having similar issues" rather than "I had similar issues", a minor difference I know. However, I believe it would indeed be welcome to share your solution as it might help the original requestor or another person that comes along with the same issue.
Like you, just trying to be a decent human and help where I can.
@rschilt Not trying to discourage you from posting but when people thread jump, it gets their info confused with the OP's info. Which makes it harder to help the OP if they continue to have issues. Again, we're happy to help but just start your own thread
I appreciate the work of the community moderators here, but I'm happy to respond. The issue was me, not the WAX206. I was going modem-to-WAX206 and trying to run it in AP mode. I was told it can't be done like that. I need to go modem-to-router-to-WAX206 if I want to run it the WAX206 in AP mode. My bad.
This worked fine for me except when "Turn on Access Control" and "Block all new devices from connection" were enabled on WAX206 - the WAX206 would lock up (same as what you reported initially) which required a reboot of WAX206 for it to work again.
When this was happening my router / modem was a pfSense appliance.
I have since switched my router /modem to an IPFire appliance - with Access Control restrictions set on WAX206 and the lock up error on WAX206 does not happen.
Robert
ps: apologies to the moderators for overacting yesterday.... must be a challenge at times keeping order in the house.
Okay, but your set-up isn't the same as the one I was attempting. Mine was Modem (CM1200) => Router (WAX206) in AP mode. I'm not being argumentative here, just making sure other readers see why my set-up wasn't working. I needed another router in between if I wanted to run the WAX206 in AP mode.
