Reply
Regular Member
Posts: 430
Registered: ‎06-08-2011
Kudos: 143
Solutions: 11

Windows firewall update is blocking discovery

I've done lots of adoptions at various sites and only run into this problem in the last week or so. My best guess is that a Windows update has tweaked the firewall such that it blocks the protocol and port necessary for discovery.
I have found this to be true on a Windows 7 and Server 2008 box. No amount of rebooting or resetting the AP (and I tried a number of them) makes them discoverable. Turn the firewall off and they show up immediately. Turn the firewall back on and they cannot be discovered.
Once they have been adopted (with the firewall off), you can turn the firewall back on and management works just fine.
Ubiquiti Enterprise Wireless Admin
Regular Member
Posts: 430
Registered: ‎06-08-2011
Kudos: 143
Solutions: 11

Re: Windows firewall update is blocking discovery

I spoke too soon about everything being OK after turning the firewall back on. It is not. The AP now shows as disconnected just as Alpha_DS reported in his post:
forum.ubnt.com/showthread.php?t=47262
Can somebody tell me exactly what protocols and ports are required for the beacon to communicate with the controller?
By the way, turning the domain firewall off on the Server 2008 machine immediately restored the connection between the AP and the controller but threw the AP into provisioning mode. It came back online after about a minute.
FYI: controller version 2.2.3. AP firmware version 2.2.3.1055
Ubiquiti Enterprise Wireless Admin
Regular Member
Posts: 430
Registered: ‎06-08-2011
Kudos: 143
Solutions: 11

Re: Windows firewall update is blocking discovery

Got it! Sorry for the thinking-out-loud thread but it will probably help someone else along the way. The Windows firewalls were blocking "Java Platform SE Binary". Allow that and all is good. Whether this is the result of a Windows update or not I'm not sure. All I know is that it used to work and quit working recently on my Win7 machine. The 2008 Server I mentioned was recently installed so I believe the firewall settings are default.
Ubiquiti Enterprise Wireless Admin
New Member
Posts: 1
Registered: ‎11-04-2015
Kudos: 1

Re: Windows firewall update is blocking discovery

I know this thread is old, but thanks so much for posting this. I am new to Ubnt products and couldn't figure out why the Unifi controller couldn't connect to APs through the Windows firewall even with openning port 8080.

 

Turns out Java Platform SE Binary was blocked in the firewall after a recent Java update.

 

 

New Member
Posts: 1
Registered: ‎06-13-2016

Re: Windows firewall update is blocking discovery

[ Edited ]

Wow, I've been scratching my head on this one and this post solved it. In the windows firewall you need to disable the extra block rules for the Java(TM) Platform SE Binary. These block the connection between the AP and the controller even if you have the other ports allowed. Thanks hendjosh!

 

New Member
Posts: 1
Registered: ‎03-26-2016

Re: Windows firewall update is blocking discovery

That was the issue for me, too, even years later than the original posts. Now I just need to figure out why there seem to be so many duplicate entries in the firewall "allowed programs" table for "Java SE Binary." If anyone is stil reading this thread, I'd also like to know whether Java SE Binary needs to be allowed for private networks only, or public, too. In any case ... it's working for me again, so thanks! ... Ron Nelson

Highlighted
New Member
Posts: 1
Registered: ‎09-25-2018

Re: Windows firewall update is blocking discovery

Keeping this thread current. 

 

It appears a Windows Defender update on 10.29 or 10.30.2018 changed things, and the UniFi controller could no longer communicate with the devices.

 

I allowed the connection to Java Platform SE binary and it appears to be working again.  Keeping my fingers crossed!

 

Reply