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-4032: adbindd error: Unsupported or invalid winbindd interface version

29 June,17 at 10:16 AM

Applies to: All versions of Centrify-Enabled Samba on all platforms
 
Question:
 
What is the meaning of following error messages and how to get rid of these error messages from the machines installed Centrify-Enabled Samba: 
 
Aug 14 01:32:25 Redhat adbindd[25715]: ERROR samba.adbindd2 Task exit with cims error: Unsupported or invalid winbindd interface version: 27 
Aug 14 01:32:25 Redhat adbindd[25715]: ERROR samba.adbindd2 Task exit with cims error: Unsupported or invalid winbindd interface version: 27 
 
Answer:
 
First, please check the version of Centrify-Enabled Samba using. For example, on Redhat:
 
[root@Redhat: /] $ rpm -qa | grep -i samba
CentrifyDC-samba-3.6.9-4.5.5.222
 
For CentrifyDC-samba-3.5.*, the winbindd interface version is 23.
For CentrifyDC-samba-3.6.*, the winbindd interface version is 27.
 
Then please check if CentrifyDC-adbindproxy package is installed or the version of CentrifyDC-adbindproxy package installed. For example, on Redhat:
 
[root@Redhat: /] $ rpm -qa | grep -i adbindproxy
CentrifyDC-adbindproxy-4.5.5.222
 
If no CentrifyDC-adbindproxy is installed, please install the correct version of CentrifyDC-adbindproxy included in the Centrify-Enabled Samba package downloaded in Centrify Customer Download Center. For example, the correct version of CentrifyDC-adbindproxy for CentrifyDC-samba-3.6.9-4.5.5.222 is CentrifyDC-adbindproxy-4.5.5.222. 
 
The error messages in question will not appear again if a correct version of CentrifyDC-adbindproxy is installed.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-10478: Upgrading to Stock Samba 4.7.x or 4.8.x Causes Shares to be Unreachable articleKB-7926: Adbindproxy 5.3.0 with Samba version 4.5.X - adbindd service will not start. 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-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?