Solved

Installing Ubiquiti Unifi AP I get the error... "No devices have been discovered.  Make sure the devices are on the same L2/switch network and try again."

Posted on 2014-07-25
33
13,675 Views
Last Modified: 2014-07-29
For our network we have a DSL modem from our ISP.  The modem connects to an ASUS RTN66U router.  The router connects to the switch to which are connected about 30 computers including the file server running Windows SBS Server 2003.  The ASUS router manages DHCP.  We also have had a Unifi AP access point Wifi unit connected to one of the ASUS router switch ports.  This worked fine until we had a lightning strike.  The lightning took out a number of items including, it seemed, the Unifi AP.  So I bought another Unifi AP.  But I cannot get the Unifi controller software to discover it.  I get the message "No devices have been discovered.  Make sure the devices are on the same L2/switch network and try again."  I know it needs Java.  I tried uninstalling Java and uninstalling the Unifi controller software, rebooting the computer, install Java, install the Unifi controller software.  Still not.  I am doing this on one of the work stations which is connected to the main switch.  In most of my efforts the computer which is hosting the Unifi controller software was connected to a small switch which is connected to the main switch.  Just now I tried removing the small switch from the picture.  I have tried suspending my AVG antivirus.  I have tried suspending the Windows firewall on my Unifi controller computer.  I have tried suspending the firewall on the ASUS router.  I have tried resetting the Unifi AP to factory default by holding the button more than 5 seconds.  What should I try next?
0
Comment
Question by:Josh Christie
  • 19
  • 14
33 Comments
 
LVL 24

Expert Comment

by:smckeown777
ID: 40219701
With the Unifi controller you generally should let it install Java - don't install Java yourself as some of the versions don't work properly with it...

So remove Java, and the controller software...reboot...reinstall the controller software(which itself will install java)

The other way to check what is happening is to ssh into the AP itself(can you see which ip was assigned to it from your router's DHCP table?)

The default user/pass for the AP is ubnt/ubnt

Once ssh'd into the AP you can issue the command
set-inform http://ip-of-controller:8080/inform

The on your controller you should see it appear and you can Adopt it
0
 

Author Comment

by:Josh Christie
ID: 40220070
So far I'm not finding its IP.  I thought I could determine which it is by taking a screen shot of the DHCP list, then unplug the AP, reset the AP, refresh the DHCP list and compare.  But it's not that simple.  I think some unused IPs are being culled out.  Do I need to run ipconfig /release and ipconfig /renew?
0
 

Author Comment

by:Josh Christie
ID: 40220073
Oh, BTW, I believe i installed Java correctly.  When i reinstalled it I let the Unifi Controller lead me to Java.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220304
Hi, how many IP's are we talking about? Meaning can you ssh to those IP's you don't know and see if you get a login? Or are we talking 20+ addresses?

Ok sounds like the controller is up and running...can you run the 'Unifi-Discover' app? Its on the Start menu - All Programs - Ubquiti Unifi - Unifi Discover...that should show your AP's that aren't managed...
0
 

Author Comment

by:Josh Christie
ID: 40220349
OK.  I have installed Angry IP Scanner and that seems to do a good job of showing me my IPs and sorting them.  After cycling a number of times of plugging in the AP and resetting and then unplugging and running the scan after each change, I think I have spotted the AP's IP.  

However, yes, I can run the Unifi-Discover app, but after 10 minutes it does not find anything.

OK, now, how do I SSH to this known IP address?
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220371
Ok normally I use Putty - http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

Run that and put in the IP of the AP
User - ubnt
Pass - ubnt

Once in there issue that command I gave earlier and things should start to move for you
0
 

Author Comment

by:Josh Christie
ID: 40220372
Will I be using Putty to do this?
0
 

Author Comment

by:Josh Christie
ID: 40220373
You answered before I asked...........
0
 

Author Comment

by:Josh Christie
ID: 40220403
OK.  This looks like progress.  The reply looks like this...
Adoption request sent to 'http://ip-of-controller:8080/inform'.
1. Please adopt it on the controller
2. issue the set-inform command again
3. <inform_url> will be saved after the device is successfully managed

At this point I still am not getting the controller nor the discover utility to find it.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220410
Ok going to ask a stupid question - did you actually supply the proper IP of controller?

http://192.168.1.20:8080/inform

Or whatever your ip is?
0
 

Author Comment

by:Josh Christie
ID: 40220417
No, not a stupid question, I put in "ip-of-controller".  OK.  I'll try again.
0
 

Author Comment

by:Josh Christie
ID: 40220443
OK, in the putty command line I entered...
set-inform http://192.168.2.187:8080/inform

controller still doesn't find it

In putty the default port is 22.  I left it at that.  Is that correct?
0
 

Author Comment

by:Josh Christie
ID: 40220449
The IP shown above is the IP that I have concluded is the IP of the AP device.  I believe it's correct because I was asked for the login as you expected I would.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220451
Yep that's correct...port 22 is ssh...

Is the controller running? Can you see the web interface ok yes? The Unifi icon that runs in the system tray - is that showing and shows the service running?

Did you have this working previously or is this the first time you have tried to get this up and running?
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220459
The IP you should be entering in this line - http://192.168.2.187:8080/inform

This should be the IP of your CONTROLLER...i.e. the pc where you've installed the Unifi software - is this the IP of that machine?
0
 

Author Comment

by:Josh Christie
ID: 40220475
Well, we must be just on the brink.  The PC hosting the controller software is 192.168.2.110.  I have now entered this IP into the line above.  (I used the ...187 IP in Putty and that seems happy.)  Controller still does not discover.  I've tried closing and reopening the controller.  Clicking the Refresh button.  no go.
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 24

Expert Comment

by:smckeown777
ID: 40220480
Ok, after installing the Unifi software did you restart the machine? Do that just to be sure...

In summary

Putty to the IP of the AP(which you've done obviously)
Issue the inform command using the IP of the CONTROLLER
Refresh the controller and you should see it appear(the web interface I mean)

Also what is the OS that you've installed the controller software on? Any 3rd party firewall installed? What AV?
0
 

Author Comment

by:Josh Christie
ID: 40220500
The OS for the controller is Windows 7 Pro.  My antivirus is AVG.  I suspended it for 10 minutes, but that expired.  I have done a reboot since installing the unifi software, but I'll do it again.  I have the Windows firewall on this machine and the router has a firewall.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40220501
Another command you can run on the controller pc - run this from a standard command prompt

netstat -anp TCP > net.txt

This will product an output in the directory where the command is run from(normally C:\Users\user) called net.txt

Attach that here so I can check that the controller is listening on port 8080
0
 

Author Comment

by:Josh Christie
ID: 40220711
Sorry I ran off without a word.  Things were getting rather snarled and the hour was getting late.  We'll pick this up again on Monday.  Thanks, smckeown777 for your excellent help.  I'll try this command on Monday.  Sounds encouraging.
0
 

Author Comment

by:Josh Christie
ID: 40224028
Monday morning, back on duty.  Don't know, smckeown777, what your schedule is.  But here is my reply.
net.txt
0
 

Author Comment

by:Josh Christie
ID: 40224090
Entry above, ID: 40224028, has net.txt attached.  Looks to me as though it is indeed listening on 8080.  I realize I did not answer your entry ID: 40220451 on the 25th at 14:01.  Here are your questions...

"Is the controller running? Can you see the web interface ok yes? The Unifi icon that runs in the system tray - is that showing and shows the service running?"

Answers:
The controller is running.  The icon shows in the Task Bar, but not in the System Tray.
As to the service... In the list of services, I do not see Ubiquiti or Unifi anything.  

As to the web interface... The dialog box us up, telling me that No devices have been discovered.  It's on a Chrome browser tab entitled Wizard - UniFi Controller, and the URL is https://127.0.0.1:8443/wizard/s/default.  In fact that made me wonder if I should be using port 8443 instead of 8080 in the PuTTY command.  I tried it and it still does not discover when I refresh the Controller dialog box.  So i think that's the latest.

I checked this morning that the AP is still plugged into the switch and is blinking at the switch showing connection.  Also I reran Angry IP Scanner and it still shows the IP active.  Putty still lets me log into the AP using ubnt, ubnt.

*****
Then you asked... "Did you have this working previously or is this the first time you have tried to get this up and running?"

Answer...
I have not had this particular AP unit running before.  This is a new one.  However, I had an identical one running for about 6 months before the lightning strike.  It was as easy as pi to set it up.  I had no issues like this.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40224337
Ok lets drill into this...

Can you browse to https://192.168.2.110:8443/ and get a login and access to the controller web interface?

What is this IP - 192.168.2.110? Is that the IP of the pc running the controller?

If so what is 192.168.2.187? I remember that from an earlier posting - if that is the IP of the pc running the controller can you access the web interface on this link - https://192.168.2.187:8443/

No port 8080 is what you supply the AP..that's correct so 8443 isn't correct for supplying to the AP
0
 

Author Comment

by:Josh Christie
ID: 40224672
Yes.  I first run the Controller software.  A windows comes up showing that the Controller is initializing.  When it is done initializing, there is a button saying "Launch a browser to manage wireless network."  At this point I can open a separate tab and browse to https://192.168.2.110:8443/  and the configuration window (web interface) comes up.  

Yes, 192.168.2.110 is the IP of the PC running the Controller software, which is the one I using right now.
192.168.2.187 is the IP of the AP.

I used ...187 in Putty to get to the AP logon.
I used ...110 in the command line inside Putty in the "inform" statement
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40225194
Ok...that all sounds perfect...so why are we not getting anywhere...

Ok from the AP(when you putty into it) can you run this command

ping 192.168.2.110

Do you get a reply?
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40225211
Another test - from a different laptop/pc can you browse to https://192.168.2.110:8443/ - does this bring up the web interface?

If yes then I think this proves that there should be no blocks from a firewall of any kind
If not - then something is blocking that(and probably other) ports on your controller pc
0
 

Author Comment

by:Josh Christie
ID: 40225361
Yes when I ping in Putty to 192.168.2.110 I get good looking results, some of which is shown in the attached file.  When I try to browse from another pc to https://192.168.2.110:8443/ it does not go.  I tried turning off the firewall of ...110.  On the browse-in pc I am logged in as network administrator.  My login on pc ...110 is not as administrator.  However this login is in the local administrator group.  Is that a show-stopper?  Another thing.  The pc whose IP is 192.168.2.110, its name is PC61.  The following url from the browse-in pc works...  file://pc61/c$/.  But file://192.168.2.110/c$/ does not work.  If I run ipconfig /all on pc61 it gives as the preferred IP for local area connection 192.168.2.110.  So this is bewildering.
PuttyPing.docx
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40225386
When I try to browse from another pc to https://192.168.2.110:8443/ it does not go

Ok this normally means something is blocking you...what firewall is running on this machine? AVG? Uninstall AVG for a test to see...something is blocking access and usually its AV that does this in a lot of cases(I don't use AVG so can't tell for sure)
0
 

Author Comment

by:Josh Christie
ID: 40225488
The firewall is Windows Firewall.  I tried disabling the Public firewall.  I uninstalled AVG and restarted.  I then disabled the Windows public firewall again.  The browsing-in pc still cannot reach https://192.168.2.110:8443/.  But if something is blocking ...110, why can I successfully reach the computer by using the computer name...  file://pc61/c$/ ?  Anyway, I need to leave the office now, so will pick it up again tomorrow.  Thanks for working with me today.
0
 
LVL 24

Accepted Solution

by:
smckeown777 earned 500 total points
ID: 40225497
Public firewall? You should be in a 'Work' based section...not Public - if you are referring to Network and Sharing center make sure your connection says 'Work' and not Public - otherwise stuff will be blocked

Yes the access by pc name and not by IP doesn't make sense...still thinking about that one
Ok pick up with you when ready...
0
 

Author Comment

by:Josh Christie
ID: 40226819
Well I think we've got it.  The key seems to have been the firewall on the "Home or Work Networks".  After I disabled that,  I got connection.  After that the remaining configuration went relatively smoothly.  One point that was bewildering was that even after the AP was connected, my iphone didn't see it.  The Controller utility said "Connected (needs upgrading)".  Well, I figured out how to upgrade it.  And after it completed that, then everything was happy.  

I greatly appreciate your patiently walking with me in this process.  I learned some good stuff in addition to the AP setup.
0
 
LVL 24

Expert Comment

by:smckeown777
ID: 40226849
Great...I was starting to lose the plot myself!

Yes that 'Work'/'Home'/'Public' thing is important - always use Work for local networks in a business environment
Home is for home laptops/pc's - bit more tied down
Public is for when you are in the coffee shop - i.e. the firewall blocks stuff by default...

Glad you are working...
0
 

Author Closing Comment

by:Josh Christie
ID: 40226891
I'll put the points on the entry about the work firewall, but there was lots of other good information as well.  You should get 1000 points for this.
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Backup UPS - email alert 3 86
Cisco 1830 AP behaving wierdly 7 28
Droid 4 15 66
SRX240 SYSLOG Setting 6 53
DECT technology has become a popular standard for wireless voice communication. DECT devices are not likely to be affected by other electronic devices and signals because they operate in a separate frequency-band.
This paper addresses the security of Sennheiser DECT Contact Center and Office (CC&O) headsets. It describes the DECT security chain comprised of “Pairing”, “Per Call Authentication” and “Encryption”, which are all part of the standard DECT protocol.
This Micro Tutorial will show you how to maximize your wireless card to its maximum capability. This will be demonstrated using Intel(R) Centrino(R) Wireless-N 2230 wireless card on Windows 8 operating system.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now