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-7411: Samba Troubleshooting - Finding the location of winbind for adbindproxy script

Centrify DirectControl ,   Centrify DirectControl Plugins ,  

31 August,16 at 11:23 PM

Applies to:

Centrify Adbindproxy 5.3.0 on all supported platforms.

Question:

How can we check where the winbindd socket is located for adbindproxy script?

Answer:

Stop all samba services:

/etc/init.d/centrifydc-samba stop

Start the winbind service by itself:
/etc/init.d/winbind start


Search for windbindd socket location:
netstat -anp | grep winbind

Note the location of where the winbindd socket is located. 
For example if you see,
/var/run/samba/winbindd/pipe
You would use /var/run/samba/winbindd when prompted.

Run
adbindproxy.pl
At option: "Please specify the stock samba winbindd listen path(dir) if it is not in [/run/samba/winbindd]"
Enter path noted earlier for windbindd.

Check:
At the bottom of
/etc/centrifydc/centrifydc.conf check if the winbindd location is correct. 


 

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