Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-8445: Nexenta users unable to connect Centrify ldapproxy when SMBv1 is disabled in AD

Authentication Service ,  

26 May,17 at 11:30 PM

Applies to: All versions of Centrify DirectControl on all platforms.

Question: 
Nexenta is Solaris network attach storage (NAS) which integrates with Centrify through ldapproxy.
After disabling SMBv1, domain level users reported they are no longer able to have the access to network share device. Does Centrify ldapproxy have something to do with this issue?

Answer:
Centrify ldapproxy is not the culprit for this issue. When Centrify ldapproxy was been removed completely out the authentication role, the issue still remains.
Nexenta (NAS) is not a Centrify product, please kindly contact Nexenta to address this issue.

 

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6041: How to show current license type in use by adclient articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-3393: crontab works for local account but not AD users