I've got SDN set up as a service on Windows 10, which all starts well. However, even though the SDN starts, the 4 EAP245 I have remain disconnected. It's as if the service did not connect to the network? I can login to the web mgmt page and use all the functions etc but the devices show as disconnected.
If I launch the SDN as normal through the start menu, then everything works fine, all EAP245 adopt and connect.
My Omada controller version is 4.2.8. My EAP245 are v3 and on firmware 5.0.0.
Any ideas what makes the service start not connect?
In the logs, I see the below difference...
Main Administrator logged in to the controller from 0:0:0:0:0:0:0:1.
|this is when i launch from the start menu, and everything works|
Main Administrator logged in to the controller from 192.168.0.181.
|this is when i launch as a service, and eap245 don't connect|