Dsconfigad will not show configuration in terminal

Question

Using dsconfigad I have previously been able to bind to our local domain. All was good for a while. Then my logins started not finding the network servers. Now when I login using a local login and run sudo dsconfigad -show in terminal it looks at me for a second then goes to the next line with the same prompt. It shows none of the configuration and gives no error. Below is what I see in terminal . . .
12-imac:~ user$ sudo dsconfigad -show
12-imac:~ user$
What is preventing this from getting the settings? What am I doing wrong?
I've repaired permissions with no change.
Any ideas?
Thanks,
John

Answer 1

Ok, so if you are getting the Unable to connect error I would suggest confirming that time and DNS are set properly.  So first, get the IP address of the DC.  Enter that IP address in the network time address in System Preferences > Date and Time.  Uncheck the box to stop the time client and then check it again to start the time sync between the Mac client and the DC.  Then open Terminal and enter this command:
ntpq -p
This is the Network Time Protocol Query tool and the -p is to pole for a time packet.  You should get a result that has a jitter value with a decimal number, something like 000.001.
Now once you have that correct, then make sure DNS is working as expected.  This includes checking on your SRV records.  Without them, the whole process falls apart.  Use these commands:
# Test Kerberos port 88 tcp
          host -t SRV _kerberos._tcp.domain.tld
          # Test Kerberos port 88 udp 
          host -t SRV _kerberos._udp.domain.tld
          # Kpasswd port 464 tcp
          host -t SRV _kpasswd._tcp.domain.tld
          # Kpasswd port 464 udp 
          host -t SRV _kpasswd._udp.domain.tld
          # gc (AD Global Catalog) port 3268
          host -t SRV _gc._tcp.domain.tld
          # LDAP port 389  
          host -t SRV _ldap._tcp.domain.tld
In all examples, replace the domain.tld with your actual domain.  Make sure you are getting results on each of these commands.  If DNS is not set properly then you will not be able to auto-discover the server for the bind.