How do I see my DHCP clients list on my new Airport Extreme AC?

I came across something somewhere that suggested you try some key combos while double clicking things.

So, I held the option/alt key down and double clicked my Extreme Icon in the latest version of Airport Utility (6.3.2)

and bam, I get a nice list of all the DHCP clients, except the one I'm using, which was weird.

But it gets you the list in the latest airport utility.

Yay.

I get a nice list of all the DHCP clients,

Not all DHCP clients, only the wireless clients are displayed. Wired are not.

Stunning that Apple took away the ability to see a wired client on the network.

Actually..... I can't believe my eyes but I now see all DHCP clients under the "DHCP Clients" tab.

I did what "Pelicani" suggested above:

1. Started Airport Utility 5.6.1 on PC

2. Waited for the device "scan" to complete then <Alt>double-click on the Airport Extreme

3. Went to Advanced > Logs and Statistics > DHCP Clients

And there it is.... even the IP address of the system I am currently working from!

Now to try it on the MacOS side.....

OK, on MacOS Airport Utility 6.3.1 it is as Bob T. states above.... only wireless clients. How terribly short sighted of Apple to take something so rudimentary from their networking devices... oh well at least it works on the PC side..... ;-)

Thanks again to Pelicani and Bob Timmons!!!

Has anyone noticed that Aairport Utility 5.6 doesn't work on the latest version of OSX??

Does the "double-click" replace the stuff that we lost in 5.6? I am guessing not. Wonder if there is a 3rd party app out there that could help. It seems possible if the PC version has it.

Try Fing - Network Scanner on the App Store on iTunes on an iPhone or iPad.

Holy cow! That's a nice app (and free!). It does show my ethernet connected devices (totally confirmed). If you have an iphone/ipad, this is a perfect solution.

This solved my problem! Thanks!

On android too... Great....

Thanks a bunch for the pointer to Fing, that is a great tool! It worked for me. Shows every host (wired or wireless) on my network, allows you to scan for services on those hosts, etc. . Very handy.

WELCOME HOME 5.6.1 !! *** SOLUTION ***

Ahrg! I've been so frustrated by Apple on this. Apple took away my ability to manage our office (ALL Mac /Apple) network!!

Apple wants us to use and BE ALL ... Apple - yet takes away our ability to use it!

You want to snub your noses at Apple on this?! A simple Apple Script that makes Terminal AirPort Utility 5.6.1 work under Mavericks!

At least an immediate and very workable solution can be found at:
http://coreyjmahler.com/2013/10/24/airport-utility-5-6-1-on-os-x-10-9-mavericks/

RIGHT NOW... I'm looking at ALL my hardwired clients, including our network printers,

print severs, all our Airport Express's, mobiles and more!

It's good to see an old friend. Welcome home Airport Utility 5.6.1 !! WELCOME HOME!

And be sure to thank Corey J. Mahler who came up with the solution!

BTW - I'm using this script and Airport Utility with:

iMac 3.4ghz i7 /32gb, with the latest Mavericks version.

Open Terminal. Type:

arp -na

And that will show all your wired connections.

Thought that would be an easy solution to remember so I tried it.

Umm... yea... that didn't work.

That command didn't show anything but our gateway IP address.

Maybe it didn't work for me because I have our modem set up on the front side of our Airport Extreme in bridge mode?

However, if this command is really supposed to work - our set up is shouldn't matter because our Extreme is still handling all our network traffic.

The terminal command would querying our Airport extreme, so even though I would like this as a simple solution - it really doesn't seem to work.

Is the command missing some text? I'd use it if this would work.

FYI:

I do know the solution I posted and mentioned previously works flawlessly. You're able to use a familar Apple tool, too - Airport Utility 5.6.x, which I like better, still, than any other revisions since.

Works for me just fine. I can't possibly know all possible situations you might have on your network, however, you can read this for more help on the arp command:

http://hints.macworld.com/article.php?story=20130821063020920&query=arp+-na

Our small office network consists of a modem, server, 4 -5 switches (technically another switch -our Extreme) and even with that - I would consider it a simple network, all of which equates to only a few possible factors that 'might' affect this issue..

But regardless...I was going to say that just reiterating "it works for me" and pasting a link to a convoluted article with multiple suggested options won't show or solve anything - UNTIL... I saw someone's response at the link.

The author of the article explained that no "friendly" names would appear, meaning only the actual IP number would show in Terminal's results ( unlike in Airport Utility - shows device names) The response to the article begins by explaining why you won't see the "friendly" names,

BUT THE REAL POINT you missed - shows why this really is not an actual viable solution to see what's currently on your network.

FROM THE LINK YOU PROVIDED:

Authored by: stevebr on Aug 21, '13 10:31:53AM

It's the

-n

But the arp utility is only looking up entries in a cached table of machines yours has had some kind of connection with. This means that may see names/addresses of machines that have shut down or left the network but are still cached, and machines that yours has had no contact with may not show up at all.

Some of your other suggested methods are probably more suitable for getting an accurate list.

MEANING: To the issue and subject of this particular discussion - those who need /want to see an accurate and current list of client machines on a network - this Terminal command line is not a viable option, or really... even a solution.

I couldn't see any other IP's on our network because I haven't looked at them by any means because I'm running on a brand new Mac, so I wouldn't have any cached IP information. So that's why the command line only showed the beginning and end of our possible addresses. But this shows why this is not really an option, nor an accurate representation of what's currently on your network.

While you think this may have worked for you - most likely you're simply looking at old "cashed" data.