@Ne. Hi I've read many related ports before.

Many people have this issue because the new controller version need to use port 29814 to adopt the devices.

Old version controller only use 29810-29813.

So you may need to check the PC firewall settings and make sure there is no limitation on these ports.

Some details.

Related posts.

  @Somnus 

Thanks @Somnus for your reply. This one seems it might be a bit different. I had already created allow rules for TCP and UDP ports 29811 - 29814.

I can see the process is running:

tasklist |findstr "java.exe"
java.exe                     13504 Console                    1    742,004 K

is listening on those 4 original ports:

netstat -n -o -p | findstr "13504"

  TCP    [::]:8043              [::]:0                 LISTENING       13504
  TCP    [::]:8088              [::]:0                 LISTENING       13504
  TCP    [::]:8843              [::]:0                 LISTENING       13504
  TCP    [::]:29811             [::]:0                 LISTENING       13504
  TCP    [::]:29812             [::]:0                 LISTENING       13504
  TCP    [::]:29813             [::]:0                 LISTENING       13504
  TCP    [::]:29814             [::]:0                 LISTENING       13504

I can also see the connection establish when it goes from Adopting to Provisioning: 

TCP    [ip.add.of.omada]:29814     [ip.add.of.wap]:52634        ESTABLISHED     13504

Any suggestions? :)

  @Ne. 

Please check below :

AP connectivity to the Controller - make it sure they are on the same LAN

If you have network filtering for traffic going to the internet - make it sure the IP address of the concern AP is allowed.