Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am thinking about joining our company domain with a linux box.
With joining the domain I can use single sign on for a web service we are running (Dekiwiki), for this I have installed winbind. And I am thinking about the limitations that might come after we joined the domain like internet access, user management on the local computer and others.


share|improve this question

migrated from Nov 1 '09 at 12:13

This question came from our site for computer enthusiasts and power users.

up vote 3 down vote accepted

On Linux, Samba is just another server daemon (or service client, if you're not running the server portion). Neither server nor client can automagically take over the administration of the Linux box just because you've told them to join a Windows Domain.

Now, if you wanted to force all local users to login and authenticate to the WDS, you can. (I think.) But that's not a requirement. Without special configuration, it won't affect your linux box's standard networking and user management.

Here's the Samba HOWTO on Domain Membership for joining with a Samba server, or see this subsection if you're joining via the Samba client (ie not running a Samba server on the box).

share|improve this answer
Thanks for the clarification that joining the domain won't affect current user management. – Ton Plomp Nov 1 '09 at 10:58

Using nss_winbind or nss_ldap with PAM (pam_krb5, and/or pam_winbind/pam_ldap, you can have the domain users show up on the linux box and enjoy single sign on capabilities of the domain.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.