Php4, Php5 Programming, Ftp Web Hosting, Subdomain, Cpanel Blog

Chapter 18 . Setting Up Windows Interoperability with Samba 521 . [groups] Configuration settings for a summary share that exports directories that are owned and writable by Linux groups. . [homes] Configuration settings for user home directories as exported by the Samba server. . [pdf] Configuration settings for a PDF file generator that is provided as a default printer in Samba. . [print$] Configuration settings for a general share that is intended to hold print drivers that Windows users can use to print to Windows printers via Samba. . [printers] Configuration settings for printers that are available via Samba. . [users] Configuration settings for a summary share that exports all Linux user home directories. If you define additional shared resources using the Advanced dialog box available by clicking the Advanced button shown previously in Figure 18-17, an smb.conf section will be created for each additional resource. The Shares tab in the YaST Samba server configuration already seen in Figure 18-16 allows you to create additional Samba shared resource sections. The SUSE Administration Guide provides examples of additional resources that you may want to define and discusses the configuration settings that you should use to manage access to those resources. Tip If you manually modify your Samba configuration file, Samba includes a useful utility called testparm that reads and parses a Samba configuration file and identifies any syntax errors that are present. You should always use this utility after making changes to your smb.conf file but before restarting your Samba server to ensure that the file itself is correct before trying to diagnose problems with the values that you specified. Samba Client and Server Packages SUSE Linux comes with a large number of Samba-related packages. You can use YaST to add packages manually after completing your initial SUSE Linux installation or to query your system to determine the Samba-related packages that were installed as part of the type of installation that you selected during the installation process. In this section, we list the Samba- and SMB-related packages provided with SUSE Linux Professional; we also discuss which of these packages are installed by the different installation types and package sets you can select when installing SUSE Linux.
Note: If you are looking for cheap webhost to host and run your apache application check Vision jboss web hosting services

520 Part IV . Implementing Network Services in SUSE Linux To obtain complete information about any of these commands, execute the command mancommandfrom any konsole, xterm, or other terminal emulation window on your SUSE system, where commandis the name of the command about which you want information. The Samba Configuration File Samba is configured through settings that are stored in a text-format configuration file, which is located in the file /etc/samba/smb.conf on your SUSE system. The huge number of settings available in this file provides an interesting demonstration of the flexibility and power of the Samba software suite. The Samba software suite provides excellent documentation about configuring and using every aspect of Samba. In addition, a number of excellent books are available on Samba and Samba 3 at your favorite brick and mortar or online bookstore. One of the best online general resources for Samba is its HOWTO collection, which is actually a single integrated document culled from many different sources by the Samba team. This document is installed as part of the samba-doc package on your SUSE system, and is also available online at many locations, including www.samba.org/samba/docs/man/Samba-HOWTO-Collection/ from the master Samba web site. The Samba HOWTO Collection for Samba 3 provides over 45 examples of Samba configuration files, showing how to configure Samba for scenarios ranging from an anonymous print server to a full-blown SMB server that functions as a primary domain controller. Rather than rehashing existing documentation, this section provides an overview of the format and main sections available in a Samba configuration file. A standard Samba configuration file is divided into a number of primary sections, each delimited by the name of that section enclosed within square brackets. The only mandatory section of a Samba configuration file is the [global] section, which sets values for the Samba server itself, such as the name of the workgroup or domain that the Samba server exports (if it is a PDC) or belongs to (if it is not a PDC). Other than this section, the smb.conf file can contain any number of other sections, each of which describes the attributes of a shared resource that is exported by your Samba server. The sections and associated resources in the default smb.conf file provided with SUSE Linux are the following: . [global] General configuration settings, such as authentication and domain/workgroup information, that apply to all subsequent portions of the smb.conf file. As mentioned in the preceding paragraph, your smb.conf file must contain a [global] section, which is customized to reflect how your Samba server interacts with your local Windows domain or workgroup.
Note: In case you are looking for affordable and reliable webhost to host and run your business application check Vision php5 hosting services

Chapter 18 . Setting Up Windows Interoperability with Samba 519 Tip If you have problems configuring or using the Winbind daemon, you can use the wbinfo command to query the PDC through the winbindd daemon. The information that it returns can help you diagnose Winbind problems by seeing how the winbindd daemon translates various Windows authentication information. For complete information about the wbinfo command, type man wbinfo from the command line within any konsole, xterm, or other terminal emulation window on your SUSE system. Command-Line Utilities for Samba The Samba software suite includes a number of utilities that you may find useful when interacting with Windows networks from the Linux command line. The next few sections provide a brief introduction to some of the more useful ones. You can obtain a complete listing of all of the utilities on your SUSE system that are related to Samba by using the apropos command to identify any commands related to Samba or the SMB protocol, as in the following examples: wvh@linux:~> apropos samba net (8) - Tool for administration of Samba and remote CIFS servers. smb.conf (5) - The configuration file for the Samba suite cupsaddsmb (8) - export printers to samba for windows clients lmhosts (5) - The Samba NetBIOS hosts file wvh@linux:~> apropos SMB smbspool (8) - send a print file to an SMB printer fs (5) - Linux filesystem types: minix, ext, ext2, ext3, xia, msdos, umsdos, vfat, proc, nfs, iso9660, hpfs, sysv, smb, ncpfs smbget (1) - wget-like utility for download files over SMB smbmnt (8) - helper utility for mounting SMB filesystems smb.conf (5) - The configuration file for the Samba suite cupsaddsmb (8) - export printers to samba for windows clients testparm (1) - check an smb.conf configuration file for internal correctness findsmb (1) - list info about machines that respond to SMB name queries on a subnet smbcquotas (1) - Set or get QUOTAs of NTFS 5 shares smbumount (8) - smbfs umount for normal users smbsh (1) - Allows access to remote SMB shares using UNIX commands smbmount (8) - mount an smbfs filesystem smbtar (1) - shell script for backing up SMB/CIFS shares directly to UNIX tape drives smbcacls (1) - Set or get ACLs on an NT file or directory names smbclient (1) - ftp-like client to access SMB/CIFS resources on servers smbtree (1) - A text based smb network browser The Samba- and SMB-related commands that are available on your system will depend on the Samba packages that you installed on your system, as explained in the section Samba Client and Server Packages, later in this chapter.
Note: In case you are looking for affordable and reliable webhost to host and run your business application check Vision ftp web hosting services

518 Part IV . Implementing Network Services in SUSE Linux auth required /lib/security/pam_securetty.so auth required /lib/security/pam_nologin.so auth sufficient /lib/security/pam_winbind.so auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok 3. Modify the account entries in all of the PAM configuration files in /etc/pam.d to contain an account entry such as the following: account required /lib/security/pam_winbind.so 4. Join the existing Windows domain by executing Samba s net command, as in the following example, where PDC is the name or IP address of your Windows primary domain controller and USER is any user with administrative privileges in that domain: net join -S PDC -U USER 5. Add appropriate winbind entries to the [global] section of your Samba server s configuration file, /etc/samba/smb.conf. The entries that you should add are the following, where MYDOMAIN is the name of the Windows domain for which the PDC you specified in the previous step provides authentication information: winbind separator = + winbind cache time = 10 template shell = /bin/bash template homedir = /home/%D/%U idmap uid = 10000-20000 idmap gid = 10000-20000 workgroup = MYDOMAIN security = domain password server = * 6. Start the Winbind daemon (/usr/sbin/winbindd) on your SUSE system, and restart the Samba daemon and NetBIOS name daemon by executing the following commands: /etc/rc.d/nmbd restart /etc/rc.d/smbd restart Any user with an entry in your Windows PDC should now be able to log in on your SUSE system using a username of the form DOMAIN+username and his or her Windows password. If you are using Winbind, you will also want to add a startup entry for the Winbind daemon to the startup scripts for your system s default runlevel, as in the following example for a system whose default runlevel is 5: ln -s /etc/rc.d/winbind /etc/rc.d/rc5.d/S14winbind
Note: In case you are looking for affordable webhost to host and run your servlet application check Vision ecommerce web hosting services

Chapter 18 . Setting Up Windows Interoperability with Samba 517 # smbpasswd -a wvh New SMB password: Retype SMB password: Enter the password that you want to assign to the specified user when prompted for it the password is not echoed to the screen as you type. When you have entered the specified user s Samba password, you must type it again to verify that you didn t mistype the password. The user that you are adding to the Samba password file must be a valid Linux user on your system, for whom an entry exists in the standard Linux /etc/passwd file. If you execute the smbpasswdcommand without an argument, the command attempts to change the password for the current user. If you specify a username without specifying the -a option, the smbpasswd command attempts to change the Samba password for the specified user. For complete information about the smbpasswdcommand, see the online manual page for the command, available by typing mansmbpasswdin any konsole, xterm, or other terminal emulation window. Working with the Winbind Daemon The Winbind daemon, winbindd, enables the Linux name switch service (NSS) to retrieve user and group information from a Windows primary domain controller (PDC). This provides a networked authentication mechanism similar to the Network Information System (NIS and NIS+) often used in computing environments that make heavy use of Sun s Network File System (NFS). The Winbind daemon enables Windows users to log in on a Linux machine using the Windows credentials provided by the PDC without requiring any local user and group entries in the Linux password file. To use winbindd, you must do the following: 1. Add Winbind entries to the /etc/nsswitch.conf file that tells your Linux system the services that it can use for authentication and the order in which those services should be queried for valid authentication information. These entries should look like the following: passwd: files winbind group: files winbind 2. Modify the auth (authentication) entries in all of the Pluggable Authentication Module (PAM) configuration files in the directory /etc/pam.d to contain authentication entries such as the following:
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision best web hosting services

516 Part IV . Implementing Network Services in SUSE Linux Figure 18-20: Setting the Samba administrative password Creating and Managing the Samba Password File Many Samba servers that serve as a PDC or that use workgroup authentication use a Samba-specific password file to store Windows username and password information. On SUSE systems, this file is /etc/samba/smbpasswd. Entries in this file are created and updated using a utility that is also named smpasswd. This file is used only by Samba servers Samba clients use the authentication mechanisms that are provided by the Samba or Windows servers that you are connecting to. If the smbpasswdfile is the only authentication mechanism that you specified when you configured your Samba server, you must create a username and password entry in this file for each user that you want to be able to access any resources that require authentication on that Samba server. To create a Samba authentication entry for a specified user, use the smbpasswd command s -a(add) option and provide the name of that user as an argument to the -aoption, as in the following example:
Note: In case you are looking for affordable webhost to host and run your web application check Vision cheap hosting services

Chapter 18 . Setting Up Windows Interoperability with Samba 515 The pop-up dialog shown in Figure 18-19 lists alternate Samba authentication mechanisms that you can add to the default smbpasswdfile selection that is displayed when you first configure a Samba server. Available authentication mechanisms are the following: smbpasswd file (default) Useful in small networks, but provides a limited amount of information and requires manual replication when multiple Samba servers share a single smbpasswdfile. LDAP Suggested for large sites with multiple Samba servers that share authentication information or that already use LDAP for other purposes. TDB database A trivial database that stores single name/value pairs. Not recommended for sites with more than 250 users or that require sharing authentication information across multiple Samba servers. MySQL database A useful authentication mechanism for sites already running MySQL and using it to store authentication information. Requires that you specify the identifier of the MySQL database that holds the authentication table as an argument in the pop-up menu that is displayed after you select this option. You can then add appropriate entries to the Samba configuration file (discussed later in this chapter) to identify the columns in your MySQL table that contain different portions of your user and authentication information. If you select multiple authentication mechanisms, you can reorder them by selecting one and clicking the Up button to move it to the top of the authentication series or clicking the Down button to move it to the bottom of the authentication series. 7. Click the Finish button to proceed. You will now be prompted for a Samba root password (Figure 18-20). 8. The configuration is now complete, and the YaST Samba server module will exit.
Note: If you are looking for reliable webhost to maintain and run your java application check Vision java hosting services

514 Part IV . Implementing Network Services in SUSE Linux Figure 18-18: Customizing Samba server authentication Figure 18-19: Samba server authentication alternatives
Note: If you are looking for high quality webhost to host and run your jsp application check Vision jsp web hosting services

Chapter 18 . Setting Up Windows Interoperability with Samba 513 To PDC or Not to PDC A domain controller supplies authentication information for a Windows domain. You will rarely want your Samba server to act as a primary domain controller if you want your Samba server to join an existing Windows domain (such as at the office) because your existing Windows domain probably already has a primary domain controller (which proba- bly runs on a Windows system). Starting a second primary domain controller on an existing Windows domain will certainly confuse any Windows systems that are already members of that domain and will definitely irritate your system administrator. However, if you are con- figuring your Samba server to host a new Windows domain, you will want it to act as the primary domain controller for that domain. If you are configuring your Samba server to act as a backup for another Samba server in your domain, you may want to configure it to act as a backup domain controller. If you define a Samba server as a backup domain controller, your primary domain controller must also be a Samba server, because Samba cannot directly access authentication information that is stored in proprietary formats on a Windows primary domain controller. You will therefore have to configure your Samba backup domain controller to use the same authen- tication information as the primary domain controller. If your primary domain controller stores information in Lightweight Directory Access Protocol (LDAP), you can easily configure your backup domain controller to access the same LDAP server. If your primary domain con- troller stores authentication information in a Samba password file, you will have to replicate that file manually on your backup domain controller and make sure that the contents of the two files are always synchronized. Configuring and using an LDAP server is explained in Chapter 25. SUSE provides a number of tools for file synchronization, such as Unison, InterMezzo, and rsync, which are explained in the SUSE Administration Guide that you received with your SUSE distribution. 6. The dialog box shown in Figure 18-18 enables you to specify alternate and auxiliary authentication methods. You may want to specify multiple methods if you want to be able to try various authentication services in order before falling through to the default Samba password file (/etc/samba/smbpasswd). To specify an alternate authentication mechanism, click the Add button on the dialog box shown in Figure 18-18 to display the pop-up dialog shown in Figure 18-19.
Note: In case you are looking for affordable webhost to host and run your servlet application check Vision servlet hosting services

512 Part IV . Implementing Network Services in SUSE Linux Identity. Here you have another chance to set the Windows domain or workgroup name, to decide whether the server is a PDC or not, and to set the Windows NetBIOS hostname (the name by which the server will be seen according to the native Windows naming scheme) (Figure 18-17). Figure 18-17: Samba configuration: Identity tab 5. By default, your Samba server will authenticate users by looking them up in a Samba password file, which is a text file that is explained in the following section of this chapter, Creating and Managing the Samba Password File. To set alternative sources of authentication information, click the Advanced Settings button in the Identity tab (seen in Figure 18-17), and then choose User Authentucation Sources. The screen shown in Figure 18-18 is displayed. Specifying an alternate authentication mechanism is a completely optional step most Samba servers in small and home environments use a Samba password file.
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check Vision mysql hosting services