Samba is a software suite that allows Linux files and other resources, such as printers, to be shared with Windows. This chapter describes how to make Linux the Windows Master http://www.aliyun.com/zixun/aggregation/13351.html ">" "> domain Name server (PDC), or Windows Workgroup server. Both configurations allow users to:
Misspelling own logins on the "All" home windows boxes while has misspelling files on the Linux box appear to is located on a new Windows drive Use shared printers on Linux to access files shared by the Linux user group
What is the difference between a domain member and a team member, a detailed description is beyond the scope of this chapter, but this simple explanation is sufficient:
A domain server stores all login information on its own database. This allows each user to log in with the same username and password on all computers on the network. In a Windows workgroup, each computer stores a user name and password locally, so a unique username and password is used for each computer.
This chapter includes only the most popular domain server setting methods. By default, Samba simulates almost all the ways a Windows domain server uses to share files. When you set up Samba, the functionality of Linux itself is completely preserved. The Samba domain shares the same username as Linux, so you can use the Linux password to log on to the Samba-based domain and immediately gain access to your Linux user's home directory. For added security, you can set different passwords for Samba and Linux.
Samba's daemon reads the configuration file/etc/samba/smb.conf to determine how to handle each time a client request is made after Samba starts. You can use a text editor or WEB based SWAT software to set up a configuration file. The SWAT setting is relatively straightforward, but if you first create/etc/samba/smb.conf with a text editor and then edit with Swat, all the comments that were added to the text editor will be lost. Here's how to configure Samba with the SWAT and text mode editors.
Note: Since smb.conf files are frequently accessed and modified, you may want to keep a copy of this file if you do not use SWAT. When the modification is complete, use the Testparm tool described in chapter 12th "Security and debugging for Samba" to verify the correctness of the modification. If you are satisfied with your changes, copy the modified file to your original location.
Most Redhat and Fedora Linux software are in RPM format. Download and install the RPM package is not difficult, you can refer to chapter 6th "Install Linux Software" (where specific operational details are involved)
Samba is made up of a series of RPM packages that can be found on the Fedora installation CD. These documents include
Samba Samba-common samba-client Samba-swat
When you search for these files, remember that these RPM packages usually have a list of numbers, such as samba-client-3.0.0-15.i386.
Start Samba
You can use the Chkconfig command to enable Samba to start at system startup [Root@bigboy tmp]# chkconfig SMB on You can also start/stop/reboot after starting with the following SMB initialization script: Samba[root@bigboy tmp]# Service SMB start[root@bigboy tmp]# service SMB stop[root@bigboy tmp]# service SMB restart
Note: Unlike other Linux software, you do not need to restart Samba after modifying the samba configuration file, because Samba reads the configuration file every time the client requests it.
You can use the Pgrep command to test that the SMB process is running, and then you will get a process number [Root@bigboy tmp]# pgrep SMB