Hello Em0gurl31,

I suggest to use either the web UI of the EAP or the Omada mobile app to manage your EAP. The Omada Controller is a business-class solution for managing a large number of EAPs and it requires basic knowledge of IP addresses and networking at least (ignore the note about layer 2/3). If you want to use the controller anyway, please google for IP addresses and HowTos to set up a home network, the Internet is full of recipes. For example, see https://en.wikipedia.org/wiki/IP_address

Hope this helps.

Hi Em0gurl31,

the IP of the controller is the IP of the PC which runs the controller, so you need to look up the controller's IP in your PC's network settings.

I admit I don't know Windows (and I'm glad to not have to). Microsoft products are strictly banned from my office/home since last 40 years.

Thus, other people know better than me, for example see this recipe for Win10. IP settings in Win10 are only 14 clicks away.

Alternatively use the UNIX way. Under the engine hood all Windows versions since Win NT actually use a UNIX-like core, albeit Microsoft won't tell you, else their customers would head over to UNIX-based MacOS or even Linux OS and save their money. So, open the cmd interpreter (also called »DOS window« or »command interface«) and enter the command ipconfig. It will show you the PC's IP in just one step.

Next, find out the EAP's IP. Log into your router and search for »active DHCP leases« or »connected devices« or something like this.

Once you know the EAP's IP, ping the EAP from the command line. ping is a UNIX command, too. If the ping succeeds, but the controller still doesn't see the EAP something in Windows prevents communication between the EAP and the controller. Windows is great in preventing communication.

If all this fails, consider to use an OC200 instead of the software controller. It's not that expensive and you save a LOT of time compared to fiddling with crazy Windows stuff. Just connect the OC200, go to it's web UI and there you are. OC200 runs Linux, thus it just works™.

For vouchers to work you have to run the controller 24/7 anyway and I really doubt that Windows can run 24/7 for more than a few days until it reboots or crashes (friends condemned to use Windows told me so).