I’m guessing you are looking at your JSS screen trying to connect an LDAP server, specifically Active Directory (AD), but things are not going well. First of all, breath. There have been countless times when I’m performing a JumpStart and things “just don’t work” in terms of integrating the JSS and Active Directory, especially if your AD is anything beyond the standard “Next, Next, Next” installation process when it was initially setup.
Network Environment Debugging
First, we’re going to do some simple network debugging that I usually perform once I’m onsite to make sure the AD environment is providing the necessary DNS records. I’m hosting this example environment on my laptop via VMware Fusion 7.1 Pro with:
- one VM running Windows Server 2012 R2 as my AD and DNS server
- one VM running Ubuntu 14.04.1 as my JSS
- one VM running OS X Yosemite as my “Admin Station”
All VMs are essentially on the same isolated network as I have configured each VM to use “NAT” for their Network Settings. My AD server’s FQDN is
dc01.pretend.co with an IP address of
192.168.204.10/24 while my JSS server’s FQDN is
jss.pretend.co with the static IP address of
192.168.204.11/24 and the gateway (my laptop) is
192.168.204.2/24. I’ve configured my test AD server to have the domain of “PRETEND” and it is also providing DNS (forwarding to the gateway), and both the JSS and “Admin Station” are pointing to the AD server for DNS lookups.
Debugging DNS overview
For debugging the AD environment, I’m going to do a host of the “pretend.co” which should give me a list of all the domain controllers, next I would verify the forward and reverse DNS names to IP address of my domain controllers, then finally verify some LDAP SRV records.
Here is the result of my test environment. You’re results should have more AD servers populated, but otherwise it would be close to this gist:
What to look for when debugging DNS
Your “dns_server” should be the IP address for one of your domain controllers. With that said, only your internal AD DNS servers should be listed in a client’s network settings. Providing internal and external DNS options (like Google’s or OpenDNS) in your DHCP scope settings will only confuse an Apple device. If any of these commands return unexpected results, there is something wrong with your network.
Next let’s make sure that we are dealing with the standard ldap port of 389 with an administrator account that should be allowed to view the entire directory tree if needed.
Here is a link to a gist that shows the expected results. You should get some positive looking results. If you get an error, you have restricted AD so much that simple lookup queries are not working. Go talk to your AD guy and find out what they have done to AD to be so cranky.
JSS LDAP Setup - Active Directory
When the Active Directory LDAP setup assistant works, it’s great! Just remember some of these tips:
- “Hostname or IP Address” is the FQDN of a Domain Controller
- For your LDAP server account, it’s looking for your DOMAIN (e.g. PRETEND) along with an AD Administrator account username and password (or better yet a Service Account).
- Have two test AD accounts ready where one user is known to be in a group and not in another (like yourself and another employee that is NOT in IT). We’ll test to make sure the lookups are displaying the correct user info and group membership.
JSS LDAP Setup - Manual
Sometimes the LDAP setup assistant just doesn’t work. No matter how many ways you enter your DOMAIN and then provide authentication credentials it never gets pass the verification. In these cases, we’ll use the manual configuration method and verify our settings from the following screen shots.
Key items to look for are:
- Server and Port should be your FQDN of a domain controller and 389 unless you have enabled LDAPS. Then you made your own nightmare.
- Yes, that is what a Distinguished Name (DN) looks like. Find the FULL path.
- On your User Mappings, sometimes organizations will have multiple CNs or OUs in the same level. If so, just use
dc=domain,dc=tldand search your whole domain. And yes, that may take longer.
- Verify the LDAP Attributes carefully. Email is sometimes just
- The group Mappings have the same issues as User Mappings. You may need to move it to
dc=domain,dc=tldand it will take longer.