Unifi - can't adopt APs when setting up a new controller

Unifi controller 2.x.x. was on an SBS 2003 server controlling 5 APs

we upgraded it to 3.xx and then to 4.6.6 and backed up the config to a thumb drive.  Disconnected the SBS box.

replaced the sbs 2003 with an essentials 2012R2.  Installed 4.6.6. controller on that box.  loaded configuration.  it lists the APs as adoption failed.

I went into each details / advanced options , entered username / password as ubnt / ubnt clicked adopt.  still adoption failed.

I found this page:

https://community.ubnt.com/t5/UniFi-Wireless/UniFi-AP-firewall-settings-for-Windows-Server-2012-R2/td-p/1090855

ran the script in PS (PS opened as admin).

repeasted the adoption steps and still adoption failed.

turned off windows firewall, repeast adoption steps, still adoption failed.

the APs have solid green lights.

I had already power cycled them (pulled injector AC power for 15 seconds, then reconnected AC power.)

thoughts?
BeGentleWithMe-INeedHelpAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BeGentleWithMe-INeedHelpAuthor Commented:
Ah, I got 1 adopted...  interesting. that one shows firmware of 3.2.12.2920.  the other machines show version of 2.3.9.1693.

the controller is 4.6.6  any issues with trying to control older APs with the new controller software?

if so, how do I update firmware?
0
Dirk MareSystems Engineer (Acting IT Manager)Commented:
http://dl.ubnt.com/guides/UniFi/UniFi_Controller_UG.pdf

Page 41 (44 of 57)
Adoption of devices managed by other

DirkMare
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BeGentleWithMe-INeedHelpAuthor Commented:
Thanks.  the status on these APs is 'adoption failed'.  not 'managed by others'. : (

again, the firmware on the APs is old.  I want to upgrade the firmware first?

But using PUTTY, connecting to the IP of the AP shown on the controller device page (version 4.6.6.) a black window opens, but no prompt for user name

There's 1 AP that has current firmware somehow... and that one I can ssh into, get the prompt for username.  So I know putty is working / can reach the APs.  I can ping the APs also.  Just can't get them to prompt for username in SSH.
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

Dirk MareSystems Engineer (Acting IT Manager)Commented:
Firmware can only be upgraded using the controller from the Manage AP tab.

I only have two recommendations..

Reset AP's to factory defaults, adopt AP.
Start from the beginning,

1. Install controller version 2.x.x and adopt AP

2. Upgrade to version 3.x.x and allow enough time or manually update the firmware

3. from version 3.x.x upgrade to version 4.x.x and make sure AP upgrade..


As far as I can tell and with working with my unifi with controller version 1.2.3 and the unifi on firmware 2.3.x I can adopt. I know this is reverse of your scenario but if firmware's and controllers were linked I would have experienced the same issues somewhere along the road.

DirkMare
0
BeGentleWithMe-INeedHelpAuthor Commented:
you said:  Firmware can only be upgraded using the controller from the Manage AP tab.

but I thought I saw pages talking about connecting to the AP via SSH then giving a command (sorry, I could google, just not right now) that tells the AP to update and the command line has the path to the new firmware.

Which goes to the issue of connecting via SSH and only getting a black window / no text from the AP prompting for username.
0
Dirk MareSystems Engineer (Acting IT Manager)Commented:
I apologies and Thank You I just learned something new. (Googled)

Have you tried connecting with telnet instead of SSH?

DirkMare
0
BeGentleWithMe-INeedHelpAuthor Commented:
no didn't telnet - anything I see about these APs is people saying SSH.  would you know is connecting via telnet  a matter of just using putty and clicking on 'telnet' as the connection method rather than SSH?  Not sure if the port number would auto change when you click on telnet.  but that's port 21, right?
0
Dirk MareSystems Engineer (Acting IT Manager)Commented:
Telnet also doesn't work.

I'm running out of ideas, have reset the units to factory defaults, login with SSH, update firmware and adopt from Controller Software.

DirkMare
0
BeGentleWithMe-INeedHelpAuthor Commented:
I'll do the factory reset and expect that to solve it. Just didn't want to climb up to each one : )  thanks for the info and time though!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.