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-9446: Cannot get adbindproxy.pl script to complete after disabled SMBv1

18 June,18 at 11:24 PM

Problem: abindproxy.pl script cannot complete successfully after disabling SMBv1 
 
Updating smb.conf with Centrify recommended settings...
Connection failed: NT_STATUS_CONNECTION_RESET

Get Domain SID failed. Please try again with authentication and a valid DC.

Cause: Disabling SMBv1 breaks all the 'net rpc getsid' that Centrify use in adbindproxy.pl

Workaround: 

Step 1:

To manually set the domainsid
Please review and follow KB-8903: How to manually set domainsid when samba server is migrating from one domain to another

Step 2: 
Using custom build adbindproxy.pl.test script instead of the pl script from the build.

Resolution: It will be fixed in Suite 2017.3

Related Articles

 articleHow to manually set domainsid when SMBv1 is disabled articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-8732: What is the Impact of Disabling SMBv1 (WannaCry) articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6834: Additional configuration steps for deploying Adbindproxy on RHEL 7 articleWhat is the Impact of Disabling SMBv1 (WannaCry)