This KB discusses what to do if the Centrify Abindproxy.pl script hangs with the latest version of Centrify adbindproxy and stock samba
Centrify Adbindproxy version 5.3.0-504 on All Platforms
When running adbindproxy.pl script, it appears to hang after getting one of the following errors:
Could not initialise lsa pipe Get Domain SID failed. Please try again with authentication and a valid DC.
Could not initialise pipe samr. Error was NT_STATUS_ACCESS_DENIED Get Domain SID failed. Please try again with authentication and a valid DC
It will prompt for an Authorized AD user and Domain Controller and then appears to hang.
Enter the Active Directory authorized user [Administrator] : Using (Administrator) Enter a valid domain controller [dc.domain.com] : Using (dc.domain.com)
When the command `/opt/centrify/samba/bin/net rpc getsid -S domaincontroller -U administrator` is run in the adbindproxy.pl script, it does not prompt for the password of the administrator user if it is unable to resolve the command without a password.
1) This issue can occur if the Group Policy, "Network access: Named pipes that can be accessed anonymously" is enabled
To turn off the Group Policy: On domain enabled GP go to: "Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network access: Named pipes that can be accessed anonymously".
Set the policy to not be defined and run 'gpupdate' from a command prompt to update the Group Policy.
Rerun the adbindproxy.pl script on the client.
2) Download the patched adbindproxy.pl script attached to this KB.
Replace the current adbindproxy.pl script with the patched version. (The location of the adbindproxy.pl script is in /usr/share/centrifydc/bin/) Rerun the adbindproxy.pl script.
This issue will be fixed in the next release of adbindproxy (CentrifyDC-adbindproxy-5.3.0-509 and newer)