Re: Centrify not using ntp server

Here is the full adcheck output:

$ sudo ./adcheck-rhel5-x86_64 ad.goldblattsystems.com
OSCHK    : Verify that this is a supported OS                          : Pass
PATCH    : Linux patch check                                           : Pass
PERL     : Verify perl is present and is a good version                : Pass
SAMBA    : Inspecting Samba installation                               : Pass
SPACECHK : Check if there is enough disk space in /var /usr /tmp       : Pass
HOSTNAME : Verify hostname setting                                     : Pass
NSHOSTS  : Check hosts line in /etc/nsswitch.conf                      : Pass
DNSPROBE : Probe DNS server 192.168.6.1                                : Pass
DNSPROBE : Probe DNS server 192.168.6.6                                : Pass
DNSCHECK : Analyze basic health of DNS servers                         : Pass
WHATSSH  : Is this an SSH that Centrify DirectControl Agent works well with: Pass
SSH      : SSHD version and configuration                              : Warning
         : You are running OpenSSH_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017.
         :
         : This version of OpenSSH does not seem to be configured for PAM,
         : ChallengeResponse and Kerberos/GSSAPI support.
         : To get Active Directory users to successfully login,
         : you need to configure your OpenSSH with the following options:
         : (display the ones we identified were not set)
         : ChallengeResponseAuthentication yes
         : UsePAM Yes
         :
         : Centrify provides a version of OpenSSH that's configured properly
         : to allow AD users to login and provides Kerberos GSSAPI support.

DOMNAME  : Check that the domain name is reasonable                    : Pass
ADDC     : Find domain controllers in DNS                              : Pass
ADDNS    : DNS lookup of DC hubcap.ad.goldblattsystems.com             : Pass
ADPORT   : Port scan of DC hubcap.ad.goldblattsystems.com 192.168.6.10 : Warning
         : One or more ports failed to respond correctly. Either:
         :   a) the DC with this IP address is offline
         :   b) a firewall is preventing access to a port
         : The following is a list of failed ports:
         :    ntp(123)/udp - timeout

ADDC     : Check Domain Controllers                                    : Pass
ADDNS    : DNS lookup of DC hubcap.ad.goldblattsystems.com             : Pass
GCPORT   : Port scan of GC hubcap.ad.goldblattsystems.com 192.168.6.10 : Pass
ADGC     : Check Global Catalog servers                                : Pass
DCUP     : Check for operational DCs in ad.goldblattsystems.com        : Failed
         : No working domain controllers were found.

1 serious issue was encountered during check. This must be fixed before proceeding
2 warnings were encountered during check. We recommend checking these before proceeding

I am aware of the DNS warning; that is because of our transition environment.