[Lvlug] Even more Samba problems
scatterbrained at usermail.com
Fri Jun 18 23:55:02 EDT 2004
On the 14th day of June in the year 2004 you wrote:
> Date: Mon, 14 Jun 2004 13:42:00 -0400
> From: "Ferguson, Scott W" <swf001 at lvc.edu>
> To: lvlug at thelinuxlink.net
> X-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,
> FROM_ENDS_IN_NUMS autolearn=no version=2.63
> Subject: [Lvlug] Even more Samba problems
> So complication #2 with my Samba network...Everybody's password is done
> via the company's network (all user profiles and passwords are remotely
> stored) and the employees all have to change their password on a regular
> basis (every few months).
How? Windows NT DC? Win2k Active Directory? (Mixed or dedicated
> Now it's my understanding with Samba, that the local Linux account has
> to be exactly the same as the remote Windows account; meaning the
> username and password have to match to be able to log into the Samba
> network. Since this job is only a summer internship I'm going to need
> some way for everybody to continue to be able to log into the network
> drive after I'm gone, since I won't be able to change the passwords on
> the Linux box, and their passwords _have_ to change. Any way to make
> this happen on it's own?
If you are running Active Directory, you could set up OpenLDAP (which can
pull from AD) and authenticate to the server using PAM. I've never done
this but I have been told that it's possible.
Samba can authenticate to a Windows NT DC on it's own. (Win2k domains need
to run in mixed mode.)
I'm not sure what you would do about Novell.
More information about the Lvlug