Using Samba: A File and Print Server for Linux, Unix & Mac OS X, 3rd Edition

Using Samba: A File and Print Server for Linux, Unix & Mac OS X, 3rd Edition

Gerald Carter, Jay Ts, Robert Eckstein

Language: English

Pages: 450

ISBN: 0596007698

Format: PDF / Kindle (mobi) / ePub


This book is the comprehensive guide to Samba administration, officially adopted by the Samba Team. Wondering how to integrate Samba's authentication with that of a Windows domain? How to get Samba to serve Microsoft Dfs shares? How to share files on Mac Os X? These and a dozen other issues of interest to system administrators are covered. A whole chapter is dedicated to troubleshooting!

The range of this book knows few bounds. Using Samba takes you from basic installation and configuration -- on both the client and server side, for a wide range of systems -- to subtle details of security, cross-platform compatibility, and resource discovery that make the difference between whether users see the folder they expect or a cryptic error message.

The current edition covers such advanced 3.x features as:

  • Integration with Active Directory and OpenLdap
  • Migrating from Windows Nt 4.0 domains to Samba
  • Delegating administrative tasks to non-root users
  • Central printer management
  • Advanced file serving features, such as making use of Virtual File System (Vfs) plugins.

Samba is a cross-platform triumph: robust, flexible and fast, it turns a Unix or Linux system into a file and print server for Microsoft Windows network clients. This book will help you make your file and print sharing as powerful and efficient as possible. The authors delve into the internals of the Windows activities and protocols to an unprecedented degree, explaining the strengths and weaknesses of each feature in Windows domains and in Samba itself.

Whether you're playing on your personal computer or an enterprise network, on one note or a full three-octave range, Using Samba will give you an efficient and secure server.

 

 

 

 

 

 

 

 

 

 

 

to Windows sids. ${lockdir}/browse.dat State information maintained by nmbd in relation to network browsing elections. ${lockdir}/wins.dat ${lockdir}/wins.tdb Contains the most recent dump of nmbd’s internal WINS database. This file is applicable only when the wins support parameter has been enabled in smb.conf. Reconfiguring Samba If you have already compiled Samba and wish to recompile the same source code with different configure options, run the following command in the source directory

is the hosts allow and hosts deny options. Unlike the previous two global parameters, these new options can be used on a perservice basis. If these options sound familiar, you’re probably thinking of the hosts.allow and hosts.deny files found in the /etc directories of many Unix systems. The purpose of these options is identical to those files; they provide security by allowing or denying the connections of other hosts based on their IP addresses. However, Samba includes its own internal

parameter operates as it has in past examples. One disadvantage of a public server such as this one is that when a connection is mapped to the guest user, you lose all ability to audit any changes made by that connection. Any files created by this user are owned by the guest user. Other tasks, such as printer page accounting, also become impossible, as all knowledge of the original user is essentially lost. Table 5-2 lists the various guest-related smb.conf parameters, and Table 5-3 lists the

query. 15 Global User Management | 129 Username Maps A username map is a mechanism for translating a login name sent by a client in the session setup request to a local Unix username. It’s independent of any passdb backend. The most common use is to handle usernames that differ between Windows and Unix. Usernames on Windows systems can violate the limits placed by Unix systems on length and characters used, so sometimes the user account must be stored on the Unix or Linux system, and

/data/staff-docs read only = no valid users = +staff Filesystem Differences | 167 Adding the valid users option is not entirely necessary, because access to the share is ultimately determined by the filesystem permissions, but it does two things: • It documents the intent of the share, in case there is ever any question as to what the permissions should be. • It protects the share somewhat if the file permissions on /data/staff-docs are accidentally changed to something less restrictive. The

Download sample

Download