EAP225 not showing in Controller
Hardware Version :
Firmware Version :
ISP : [/COLOR]
Router -> EAP225 -> PC (home user).
Unknown firmware version.
PC is running Win10Pro, and is using an Alfa AWUS036H wifi adapter.
I've set up the TP-Link Controller - no issues - but the EAP225 is not showing up as an access point (so I can't adopt it).
The EAP225 appears to be broadcasting 2 open networks.
I can see both on my phone, and connect to them, but I can't see either of them in the list of available networks on my PC.
Other networks are showing up fine, and the AWUS036h supports b/g so should see the 2.4GHz one, right?
I'm too far from the router to get the default wifi, so I've dragged a long LAN cable from the router to my EAP.
(Works great with the AirportExpress AP I was using, but that drops a 12MB/s connection to a <1MB/s, I was hoping this EAP225 would speed things up).
Please help me set this thing up.
If you can see the EAP's WiFi network on your phone, but not on your PC, the problem is with your PC or its WiFi card, not the EAP.
Originally Posted by dean0048
In order to have the EAP Controller (EAC) see a pending AP, the EAP needs to know the IP address of the Controller. Use the EAP Discovery tool to configure the EAP so it connects to the EAC.
In my router's settings I went to DHCP settings and clicked "force available" for the MAC address of the EAP.
It then showed up in the Connector and it's adopted and listed as Connected.
My AWUS036h is 802.11b/g, and apparently 802.11ac only falls back to /n, which is the one letter the awus is missing.
So I ordered a TP-Link Archer T2U ac WiFi adapter. That should have everything up and running soon - on my phone it has doubled download speeds