Thank You all for the advice. I really appreciate it. I am running a couple Slackware boxes (headless) in a primarily M$ environment at my job. Up to now I have had no issues with authentication (although it's alot of work manually maintaning the users in samba), but the time has come for my slack boxes to join the family, so to speak. We are running exchange 2003 (hey you in the back, stop laughing...), and I have decided to pull it from the front lines, and put a slack box to send & receive our companies mail then forward it to the exchange server. There are a few other things on my list as well. Thanks, Robert De Mars Andrew Zbikowski writes: > I always follow the directions from the Samba documentation. When you > use samba to join the domain samba will create the SPN (Service > Principle Names) for Windows file sharing. This is needed if you want > your windows clients to connect to your samba server with the single > sign on capability provided by AD/Kerberos. Samba's net command is > also able to create the krb.keytab file for you, which can be handy. > > I haven't worked with it much beyond using the winbind pam module. > Using the krb5 pam modules should also be possible, and may work > better in the long run if you're planning on using the Linux computer > as a client instead of a server. > > -- > Andrew S. Zbikowski | http://andy.zibnet.us > IT Outhouse Blog Thing | http://www.itouthouse.com > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list