Samba Server Configuration and Management
Whenever you modify file smb.conf, you should run the command
testparm
to check that you have not made any basic syntactic errors.
With the configuration above, the Samba server becomes a Domain Controller
for domain UNISYS and shares homes, users home directories, and printers
listed in /etc/printcap
Default Samba log files are located in directory /var/log/samba.
You can run man smb.conf to see the list of all
possible configuration parameters and options for smb.conf.
Create Samba user and client host (trust) accounts.
Users should exist in both Unix and Samba password files.
If login names are different in the two accounts, map them in /etc/samba/smbusers.
Unix passwords (/etc/passwd, /etc/shadow, or NIS maps):
mike:$1$Dblngr.F$.ZQdmksQzAqFSegnUp0ZB:500:500::/home/alexei:/bin/bash
Windows passwords (/etc/samba/smbpasswd):
mike:500:40B5546653BF1E471D71060D896B7A46:72B51AA6979379A20D2936E4E0B1D6B0:[UX]:LCT-3E52CBFE:
With clear text passwords, encrypt passwords = no, authentication for SMB
shares is done through Unix passwords; Domain Controller authentication
can be done only through Samba passwords.
Unix and Windows use different encryprion schemes for passwords, /etc/passwd and /etc/samba/smbpasswd.
The password synchronization is still a serious open issue.
Start Samba daemons, smb and nmb.
Every time you modify /etc/samba/smb.conf file, you need to restart the
Samba daemons for changes to take effect.
Now you should be able to map the home directories onto Windows clients,
bind the clients to Domain UNISYS, and authenticate users with the Domain
Controller.
previous
top
next