From cad70ca6eda6498db9acdae97fade2c615c3ce5b Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 28 Aug 2003 22:13:10 +0000 Subject: Regenerate docs (This used to be commit b78c6ee1d155f255d329899c237281c7cf662260) --- docs/htmldocs/Samba-HOWTO-Collection.html | 4329 +++++++++++++++-------------- 1 file changed, 2166 insertions(+), 2163 deletions(-) (limited to 'docs/htmldocs/Samba-HOWTO-Collection.html') diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index a721fea6f1..bd68f32566 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -22,7 +22,7 @@ Samba is always under development, and so is its' documentation. This release of documentation represents a major revision or layout as well as contents. The most recent version of this document can be found at http://www.samba.org/ -on the "Documentation" page. Please send updates to +on the "Documentation" page. Please send updates to Jelmer Vernooij, John H. Terpstra or Gerald (Jerry) Carter. @@ -31,53 +31,53 @@ The Samba-Team would like to express sincere thanks to the many people who have or without their knowledge contributed to this update. The size and scope of this project would not have been possible without significant community contribution. A not insignificant number of ideas for inclusion (if not content itself) has been obtained -from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. +from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. -

Table of Contents

Legal Notice
Attributions
I. General Installation
1. Introduction to Samba
Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous
2. How to Install and Test SAMBA
Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your - server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"
3. Fast Start for the Impatient
Note
II. Server Configuration Basics
4. Server Types and Security Modes
Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server
5. Domain Control
Features and Benefits
Basics of Domain Control
Domain Controller Types
Preparing for Domain Control
Domain Control - Example Configuration
Samba ADS Domain Control
Domain and Network Logon Configuration
Domain Network Logon Service
Security Mode and Master Browsers
Common Errors
'$' cannot be included in machine name
Joining domain fails because of existing machine account
The system can not log you on (C000019B)....
The machine trust account not accessible
Account disabled
Domain Controller Unavailable
Can not log onto domain member workstation after joining domain
6. Backup Domain Control
Features And Benefits
Essential Background Information
MS Windows NT4 Style Domain Control
Active Directory Domain Control
What qualifies a Domain Controller on the network?
How does a Workstation find its domain controller?
Backup Domain Controller Configuration
Example Configuration
Common Errors
Machine Accounts keep expiring, what can I do?
Can Samba be a Backup Domain Controller to an NT4 PDC?
How do I replicate the smbpasswd file?
Can I do this all with LDAP?
7. Domain Membership
Features and Benefits
MS Windows Workstation/Server Machine Trust Accounts
Manual Creation of Machine Trust Accounts
Using NT4 Server Manager to Add Machine Accounts to the Domain
"On-the-Fly" Creation of Machine Trust Accounts
Making an MS Windows Workstation or Server a Domain Member
Domain Member Server
Joining an NT4 type Domain with Samba-3
Why is this better than security = server?
Samba ADS Domain Membership
Setup your smb.conf
Setup your /etc/krb5.conf
Create the computer account
Test your server setup
Testing with smbclient
Notes
Common Errors
Can Not Add Machine Back to Domain
Adding Machine to Domain Fails
I can't join a Windows 2003 PDC
8. Stand-Alone Servers
Features and Benefits
Background
Example Configuration
Reference Documentation Server
Central Print Serving
Common Errors
9. MS Windows Network Configuration Guide
Note
III. Advanced Configuration
10. Samba / MS Windows Network Browsing Guide
Features and Benefits
What is Browsing?
Discussion
NetBIOS over TCP/IP
TCP/IP - without NetBIOS
DNS and Active Directory
How Browsing Functions
Setting up WORKGROUP Browsing
Setting up DOMAIN Browsing
Forcing Samba to be the master
Making Samba the domain master
Note about broadcast addresses
Multiple interfaces
Use of the Remote Announce parameter
Use of the Remote Browse Sync parameter
WINS - The Windows Internetworking Name Server
Setting up a WINS server
WINS Replication
Static WINS Entries
Helpful Hints
Windows Networking Protocols
Name Resolution Order
Technical Overview of browsing
Browsing support in Samba
Problem resolution
Browsing across subnets
Common Errors
How can one flush the Samba NetBIOS name cache without restarting Samba?
My client reports "This server is not configured to list shared resources"
I get an Unable to browse the network error
11. Account Information Databases
Features and Benefits
Backwards Compatibility Backends
New Backends
Technical Information
Important Notes About Security
Mapping User Identifiers between MS Windows and UNIX
Mapping Common UIDs/GIDs on Distributed Machines
Account Management Tools
The smbpasswd Command
The pdbedit Command
Password Backends
Plain Text
smbpasswd - Encrypted Password Database
tdbsam
ldapsam
MySQL
XML
Common Errors
Users can not logon
Users being added to wrong backend database
auth methods does not work
12. Mapping MS Windows and UNIX Groups
Features and Benefits
Discussion
Example Configuration
Configuration Scripts
Sample smb.conf add group script
Script to configure Group Mapping
Common Errors
Adding Groups Fails
Adding MS Windows Groups to MS Windows Groups Fails
Adding Domain Users to the Power Users group
13. File, Directory and Share Access Controls
Features and Benefits
File System Access Controls
MS Windows NTFS Comparison with UNIX File Systems
Managing Directories
File and Directory Access Control
Share Definition Access Controls
User and Group Based Controls
File and Directory Permissions Based Controls
Miscellaneous Controls
Access Controls on Shares
Share Permissions Management
MS Windows Access Control Lists and UNIX Interoperability
Managing UNIX permissions Using NT Security Dialogs
Viewing File Security on a Samba Share
Viewing file ownership
Viewing File or Directory Permissions
Modifying file or directory permissions
Interaction with the standard Samba create mask - parameters
Interaction with the standard Samba file attribute mapping
Common Errors
Users can not write to a public share
I have set force user but Samba still makes root the owner of all the files I touch!
MS Word with Samba changes owner of file
14. File and Record Locking
Features and Benefits
Discussion
Opportunistic Locking Overview
Samba Opportunistic Locking Control
Example Configuration
MS Windows Opportunistic Locking and Caching Controls
Workstation Service Entries
Server Service Entries
Persistent Data Corruption
Common Errors
locking.tdb error messages
Problems saving files in MS Office on Windows XP
Long delays deleting files over network with XP SP1
Additional Reading
15. Securing Samba
Introduction
Features and Benefits
Technical Discussion of Protective Measures and Issues
Using host based protection
User based protection
Using interface protection
Using a firewall
Using a IPC$ share deny
NTLMv2 Security
Upgrading Samba
Common Errors
Smbclient works on localhost, but the network is dead
Why can users access home directories of other users?
16. Interdomain Trust Relationships
Features and Benefits
Trust Relationship Background
Native MS Windows NT4 Trusts Configuration
Creating an NT4 Domain Trust
Completing an NT4 Domain Trust
Inter-Domain Trust Facilities
Configuring Samba NT-style Domain Trusts
Samba as the Trusted Domain
Samba as the Trusting Domain
NT4-style Domain Trusts with Windows 2000
Common Errors
17. Hosting a Microsoft Distributed File System tree on Samba
Features and Benefits
Common Errors
18. Classical Printing Support
Features and Benefits
Technical Introduction
What happens if you send a Job from a Client
Printing Related Configuration Parameters
Parameters Recommended for Use
A simple Configuration to Print
Verification of "Settings in Use" with testparm
A little Experiment to warn you
Extended Sample Configuration to Print
Detailed Explanation of the Example's Settings
The [global] Section
The [printers] Section
Any [my_printer_name] Section
Print Commands
Default Print Commands for various UNIX Print Subsystems
Setting up your own Print Commands
Innovations in Samba Printing since 2.2
Client Drivers on Samba Server for Point'n'Print
The [printer$] Section is removed from Samba 3
Creating the [print$] Share
Parameters in the [print$] Section
Subdirectory Structure in [print$]
Installing Drivers into [print$]
Setting Drivers for existing Printers with a Client GUI
Setting Drivers for existing Printers with -rpcclient
Client Driver Install Procedure
The first Client Driver Installation
IMPORTANT! Setting Device Modes on new Printers
Further Client Driver Install Procedures
Always make first Client Connection as root or "printer admin"
Other Gotchas
Setting Default Print Options for the Client Drivers
Supporting large Numbers of Printers
Adding new Printers with the Windows NT APW
Weird Error Message Cannot connect under a -different Name
Be careful when assembling Driver Files
Samba and Printer Ports
Avoiding the most common Misconfigurations of the Client Driver
The Imprints Toolset
What is Imprints?
Creating Printer Driver Packages
The Imprints Server
The Installation Client
Add Network Printers at Logon without User Interaction
The addprinter command
Migration of "Classical" printing to Samba
Publishing Printer Information in Active Directory or LDAP
Common Errors
I give my root password but I don't get access
My printjobs get spooled into the spooling directory, but then get lost
19. CUPS Printing Support in Samba 3.0
Introduction
Features and Benefits
Overview
Basic Configuration of CUPS support
Linking of smbd with libcups.so
Simple smb.conf Settings for CUPS
More complex smb.conf Settings for -CUPS
Advanced Configuration
Central spooling vs. "Peer-to-Peer" printing
CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
Driver Installation Methods on Windows Clients
Explicitly enable "raw" printing for -application/octet-stream!
Three familiar Methods for driver upload plus a new one
Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download
GDI on Windows -- PostScript on UNIX
Windows Drivers, GDI and EMF
UNIX Printfile Conversion and GUI Basics
PostScript and Ghostscript
Ghostscript -- the Software RIP for non-PostScript Printers
PostScript Printer Description (PPD) Specification
CUPS can use all Windows-formatted Vendor PPDs
CUPS also uses PPDs for non-PostScript Printers
The CUPS Filtering Architecture
MIME types and CUPS Filters
MIME type Conversion Rules
Filter Requirements
Prefilters
pstops
pstoraster
imagetops and imagetoraster
rasterto [printers specific]
CUPS Backends
cupsomatic/Foomatic -- how do they fit into the Picture?
The Complete Picture
mime.convs
"Raw" printing
"application/octet-stream" printing
PostScript Printer Descriptions (PPDs) for non-PS Printers
Difference between cupsomatic/foomatic-rip and -native CUPS printing
Examples for filtering Chains
Sources of CUPS drivers / PPDs
Printing with Interface Scripts
Network printing (purely Windows)
From Windows Clients to an NT Print Server
Driver Execution on the Client
Driver Execution on the Server
Network Printing (Windows clients -- UNIX/Samba Print -Servers)
From Windows Clients to a CUPS/Samba Print Server
Samba receiving Jobfiles and passing them to CUPS
Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
PPDs for non-PS Printers on UNIX
PPDs for non-PS Printers on Windows
Windows Terminal Servers (WTS) as CUPS Clients
Printer Drivers running in "Kernel Mode" cause many -Problems
Workarounds impose Heavy Limitations
CUPS: a "Magical Stone"?
PostScript Drivers with no major problems -- even in Kernel -Mode
Setting up CUPS for driver Download
cupsaddsmb: the unknown Utility
Prepare your smb.conf for cupsaddsmb
CUPS Package of "PostScript Driver for WinNT/2k/XP"
Recognize the different Driver Files
Acquiring the Adobe Driver Files
ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
Caveats to be considered
Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver
Run "cupsaddsmb" (quiet Mode)
Run "cupsaddsmb" with verbose Output
Understanding cupsaddsmb
How to recognize if cupsaddsmb completed successfully
cupsaddsmb with a Samba PDC
cupsaddsmb Flowchart
Installing the PostScript Driver on a Client
Avoiding critical PostScript Driver Settings on the -Client
Installing PostScript Driver Files manually (using -rpcclient)
A Check of the rpcclient man Page
Understanding the rpcclient man page
Producing an Example by querying a Windows Box
What is required for adddriver and setdriver to succeed
Manual Driver Installation in 15 Steps
Troubleshooting revisited
The printing *.tdb Files
Trivial DataBase Files
Binary Format
Losing *.tdb Files
Using tdbbackup
CUPS Print Drivers from Linuxprinting.org
foomatic-rip and Foomatic explained
foomatic-rip and Foomatic-PPD Download and Installation
Page Accounting with CUPS
Setting up Quotas
Correct and incorrect Accounting
Adobe and CUPS PostScript Drivers for Windows Clients
The page_log File Syntax
Possible Shortcomings
Future Developments
Other Accounting Tools
Additional Material
Auto-Deletion or Preservation of CUPS Spool Files
CUPS Configuration Settings explained
Pre-conditions
Manual Configuration
In Case of Trouble.....
Printing from CUPS to Windows attached -Printers
More CUPS filtering Chains
Common Errors
Win9x client can't install driver
"cupsaddsmb" keeps asking for root password in - neverending loop
"cupsaddsmb" gives "No PPD file for printer..." - message while PPD file is present
Client can't connect to Samba printer
Can't reconnect to Samba under new account - from Win2K/XP
Avoid being connected to the Samba server as the - "wrong" user
Upgrading to CUPS drivers from Adobe drivers on - NT/2K/XP clients gives problems
Can't use "cupsaddsmb" on Samba server which is - a PDC
Deleted Win2K printer driver is still shown
Win2K/XP "Local Security - Policies"
WinXP clients: "Administrator can not install - printers for all local users"
"Print Change Notify" functions on - NT-clients
WinXP-SP1
Print options for all users can't be set on Win2K/XP
Most common blunders in driver - settings on Windows clients
cupsaddsmb does not work - with newly installed printer
Permissions on +

Table of Contents

Legal Notice
Attributions
I. General Installation
1. Introduction to Samba
Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous
2. How to Install and Test SAMBA
Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your + server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"
3. Fast Start for the Impatient
Note
II. Server Configuration Basics
4. Server Types and Security Modes
Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server
5. Domain Control
Features and Benefits
Basics of Domain Control
Domain Controller Types
Preparing for Domain Control
Domain Control - Example Configuration
Samba ADS Domain Control
Domain and Network Logon Configuration
Domain Network Logon Service
Security Mode and Master Browsers
Common Errors
'$' cannot be included in machine name
Joining domain fails because of existing machine account
The system can not log you on (C000019B)....
The machine trust account not accessible
Account disabled
Domain Controller Unavailable
Can not log onto domain member workstation after joining domain
6. Backup Domain Control
Features And Benefits
Essential Background Information
MS Windows NT4 Style Domain Control
Active Directory Domain Control
What qualifies a Domain Controller on the network?
How does a Workstation find its domain controller?
Backup Domain Controller Configuration
Example Configuration
Common Errors
Machine Accounts keep expiring, what can I do?
Can Samba be a Backup Domain Controller to an NT4 PDC?
How do I replicate the smbpasswd file?
Can I do this all with LDAP?
7. Domain Membership
Features and Benefits
MS Windows Workstation/Server Machine Trust Accounts
Manual Creation of Machine Trust Accounts
Using NT4 Server Manager to Add Machine Accounts to the Domain
"On-the-Fly" Creation of Machine Trust Accounts
Making an MS Windows Workstation or Server a Domain Member
Domain Member Server
Joining an NT4 type Domain with Samba-3
Why is this better than security = server?
Samba ADS Domain Membership
Setup your smb.conf
Setup your /etc/krb5.conf
Create the computer account
Test your server setup
Testing with smbclient
Notes
Common Errors
Can Not Add Machine Back to Domain
Adding Machine to Domain Fails
8. Stand-Alone Servers
Features and Benefits
Background
Example Configuration
Reference Documentation Server
Central Print Serving
Common Errors
9. MS Windows Network Configuration Guide
Note
III. Advanced Configuration
10. Samba / MS Windows Network Browsing Guide
Features and Benefits
What is Browsing?
Discussion
NetBIOS over TCP/IP
TCP/IP - without NetBIOS
DNS and Active Directory
How Browsing Functions
Setting up WORKGROUP Browsing
Setting up DOMAIN Browsing
Forcing Samba to be the master
Making Samba the domain master
Note about broadcast addresses
Multiple interfaces
Use of the Remote Announce parameter
Use of the Remote Browse Sync parameter
WINS - The Windows Internetworking Name Server
Setting up a WINS server
WINS Replication
Static WINS Entries
Helpful Hints
Windows Networking Protocols
Name Resolution Order
Technical Overview of browsing
Browsing support in Samba
Problem resolution
Browsing across subnets
Common Errors
How can one flush the Samba NetBIOS name cache without restarting Samba?
My client reports "This server is not configured to list shared resources"
I get an Unable to browse the network error
11. Account Information Databases
Features and Benefits
Backwards Compatibility Backends
New Backends
Technical Information
Important Notes About Security
Mapping User Identifiers between MS Windows and UNIX
Mapping Common UIDs/GIDs on Distributed Machines
Account Management Tools
The smbpasswd Command
The pdbedit Command
Password Backends
Plain Text
smbpasswd - Encrypted Password Database
tdbsam
ldapsam
MySQL
XML
Common Errors
Users can not logon
Users being added to wrong backend database
auth methods does not work
12. Mapping MS Windows and UNIX Groups
Features and Benefits
Discussion
Example Configuration
Configuration Scripts
Sample smb.conf add group script
Script to configure Group Mapping
Common Errors
Adding Groups Fails
Adding MS Windows Groups to MS Windows Groups Fails
Adding Domain Users to the Power Users group
13. File, Directory and Share Access Controls
Features and Benefits
File System Access Controls
MS Windows NTFS Comparison with UNIX File Systems
Managing Directories
File and Directory Access Control
Share Definition Access Controls
User and Group Based Controls
File and Directory Permissions Based Controls
Miscellaneous Controls
Access Controls on Shares
Share Permissions Management
MS Windows Access Control Lists and UNIX Interoperability
Managing UNIX permissions Using NT Security Dialogs
Viewing File Security on a Samba Share
Viewing file ownership
Viewing File or Directory Permissions
Modifying file or directory permissions
Interaction with the standard Samba create mask + parameters
Interaction with the standard Samba file attribute mapping
Common Errors
Users can not write to a public share
I have set force user but Samba still makes root the owner of all the files I touch!
MS Word with Samba changes owner of file
14. File and Record Locking
Features and Benefits
Discussion
Opportunistic Locking Overview
Samba Opportunistic Locking Control
Example Configuration
MS Windows Opportunistic Locking and Caching Controls
Workstation Service Entries
Server Service Entries
Persistent Data Corruption
Common Errors
locking.tdb error messages
Problems saving files in MS Office on Windows XP
Long delays deleting files over network with XP SP1
Additional Reading
15. Securing Samba
Introduction
Features and Benefits
Technical Discussion of Protective Measures and Issues
Using host based protection
User based protection
Using interface protection
Using a firewall
Using a IPC$ share deny
NTLMv2 Security
Upgrading Samba
Common Errors
Smbclient works on localhost, but the network is dead
Why can users access home directories of other users?
16. Interdomain Trust Relationships
Features and Benefits
Trust Relationship Background
Native MS Windows NT4 Trusts Configuration
Creating an NT4 Domain Trust
Completing an NT4 Domain Trust
Inter-Domain Trust Facilities
Configuring Samba NT-style Domain Trusts
Samba as the Trusted Domain
Samba as the Trusting Domain
NT4-style Domain Trusts with Windows 2000
Common Errors
17. Hosting a Microsoft Distributed File System tree on Samba
Features and Benefits
Common Errors
18. Classical Printing Support
Features and Benefits
Technical Introduction
What happens if you send a Job from a Client
Printing Related Configuration Parameters
Parameters Recommended for Use
A simple Configuration to Print
Verification of "Settings in Use" with testparm
A little Experiment to warn you
Extended Sample Configuration to Print
Detailed Explanation of the Example's Settings
The [global] Section
The [printers] Section
Any [my_printer_name] Section
Print Commands
Default Print Commands for various UNIX Print Subsystems
Setting up your own Print Commands
Innovations in Samba Printing since 2.2
Client Drivers on Samba Server for Point'n'Print
The [printer$] Section is removed from Samba 3
Creating the [print$] Share
Parameters in the [print$] Section
Subdirectory Structure in [print$]
Installing Drivers into [print$]
Setting Drivers for existing Printers with a Client GUI
Setting Drivers for existing Printers with +rpcclient
Client Driver Install Procedure
The first Client Driver Installation
IMPORTANT! Setting Device Modes on new Printers
Further Client Driver Install Procedures
Always make first Client Connection as root or "printer admin"
Other Gotchas
Setting Default Print Options for the Client Drivers
Supporting large Numbers of Printers
Adding new Printers with the Windows NT APW
Weird Error Message Cannot connect under a +different Name
Be careful when assembling Driver Files
Samba and Printer Ports
Avoiding the most common Misconfigurations of the Client Driver
The Imprints Toolset
What is Imprints?
Creating Printer Driver Packages
The Imprints Server
The Installation Client
Add Network Printers at Logon without User Interaction
The addprinter command
Migration of "Classical" printing to Samba
Publishing Printer Information in Active Directory or LDAP
Common Errors
I give my root password but I don't get access
My printjobs get spooled into the spooling directory, but then get lost
19. CUPS Printing Support in Samba 3.0
Introduction
Features and Benefits
Overview
Basic Configuration of CUPS support
Linking of smbd with libcups.so
Simple smb.conf Settings for CUPS
More complex smb.conf Settings for +CUPS
Advanced Configuration
Central spooling vs. "Peer-to-Peer" printing
CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
Driver Installation Methods on Windows Clients
Explicitly enable "raw" printing for +application/octet-stream!
Three familiar Methods for driver upload plus a new one
Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download
GDI on Windows -- PostScript on UNIX
Windows Drivers, GDI and EMF
UNIX Printfile Conversion and GUI Basics
PostScript and Ghostscript
Ghostscript -- the Software RIP for non-PostScript Printers
PostScript Printer Description (PPD) Specification
CUPS can use all Windows-formatted Vendor PPDs
CUPS also uses PPDs for non-PostScript Printers
The CUPS Filtering Architecture
MIME types and CUPS Filters
MIME type Conversion Rules
Filter Requirements
Prefilters
pstops
pstoraster
imagetops and imagetoraster
rasterto [printers specific]
CUPS Backends
cupsomatic/Foomatic -- how do they fit into the Picture?
The Complete Picture
mime.convs
"Raw" printing
"application/octet-stream" printing
PostScript Printer Descriptions (PPDs) for non-PS Printers
Difference between cupsomatic/foomatic-rip and +native CUPS printing
Examples for filtering Chains
Sources of CUPS drivers / PPDs
Printing with Interface Scripts
Network printing (purely Windows)
From Windows Clients to an NT Print Server
Driver Execution on the Client
Driver Execution on the Server
Network Printing (Windows clients -- UNIX/Samba Print +Servers)
From Windows Clients to a CUPS/Samba Print Server
Samba receiving Jobfiles and passing them to CUPS
Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
PPDs for non-PS Printers on UNIX
PPDs for non-PS Printers on Windows
Windows Terminal Servers (WTS) as CUPS Clients
Printer Drivers running in "Kernel Mode" cause many +Problems
Workarounds impose Heavy Limitations
CUPS: a "Magical Stone"?
PostScript Drivers with no major problems -- even in Kernel +Mode
Setting up CUPS for driver Download
cupsaddsmb: the unknown Utility
Prepare your smb.conf for cupsaddsmb
CUPS Package of "PostScript Driver for WinNT/2k/XP"
Recognize the different Driver Files
Acquiring the Adobe Driver Files
ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
Caveats to be considered
Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
Run "cupsaddsmb" (quiet Mode)
Run "cupsaddsmb" with verbose Output
Understanding cupsaddsmb
How to recognize if cupsaddsmb completed successfully
cupsaddsmb with a Samba PDC
cupsaddsmb Flowchart
Installing the PostScript Driver on a Client
Avoiding critical PostScript Driver Settings on the +Client
Installing PostScript Driver Files manually (using +rpcclient)
A Check of the rpcclient man Page
Understanding the rpcclient man page
Producing an Example by querying a Windows Box
What is required for adddriver and setdriver to succeed
Manual Driver Installation in 15 Steps
Troubleshooting revisited
The printing *.tdb Files
Trivial DataBase Files
Binary Format
Losing *.tdb Files
Using tdbbackup
CUPS Print Drivers from Linuxprinting.org
foomatic-rip and Foomatic explained
foomatic-rip and Foomatic-PPD Download and Installation
Page Accounting with CUPS
Setting up Quotas
Correct and incorrect Accounting
Adobe and CUPS PostScript Drivers for Windows Clients
The page_log File Syntax
Possible Shortcomings
Future Developments
Other Accounting Tools
Additional Material
Auto-Deletion or Preservation of CUPS Spool Files
CUPS Configuration Settings explained
Pre-conditions
Manual Configuration
In Case of Trouble.....
Printing from CUPS to Windows attached +Printers
More CUPS filtering Chains
Common Errors
Win9x client can't install driver
"cupsaddsmb" keeps asking for root password in + neverending loop
"cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
Client can't connect to Samba printer
Can't reconnect to Samba under new account + from Win2K/XP
Avoid being connected to the Samba server as the + "wrong" user
Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
Can't use "cupsaddsmb" on Samba server which is + a PDC
Deleted Win2K printer driver is still shown
Win2K/XP "Local Security + Policies"
WinXP clients: "Administrator can not install + printers for all local users"
"Print Change Notify" functions on + NT-clients
WinXP-SP1
Print options for all users can't be set on Win2K/XP
Most common blunders in driver + settings on Windows clients
cupsaddsmb does not work + with newly installed printer
Permissions on /var/spool/samba/ get reset after each -reboot
Printer named "lp" +reboot
Printer named "lp" intermittently swallows jobs and spits out completely different -ones
Location of Adobe PostScript driver files necessary for "cupsaddsmb"
An Overview of the CUPS Printing Processes
20. Stackable VFS modules
Features and Benefits
Discussion
Included modules
audit
extd_audit
fake_perms
recycle
netatalk
VFS modules available elsewhere
DatabaseFS
vscan
21. Winbind: Use of Domain Accounts
Features and Benefits
Introduction
What Winbind Provides
Target Uses
How Winbind Works
Microsoft Remote Procedure Calls
Microsoft Active Directory Services
Name Service Switch
Pluggable Authentication Modules
User and Group ID Allocation
Result Caching
Installation and Configuration
Introduction
Requirements
Testing Things Out
Conclusion
Common Errors
NSCD Problem Warning
22. Advanced Network Management
Features and Benefits
Remote Server Administration
Remote Desktop Management
Remote Management from NoMachines.Com
Network Logon Script Magic
Adding printers without user intervention
Common Errors
23. System and Account Policies
Features and Benefits
Creating and Managing System Policies
Windows 9x/Me Policies
Windows NT4 Style Policy Files
MS Windows 200x / XP Professional Policies
Managing Account/User Policies
Samba Editreg Toolset
Windows NT4/200x
Samba PDC
System Startup and Logon Processing Overview
Common Errors
Policy Does Not Work
24. Desktop Profile Management
Features and Benefits
Roaming Profiles
Samba Configuration for Profile Handling
Windows Client Profile Configuration Information
Sharing Profiles between W9x/Me and NT4/200x/XP workstations
Profile Migration from Windows NT4/200x Server to Samba
Mandatory profiles
Creating/Managing Group Profiles
Default Profile for Windows Users
MS Windows 9x/Me
MS Windows NT4 Workstation
MS Windows 200x/XP
Common Errors
Setting up roaming profiles for just a few user's or group's?
Can NOT use Roaming Profiles
Changing the default profile
25. PAM based Distributed Authentication
Features and Benefits
Technical Discussion
PAM Configuration Syntax
Example System Configurations
smb.conf PAM Configuration
Remote CIFS Authentication using winbindd.so
Password Synchronization using pam_smbpass.so
Common Errors
pam_winbind problem
Winbind is not resolving users and groups
26. Integrating MS Windows networks with Samba
Features and Benefits
Background Information
Name Resolution in a pure UNIX/Linux world
/etc/hosts
/etc/resolv.conf
/etc/host.conf
/etc/nsswitch.conf
Name resolution as used within MS Windows networking
The NetBIOS Name Cache
The LMHOSTS file
HOSTS file
DNS Lookup
WINS Lookup
Common Errors
Pinging works only in one way
Very Slow Network Connections
Samba server name change problem
27. Unicode/Charsets
Features and Benefits
What are charsets and unicode?
Samba and charsets
Conversion from old names
Japanese charsets
Common errors
CP850.so can't be found
28. Samba Backup Techniques
Note
Features and Benefits
29. High Availability Options
Note
IV. Migration and Updating
30. Upgrading from Samba-2.x to Samba-3.0.0
New Features in Samba-3
Configuration Parameter Changes
Removed Parameters
New Parameters
Modified Parameters (changes in behavior):
New Functionality
Databases
Changes in Behavior
Charsets
Passdb Backends and Authentication
Charsets
LDAP
31. Migration from NT4 PDC to Samba-3 PDC
Planning and Getting Started
Objectives
Steps In Migration Process
Migration Options
Planning for Success
Samba-3 Implementation Choices
32. SWAT - The Samba Web Administration Tool
Features and Benefits
Enabling SWAT for use
Securing SWAT through SSL
The SWAT Home Page
Global Settings
Share Settings
Printers Settings
The SWAT Wizard
The Status Page
The View Page
The Password Change Page
V. Troubleshooting
33. The Samba checklist
Introduction
Assumptions
The tests
34. Analysing and solving samba problems
Diagnostics tools
Debugging with Samba itself
Tcpdump
Ethereal
The Windows Network Monitor
Useful URLs
Getting help from the mailing lists
How to get off the mailing lists
35. Reporting Bugs
Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches
VI. Appendixes
36. How to compile Samba
Access Samba source code via CVS
Introduction
CVS Access to samba.org
Accessing the samba sources via rsync and ftp
Verifying Samba's PGP signature
Building the Binaries
Compiling samba with Active Directory support
Starting the smbd and nmbd
Starting from inetd.conf
Alternative: starting it as a daemon
37. Portability
HPUX
SCO UNIX
DNIX
RedHat Linux Rembrandt-II
AIX
Sequential Read Ahead
Solaris
Locking improvements
Winbind on Solaris 9
38. Samba and other CIFS clients
Macintosh clients?
OS2 Client
Configuring OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba
Configuring OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba
Printer driver download for for OS/2 clients?
Windows for Workgroups
Latest TCP/IP stack from Microsoft
Delete .pwl files after password change
Configuring WfW password handling
Case handling of passwords
Use TCP/IP as default protocol
Speed improvement
Windows '95/'98
Speed improvement
Windows 2000 Service Pack 2
Windows NT 3.1
39. Samba Performance Tuning
Comparisons
Socket options
Read size
Max xmit
Log level
Read raw
Write raw
Slow Logins
Client tuning
Samba performance problem due changing kernel
Corrupt tdb Files
40. DNS and DHCP Configuration Guide
Note
41. Further Resources
Websites
Related updates from Microsoft
Index

List of Figures

5.1. An Example Domain
10.1. Cross subnet browsing example
11.1. IDMAP
12.1. IDMAP groups
13.1. Overview of unix permissions field
16.1. Trusts overview
19.1. Windows Printing to a local Printer
19.2. Printing to a Postscript Printer
19.3. Ghostscript as a RIP for non-postscript printers
19.4. Prefiltering in CUPS to form Postscript
19.5. Adding Device-specific Print Options
19.6. Postscript to intermediate Raster format
19.7. CUPS-raster production using Ghostscript
19.8. Image format to CUPS-raster format conversion
19.9. Raster to Printer Specific formats
19.10. cupsomatic/foomatic processing versus Native CUPS
19.11. PDF to socket chain
19.12. PDF to USB chain
19.13. Print Driver execution on the Client
19.14. Print Driver execution on the Server
19.15. Printing via CUPS/samba server
19.16. cupsaddsmb flowchart
19.17. Filtering chain 1
19.18. Filtering chain with cupsomatic
19.19. CUPS Printing Overview

List of Tables

7.1. Assumptions
10.1. Browse subnet example 1
10.2. Browse subnet example 2
10.3. Browse subnet example 3
10.4. Browse subnet example 4
11.1. Attributes in the sambaSamAccount objectclass (LDAP)
11.2. Basic smb.conf options for MySQL passdb backend
11.3. MySQL field names for MySQL passdb backend
13.1. Managing directories with unix and windows
13.2. User and Group Based Controls
13.3. File and Directory Permission Based Controls
13.4. Other Controls
19.1. PPD's shipped with CUPS
20.1. Extended Auditing Log Information
24.1. User Shell Folder registry keys default values
24.2. Defaults of profile settings registry keys
24.3. Defaults of default user profile paths registry keys
25.1. Options recognized by pam_smbpass
26.1. Unique NetBIOS names
26.2. Group Names
30.1. TDB File Descriptions
31.1. The 3 Major Site Types
31.2. Nature of the Conversion Choices

List of Examples

2.1. Simplest possible smb.conf file
5.1. smb.conf for being a PDC
5.2. smb.conf for being a PDC
6.1. Minimal smb.conf for being a PDC
6.2. Minimal setup for being a BDC
8.1. smb.conf for Reference Documentation Server
8.2. smb.conf for anonymous printing
10.1. Domain master browser smb.conf
10.2. Local master browser smb.conf
10.3. smb.conf for not being a master browser
10.4. Local master browser smb.conf
10.5. smb.conf for not being a master browser
11.1.
11.2. Configuration with LDAP
12.1. smbgrpadd.sh
13.1. Example File
14.1. Share with some files oplocked
14.2.
17.1. smb.conf with DFS configured
18.1. Simple configuration with BSD printing
18.2. Extended configuration with BSD printing
18.3. [print\$] example
19.1. Simplest printing-related smb.conf
19.2. Overriding global CUPS settings for one printer
19.3. smb.conf for cupsaddsmb usage
20.1. smb.conf with VFS modules
20.2. smb.conf with multiple VFS modules
21.1. smb.conf for winbind set-up
33.1. smb.conf with [tmp] share
38.1. Minimal profile share

Legal Notice

+ones

Location of Adobe PostScript driver files necessary for "cupsaddsmb"
An Overview of the CUPS Printing Processes
20. Stackable VFS modules
Features and Benefits
Discussion
Included modules
audit
extd_audit
fake_perms
recycle
netatalk
VFS modules available elsewhere
DatabaseFS
vscan
21. Winbind: Use of Domain Accounts
Features and Benefits
Introduction
What Winbind Provides
Target Uses
How Winbind Works
Microsoft Remote Procedure Calls
Microsoft Active Directory Services
Name Service Switch
Pluggable Authentication Modules
User and Group ID Allocation
Result Caching
Installation and Configuration
Introduction
Requirements
Testing Things Out
Conclusion
Common Errors
NSCD Problem Warning
22. Advanced Network Management
Features and Benefits
Remote Server Administration
Remote Desktop Management
Remote Management from NoMachines.Com
Network Logon Script Magic
Adding printers without user intervention
Common Errors
23. System and Account Policies
Features and Benefits
Creating and Managing System Policies
Windows 9x/Me Policies
Windows NT4 Style Policy Files
MS Windows 200x / XP Professional Policies
Managing Account/User Policies
Samba Editreg Toolset
Windows NT4/200x
Samba PDC
System Startup and Logon Processing Overview
Common Errors
Policy Does Not Work
24. Desktop Profile Management
Features and Benefits
Roaming Profiles
Samba Configuration for Profile Handling
Windows Client Profile Configuration Information
Sharing Profiles between W9x/Me and NT4/200x/XP workstations
Profile Migration from Windows NT4/200x Server to Samba
Mandatory profiles
Creating/Managing Group Profiles
Default Profile for Windows Users
MS Windows 9x/Me
MS Windows NT4 Workstation
MS Windows 200x/XP
Common Errors
Setting up roaming profiles for just a few user's or group's?
Can NOT use Roaming Profiles
Changing the default profile
25. PAM based Distributed Authentication
Features and Benefits
Technical Discussion
PAM Configuration Syntax
Example System Configurations
smb.conf PAM Configuration
Remote CIFS Authentication using winbindd.so
Password Synchronization using pam_smbpass.so
Common Errors
pam_winbind problem
Winbind is not resolving users and groups
26. Integrating MS Windows networks with Samba
Features and Benefits
Background Information
Name Resolution in a pure UNIX/Linux world
/etc/hosts
/etc/resolv.conf
/etc/host.conf
/etc/nsswitch.conf
Name resolution as used within MS Windows networking
The NetBIOS Name Cache
The LMHOSTS file
HOSTS file
DNS Lookup
WINS Lookup
Common Errors
Pinging works only in one way
Very Slow Network Connections
Samba server name change problem
27. Unicode/Charsets
Features and Benefits
What are charsets and unicode?
Samba and charsets
Conversion from old names
Japanese charsets
Common errors
CP850.so can't be found
28. Samba Backup Techniques
Note
Features and Benefits
29. High Availability Options
Note
IV. Migration and Updating
30. Upgrading from Samba-2.x to Samba-3.0.0
New Features in Samba-3
Configuration Parameter Changes
Removed Parameters
New Parameters
Modified Parameters (changes in behavior):
New Functionality
Databases
Changes in Behavior
Charsets
Passdb Backends and Authentication
Charsets
LDAP
31. Migration from NT4 PDC to Samba-3 PDC
Planning and Getting Started
Objectives
Steps In Migration Process
Migration Options
Planning for Success
Samba-3 Implementation Choices
32. SWAT - The Samba Web Administration Tool
Features and Benefits
Enabling SWAT for use
Securing SWAT through SSL
The SWAT Home Page
Global Settings
Share Settings
Printers Settings
The SWAT Wizard
The Status Page
The View Page
The Password Change Page
V. Troubleshooting
33. The Samba checklist
Introduction
Assumptions
The tests
34. Analysing and solving samba problems
Diagnostics tools
Debugging with Samba itself
Tcpdump
Ethereal
The Windows Network Monitor
Useful URLs
Getting help from the mailing lists
How to get off the mailing lists
35. Reporting Bugs
Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches
VI. Appendixes
36. How to compile Samba
Access Samba source code via CVS
Introduction
CVS Access to samba.org
Accessing the samba sources via rsync and ftp
Verifying Samba's PGP signature
Building the Binaries
Compiling samba with Active Directory support
Starting the smbd and nmbd
Starting from inetd.conf
Alternative: starting it as a daemon
37. Portability
HPUX
SCO UNIX
DNIX
RedHat Linux Rembrandt-II
AIX
Sequential Read Ahead
Solaris
Locking improvements
Winbind on Solaris 9
38. Samba and other CIFS clients
Macintosh clients?
OS2 Client
Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
Printer driver download for for OS/2 clients?
Windows for Workgroups
Latest TCP/IP stack from Microsoft
Delete .pwl files after password change
Configuring WfW password handling
Case handling of passwords
Use TCP/IP as default protocol
Speed improvement
Windows '95/'98
Speed improvement
Windows 2000 Service Pack 2
Windows NT 3.1
39. Samba Performance Tuning
Comparisons
Socket options
Read size
Max xmit
Log level
Read raw
Write raw
Slow Logins
Client tuning
Samba performance problem due changing kernel
Corrupt tdb Files
40. DNS and DHCP Configuration Guide
Note
41. Further Resources
Websites
Related updates from Microsoft
Index

List of Figures

5.1. An Example Domain
10.1. Cross subnet browsing example
11.1. IDMAP
12.1. IDMAP groups
13.1. Overview of unix permissions field
16.1. Trusts overview
19.1. Windows Printing to a local Printer
19.2. Printing to a Postscript Printer
19.3. Ghostscript as a RIP for non-postscript printers
19.4. Prefiltering in CUPS to form Postscript
19.5. Adding Device-specific Print Options
19.6. Postscript to intermediate Raster format
19.7. CUPS-raster production using Ghostscript
19.8. Image format to CUPS-raster format conversion
19.9. Raster to Printer Specific formats
19.10. cupsomatic/foomatic processing versus Native CUPS
19.11. PDF to socket chain
19.12. PDF to USB chain
19.13. Print Driver execution on the Client
19.14. Print Driver execution on the Server
19.15. Printing via CUPS/samba server
19.16. cupsaddsmb flowchart
19.17. Filtering chain 1
19.18. Filtering chain with cupsomatic
19.19. CUPS Printing Overview

List of Tables

7.1. Assumptions
10.1. Browse subnet example 1
10.2. Browse subnet example 2
10.3. Browse subnet example 3
10.4. Browse subnet example 4
11.1. Attributes in the sambaSamAccount objectclass (LDAP)
11.2. Basic smb.conf options for MySQL passdb backend
11.3. MySQL field names for MySQL passdb backend
13.1. Managing directories with unix and windows
13.2. User and Group Based Controls
13.3. File and Directory Permission Based Controls
13.4. Other Controls
19.1. PPD's shipped with CUPS
20.1. Extended Auditing Log Information
24.1. User Shell Folder registry keys default values
24.2. Defaults of profile settings registry keys
24.3. Defaults of default user profile paths registry keys
25.1. Options recognized by pam_smbpass
26.1. Unique NetBIOS names
26.2. Group Names
30.1. TDB File Descriptions
31.1. The 3 Major Site Types
31.2. Nature of the Conversion Choices

List of Examples

2.1. Simplest possible smb.conf file
5.1. smb.conf for being a PDC
5.2. smb.conf for being a PDC
6.1. Minimal smb.conf for being a PDC
6.2. Minimal setup for being a BDC
8.1. smb.conf for Reference Documentation Server
8.2. smb.conf for anonymous printing
10.1. Domain master browser smb.conf
10.2. Local master browser smb.conf
10.3. smb.conf for not being a master browser
10.4. Local master browser smb.conf
10.5. smb.conf for not being a master browser
11.1.
11.2. Configuration with LDAP
12.1. smbgrpadd.sh
13.1. Example File
14.1. Share with some files oplocked
14.2.
17.1. smb.conf with DFS configured
18.1. Simple configuration with BSD printing
18.2. Extended configuration with BSD printing
18.3. [print\$] example
19.1. Simplest printing-related smb.conf
19.2. Overriding global CUPS settings for one printer
19.3. smb.conf for cupsaddsmb usage
20.1. smb.conf with VFS modules
20.2. smb.conf with multiple VFS modules
21.1. smb.conf for winbind set-up
33.1. smb.conf with [tmp] share
38.1. Minimal profile share

Legal Notice

This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt -

Attributions

Introduction to Samba

How to Install and Test SAMBA

Fast Start for the Impatient

Server Types and Security Modes

Domain Control

Backup Domain Control

Domain Membership

Stand-Alone Servers

MS Windows Network Configuration Guide

Samba / MS Windows Network Browsing Guide

Account Information Databases

Mapping MS Windows and UNIX Groups

File, Directory and Share Access Controls

File and Record Locking

Securing Samba

Interdomain Trust Relationships

Hosting a Microsoft Distributed File System tree on Samba

Classical Printing Support

CUPS Printing Support in Samba 3.0

Stackable VFS modules

  • Jelmer R. Vernooij <jelmer@samba.org>

  • John H. Terpstra <jht@samba.org>

  • Tim Potter

  • Simo Sorce (original vfs_skel README)

  • Alexander Bokovoy (original vfs_netatalk docs)

  • Stefan Metzmacher (Update for multiple modules)

Advanced Network Management

System and Account Policies

Desktop Profile Management

PAM based Distributed Authentication

Integrating MS Windows networks with Samba

Unicode/Charsets

Samba Backup Techniques

High Availability Options

Upgrading from Samba-2.x to Samba-3.0.0

Migration from NT4 PDC to Samba-3 PDC

SWAT - The Samba Web Administration Tool

The Samba checklist

Analysing and solving samba problems

Reporting Bugs

How to compile Samba

Portability

Samba and other CIFS clients

Samba Performance Tuning

DNS and DHCP Configuration Guide

Further Resources

General Installation

Preparing Samba for Configuration

This section of the Samba-HOWTO-Collection contains general info on how to install samba +

Attributions

Introduction to Samba

How to Install and Test SAMBA

Fast Start for the Impatient

Server Types and Security Modes

Domain Control

Backup Domain Control

Domain Membership

Stand-Alone Servers

MS Windows Network Configuration Guide

Samba / MS Windows Network Browsing Guide

Account Information Databases

Mapping MS Windows and UNIX Groups

File, Directory and Share Access Controls

File and Record Locking

Securing Samba

Interdomain Trust Relationships

Hosting a Microsoft Distributed File System tree on Samba

Classical Printing Support

CUPS Printing Support in Samba 3.0

Stackable VFS modules

  • Jelmer R. Vernooij <jelmer@samba.org>

  • John H. Terpstra <jht@samba.org>

  • Tim Potter

  • Simo Sorce (original vfs_skel README)

  • Alexander Bokovoy (original vfs_netatalk docs)

  • Stefan Metzmacher (Update for multiple modules)

Advanced Network Management

System and Account Policies

Desktop Profile Management

PAM based Distributed Authentication

Integrating MS Windows networks with Samba

Unicode/Charsets

Samba Backup Techniques

High Availability Options

Upgrading from Samba-2.x to Samba-3.0.0

Migration from NT4 PDC to Samba-3 PDC

SWAT - The Samba Web Administration Tool

The Samba checklist

Analysing and solving samba problems

Reporting Bugs

How to compile Samba

Portability

Samba and other CIFS clients

Samba Performance Tuning

DNS and DHCP Configuration Guide

Further Resources

General Installation

Preparing Samba for Configuration

This section of the Samba-HOWTO-Collection contains general info on how to install samba and how to configure the parts of samba you will most likely need. -PLEASE read this.

Table of Contents

1. Introduction to Samba
Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous
2. How to Install and Test SAMBA
Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your - server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"
3. Fast Start for the Impatient
Note

Chapter 1. Introduction to Samba

David Lechnyr

Unofficial HOWTO

April 14, 2003

Table of Contents

Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous

“ -"If you understand what you're doing, you're not learning anything." +PLEASE read this.

Table of Contents

1. Introduction to Samba
Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous
2. How to Install and Test SAMBA
Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your + server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"
3. Fast Start for the Impatient
Note

Chapter 1. Introduction to Samba

David Lechnyr

Unofficial HOWTO

April 14, 2003

Table of Contents

Background
Terminology
Related Projects
SMB Methodology
Epilogue
Miscellaneous

“ +"If you understand what you're doing, you're not learning anything." -- Anonymous ”

Samba is a file and print server for Windows-based clients using TCP/IP as the underlying @@ -85,7 +85,7 @@ transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of strengths is that you can use it to blend your mix of Windows and Linux machines together without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. -

Background

+

Background

Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only @@ -93,12 +93,12 @@ ran over UDP. When there was a need to run it over TCP so that it would be compa with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the -concept continued in the form of SMB (Server Message Block, or the "what") using the -NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can +concept continued in the form of SMB (Server Message Block, or the "what") using the +NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can run SMB (i.e., transport) over several different protocols; many different implementations arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT (NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form -of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing +of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 only. As of yet, direct-hosted TCP has yet to catch on.

@@ -111,23 +111,23 @@ been dutifully waded through during the information-gathering stages of this pro are *still* many missing pieces... While often tedious, at least the way has been generously littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they thinking? -

Terminology

  • - SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. +

Terminology

  • + SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.

  • - CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently - decided that SMB needed the word "Internet" in it, so they changed it to CIFS. + CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently + decided that SMB needed the word "Internet" in it, so they changed it to CIFS.

  • Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp only using DNS for name resolution instead of WINS.

  • - IPC: Acronym for "Inter-Process Communication". A method to communicate specific + IPC: Acronym for "Inter-Process Communication". A method to communicate specific information between programs.

  • Marshalling: - A method of serializing (i.e., sequential ordering of) variable data suitable for transmission via a network connection or storing in a file. The source data can be re-created using a similar process called unmarshalling.

  • - NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; + NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; it is a method of communication across an existing protocol. This is a standard which was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, it can help to think of this in comparison your computer's BIOS -- it controls the @@ -138,15 +138,15 @@ thinking? brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second thought; this will cause no end (and no doubt) of confusion.

  • - NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI + NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI is a protocol, not a standard. It is also not routable, so traffic on one side of a router will be unable to communicate with the other side. Understanding NetBEUI is not essential to deciphering SMB; however it helps to point out that it is not the same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally - referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". + referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". It is not often heard from these days.

  • - NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use + NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. This is how file and printer sharing are accomplished in Windows 95/98/ME. They @@ -161,7 +161,7 @@ thinking? W3K: Acronym for Windows 2003 Server

If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at http://www.samba.org). -

Related Projects

+

Related Projects

There are currently two network filesystem client projects for Linux that are directly related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself.

  • @@ -183,21 +183,21 @@ nothing to do with acting as a file and print server for SMB/CIFS clients. There are other Open Source CIFS client implementations, such as the jCIFS project which provides an SMB client toolkit written in Java. -

SMB Methodology

+

SMB Methodology

Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good packet sniffer will be amazed at the amount of traffic generated by just opening up a single file. In general, SMB sessions are established in the following order:

  • - "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp + "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp or 445/tcp.

  • - "NetBIOS Session Request" - using the following "Calling Names": The local + "NetBIOS Session Request" - using the following "Calling Names": The local machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS name plus the 16th character 0x20

  • - "SMB Negotiate Protocol" - determine the protocol dialect to use, which will + "SMB Negotiate Protocol" - determine the protocol dialect to use, which will be one of the following: PC Network Program 1.0 (Core) - share level security mode only; Microsoft Networks 1.03 (Core Plus) - share level security mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response @@ -215,7 +215,7 @@ up a single file. In general, SMB sessions are established in the following orde A good way to examine this process in depth is to try out SecurityFriday's SWB program. It allows you to walk through the establishment of a SMB/CIFS session step by step. -

Epilogue

“ +

Epilogue

“ What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft @@ -239,18 +239,18 @@ halts in the middle of something that shouldn't be strange. Normally it works fine and then once in a blue moon for some completely unknown reason, it's dead, and nobody knows why. Not Microsoft, not the experienced user and certainly not the completely clueless user who probably sits there shivering thinking -"What did I do wrong?" when they didn't do anything wrong at all. +"What did I do wrong?" when they didn't do anything wrong at all. ”

“ -That's what's really irritating to me." +That's what's really irritating to me." ”

-- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -

Miscellaneous

+

Miscellaneous

This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. -

Chapter 2. How to Install and Test SAMBA

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

John H. Terpstra

Samba Team

Karl Auer

Table of Contents

Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your - server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"

Obtaining and installing samba

+

Chapter 2. How to Install and Test SAMBA

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

John H. Terpstra

Samba Team

Karl Auer

Table of Contents

Obtaining and installing samba
Configuring samba (smb.conf)
Example Configuration
SWAT
Try listing the shares available on your + server
Try connecting with the unix client
Try connecting from another SMB client
What If Things Don't Work?
Common Errors
Large number of smbd processes
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
"The network name cannot be found"

Obtaining and installing samba

Binary packages of samba are included in almost any Linux or UNIX distribution. There are also some packages available at the samba homepage. @@ -258,24 +258,24 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li the chapter about compiling samba from scratch.

If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow - for information about updating samba.

Configuring samba (smb.conf)

+ for information about updating samba.

Configuring samba (smb.conf)

Samba's configuration is stored in the smb.conf file, that usually resides in /etc/samba/smb.conf or /usr/local/samba/lib/smb.conf. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the web-based interface swat, that is included with samba. -

Example Configuration

+

Example Configuration

There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options.

The simplest useful configuration file would be something like this:

-

Example 2.1. Simplest possible smb.conf file

[global]
workgroup = MIDEARTH
[homes]
guest ok = no
read only = no

+

Example 2.1. Simplest possible smb.conf file

[global]
workgroup = MIDEARTH
[homes]
guest ok = no
read only = no

This will allow connections by anyone with an account on the server, using either - their login name or homes" as the service name. + their login name or homes" as the service name. (Note that the workgroup that Samba must also be set.)

Make sure you put the smb.conf file in the correct place @@ -283,8 +283,8 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li

For more information about security settings for the [homes] share please refer to - "Securing Samba". -

Test your config file with testparm

+ "Securing Samba". +

Test your config file with testparm

It's important that you test the validity of your smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -292,7 +292,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li Make sure it runs OK and that the services look reasonable before proceeding.

Always run testparm again when you change smb.conf! -

SWAT

+

SWAT

SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage @@ -308,7 +308,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. -

Try listing the shares available on your +

Try listing the shares available on your server

 $ smbclient -L yourhostname

You should get back a list of shares available on @@ -319,7 +319,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

Try connecting with the unix client

+ with non-Samba servers)

Try connecting with the unix client

 $ smbclient  //yourhostname/aservice

Typically the yourhostname @@ -331,19 +331,19 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li in smb.conf.

For example if your unix host is bambi and your login name is fred you would type:

 $ smbclient //bambi/fred
-

Try connecting from another SMB client

Try mounting disks. from a DOS, Windows or OS/2 client, eg:

+

Try connecting from another SMB client

Try mounting disks. from a DOS, Windows or OS/2 client, eg:

 C:\> net use d: \\servername\service

Try printing. eg:

 C:\> net use lpt1:	\\servername\spoolservice
 

C:\> print filename
-

What If Things Don't Work?

Then you might read the file chapter diagnosis - and the FAQ. If you are still stuck then refer to "Analysing and solving problems". +

What If Things Don't Work?

Then you might read the file chapter diagnosis + and the FAQ. If you are still stuck then refer to "Analysing and solving problems". Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

Common Errors

+ so maybe someone else has hit your problem and has overcome it.

Common Errors

The following questions and issues get raised on the samba mailing list over and over again. -

Large number of smbd processes

+

Large number of smbd processes

Samba consists on three core programs: nmbd, smbd, winbindd. nmbd is the name server message daemon, smbd is the server message daemon, winbindd is the daemon that @@ -357,20 +357,20 @@ two (2) instances - one to handle the WINS requests. connection made. That is why you are seeing so many of them, one (1) per client connection.

winbindd will run as one or two daemons, depending on whether or not it is being -run in "split mode" (in which case there will be two instances). -

"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"

Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with +run in "split mode" (in which case there will be two instances). +

"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"

Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with the ip address 127.0.0.1. Read your OS documentation for details - on how to configure the loopback on your system.

"The network name cannot be found"

+ on how to configure the loopback on your system.

"The network name cannot be found"

This error can be caused by one of these misconfigurations: -

  • You specified an nonexisting path for the share in smb.conf

  • The user you are trying to access the share with does not - have sufficient permissions to access the path for the share. Both read (r) and access (x) should be possible.

  • The share you are trying to access does not exist.

Chapter 3. Fast Start for the Impatient

John H. Terpstra

Samba Team

Table of Contents

Note

Note

+

  • You specified an nonexisting path for the share in smb.conf

  • The user you are trying to access the share with does not + have sufficient permissions to access the path for the share. Both read (r) and access (x) should be possible.

  • The share you are trying to access does not exist.

Chapter 3. Fast Start for the Impatient

John H. Terpstra

Samba Team

Table of Contents

Note

Note

This chapter did not make it into this release. It is planned for the published release of this document. -

Server Configuration Basics

First Steps in Server Configuration

+

Server Configuration Basics

First Steps in Server Configuration

Samba can operate in various modes within SMB networks. This HOWTO section contains information on configuring samba to function as the type of server your network requires. Please read this section carefully. -

Table of Contents

4. Server Types and Security Modes
Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server
5. Domain Control
Features and Benefits
Basics of Domain Control
Domain Controller Types
Preparing for Domain Control
Domain Control - Example Configuration
Samba ADS Domain Control
Domain and Network Logon Configuration
Domain Network Logon Service
Security Mode and Master Browsers
Common Errors
'$' cannot be included in machine name
Joining domain fails because of existing machine account
The system can not log you on (C000019B)....
The machine trust account not accessible
Account disabled
Domain Controller Unavailable
Can not log onto domain member workstation after joining domain
6. Backup Domain Control
Features And Benefits
Essential Background Information
MS Windows NT4 Style Domain Control
Active Directory Domain Control
What qualifies a Domain Controller on the network?
How does a Workstation find its domain controller?
Backup Domain Controller Configuration
Example Configuration
Common Errors
Machine Accounts keep expiring, what can I do?
Can Samba be a Backup Domain Controller to an NT4 PDC?
How do I replicate the smbpasswd file?
Can I do this all with LDAP?
7. Domain Membership
Features and Benefits
MS Windows Workstation/Server Machine Trust Accounts
Manual Creation of Machine Trust Accounts
Using NT4 Server Manager to Add Machine Accounts to the Domain
"On-the-Fly" Creation of Machine Trust Accounts
Making an MS Windows Workstation or Server a Domain Member
Domain Member Server
Joining an NT4 type Domain with Samba-3
Why is this better than security = server?
Samba ADS Domain Membership
Setup your smb.conf
Setup your /etc/krb5.conf
Create the computer account
Test your server setup
Testing with smbclient
Notes
Common Errors
Can Not Add Machine Back to Domain
Adding Machine to Domain Fails
I can't join a Windows 2003 PDC
8. Stand-Alone Servers
Features and Benefits
Background
Example Configuration
Reference Documentation Server
Central Print Serving
Common Errors
9. MS Windows Network Configuration Guide
Note

Chapter 4. Server Types and Security Modes

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

John H. Terpstra

Samba Team

Table of Contents

Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server

+

Table of Contents

4. Server Types and Security Modes
Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server
5. Domain Control
Features and Benefits
Basics of Domain Control
Domain Controller Types
Preparing for Domain Control
Domain Control - Example Configuration
Samba ADS Domain Control
Domain and Network Logon Configuration
Domain Network Logon Service
Security Mode and Master Browsers
Common Errors
'$' cannot be included in machine name
Joining domain fails because of existing machine account
The system can not log you on (C000019B)....
The machine trust account not accessible
Account disabled
Domain Controller Unavailable
Can not log onto domain member workstation after joining domain
6. Backup Domain Control
Features And Benefits
Essential Background Information
MS Windows NT4 Style Domain Control
Active Directory Domain Control
What qualifies a Domain Controller on the network?
How does a Workstation find its domain controller?
Backup Domain Controller Configuration
Example Configuration
Common Errors
Machine Accounts keep expiring, what can I do?
Can Samba be a Backup Domain Controller to an NT4 PDC?
How do I replicate the smbpasswd file?
Can I do this all with LDAP?
7. Domain Membership
Features and Benefits
MS Windows Workstation/Server Machine Trust Accounts
Manual Creation of Machine Trust Accounts
Using NT4 Server Manager to Add Machine Accounts to the Domain
"On-the-Fly" Creation of Machine Trust Accounts
Making an MS Windows Workstation or Server a Domain Member
Domain Member Server
Joining an NT4 type Domain with Samba-3
Why is this better than security = server?
Samba ADS Domain Membership
Setup your smb.conf
Setup your /etc/krb5.conf
Create the computer account
Test your server setup
Testing with smbclient
Notes
Common Errors
Can Not Add Machine Back to Domain
Adding Machine to Domain Fails
8. Stand-Alone Servers
Features and Benefits
Background
Example Configuration
Reference Documentation Server
Central Print Serving
Common Errors
9. MS Windows Network Configuration Guide
Note

Chapter 4. Server Types and Security Modes

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

John H. Terpstra

Samba Team

Table of Contents

Features and Benefits
Server Types
Samba Security Modes
User Level Security
Share Level Security
Domain Security Mode (User Level Security)
ADS Security Mode (User Level Security)
Server Security (User Level Security)
Password checking
Common Errors
What makes Samba a SERVER?
What makes Samba a Domain Controller?
What makes Samba a Domain Member?
Constantly Losing Connections to Password Server

This chapter provides information regarding the types of server that Samba may be configured to be. A Microsoft network administrator who wishes to migrate to or to use Samba will want to know what, within a Samba context, terms familiar to MS Windows @@ -380,11 +380,11 @@ modes function BEFORE we get into the details of how to configure the server its The chapter provides an overview of the security modes of which Samba is capable and how these relate to MS Windows servers and clients.

-A question often asked is, "Why would I want to use Samba?" Most chapters contain a section +A question often asked is, "Why would I want to use Samba?" Most chapters contain a section that highlights features and benefits. We hope that the information provided will help to answer this question. Be warned though, we want to be fair and reasonable, so not all features are positive towards Samba so the benefit may be on the side of our competition. -

Features and Benefits

+

Features and Benefits

Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion and fury fitting his anguish. The other looked at the stone and said, that is a garnet - I @@ -420,14 +420,14 @@ So now, what are the benefits of features mentioned in this chapter? greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. -

Server Types

Administrators of Microsoft networks often refer to three +

Server Types

Administrators of Microsoft networks often refer to three different type of servers:

  • Domain Controller

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

  • Domain Member Server

    • Active Directory Domain Server

    • NT4 Style Domain Domain Server

  • Stand Alone Server

The chapters covering Domain Control, Backup Domain Control and Domain Membership provide pertinent information regarding Samba configuration for each of these server roles. The reader is strongly encouraged to become intimately familiar with the information presented. -

Samba Security Modes

-In this section the function and purpose of Samba's security +

Samba Security Modes

+In this section the function and purpose of Samba's security modes are described. An accurate understanding of how Samba implements each security mode as well as how to configure MS Windows clients for each mode will significantly reduce user complaints and administrator heartache. @@ -450,7 +450,7 @@ the way the client then tries to authenticate itself. It does not directly affec but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is allowed. -

User Level Security

+

User Level Security

We will describe user level security first, as it's simpler. In user level security, the client will send a session setup command directly after the protocol negotiation. @@ -468,11 +468,11 @@ It is also possible for a client to send multiple ses requests. When the server responds, it gives the client a uid to use as an authentication tag for that username/password. The client can maintain multiple authentication contexts in this way (WinDD is an example of an application that does this). -

Example Configuration

+

Example Configuration

The smb.conf parameter that sets User Level Security is:

security = user

This is the default setting since samba-2.2.x. -

Share Level Security

+

Share Level Security

Ok, now for share level security. In share level security, the client authenticates itself separately for each share. It will send a password along with each tree connection (share mount). It does not explicitly send a @@ -492,19 +492,19 @@ level security. They normally send a valid username but no password. Samba recor this username in a list of possible usernames. When the client then does a tree connection it also adds to this list the name of the share they try to connect to (useful for home directories) and any users -listed in the user smb.conf line. The password is then checked +listed in the user smb.conf line. The password is then checked in turn against these possible usernames. If a match is found then the client is authenticated as that user. -

Example Configuration

+

Example Configuration

The smb.conf parameter that sets Share Level Security is:

security = share

Please note that there are reports that recent MS Windows clients do not like to work with share mode security servers. You are strongly discouraged from using share level security. -

Domain Security Mode (User Level Security)

-When Samba is operating in security = domain mode, +

Domain Security Mode (User Level Security)

+When Samba is operating in security = domain mode, the Samba server has a domain security trust account (a machine account) and will cause all authentication requests to be passed through to the domain controllers. -

Example Configuration

+

Example Configuration

Samba as a Domain Member Server

This method involves addition of the following parameters in the smb.conf file: @@ -537,7 +537,7 @@ An alternative to assigning UIDs to Windows users on a Samba member server is presented in the chapter about winbind.

For more information of being a domain member, see the chapter about domain membership. -

ADS Security Mode (User Level Security)

+

ADS Security Mode (User Level Security)

Both Samba 2.2 and 3.0 can join an Active Directory domain. This is possible if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style domain members. This is contrary to @@ -551,12 +551,12 @@ authentication protocols. All your machines are running Windows 2000 and above and all use Kerberos. In this case Samba as a NT4-style domain would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos tickets. -

Example Configuration

realm = your.kerberos.REALM
security = ADS

+

Example Configuration

realm = your.kerberos.REALM
security = ADS

The following parameter may be required:

ads server = your.kerberos.server

Please refer to the chapter on domain membership for more information regarding this configuration option. -

Server Security (User Level Security)

+

Server Security (User Level Security)

Server security mode is a left over from the time when Samba was not capable of acting as a domain member server. It is highly recommended NOT to use this feature. Server security mode has many draw backs. The draw backs include: @@ -564,20 +564,20 @@ security mode has many draw backs. The draw backs include: In server security mode the Samba server reports to the client that it is in user level security. The client then does a session setup as described earlier. The Samba server takes the username/password that the client sends and attempts to login to the -password server by sending exactly the same username/password that +password server by sending exactly the same username/password that it got from the client. If that server is in user level security and accepts the password, then Samba accepts the clients connection. This allows the Samba server to use another SMB -server as the password server. +server as the password server.

You should also note that at the very start of all this, where the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does then it supplies the client with a random cryptkey. The client will then send all passwords in encrypted form. Samba supports this type of encryption by default.

-The parameter security = server means that Samba reports to clients that +The parameter security = server means that Samba reports to clients that it is running in user mode but actually passes off all authentication requests to another user mode server. This requires an additional -parameter password server that points to the real authentication server. +parameter password server that points to the real authentication server. That real authentication server can be another Samba server or can be a Windows NT server, the later natively capable of encrypted password support.

Note

@@ -588,11 +588,11 @@ lookups because the choice of the target authentication server is arbitrary and be determined from a domain name. In essence, a Samba server that is in server security mode is operating in what used to be known as workgroup mode. -

Example Configuration

+

Example Configuration

Using MS Windows NT as an authentication server

This method involves the additions of the following parameters in the smb.conf file: -

encrypt passwords = Yes
security = server
password server = "NetBIOS_name_of_a_DC"

+

encrypt passwords = Yes
security = server
password server = "NetBIOS_name_of_a_DC"

There are two ways of identifying whether or not a username and password pair was valid. One uses the reply information provided as part of the authentication messaging process, the other uses just an error code. @@ -605,7 +605,7 @@ certain number of failed authentication attempts this will result in user lockou

Use of this mode of authentication does require there to be a standard UNIX account for the user, though this account can be blocked to prevent logons by non-SMB/CIFS clients. -

Password checking

+

Password checking

MS Windows clients may use encrypted passwords as part of a challenge/response authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear text strings for simple password based authentication. It should be realized that with the SMB protocol, @@ -619,7 +619,7 @@ is encrypted in two ways:

  • The password is converted to upper case, and then padded or truncated to 14 bytes. This string is then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. + form two 56 bit DES keys to encrypt a "magic" 8 byte value. The resulting 16 bytes form the LanMan hash.

    • MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 @@ -645,15 +645,15 @@ when using clear text authentication.

    password level = integer
    username level = integer

    By default Samba will lower case the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally -only contain lower-case character, the username level parameter +only contain lower-case character, the username level parameter is rarely needed.

    However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level +server using clear text authentication, the password level must be set to the maximum number of upper case letters which could appear in a password. Note that if the server OS uses the traditional DES version -of crypt(), a password level of 8 will result in case +of crypt(), a password level of 8 will result in case insensitive passwords as seen from Windows users. This will also result in longer login times as Samba has to compute the permutations of the password string and try them one by one until a match is located (or all combinations fail). @@ -661,7 +661,7 @@ try them one by one until a match is located (or all combinations fail). The best option to adopt is to enable support for encrypted passwords wherever Samba is used. Most attempts to apply the registry change to re-enable plain text passwords will eventually lead to user complaints and unhappiness. -

    Common Errors

    +

    Common Errors

    We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake made in a developmental test lab is expected. @@ -671,19 +671,19 @@ on the Samba mailing lists. Many of these are avoidable by doing you homework be a Samba implementation. Some are the result of misunderstanding of the English language. The English language has many turns of phrase that are potentially vague and may be highly confusing to those for whom English is not their native tongue. -

    What makes Samba a SERVER?

    +

    What makes Samba a SERVER?

    To some the nature of the Samba security mode is very obvious, but entirely -wrong all the same. It is assumed that security = server means that Samba +wrong all the same. It is assumed that security = server means that Samba will act as a server. Not so! See above - this setting means that Samba will try to use another SMB server as its source of user authentication alone. -

    What makes Samba a Domain Controller?

    -The smb.conf parameter security = domain does NOT really make Samba behave +

    What makes Samba a Domain Controller?

    +The smb.conf parameter security = domain does NOT really make Samba behave as a Domain Controller! This setting means we want Samba to be a domain member! -

    What makes Samba a Domain Member?

    -Guess! So many others do. But whatever you do, do NOT think that security = user +

    What makes Samba a Domain Member?

    +Guess! So many others do. But whatever you do, do NOT think that security = user makes Samba act as a domain member. Read the manufacturers manual before the warranty expires! See the chapter about domain membership for more information. -

    Constantly Losing Connections to Password Server

    +

    Constantly Losing Connections to Password Server

    “ Why does server_validate() simply give up rather than re-establishing its connection to the password server? Though I am not fluent in the SMB protocol, perhaps the cluster server @@ -691,9 +691,9 @@ process passes along to its client workstation the session key it receives from server, which means the password hashes submitted by the client would not work on a subsequent connection, whose session key would be different. So server_validate() must give up.”

    - Indeed. That's why security = server is at best a nasty hack. Please use security = domain. -security = server mode is also known as pass-through authentication. -

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control - Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    '$' cannot be included in machine name
    Joining domain fails because of existing machine account
    The system can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain

    The Essence of Learning:  + Indeed. That's why security = server is at best a nasty hack. Please use security = domain. +security = server mode is also known as pass-through authentication. +

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control - Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    '$' cannot be included in machine name
    Joining domain fails because of existing machine account
    The system can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain

    The Essence of Learning:  There are many who approach MS Windows networking with incredible misconceptions. That's OK, because it gives the rest of us plenty of opportunity to be of assistance. Those who really want help would be well advised to become familiar with information @@ -723,7 +723,7 @@ burden on an organisation. Where is the right place to make mistakes? Only out of harm's way! If you are going to make mistakes, then please do this on a test network, away from users and in such a way as to not inflict pain on others. Do your learning on a test network. -

    Features and Benefits

    +

    Features and Benefits

    What is the key benefit of Microsoft Domain security?

    In a word, Single Sign On, or SSO for short. To many, this is the holy @@ -795,11 +795,11 @@ user and machine trust account information in a suitable backend data store. Refer to the section on machine trust accounts. With Samba-3 there can be multiple back-ends for this. A complete discussion of account database backends can be found in the chapter on Account Information Databases. -

    Basics of Domain Control

    +

    Basics of Domain Control

    Over the years, public perceptions of what Domain Control really is has taken on an almost mystical nature. Before we branch into a brief overview of Domain Control, there are three basic types of domain controllers: -

    Domain Controller Types

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    +

    Domain Controller Types

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    The Primary Domain Controller or PDC plays an important role in the MS Windows NT4. In Windows 200x Domain Control architecture this role is held by domain controllers. There is folk lore that dictates that because of it's role in the MS Windows @@ -821,7 +821,7 @@ LDAP based user and machine account back end.

    New to Samba-3 is the ability to use a back-end database that holds the same type of data as the NT4 style SAM (Security Account Manager) database (one of the registry files). -[1] +[1]

    The Backup Domain Controller or BDC plays a key role in servicing network authentication requests. The BDC is biased to answer logon requests in preference to the PDC. @@ -852,7 +852,7 @@ management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP environment. However, there are certain compromises:

    • No machine policy files

    • No Group Policy Objects

    • No synchronously executed AD logon scripts

    • Can't use ANY Active Directory management tools to manage users and machines

    • Registry changes tattoo the main registry, while with AD they do NOT. ie: Leave permanent changes in effect

    • Without AD you can not peprform the function of exporting specific applications to specific users or groups

    -

    Preparing for Domain Control

    +

    Preparing for Domain Control

    There are two ways that MS Windows machines may interact with each other, with other servers, and with Domain Controllers: Either as Stand-Alone systems, more commonly called Workgroup members, or as full participants in a security system, @@ -879,11 +879,11 @@ Domain, then it will operate like a workgroup (stand-alone) machine. Please refe

    The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows NT4 / 200x / XP clients. -

    • Configuration of basic TCP/IP and MS Windows Networking

    • Correct designation of the Server Role (security = user)

    • Consistent configuration of Name Resolution (See chapter on Network Browsing and on +

      • Configuration of basic TCP/IP and MS Windows Networking

      • Correct designation of the Server Role (security = user)

      • Consistent configuration of Name Resolution (See chapter on Network Browsing and on Integrating Unix into Windows networks)

      • Domain logons for Windows NT4 / 200x / XP Professional clients

      • Configuration of Roaming Profiles or explicit configuration to force local profile usage

      • Configuration of Network/System Policies

      • Adding and managing domain user accounts

      • Configuring MS Windows client machines to become domain members

      The following provisions are required to serve MS Windows 9x / Me Clients: -

      • Configuration of basic TCP/IP and MS Windows Networking

      • Correct designation of the Server Role (security = user)

      • Network Logon Configuration (Since Windows 9x / XP Home are not technically domain - members, they do not really participate in the security aspects of Domain logons as such)

      • Roaming Profile Configuration

      • Configuration of System Policy handling

      • Installation of the Network driver "Client for MS Windows Networks" and configuration +

        • Configuration of basic TCP/IP and MS Windows Networking

        • Correct designation of the Server Role (security = user)

        • Network Logon Configuration (Since Windows 9x / XP Home are not technically domain + members, they do not really participate in the security aspects of Domain logons as such)

        • Roaming Profile Configuration

        • Configuration of System Policy handling

        • Installation of the Network driver "Client for MS Windows Networks" and configuration to log onto the domain

        • Placing Windows 9x / Me clients in user level security - if it is desired to allow all client share access to be controlled according to domain user / group identities.

        • Adding and managing domain user accounts

        Note

        Roaming Profiles and System/Network policies are advanced network administration topics @@ -904,15 +904,15 @@ A Domain Controller is an SMB/CIFS server that: Provides a share called NETLOGON

      For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide -the NETLOGON service which Samba calls the domain logons functionality +the NETLOGON service which Samba calls the domain logons functionality (after the name of the parameter in the smb.conf file). Additionally, one (1) server in a Samba-3 -Domain must advertise itself as the domain master browser[2]. This causes the Primary Domain Controller +Domain must advertise itself as the domain master browser[2]. This causes the Primary Domain Controller to claim domain specific NetBIOS name that identifies it as a domain master browser for its given domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet. -

    Domain Control - Example Configuration

    +

    Domain Control - Example Configuration

    The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. An example smb.conf for acting as a PDC can be found in the example for being a PDC. @@ -960,7 +960,7 @@ of operation. The following smb.conf parameters are th

    The additional parameters shown in the longer listing above just makes for more complete explanation. -

    Samba ADS Domain Control

    +

    Samba ADS Domain Control

    Samba-3 is not, and can not act as, an Active Directory Server. It can not truly function as an Active Directory Primary Domain Controller. The protocols for some of the functionality the Active Directory Domain Controllers has been partially implemented on an experimental @@ -975,15 +975,15 @@ domain controllers have. Samba-3 does NOT have all the capabilities of Windows N a number of features that Windows NT4 domain contollers do not have. In short, Samba-3 is not NT4 and it is not Windows Server 200x and it is not an Active Directory server. We hope this is plain and simple enough for all to understand. -

    Domain and Network Logon Configuration

    +

    Domain and Network Logon Configuration

    The subject of Network or Domain Logons is discussed here because it forms an integral part of the essential functionality that is provided by a Domain Controller. -

    Domain Network Logon Service

    +

    Domain Network Logon Service

    All Domain Controllers must run the netlogon service (domain logons -in Samba). One Domain Controller must be configured with domain master = Yes -(the Primary Domain Controller); on ALL Backup Domain Controllers domain master = No +in Samba). One Domain Controller must be configured with domain master = Yes +(the Primary Domain Controller); on ALL Backup Domain Controllers domain master = No must be set. -

    Example Configuration

    Example 5.2. smb.conf for being a PDC

    [global]
    domain logons = Yes
    domain master = (Yes on PDC, No on BDCs)
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    browseable = No

    The Special Case of MS Windows XP Home Edition

    Note

    +

    Example Configuration

    Example 5.2. smb.conf for being a PDC

    [global]
    domain logons = Yes
    domain master = (Yes on PDC, No on BDCs)
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    browseable = No

    The Special Case of MS Windows XP Home Edition

    Note

    MS Windows XP Home Edition does not have the ability to join any type of Domain security facility. Unlike, MS Windows 9x / Me, MS Windows XP Home Edition also completely lacks the ability to log onto a network. @@ -997,7 +997,7 @@ Now that this has been said, please do NOT ask the mailing list, or email any of Samba-Team members with your questions asking how to make this work. It can't be done. If it can be done, then to do so would violate your software license agreement with Microsoft, and we recommend that you do not do that. -

    The Special Case of Windows 9x / Me

    +

    The Special Case of Windows 9x / Me

    A domain and a workgroup are exactly the same in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a @@ -1080,7 +1080,7 @@ network logon services that MS Windows 9x / Me expect to find.

    Note

    Use of plain-text passwords is strongly discouraged. Where used they are easily detected using a sniffer tool to examine network traffic. -

    Security Mode and Master Browsers

    +

    Security Mode and Master Browsers

    There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue of whether or not it is ok to configure Samba as a Domain Controller in security @@ -1101,21 +1101,21 @@ A DMB is a Domain Master Browser - see security = user. If a Samba host is configured to use +than security = user. If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network -(the password server) knows more about the user than the Samba host. +(the password server) knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the workgroup parameter +in order to operate in domain mode security, the workgroup parameter must be set to the name of the Windows NT domain (which already has a domain controller). If the domain does NOT already have a Domain Controller then you do not yet have a Domain!

    Configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC -to be the DMB for its domain and set security = user. +to be the DMB for its domain and set security = user. This is the only officially supported mode of operation. -

    Common Errors

    '$' cannot be included in machine name

    +

    Common Errors

    '$' cannot be included in machine name

    A 'machine account', (typically) stored in /etc/passwd, takes the form of the machine name with a '$' appended. FreeBSD (and other BSD systems?) won't create a user with a '$' in their name. @@ -1125,9 +1125,9 @@ Create a user without the '$'. Then use vipw to edit the the '$'. Or create the whole entry with vipw if you like; make sure you use a unique User ID!

    Note

    The UNIX tool vipw is a common tool for directly editting the /etc/passwd file. -

    Joining domain fails because of existing machine account

    “I get told "You already have a connection to the Domain...." -or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.”

    +

    Joining domain fails because of existing machine account

    “I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.”

    This happens if you try to create a machine trust account from the machine itself and already have a connection (e.g. mapped drive) to a share (or IPC$) on the Samba PDC. The following command @@ -1139,7 +1139,7 @@ Further, if the machine is already a 'member of a workgroup' that is the same name as the domain you are joining (bad idea) you will get this message. Change the workgroup name to something else, it does not matter what, reboot, and try again. -

    The system can not log you on (C000019B)....

    “I joined the domain successfully but after upgrading +

    The system can not log you on (C000019B)....

    “I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, The system can not log you on (C000019B), Please try again or consult your system administrator when attempting to logon.” @@ -1162,13 +1162,13 @@ Workstation machine trust accounts work only with the Domain (or network) SID. I then domain members (workstations) will not be able to log onto the domain. The original Domain SID can be recovered from the secrets.tdb file. The alternative is to visit each workstation to re-join it to the domain. -

    The machine trust account not accessible

    +

    The machine trust account not accessible

    “When I try to join the domain I get the message The machine account for this computer either does not exist or is not accessible. What's wrong?”

    This problem is caused by the PDC not having a suitable machine trust account. -If you are using the add machine script method to create +If you are using the add machine script method to create accounts then this would indicate that it has not worked. Ensure the domain admin user system is working.

    @@ -1184,13 +1184,13 @@ Some people have also reported that inconsistent subnet masks between the Samba server and the NT client can cause this problem. Make sure that these are consistent for both client and server. -

    Account disabled

    “When I attempt to login to a Samba Domain from a NT4/W2K workstation, +

    Account disabled

    “When I attempt to login to a Samba Domain from a NT4/W2K workstation, I get a message about my account being disabled.”

    Enable the user accounts with smbpasswd -e username , this is normally done as an account is created. -

    Domain Controller Unavailable

    “Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"”

    +

    Domain Controller Unavailable

    “Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"”

    A domain controller has to announce on the network who it is. This usually takes a while. -

    Can not log onto domain member workstation after joining domain

    After successfully joining the domain user logons fail with one of two messages:

    One to the effect that the domain controller can not be found, the other claiming that the +

    Can not log onto domain member workstation after joining domain

    After successfully joining the domain user logons fail with one of two messages:

    One to the effect that the domain controller can not be found, the other claiming that the account does not exist in the domain or that the password is incorrect.

    This may be due to incompatible settings between the Windows client and the Samba-3 server for schannel (secure channel) settings or smb signing settings. Check your samba settings for @@ -1202,10 +1202,10 @@ Enable the user accounts with smbpasswd -e Secure Channel: ..., and Digitally sign ....

    It is important that these be set consistently with the Samba-3 server settings. -


    [1] See also the chapter on Account Information Databases.

    [2] See also the chapter about network browsing

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    Active Directory Domain Control
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts keep expiring, what can I do?
    Can Samba be a Backup Domain Controller to an NT4 PDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?

    +


    [1] See also the chapter on Account Information Databases.

    [2] See also the chapter about network browsing

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    Active Directory Domain Control
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts keep expiring, what can I do?
    Can Samba be a Backup Domain Controller to an NT4 PDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?

    Before you continue reading in this section, please make sure that you are comfortable with configuring a Samba Domain Controller as described in chapter on setting up Samba as a PDC. -

    Features And Benefits

    +

    Features And Benefits

    This is one of the most difficult chapters to summarise. It does not matter what we say here for someone will still draw conclusions and / or approach the Samba-Team with expectations that are either not yet capable of being delivered, or that can be achieved far more @@ -1246,7 +1246,7 @@ lets consider each possible option and look at the pro's and con's for each theo

  • Passdb Backend is tdbsam based, BDCs use cron based net rpc vampire to obtain the Accounts database from the PDC and place them into the Samba SAM. - net rpc vampire is a Samba function of the "net" command. + net rpc vampire is a Samba function of the "net" command.

    Arguments For: It would be a nice solution

    @@ -1267,7 +1267,7 @@ lets consider each possible option and look at the pro's and con's for each theo Arguments Against: All machine trust accounts and user accounts will be locally maintained. Domain users will NOT be able to roam from office to office. This is a broken and flawed solution. Do NOT do this. -

    • Essential Background Information

    +

    Essential Background Information

    A Domain Controller is a machine that is able to answer logon requests from network workstations. Microsoft LanManager and IBM LanServer were two early products that provided this capability. The technology has become known as the LanMan Netlogon service. @@ -1277,7 +1277,7 @@ and with it a new form of the network logon service that has extended functional This service became known as the NT NetLogon Service. The nature of this service has changed with the evolution of MS Windows NT and today provides a very complex array of services that are implemented over a complex spectrum of technologies. -

    MS Windows NT4 Style Domain Control

    +

    MS Windows NT4 Style Domain Control

    Whenever a user logs into a Windows NT4 / 200x / XP Professional Workstation, the workstation connects to a Domain Controller (authentication server) to validate the username and password that the user entered are valid. If the information entered @@ -1335,29 +1335,29 @@ one of the BDCs can be promoted to a PDC. If this happens while the original PDC line then it is automatically demoted to a BDC. This is an important aspect of Domain Controller management. The tool that is used to affect a promotion or a demotion is the Server Manager for Domains. -

    Example PDC Configuration

    +

    Example PDC Configuration

    Since version 2.2 Samba officially supports domain logons for all current Windows Clients, including Windows NT4, 2003 and XP Professional. For samba to be enabled as a PDC some parameters in the [global]-section of the smb.conf have to be set: -

    Example 6.1. Minimal smb.conf for being a PDC

    workgroup = MIDEARTH
    domain master = yes
    domain logons = yes

    +

    Example 6.1. Minimal smb.conf for being a PDC

    workgroup = MIDEARTH
    domain master = yes
    domain logons = yes

    Several other things like a [homes] and a [netlogon] share also need to be set along with settings for the profile path, the users home drive, etc.. This will not be covered in this chapter, for more information please refer to the chapter about samba as a PDC. -

    Active Directory Domain Control

    +

    Active Directory Domain Control

    As of the release of MS Windows 2000 and Active Directory, this information is now stored in a directory that can be replicated and for which partial or full administrative control can be delegated. Samba-3 is NOT able to be a Domain Controller within an Active Directory tree, and it can not be an Active Directory server. This means that Samba-3 also can NOT act as a Backup Domain Controller to an Active Directory Domain Controller. -

    What qualifies a Domain Controller on the network?

    +

    What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA<#1c> with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA<#1b> with the WINS server. The name type <#1b> name is normally reserved for the Domain Master Browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to be on the same machine as the PDC. -

    How does a Workstation find its domain controller?

    +

    How does a Workstation find its domain controller?

    An MS Windows NT4 / 200x / XP Professional workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA<#1c>. It assumes that each @@ -1365,7 +1365,7 @@ of the machines it gets back from the queries is a domain controller and can ans requests. To not open security holes both the workstation and the selected domain controller authenticate each other. After that the workstation sends the user's credentials (name and password) to the local Domain Controller, for validation. -

    Backup Domain Controller Configuration

    +

    Backup Domain Controller Configuration

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to @@ -1400,14 +1400,14 @@ Several things have to be done: BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd synchronization. -

    Example Configuration

    +

    Example Configuration

    Finally, the BDC has to be found by the workstations. This can be done by setting: -

    Example 6.2. Minimal setup for being a BDC

    workgroup = MIDEARTH
    domain master = no
    domain logons = yes
    idmap backend = ldapsam://slave-ldap.quenya.org

    +

    Example 6.2. Minimal setup for being a BDC

    workgroup = MIDEARTH
    domain master = no
    domain logons = yes
    idmap backend = ldapsam://slave-ldap.quenya.org

    In the [global]-section of the smb.conf of the BDC. This makes the BDC only register the name SAMBA<#1c> with the WINS server. This is no problem as the name SAMBA<#1c> is a NetBIOS group name that is meant to be registered by more than one machine. The parameter -domain master = no +domain master = no forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS name is reserved for the Primary Domain Controller.

    @@ -1420,10 +1420,10 @@ SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Lin will be consistent on the PDC, all BDCs and all Domain Member servers. The parameter that controls this is called idmap backend. Please refer to the man page for smb.conf for more information regarding it's behaviour. Do NOT set this parameter except where an LDAP backend (ldapsam) is in use. -

    Common Errors

    +

    Common Errors

    As this is a rather new area for Samba there are not many examples that we may refer to. Keep watching for updates to this section. -

    Machine Accounts keep expiring, what can I do?

    +

    Machine Accounts keep expiring, what can I do?

    This problem will occur when occur when the passdb (SAM) files are copied from a central server but the local Backup Domain Controllers. Local machine trust account password updates are not copied back to the central server. The newer machine account password is then over @@ -1434,7 +1434,7 @@ to proceed and the account expiry error will be reported.

    The solution: use a more robust passdb backend, such as the ldapsam backend, setting up an slave LDAP server for each BDC, and a master LDAP server for the PDC. -

    Can Samba be a Backup Domain Controller to an NT4 PDC?

    +

    Can Samba be a Backup Domain Controller to an NT4 PDC?

    With version 2.2, no. The native NT4 SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for Samba-3. @@ -1442,7 +1442,7 @@ but this work has not been finished for Samba-3. Can I get the benefits of a BDC with Samba? Yes, but only to a Samba PDC. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to service logon requests whenever the PDC is down. -

    How do I replicate the smbpasswd file?

    +

    How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is done in the smbpasswd file and has to be replicated to the BDC. So replicating the smbpasswd file very often is necessary. @@ -1456,12 +1456,12 @@ to type a password. As said a few times before, use of this method is broken and flawed. Machine trust accounts will go out of sync, resulting in a very broken domain. This method is not recommended. Try using LDAP instead. -

    Can I do this all with LDAP?

    +

    Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports binding to a replica LDAP server, and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read only, so this will not occur often). -

    Chapter 7. Domain Membership

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "On-the-Fly" Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4 type Domain with Samba-3
    Why is this better than security = server?
    Samba ADS Domain Membership
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    I can't join a Windows 2003 PDC

    +

    Chapter 7. Domain Membership

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "On-the-Fly" Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4 type Domain with Samba-3
    Why is this better than security = server?
    Samba ADS Domain Membership
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails

    Domain Membership is a subject of vital concern, Samba must be able to participate as a member server in a Microsoft Domain security context, and Samba must be capable of providing Domain machine member trust accounts, @@ -1474,7 +1474,7 @@ within the current MS Windows networking world and particularly in the UNIX/Linux networking and administration world, a considerable level of mis-information, incorrect understanding, and a lack of knowledge. Hopefully this chapter will fill the voids. -

    Features and Benefits

    +

    Features and Benefits

    MS Windows workstations and servers that want to participate in domain security need to be made Domain members. Participating in Domain security is often called Single Sign On or SSO for short. This @@ -1510,11 +1510,11 @@ Domain membership has many advantages: client or server, other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an LDAP directory, or via an Active Directory infrastructure) -

    MS Windows Workstation/Server Machine Trust Accounts

    +

    MS Windows Workstation/Server Machine Trust Accounts

    A machine trust account is an account that is used to authenticate a client machine (rather than a user) to the Domain Controller server. In Windows terminology, -this is known as a "Computer Account." +this is known as a "Computer Account."

    The password of a machine trust account acts as the shared secret for secure communication with the Domain Controller. This is a security @@ -1535,7 +1535,7 @@ as follows:

    • A Domain Security Account (stored in the - passdb backend that has been configured in the + passdb backend that has been configured in the smb.conf file. The precise nature of the account information that is stored depends on the type of backend database that has been chosen.

      @@ -1554,49 +1554,49 @@ as follows: simplified mode of operation that does not require UNIX user accounts, but this may not be a feature of the early releases of Samba-3.

    -

    +

    There are three ways to create machine trust accounts:

    • Manual creation from the UNIX/Linux command line. Here, both the Samba and corresponding UNIX account are created by hand.

    • - + Using the MS Windows NT4 Server Manager (either from an NT4 Domain member server, or using the Nexus toolkit available from the Microsoft web site. This tool can be run from any MS Windows machine so long as the user is logged on as the administrator account.

    • - "On-the-fly" creation. The Samba machine trust account is automatically + "On-the-fly" creation. The Samba machine trust account is automatically created by Samba at the time the client is joined to the domain. (For security, this is the recommended method.) The corresponding UNIX account may be created automatically or manually. -

    Manual Creation of Machine Trust Accounts

    +

    Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to manually create the corresponding UNIX account in /etc/passwd. This can be done using vipw or another 'add user' command that is normally used to create new UNIX accounts. The following is an example for a Linux based Samba server: - - + + 

    -root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" \
+root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" \
    -s /bin/false machine_name$ 
 
 root# passwd -l machine_name$

    - + On *BSD systems, this can be done using the chpass utility: 

     root# chpass -a \
-  "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"
+  "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"

    The /etc/passwd entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no +with a "$" appended, won't have a password, will have a null shell and no home directory. For example a machine named 'doppy' would have an /etc/passwd entry like this: 

    @@ -1605,7 +1605,7 @@ doppy$:x:505:100:machine_nickname:/dev/null:
 Above, machine_nickname can be any
 descriptive name for the client, i.e., BasementComputer.
 machine_name absolutely must be the NetBIOS
-name of the client to be joined to the domain.  The "$" must be
+name of the client to be joined to the domain.  The "$" must be
 appended to the NetBIOS name of the client or Samba will not recognize
 this as a machine trust account.
 
    
@@ -1625,14 +1625,14 @@ the corresponding UNIX account.
 
    Join the client to the domain immediately
    
 	Manually creating a machine trust account using this method is the 
 	equivalent of creating a machine trust account on a Windows NT PDC using 
-	
+	
 	the Server Manager.  From the time at which the 
 	account is created to the time which the client joins the domain and 
 	changes the password, your domain is vulnerable to an intruder joining 
 	your domain using a machine with the same NetBIOS name.  A PDC inherently 
 	trusts members of the domain and will serve out a large degree of user 
 	information to such clients.  You have been warned!
-

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    +

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    If the machine from which you are trying to manage the domain is an MS Windows NT4 workstation or MS Windows 200x / XP Professional then the tool of choice is the package called SRVTOOLS.EXE. @@ -1666,7 +1666,7 @@ Launch the srvmgr.exe (Server Manager for Domains) and fo Add NT Workstation of Server, then enter the machine name in the field provided, then click the Add button. -

    "On-the-Fly" Creation of Machine Trust Accounts

    +

    "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client is joined to the domain. @@ -1677,10 +1677,10 @@ add machine script option in accounts may also be created manually.

    Below is an example for a RedHat Linux system. -

    [global]
    # <...remainder of parameters...>
    add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

    Making an MS Windows Workstation or Server a Domain Member

    +

    [global]
    # <...remainder of parameters...>
    add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

    Making an MS Windows Workstation or Server a Domain Member

    The procedure for making an MS Windows workstation of server a member of the domain varies with the version of Windows: -

    Windows 200x XP Professional

    +

    Windows 200x XP Professional

    When the user elects to make the client a domain member, Windows 200x prompts for an account and password that has privileges to create machine accounts in the domain. A Samba administrative account (i.e., a Samba account that has root privileges on the @@ -1694,13 +1694,13 @@ with the version of Windows: The name of the account that is used to create domain member machine accounts can be anything the network administrator may choose. If it is other than root then this is easily mapped to root using the file pointed to be the smb.conf parameter - username map = /etc/samba/smbusers. + username map = /etc/samba/smbusers.

    The session key of the Samba administrative account acts as an encryption key for setting the password of the machine trust account. The machine trust account will be created on-the-fly, or updated if it already exists. -

    Windows NT4

    +

    Windows NT4

    If the machine trust account was created manually, on the Identification Changes menu enter the domain name, but do not check the box Create a Computer Account in the Domain. @@ -1713,7 +1713,7 @@ with the version of Windows: Domain. In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when prompted). -

    Samba

    Joining a Samba client to a domain is documented in +

    Samba

    Joining a Samba client to a domain is documented in the domain member chapter.

    Domain Member Server

    This mode of server operation involves the Samba machine being made a member @@ -1735,19 +1735,19 @@ for more information regarding how to create a domain machine account for a domain member server as well as for information regarding how to enable the Samba domain member machine to join the domain and to be fully trusted by it. -

    Joining an NT4 type Domain with Samba-3

    -

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/NT domain name:MIDEARTH
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    +

    Joining an NT4 type Domain with Samba-3

    +

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/NT domain name:MIDEARTH
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    First, you must edit your smb.conf file to tell Samba it should now use domain security.

    Change (or add) your - security line in the [global] section + security line in the [global] section of your smb.conf to read:

    security = domain

    -Next change the workgroup line in the [global] +Next change the workgroup line in the [global] section to read:

    workgroup = MIDEARTH

    @@ -1755,10 +1755,10 @@ section to read: as this is the name of the domain we are joining.

    You must also have the parameter -encrypt passwords set to yes +encrypt passwords set to yes in order for your users to authenticate to the NT PDC.

    -Finally, add (or modify) a password server line in the [global] +Finally, add (or modify) a password server line in the [global] section to read:

    password server = DOMPDC DOMBDC1 DOMBDC2

    @@ -1824,7 +1824,7 @@ samba daemons depends on your distribution, but in most cases running root# /etc/init.d/samba restart

    does the job. -

    Why is this better than security = server?

    +

    Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from having to create local UNIX users to represent the users attaching to your server. This means that if domain user DOM\fred @@ -1846,11 +1846,11 @@ exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource domain PDC to an account domain PDC).

    -In addition, with security = server every Samba +In addition, with security = server every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run -out of available connections. With security = domain, +out of available connections. With security = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. @@ -1864,22 +1864,22 @@ Much of the text of this document was first published in the Web magazine LinuxWorld as the article Doing the NIS/NT Samba. -

    Samba ADS Domain Membership

    +

    Samba ADS Domain Membership

    This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a Windows2000 KDC. A familiarity with Kerberos is assumed. -

    Setup your smb.conf

    +

    Setup your smb.conf

    You must use at least the following 3 options in smb.conf:

    realm = your.kerberos.REALM
    security = ADS
    encrypt passwords = yes

    In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: +ads server option in smb.conf:

    ads server = your.kerberos.server

    Note

    You do not need a smbpasswd file, and older clients will be authenticated as -if security = domain, although it won't do any harm and +if security = domain, although it won't do any harm and allows you to have local users not in the domain. It is expected that the above required options will change soon when active directory integration will get better. -

    Setup your /etc/krb5.conf

    +

    Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is: 

     [libdefaults]
@@ -1889,7 +1889,7 @@ The minimal configuration for krb5.conf is:
 	YOUR.KERBEROS.REALM = {
 	kdc = your.kerberos.server
 	    }
-

    +

    Test your config by doing a kinit USERNAME@REALM and making sure that your password is accepted by the Win2000 KDC. @@ -1924,7 +1924,7 @@ As a user that has write permission on the Samba private directory 

     root#  net ads join -U Administrator%password

    -

    Possible errors

    +

    Possible errors

    ADS support not compiled in

    Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the Kerberos libs and headers are installed.

    net ads join prompts for user name

    You need to login to the domain using kinit @@ -1933,32 +1933,32 @@ As a user that has write permission on the Samba private directory to the domain.

    Test your server setup

    If the join was successful, you will see a new computer account with the -NetBIOS name of your Samba server in Active Directory (in the "Computers" +NetBIOS name of your Samba server in Active Directory (in the "Computers" folder under Users and Computers.

    On a Windows 2000 client try net use * \\server\share. You should be logged in with Kerberos without needing to know a password. If this fails then run klist tickets. Did you get a ticket for the server? Does it have an encoding type of DES-CBC-MD5 ? -

    Testing with smbclient

    +

    Testing with smbclient

    On your Samba server try to login to a Win2000 server or your Samba server using smbclient and Kerberos. Use smbclient as usual, but specify the -k option to choose Kerberos authentication. -

    Notes

    +

    Notes

    You must change administrator password at least once after DC install, to create the right encoding types

    W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in their defaults DNS setup. Maybe this will be fixed later in service packs. -

    Common Errors

    +

    Common Errors

    In the process of adding / deleting / re-adding domain member machine accounts there are many traps for the unwary player and there are many “little” things that can go wrong. It is particularly interesting how often subscribers on the samba mailing list have concluded -after repeated failed attempts to add a machine account that it is necessary to "re-install" +after repeated failed attempts to add a machine account that it is necessary to "re-install" MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type of problem. The real solution is often very simple, and with understanding of how MS Windows networking functions easy to overcome. -

    Can Not Add Machine Back to Domain

    +

    Can Not Add Machine Back to Domain

    “ A Windows workstation was reinstalled. The original domain machine account was deleted and added immediately. The workstation will not join the domain if I use the same machine name. Attempts to add the machine fail with a message that the machine already @@ -1967,14 +1967,14 @@ exists on the network - I know it doesn't. Why is this failing?” The original name is still in the NetBIOS name cache and must expire after machine account deletion BEFORE adding that same name as a domain member again. The best advice is to delete the old account and then to add the machine with a new name. -

    Adding Machine to Domain Fails

    +

    Adding Machine to Domain Fails

    “Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a message that, The machine could not be added at this time, there is a network problem. Please try again later. Why?”

    -You should check that there is an add machine script in your smb.conf +You should check that there is an add machine script in your smb.conf file. If there is not, please add one that is appropriate for your OS platform. If a script -has been defined you will need to debug it's operation. Increase the log level +has been defined you will need to debug it's operation. Increase the log level in the smb.conf file to level 10, then try to rejoin the domain. Check the logs to see which operation is failing.

    @@ -1992,14 +1992,12 @@ Possible causes include: then make sure that the machine name you are trying to add can be added using this tool. Useradd on some systems will not allow any upper case characters nor will it allow spaces in the name. -

    I can't join a Windows 2003 PDC

    Windows 2003 requires SMB signing. Client side SMB signing has - only been implemented partially in Samba 3.0. Set client use spnego = no when communicating - with a windows 2003 server.

    Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    +

    Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    Stand-Alone servers are independent of Domain Controllers on the network. They are NOT domain members and function more like workgroup servers. In many cases a stand-alone server is configured with a minimum of security control with the intent that all data served will be readily accessible to all users. -

    Features and Benefits

    +

    Features and Benefits

    Stand-Alone servers can be as secure or as insecure as needs dictate. They can have simple or complex configurations. Above all, despite the hoopla about Domain security they remain a very common installation. @@ -2016,7 +2014,7 @@ that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to affect any access controls and no files will be served from the print server. Again a share mode stand-alone server makes a great solution. -

    Background

    +

    Background

    The term stand-alone server means that the server will provide local authentication and access control for all resources that are available from it. In general this means that there will be a @@ -2045,7 +2043,7 @@ This means that the Samba server may use the local UNIX/Linux system password da local smbpasswd file, or may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB server for authentication. -

    Example Configuration

    +

    Example Configuration

    The following examples are designed to inspire simplicity. It is too easy to attempt a high level of creativity and to introduce too much complexity in server and network design. @@ -2055,10 +2053,10 @@ Here is the smb.conf file that will do this. Assume that all the reference docum are stored in the directory /export, that the documents are owned by a user other than nobody. No home directories are shared, that are no users in the /etc/passwd UNIX system database. This is a very simple system to administer. -

    Example 8.1. smb.conf for Reference Documentation Server

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = 192.168.1.1
    [data]
    comment = Data
    path = /export
    guest only = Yes

    +

    Example 8.1. smb.conf for Reference Documentation Server

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = 192.168.1.1
    [data]
    comment = Data
    path = /export
    guest only = Yes

    In the above example the machine name is set to REFDOCS, the workgroup is set to the name of the local workgroup so that the machine will appear in with systems users are familiar -with. The only password backend required is the "guest" backend so as to allow default +with. The only password backend required is the "guest" backend so as to allow default unprivileged account names to be used. Given that there is a WINS server on this network we do use it.

    Central Print Serving

    @@ -2087,7 +2085,7 @@ the anonymous (guest) user, two things will be required: To find the correct name to use for your version of Samba do the following: 

    -$ testparm -s -v | grep "guest account"
+$ testparm -s -v | grep "guest account"

    Then make sure that this account exists in your system password database (/etc/passwd). @@ -2101,48 +2099,48 @@ the anonymous (guest) user, two things will be required: root# chmod a+rwt /var/spool/samba

    -

    Example 8.2. smb.conf for anonymous printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = noldor
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    -

    Common Errors

    +

    Example 8.2. smb.conf for anonymous printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = noldor
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    +

    Common Errors

    The greatest mistake so often made is to make a network configuration too complex. It pays to use the simplest solution that will meet the needs of the moment. -

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Advanced Configuration

    Valuable Nuts and Bolts Information

    +

    Advanced Configuration

    Valuable Nuts and Bolts Information

    Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. -

    Table of Contents

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing Samba to be the master
    Making Samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. File, Directory and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User and Group Based Controls
    File and Directory Permissions Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing file ownership
    Viewing File or Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask - parameters
    Interaction with the standard Samba file attribute mapping
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Problems saving files in MS Office on Windows XP
    Long delays deleting files over network with XP SP1
    Additional Reading
    15. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using host based protection
    User based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Inter-Domain Trust Facilities
    Configuring Samba NT-style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-style Domain Trusts with Windows 2000
    Common Errors
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download
    GDI on Windows -- PostScript on UNIX
    Windows Drivers, GDI and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript -- the Software RIP for non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    CUPS can use all Windows-formatted Vendor PPDs
    CUPS also uses PPDs for non-PostScript Printers
    The CUPS Filtering Architecture
    MIME types and CUPS Filters
    MIME type Conversion Rules
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -native CUPS printing
    Examples for filtering Chains
    Sources of CUPS drivers / PPDs
    Printing with Interface Scripts
    Network printing (purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows clients -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    PPDs for non-PS Printers on UNIX
    PPDs for non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers running in "Kernel Mode" cause many -Problems
    Workarounds impose Heavy Limitations
    CUPS: a "Magical Stone"?
    PostScript Drivers with no major problems -- even in Kernel -Mode
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsmb completed successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding critical PostScript Driver Settings on the -Client
    Installing PostScript Driver Files manually (using -rpcclient)
    A Check of the rpcclient man Page
    Understanding the rpcclient man page
    Producing an Example by querying a Windows Box
    What is required for adddriver and setdriver to succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting revisited
    The printing *.tdb Files
    Trivial DataBase Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic explained
    foomatic-rip and Foomatic-PPD Download and Installation
    Page Accounting with CUPS
    Setting up Quotas
    Correct and incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in - neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." - message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account - from Win2K/XP
    Avoid being connected to the Samba server as the - "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on - NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is - a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security - Policies"
    WinXP clients: "Administrator can not install - printers for all local users"
    "Print Change Notify" functions on - NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/XP
    Most common blunders in driver - settings on Windows clients
    cupsaddsmb does not work - with newly installed printer
    Permissions on +

    Table of Contents

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing Samba to be the master
    Making Samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. File, Directory and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User and Group Based Controls
    File and Directory Permissions Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing file ownership
    Viewing File or Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute mapping
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Problems saving files in MS Office on Windows XP
    Long delays deleting files over network with XP SP1
    Additional Reading
    15. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using host based protection
    User based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Inter-Domain Trust Facilities
    Configuring Samba NT-style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-style Domain Trusts with Windows 2000
    Common Errors
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download
    GDI on Windows -- PostScript on UNIX
    Windows Drivers, GDI and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript -- the Software RIP for non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    CUPS can use all Windows-formatted Vendor PPDs
    CUPS also uses PPDs for non-PostScript Printers
    The CUPS Filtering Architecture
    MIME types and CUPS Filters
    MIME type Conversion Rules
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +native CUPS printing
    Examples for filtering Chains
    Sources of CUPS drivers / PPDs
    Printing with Interface Scripts
    Network printing (purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows clients -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    PPDs for non-PS Printers on UNIX
    PPDs for non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers running in "Kernel Mode" cause many +Problems
    Workarounds impose Heavy Limitations
    CUPS: a "Magical Stone"?
    PostScript Drivers with no major problems -- even in Kernel +Mode
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsmb completed successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding critical PostScript Driver Settings on the +Client
    Installing PostScript Driver Files manually (using +rpcclient)
    A Check of the rpcclient man Page
    Understanding the rpcclient man page
    Producing an Example by querying a Windows Box
    What is required for adddriver and setdriver to succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting revisited
    The printing *.tdb Files
    Trivial DataBase Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic explained
    foomatic-rip and Foomatic-PPD Download and Installation
    Page Accounting with CUPS
    Setting up Quotas
    Correct and incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/XP
    Most common blunders in driver + settings on Windows clients
    cupsaddsmb does not work + with newly installed printer
    Permissions on /var/spool/samba/ get reset after each -reboot
    Printer named "lp" +reboot
    Printer named "lp" intermittently swallows jobs and spits out completely different -ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. PAM based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication using winbindd.so
    Password Synchronization using pam_smbpass.so
    Common Errors
    pam_winbind problem
    Winbind is not resolving users and groups
    26. Integrating MS Windows networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a pure UNIX/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging works only in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    July 5, 1998

    Updated: April 21, 2003

    Table of Contents

    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing Samba to be the master
    Making Samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error

    +ones

    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. PAM based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication using winbindd.so
    Password Synchronization using pam_smbpass.so
    Common Errors
    pam_winbind problem
    Winbind is not resolving users and groups
    26. Integrating MS Windows networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a pure UNIX/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging works only in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    July 5, 1998

    Updated: April 21, 2003

    Table of Contents

    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing Samba to be the master
    Making Samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error

    This document contains detailed information as well as a fast track guide to implementing browsing across subnets and / or across workgroups (or domains). WINS is the best tool for resolution of NetBIOS names to IP addresses. WINS is @@ -2153,11 +2151,11 @@ over TCP/IP. Samba-3 and later also supports this mode of operation. When the use of NetBIOS over TCP/IP has been disabled then the primary means for resolution of MS Windows machine names is via DNS and Active Directory. The following information assumes that your site is running NetBIOS over TCP/IP. -

    Features and Benefits

    +

    Features and Benefits

    Someone once referred to the past in terms of: They were the worst of times, they were the best of times. The more we look back, them more we long for what was and hope it never returns!. -

    +

    For many MS Windows network administrators, that statement sums up their feelings about NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle nature was just par for the course. For those who never quite managed to tame its @@ -2186,7 +2184,7 @@ support for NetBIOS, in which case WINS is of no relevance. Samba supports this

    For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) the use of DNS is necessary for host name resolution. -

    What is Browsing?

    +

    What is Browsing?

    To most people browsing means that they can see the MS Windows and Samba servers in the Network Neighborhood, and when the computer icon for a particular server is clicked, it opens up and shows the shares and printers available on the target server. @@ -2196,41 +2194,41 @@ The technologies (or methods) employed in making all of this work includes:

    • MS Windows machines register their presence to the network

    • Machines announce themselves to other machines on the network

    • One or more machine on the network collates the local announcements

    • The client machine finds the machine that has the collated list of machines

    • The client machine is able to resolve the machine names to IP addresses

    • The client machine is able to connect to a target machine

    The Samba application that controls browse list management and name resolution is called nmbd. The configuration parameters involved in nmbd's operation are: -

    Browsing options: os level(*), - lm announce, - lm interval, - preferred master(*), - local master(*), - domain master(*), - browse list, - enhanced browsing. +

    Browsing options: os level(*), + lm announce, + lm interval, + preferred master(*), + local master(*), + domain master(*), + browse list, + enhanced browsing.

    Name Resolution Method: - name resolve order(*). + name resolve order(*).

    WINS options: - dns proxy, - wins proxy, - wins server(*), - wins support(*), - wins hook. -

    + dns proxy, + wins proxy, + wins server(*), + wins support(*), + wins hook. +

    For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are the only options that commonly MAY need to be modified. Even if not one of these parameters is set nmbd will still do it's job. -

    Discussion

    +

    Discussion

    Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging. SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft is intent on phasing out NetBIOS support. -

    NetBIOS over TCP/IP

    +

    NetBIOS over TCP/IP

    Samba implements NetBIOS, as does MS Windows NT / 200x / XP, by encapsulating it over TCP/IP. MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to affect browse list management. When running NetBIOS over TCP/IP, this uses UDP based messaging. UDP messages can be broadcast or unicast. -

    +

    Normally, only unicast UDP messaging can be forwarded by routers. The -remote announce parameter to smb.conf helps to project browse announcements +remote announce parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP. Similarly, the -remote browse sync parameter of smb.conf +remote browse sync parameter of smb.conf implements browse list collation using unicast UDP.

    Secondly, in those networks where Samba is the only SMB server technology, @@ -2238,13 +2236,13 @@ wherever possible nmbd should be configured on one (1) server. This makes it easy to manage the browsing environment. If each network segment is configured with it's own Samba WINS server, then the only way to get cross segment browsing to work is by using the -remote announce and the remote browse sync +remote announce and the remote browse sync parameters to your smb.conf file.

    - + If only one WINS server is used for an entire multi-segment network then -the use of the remote announce and the -remote browse sync parameters should NOT be necessary. +the use of the remote announce and the +remote browse sync parameters should NOT be necessary.

    As of Samba 3 WINS replication is being worked on. The bulk of the code has been committed, but it still needs maturation. This is NOT a supported feature @@ -2255,7 +2253,7 @@ Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server there must only be one nmbd configured as a WINS server on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used -remote browse sync and remote announce +remote browse sync and remote announce to affect browse list collation across all segments. Note that this means clients will only resolve local names, and must be configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers they can see @@ -2266,10 +2264,10 @@ Lastly, take note that browse lists are a collection of unreliable broadcast messages that are repeated at intervals of not more than 15 minutes. This means that it will take time to establish a browse list and it can take up to 45 minutes to stabilise, particularly across network segments. -

    TCP/IP - without NetBIOS

    - - - +

    TCP/IP - without NetBIOS

    + + + All TCP/IP using systems use various forms of host name resolution. The primary methods for TCP/IP hostname resolutions involves either a static file (/etc/hosts ) or DNS (the Domain Name System). DNS is the technology that makes @@ -2292,7 +2290,7 @@ it follows a defined path:

  • Looks up entries in LMHOSTS. It is located in C:\WinNT\System32\Drivers\etc. -

    • +

    Windows 200x / XP can register it's host name with a Dynamic DNS server. You can force register with a Dynamic DNS server in Windows 200x / XP using: ipconfig /registerdns @@ -2305,7 +2303,7 @@ consequently network services will be severely impaired. The use of Dynamic DNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for it's ability to adequately support the SRV (service) records that are needed for Active Directory. -

    DNS and Active Directory

    +

    DNS and Active Directory

    Occasionally we hear from UNIX network administrators who want to use a UNIX based Dynamic DNS server in place of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible @@ -2327,7 +2325,7 @@ The following are some of the default service records that Active Directory requ

  • _ldap._tcp.Site.gc.ms-dcs.DomainTree

    Used by MS Windows clients to locate site configuration dependent Global Catalog server. -

    • How Browsing Functions

    +

    How Browsing Functions

    MS Windows machines register their NetBIOS names (ie: the machine name for each service type in operation) on start up. The exact method by which this name registration @@ -2341,7 +2339,7 @@ resolution to the local subnet, unless LMHOSTS is used to list all names and IP addresses. In such situations Samba provides a means by which the Samba server name may be forcibly injected into the browse list of a remote MS Windows network (using the -remote announce parameter). +remote announce parameter).

    Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such packets can be routed @@ -2369,12 +2367,12 @@ will annoy users because they will have to put up with protracted inability to use the network services.

    Samba supports a feature that allows forced synchronisation -of browse lists across routed networks using the remote browse sync parameter in the smb.conf file. +of browse lists across routed networks using the remote browse sync parameter in the smb.conf file. This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the remote browse sync parameter provides browse list synchronisation - and +based name resolution, but it should be noted that the remote browse sync parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, for cross subnet browsing to function correctly it is essential that a name to address resolution mechanism be provided. @@ -2405,7 +2403,7 @@ The domain master browser should also preferably be the local master browser for its own subnet. In order to achieve this set the following options in the [global] section of the smb.conf file :

    -

    Example 10.1. Domain master browser smb.conf

    [global]
    domain master = yes
    local master = yes
    preferred master = yes
    os level = 65

    +

    Example 10.1. Domain master browser smb.conf

    [global]
    domain master = yes
    local master = yes
    preferred master = yes
    os level = 65

    The domain master browser may be the same machine as the WINS server, if you require. @@ -2419,15 +2417,15 @@ to use these). To make a Samba server a local master browser set the following options in the [global] section of the smb.conf file :

    -

    Example 10.2. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    +

    Example 10.2. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    Do not do this for more than one Samba server on each subnet, or they will war with each other over which is to be the local master browser.

    -The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level +The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level parameter sets Samba high enough so that it should win any browser elections.

    If you have an NT machine on the subnet that you wish to @@ -2436,8 +2434,8 @@ becoming a local master browser by setting the following options in the [global] section of the smb.conf file :

    -

    Example 10.3. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    -

    Setting up DOMAIN Browsing

    +

    Example 10.3. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    +

    Setting up DOMAIN Browsing

    If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a domain @@ -2452,10 +2450,10 @@ described. To make a Samba server a local master browser set the following options in the [global] section of the smb.conf file :

    -

    Example 10.4. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    +

    Example 10.4. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    If you wish to have a Samba server fight the election with machines -on the same subnet you may set the os level parameter +on the same subnet you may set the os level parameter to lower levels. By doing this you can tune the order of machines that will become local master browsers if they are running. For more details on this see the section @@ -2469,7 +2467,7 @@ ever becoming a local master browser by setting following options in the [global] section of the smb.conf file :

    -

    Example 10.5. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    +

    Example 10.5. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    Forcing Samba to be the master

    Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters @@ -2477,25 +2475,25 @@ which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else.

    -If you want Samba to win elections then just set the os level global +If you want Samba to win elections then just set the os level global option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)

    -A os level of 2 would make it beat WfWg and Win95, but not MS Windows +A os level of 2 would make it beat WfWg and Win95, but not MS Windows NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want Samba to force an election on startup, then set the -preferred master global option in smb.conf to yes. Samba will +preferred master global option in smb.conf to yes. Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with care, as if you have two hosts (whether they are Windows 95 or NT or -Samba) on the same local subnet both set with preferred master to +Samba) on the same local subnet both set with preferred master to yes, then periodically and continually they will force an election in order to become the local master browser.

    If you want Samba to be a domain master browser, then it is -recommended that you also set preferred master to yes, because +recommended that you also set preferred master to yes, because Samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet. @@ -2507,10 +2505,10 @@ attempt to become the domain master browser every 5 minutes. They will find that another Samba server is already the domain master browser and will fail. This provides automatic redundancy, should the current domain master browser fail. -

    Making Samba the domain master

    +

    Making Samba the domain master

    The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make Samba act as the domain master by setting domain master = yes +make Samba act as the domain master by setting domain master = yes in smb.conf. By default it will not be a domain master.

    Note that you should not set Samba to be the domain master for a @@ -2522,8 +2520,8 @@ master browsers on other subnets and then contact them to synchronise browse lists.

    If you want Samba to be the domain master then I suggest you also set -the os level high enough to make sure it wins elections, and set -preferred master to yes, to get Samba to force an election on +the os level high enough to make sure it wins elections, and set +preferred master to yes, to get Samba to force an election on startup.

    Note that all your servers (including Samba) and clients should be @@ -2549,20 +2547,20 @@ If, however, both Samba and your clients are using a WINS server, then: resolve the NetBIOS name of that host. as long as that host has registered its NetBIOS name with the same WINS server, the user will be able to see that host. -

    Note about broadcast addresses

    -If your network uses a "0" based broadcast address (for example if it +

    Note about broadcast addresses

    +If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups does not seem to support a 0's broadcast and you will probably find that browsing and name lookups won't work. -

    Multiple interfaces

    +

    Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces +have multiple interfaces then you will need to use the interfaces option in smb.conf to configure them. -

    Use of the Remote Announce parameter

    -The remote announce parameter of +

    Use of the Remote Announce parameter

    +The remote announce parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. -The syntax of the remote announce parameter is: +The syntax of the remote announce parameter is:

    remote announce = a.b.c.d [e.f.g.h] ...

    or

    remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...

    @@ -2570,8 +2568,8 @@ The syntax of the

    a.b.c.d and e.f.g.h

    - - + + is either the LMB (Local Master Browser) IP address or the broadcast address of the remote network. @@ -2589,20 +2587,20 @@ NetBIOS machine names will end up looking like they belong to that workgroup, this may cause name resolution problems and should be avoided.

    -

    Use of the Remote Browse Sync parameter

    -The remote browse sync parameter of +

    Use of the Remote Browse Sync parameter

    +The remote browse sync parameter of smb.conf is used to announce to another LMB that it must synchronise its NetBIOS name list with our Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on its network segment.

    -The syntax of the remote browse sync parameter is: +The syntax of the remote browse sync parameter is:

    remote browse sync = a.b.c.d

    where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. -

    WINS - The Windows Internetworking Name Server

    +

    WINS - The Windows Internetworking Name Server

    Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. @@ -2643,17 +2641,17 @@ lookup attempts by other clients and will therefore cause workstation access errors.

    To configure Samba as a WINS server just add -wins support = yes to the smb.conf +wins support = yes to the smb.conf file [global] section.

    To configure Samba to register with a WINS server just add -wins server = a.b.c.d to your smb.conf file [global] section. +wins server = a.b.c.d to your smb.conf file [global] section.

    Important

    -Never use both wins support = yes together -with wins server = a.b.c.d +Never use both wins support = yes together +with wins server = a.b.c.d particularly not using it's own IP address. Specifying both will cause nmbd to refuse to start! -

    Setting up a WINS server

    +

    Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must add the following option to the smb.conf file on the selected machine : @@ -2666,11 +2664,11 @@ yes. If you have any older versions of Samba on your network it is strongly suggested you upgrade to a recent version, or at the very least set the parameter to 'no' on all these machines.

    -Machines with wins support = yes will keep a list of +Machines with wins support = yes will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    You should set up only ONE WINS server. Do NOT set the -wins support = yes option on more than one Samba +wins support = yes option on more than one Samba server.

    To set up a Windows NT Server as a WINS server you need to set up @@ -2682,7 +2680,7 @@ participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server but currently only one Samba server should have the -wins support = yes parameter set. +wins support = yes parameter set.

    After the WINS server has been configured you must ensure that all machines participating on the network are configured with the address @@ -2700,8 +2698,8 @@ machine or its IP address.

    Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then +wins support = yes option and the +wins server = <name> option then nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. @@ -2709,12 +2707,12 @@ The first details setting up cross subnet browsing on a network containing Windows 95, Samba and Windows NT machines that are not configured as part of a Windows NT Domain. The second details setting up cross subnet browsing on networks that contain NT Domains. -

    WINS Replication

    +

    WINS Replication

    Samba-3 permits WINS replication through the use of the wrepld utility. This tool is not currently capable of being used as it is still in active development. As soon as this tool becomes moderately functional we will prepare man pages and enhance this section of the documentation to provide usage and technical details. -

    Static WINS Entries

    +

    Static WINS Entries

    Adding static entries to your Samba WINS server is actually fairly easy. All you have to do is add a line to wins.dat, typically located in /usr/local/samba/var/locks. @@ -2722,7 +2720,7 @@ located in /usr/local/samba/var/locks. Entries in wins.dat take the form of 

    -"NAME#TYPE" TTL ADDRESS+ FLAGS
+"NAME#TYPE" TTL ADDRESS+ FLAGS

    where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the @@ -2732,22 +2730,22 @@ flags for the registration.

    A typical dynamic entry looks like: 

    -"MADMAN#03" 1055298378 192.168.1.2 66R
+"MADMAN#03" 1055298378 192.168.1.2 66R

    To make it static, all that has to be done is set the TTL to 0: 

    -"MADMAN#03" 0 192.168.1.2 66R
+"MADMAN#03" 0 192.168.1.2 66R

    Though this method works with early Samba-3 versions, there's a possibility that it may change in future versions if WINS replication is added. -

    Helpful Hints

    +

    Helpful Hints

    The following hints should be carefully considered as they are stumbling points for many new network administrators. -

    Windows Networking Protocols

    Warning

    +

    Windows Networking Protocols

    Warning

    Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than @@ -2759,7 +2757,7 @@ of precedence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably win and thus retain it's role.

    -The election process is "fought out" so to speak over every NetBIOS network +The election process is "fought out" so to speak over every NetBIOS network interface. In the case of a Windows 9x machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both protocols the election will be decided over both protocols. As often happens, if the Windows 9x machine is @@ -2777,7 +2775,7 @@ differently from MS Windows NT4. Generally, where a server does NOT support the newer or extended protocol, these will fall back to the NT4 protocols.

    The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! -

    Name Resolution Order

    +

    Name Resolution Order

    Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information are: @@ -2792,12 +2790,12 @@ The syntax of the name resolve order parameter

    name resolve order = wins lmhosts (eliminates bcast and host)

    The default is:

    name resolve order = host lmhost wins bcast

    -where "host" refers to the native methods used by the UNIX system +where "host" refers to the native methods used by the UNIX system to implement the gethostbyname() function call. This is normally controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf. -

    Technical Overview of browsing

    +

    Technical Overview of browsing

    SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called browse list. This list +of machines in a network, a so-called browse list. This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse @@ -2815,7 +2813,7 @@ Where NetBIOS over TCP/IP is enabled use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that can NOT be provided by any other means of name resolution. -

    Browsing support in Samba

    +

    Browsing support in Samba

    Samba facilitates browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file. Samba can act as a local browse master for a workgroup and the ability @@ -2842,15 +2840,15 @@ WINS server capabilities. In a Samba-only environment, it is recommended that you use one and only one Samba server as your WINS server.

    To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in smb.conf +to use the workgroup option in smb.conf to control what workgroup Samba becomes a part of.

    Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is recommended that this option is only used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the +example. See remote announce in the smb.conf man page. -

    Problem resolution

    +

    Problem resolution

    If something doesn't work then hopefully the log.nmbd file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored @@ -2861,7 +2859,7 @@ type the server name as \\SERVER in filemanager then hit enter and filemanager should display the list of available shares.

    Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the +guest account set to a valid account. Remember that the IPC$ connection that lists the shares is done as guest, and thus you must have a valid guest account.

    @@ -2873,9 +2871,9 @@ name of the currently logged in user to query the IPC$ share. MS Windows server resources.

    The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option +netmask or IP address is wrong (specified with the "interfaces" option in smb.conf) -

    Browsing across subnets

    +

    Browsing across subnets

    Since the release of Samba 1.9.17(alpha1), Samba has supported the replication of browse lists across subnet boundaries. This section describes how to set this feature up in different settings. @@ -2896,7 +2894,7 @@ be they Windows 95, Windows NT, or Samba servers must have the IP address of a WINS server given to them by a DHCP server, or by manual configuration (for Win95 and WinNT, this is in the TCP/IP Properties, under Network settings) for Samba this is in the smb.conf file. -

    How does cross subnet browsing work ?

    +

    How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. @@ -2945,7 +2943,7 @@ At this point the browse lists look as follows (these are the machines you would see in your network neighborhood if you looked in it on a particular network right now).

    -

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    +

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no machine is seen across any of the subnets. @@ -2967,7 +2965,7 @@ the MasterAnnouncement packet it schedules a synchronization request to the sender of that packet. After both synchronizations are done the browse lists look like :

    -

    Table 10.2. Browse subnet example 2

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +

    Table 10.2. Browse subnet example 2

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    @@ -2984,7 +2982,7 @@ it gets both the server entries on subnet 1, and those on subnet 2. After N3_D has synchronized with N1_C and vica-versa the browse lists look like.

    -

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    @@ -3000,7 +2998,7 @@ with the domain master browser (N1_C) and will receive the missing server entries. Finally - and as a steady state (if no machines are removed or shut off) the browse lists will look like :

    -

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), @@ -3027,11 +3025,11 @@ If either router R1 or R2 fails the following will occur: be able to access servers on its local subnet, by using subnet-isolated broadcast NetBIOS name resolution. The effects are similar to that of losing access to a DNS server. -

    Common Errors

    +

    Common Errors

    Many questions are asked on the mailing lists regarding browsing. The majority of browsing problems originate out of incorrect configuration of NetBIOS name resolution. Some are of particular note. -

    How can one flush the Samba NetBIOS name cache without restarting Samba?

    +

    How can one flush the Samba NetBIOS name cache without restarting Samba?

    Samba's nmbd process controls all browse list handling. Under normal circumstances it is safe to restart nmbd. This will effectively flush the Samba NetBIOS name cache and cause it to be rebuilt. Note that this does NOT make certain that a rogue machine name will not re-appear @@ -3041,14 +3039,14 @@ want to clear a rogue machine from the list then every machine on the network wi shut down and restarted at after all machines are down. Failing a complete restart, the only other thing you can do is wait until the entry times out and is then flushed from the list. This may take a long time on some networks (months). -

    My client reports "This server is not configured to list shared resources"

    +

    My client reports "This server is not configured to list shared resources"

    Your guest account is probably invalid for some reason. Samba uses the guest account for browsing in smbd. Check that your guest account is valid. -

    See also guest account in the smb.conf man page.

    I get an Unable to browse the network error

    This error can have multiple causes:

    • There is no local master browser. Configure nmbd +

      See also guest account in the smb.conf man page.

    I get an Unable to browse the network error

    This error can have multiple causes:

    • There is no local master browser. Configure nmbd or any other machine to serve as local master browser.

    • You can not log onto the machine that is the local master browser. Can you logon to it as guest user?

    • There is no IP connectivity to the local master browser. - Can you reach it by broadcast?

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work

    + Can you reach it by broadcast?

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work

    Samba 3 implements a new capability to work concurrently with multiple account backends. The possible new combinations of password backends allows Samba 3 a degree of flexibility and scalability that previously could be achieved only with MS Windows Active Directory. @@ -3058,7 +3056,7 @@ In the course of development of Samba-3, a number of requests were received to p ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide matching UNIX/Linux accounts. We called this the Non UNIX Accounts (NUA) capability. The intent was that an administrator could decide to use the tdbsam -backend and by simply specifying passdb backend = tdbsam_nua +backend and by simply specifying passdb backend = tdbsam_nua this would allow Samba-3 to implement a solution that did not use UNIX accounts per se. Late in the development cycle, the team doing this work hit upon some obstacles that prevents this solution from being used. Given the delays with Samba-3 release a decision was made to NOT @@ -3067,10 +3065,10 @@ SIDs could be found. This feature may thus return during the life cycle for the

    Note

    Samba-3 does NOT support Non-UNIX Account (NUA) operation for user accounts. Samba-3 does support NUA operation for machine accounts. -

    Features and Benefits

    +

    Features and Benefits

    Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality as follows: -

    Backwards Compatibility Backends

    Plain Text:

    +

    Backwards Compatibility Backends

    Plain Text:

    This option uses nothing but the UNIX/Linux /etc/passwd style back end. On systems that have PAM (Pluggable Authentication Modules) support all PAM modules are supported. The behaviour is just as it was with @@ -3093,7 +3091,7 @@ as follows: This option is provided primarily as a migration tool, although there is no reason to force migration at this time. Note that this tool will eventually be deprecated. -

    New Backends

    +

    New Backends

    Samba-3 introduces the following new password backend capabilities:

    tdbsam:

    This backend provides a rich database backend for local servers. This @@ -3121,7 +3119,7 @@ Samba-3 introduces the following new password backend capabilities:

    The new LDAP implementation significantly expands the control abilities that were possible with prior versions of Samba. It is now possible to specify - "per user" profile settings, home directories, account access controls, and + "per user" profile settings, home directories, account access controls, and much more. Corporate sites will see that the Samba-Team has listened to their requests both for capability and to allow greater scalability.

    mysqlsam (MySQL based backend):

    @@ -3137,7 +3135,7 @@ Samba-3 introduces the following new password backend capabilities: The xmlsam option can be useful for account migration between database backends or backups. Use of this tool will allow the data to be edited before migration into another backend format. -

    Technical Information

    +

    Technical Information

    Old windows clients send plain text passwords over the wire. Samba can check these passwords by crypting them and comparing them to the hash stored in the unix user database.

    @@ -3152,16 +3150,16 @@ Samba-3 introduces the following new password backend capabilities: In addition to differently encrypted passwords, windows also stores certain data for each user that is not stored in a unix user database. e.g: workstations the user may logon from, the location where the users' profile is stored, and so on. Samba retrieves and stores this - information using a passdb backend. Commonly available backends are LDAP, plain text + information using a passdb backend. Commonly available backends are LDAP, plain text file, MySQL and nisplus. For more information, see the man page for smb.conf regarding the - passdb backend parameter. -

    Figure 11.1. IDMAP

    IDMAP

    Important Notes About Security

    + passdb backend parameter. +

    Figure 11.1. IDMAP

    IDMAP

    Important Notes About Security

    The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix scheme typically sends clear text passwords over the network when logging in. This is bad. The SMB encryption scheme never sends the cleartext password over the network but it does store the 16 byte hashed values on disk. This is also bad. Why? Because the 16 byte hashed values - are a "password equivalent". You cannot derive the user's password from them, but + are a "password equivalent". You cannot derive the user's password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. You should thus treat the data stored in whatever passdb @@ -3197,7 +3195,7 @@ Samba-3 introduces the following new password backend capabilities: (broken) only the cached (encrypted) password will be sent to the resource server to affect a auto-reconnect. If the resource server does not support encrypted passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS IS STRONGLY ADVISED. -

    Advantages of Encrypted Passwords

    • Plain text passwords are not passed across +

      Advantages of Encrypted Passwords

      • Plain text passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server.

      • Plain text passwords are not stored anywhere in memory or on disk.

      • WinNT doesn't like talking to a server @@ -3208,18 +3206,18 @@ Samba-3 introduces the following new password backend capabilities: only things you can do to stop this is to use SMB encryption.

      • Encrypted password support allows automatic share (resource) reconnects.

      • Encrypted passwords are essential for PDC/BDC - operation.

      Advantages of non-encrypted passwords

      • Plain text passwords are not kept + operation.

      Advantages of non-encrypted passwords

      • Plain text passwords are not kept on disk, and are NOT cached in memory.

      • Uses same password file as other unix services such as login and ftp

      • Use of other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB - isn't such a big deal.

    Mapping User Identifiers between MS Windows and UNIX

    + isn't such a big deal.

    Mapping User Identifiers between MS Windows and UNIX

    Every operation in UNIX/Linux requires a user identifier (UID), just as in MS Windows NT4 / 200x this requires a Security Identifier (SID). Samba provides two means for mapping an MS Windows user to a UNIX/Linux UID.

    Firstly, all Samba SAM (Security Account Manager database) accounts require a UNIX/Linux UID that the account will map to. As users are added to the account - information database, Samba will call the add user script + information database, Samba will call the add user script interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local user account.

    @@ -3245,7 +3243,7 @@ called smbpasswd and pdbedit. A th development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will be announced in time for the Samba-3.0.1 release. -

    The smbpasswd Command

    +

    The smbpasswd Command

    The smbpasswd utility is a utility similar to the passwd or yppasswd programs. It maintains the two 32 byte password fields in the passdb backend. @@ -3291,7 +3289,7 @@ be announced in time for the Samba-3.0.1 release.

    For more details on using smbpasswd refer to the man page (the definitive reference). -

    The pdbedit Command

    +

    The pdbedit Command

    pdbedit is a tool that can be used only by root. It is used to manage the passdb backend. pdbedit can be used to:

    • add, remove or modify user accounts

    • listing user accounts

    • migrate user accounts

    @@ -3333,7 +3331,7 @@ Password must change: Mon, 18 Jan 2038 20:14:07 GMT old smbpasswd database to a tdbsam backend:

    1. - Set the passdb backend = tdbsam, smbpasswd. + Set the passdb backend = tdbsam, smbpasswd.

    2. Execute: 

      @@ -3342,7 +3340,7 @@ Password must change: Mon, 18 Jan 2038 20:14:07 GMT

    3. Now remove the smbpasswd from the passdb backend configuration in smb.conf. -

    Password Backends

    +

    Password Backends

    Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server technology available today. The flexibility is immediately obvious as one begins to explore this capability. @@ -3351,15 +3349,15 @@ It is possible to specify not only multiple different password backends, but eve backends of the same type. For example, to use two different tdbsam databases:

    passdb backend = tdbsam:/etc/samba/passdb.tdb, tdbsam:/etc/samba/old-passdb.tdb

    -

    Plain Text

    +

    Plain Text

    Older versions of Samba retrieved user information from the unix user database and eventually some other fields from the file /etc/samba/smbpasswd or /etc/smbpasswd. When password encryption is disabled, no SMB specific data is stored at all. Instead all operations are conducted via the way that the Samba host OS will access its /etc/passwd database. eg: On Linux systems that is done via PAM. -

    smbpasswd - Encrypted Password Database

    - Traditionally, when configuring encrypt passwords = yes in Samba's smb.conf file, user account +

    smbpasswd - Encrypted Password Database

    + Traditionally, when configuring encrypt passwords = yes in Samba's smb.conf file, user account information such as username, LM/NT password hashes, password change times, and account flags have been stored in the smbpasswd(5) file. There are several disadvantages to this approach for sites with very large numbers of users (counted @@ -3388,7 +3386,7 @@ backends of the same type. For example, to use two different tdbsam databases: Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam. Of these ldapsam will be of most interest to large corporate or enterprise sites. -

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). +

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). Using this backend doesn't require any additional configuration. This backend is recommended for new installations that do not require LDAP.

    @@ -3396,7 +3394,7 @@ backends of the same type. For example, to use two different tdbsam databases: that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that requires replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. -

    ldapsam

    +

    ldapsam

    There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in the this documentation does not include:

    • A means of retrieving user account information from @@ -3404,8 +3402,8 @@ backends of the same type. For example, to use two different tdbsam databases: The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from PADL Software (http://www.padl.com/). More - information about the configuration of these packages may be found at "LDAP, - System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". + information about the configuration of these packages may be found at "LDAP, + System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". Refer to http://safari.oreilly.com/?XmlId=1-56592-491-6 for those who might wish to know more about configuration and administration of an OpenLDAP server. @@ -3424,12 +3422,12 @@ backends of the same type. For example, to use two different tdbsam databases:

      • The Samba-PDC-LDAP-HOWTO maintained by Ignacio Coupeau.

      • The NT migration scripts from IDEALX that are geared to manage users and group in such a Samba-LDAP Domain Controller configuration. -

      Supported LDAP Servers

      +

    Supported LDAP Servers

    The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and client libraries. The same code should work with Netscape's Directory Server and client SDK. However, there are bound to be compile errors and bugs. These should not be hard to fix. Please submit fixes via Bug reporting facility. -

    Schema and Relationship to the RFC 2307 posixAccount

    +

    Schema and Relationship to the RFC 2307 posixAccount

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in examples/LDAP/samba.schema. The sambaSamAccount objectclass is given here:

    @@ -3466,7 +3464,7 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account information in NIS while the network is transitioning to a full LDAP infrastructure. -

    OpenLDAP configuration

    +

    OpenLDAP configuration

    To include support for the sambaSamAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory. The samba.schema file can be found in the directory examples/LDAP @@ -3535,7 +3533,7 @@ index default sub 

     root# /etc/init.d/slapd restart

    -

    Initialise the LDAP database

    +

    Initialise the LDAP database

    Before you can add accounts to the LDAP database you must create the account containers that they will be stored in. The following LDIF file should be modified to match your needs (ie: Your DNS entries, etc.). @@ -3587,36 +3585,36 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 

     root# smbpasswd -w secret

    -

    Configuring Samba

    +

    Configuring Samba

    The following parameters are available in smb.conf only if your version of samba was built with LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found.

    LDAP related smb.conf options: - passdb backend = ldapsam:url, - ldap ssl, - ldap admin dn, - ldap suffix, - ldap filter, - ldap machine suffix, - ldap user suffix, - ldap delete dn, - ldap passwd sync, - ldap trust ids. + passdb backend = ldapsam:url, + ldap ssl, + ldap admin dn, + ldap suffix, + ldap filter, + ldap machine suffix, + ldap user suffix, + ldap delete dn, + ldap passwd sync, + ldap trust ids.

    These are described in the smb.conf man page and so will not be repeated here. However, a sample smb.conf file for use with an LDAP directory could appear as

    -

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = TASHTEGO
    workgroup = NARNIA
    # ldap related parameters
    # define the DN to use when binding to the directory servers
    # The password for this DN is not stored in smb.conf. Rather it
    # must be set by using 'smbpasswd -w secretpw' to store the
    # passphrase in the secrets.tdb file. If the "ldap admin dn" values
    # change, this password will need to be reset.
    ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
    # Define the SSL option when connecting to the directory
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://funball.samba.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # the machine and user suffix added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap machine suffix = ou=Systems
    # Trust unix account information in LDAP
    # (see the smb.conf manpage for details)
    ldap trust ids = Yes
    # specify the base DN to use when searching the directory
    ldap suffix = "ou=people,dc=samba,dc=org"
    # generally the default ldap search filter is ok
    ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"

    -

    Accounts and Groups management

    +

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = TASHTEGO
    workgroup = NARNIA
    # ldap related parameters
    # define the DN to use when binding to the directory servers
    # The password for this DN is not stored in smb.conf. Rather it
    # must be set by using 'smbpasswd -w secretpw' to store the
    # passphrase in the secrets.tdb file. If the "ldap admin dn" values
    # change, this password will need to be reset.
    ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
    # Define the SSL option when connecting to the directory
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://funball.samba.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # the machine and user suffix added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap machine suffix = ou=Systems
    # Trust unix account information in LDAP
    # (see the smb.conf manpage for details)
    ldap trust ids = Yes
    # specify the base DN to use when searching the directory
    ldap suffix = "ou=people,dc=samba,dc=org"
    # generally the default ldap search filter is ok
    ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"

    +

    Accounts and Groups management

    As users accounts are managed through the sambaSamAccount objectclass, you should modify your existing administration tools to deal with sambaSamAccount attributes.

    Machines accounts are managed with the sambaSamAccount objectclass, just like users accounts. However, it's up to you to store those accounts in a different tree of your LDAP namespace: you should use - "ou=Groups,dc=quenya,dc=org" to store groups and - "ou=People,dc=quenya,dc=org" to store users. Just configure your + "ou=Groups,dc=quenya,dc=org" to store groups and + "ou=People,dc=quenya,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration file).

    @@ -3624,7 +3622,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz groups. This means that Samba makes use of the posixGroup objectclass. For now, there is no NT-like group system management (global and local groups). -

    Security and sambaSamAccount

    +

    Security and sambaSamAccount

    There are two important points to remember when discussing the security of sambaSamAccount entries in the directory.

    • Never retrieve the lmPassword or @@ -3635,13 +3633,13 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz on the details of LM/NT password hashes, refer to the Account Information Database section of this chapter.

      - To remedy the first security issue, the ldap ssl smb.conf parameter defaults - to require an encrypted session (ldap ssl = on) using + To remedy the first security issue, the ldap ssl smb.conf parameter defaults + to require an encrypted session (ldap ssl = on) using the default port of 636 when contacting the directory server. When using an OpenLDAP server, it is possible to use the use the StartTLS LDAP extended operation in the place of LDAPS. In either case, you are strongly discouraged to disable this security - (ldap ssl = off). + (ldap ssl = off).

      Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS extended operation. However, the OpenLDAP library still provides support for @@ -3652,15 +3650,15 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz following ACL in slapd.conf: 

      -## allow the "ldap admin dn" access, but deny everyone else
+## allow the "ldap admin dn" access, but deny everyone else
 access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write
+     by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write
      by * none

      -

    LDAP special attributes for sambaSamAccounts

    +

    LDAP special attributes for sambaSamAccounts

    The sambaSamAccount objectclass is composed of the following attributes:

    -

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    sambaLMPasswordthe LANMAN password 16-byte hash stored as a character +

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    sambaLMPasswordthe LANMAN password 16-byte hash stored as a character representation of a hexadecimal string.
    sambaNTPasswordthe NT password hash 16-byte stored as a character representation of a hexadecimal string.
    sambaPwdLastSetThe integer time in seconds since 1970 when the sambaLMPassword and sambaNTPassword attributes were last set. @@ -3668,14 +3666,14 @@ representation of a hexadecimal string.
    sambaLogonTimeInteger value currently unused
    sambaLogoffTimeInteger value currently unused
    sambaKickoffTimeInteger value currently unused
    sambaPwdCanChangeInteger value currently unused
    sambaPwdMustChangeInteger value currently unused
    sambaHomeDrivespecifies the drive letter to which to map the - UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the smb.conf(5) man page for more information.
    sambaLogonScriptThe sambaLogonScript property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the logon script parameter in the + is relative to the netlogon share. Refer to the logon script parameter in the smb.conf man page for more information.
    sambaProfilePathspecifies a path to the user's profile. This value can be a null string, a local absolute path, or a UNC path. Refer to the - logon path parameter in the smb.conf man page for more information.
    sambaHomePathThe sambaHomePath property specifies the path of + logon path parameter in the smb.conf man page for more information.
    sambaHomePathThe sambaHomePath property specifies the path of the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies a drive letter, sambaHomePath should be a UNC path. The path must be a network UNC path of the form \\server\share\directory. This value can be a null string. @@ -3691,15 +3689,15 @@ Refer to the logon home parameter in the

    • sambaHomePath

    • sambaLogonScript

    • sambaProfilePath

    • sambaHomeDrive

    These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume TASHTEGO has now been - configured as a PDC and that logon home = \\%L\%u was defined in - its smb.conf file. When a user named "becky" logons to the domain, - the logon home string is expanded to \\TASHTEGO\becky. - If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", + configured as a PDC and that logon home = \\%L\%u was defined in + its smb.conf file. When a user named "becky" logons to the domain, + the logon home string is expanded to \\TASHTEGO\becky. + If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value - of the logon home parameter is used in its place. Samba + of the logon home parameter is used in its place. Samba will only write the attribute value to the directory entry if the value is something other than the default (e.g. \\MOBY\becky). -

    Example LDIF Entries for a sambaSamAccount

    +

    Example LDIF Entries for a sambaSamAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass: 

    @@ -3746,20 +3744,20 @@ Refer to the logon home parameter in the 
    Password synchronisation
    
+

    Password synchronisation

    Since version 3.0 samba can update the non-samba (LDAP) password stored with an account. When using pam_ldap, this allows changing both unix and windows passwords at once. -

    The ldap passwd sync options can have the following values:

    yes

    When the user changes his password, update +

    The ldap passwd sync options can have the following values:

    yes

    When the user changes his password, update ntPassword, lmPassword - and the password fields.

    no

    Only update ntPassword and lmPassword.

    only

    Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers. [3]

    More information can be found in the smb.conf manpage. -

    MySQL

    + and the password fields.

    no

    Only update ntPassword and lmPassword.

    only

    Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers. [3]

    More information can be found in the smb.conf manpage. +

    MySQL

    Every so often someone will come along with a great new idea. Storing of user accounts in an SQL backend is one of them. Those who want to do this are in the best position to know what the specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt to document every nitty little detail why certain things of marginal utility to the bulk of Samba users might make sense to the rest. In any case, the following instructions should help the determined SQL user to implement a working system. -

    Creating the database

    +

    Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump contains the correct queries to create the required tables. Use the command : @@ -3768,29 +3766,29 @@ Refer to the logon home parameter in the $ mysql -uusername -hhostname -ppassword \ databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    -

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: +

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf:

    passdb backend = [other-plugins] mysql:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with the identifiers of other plugins or other instances of pdb_mysql. If you - specify multiple pdb_mysql.so entries in passdb backend, you also need to + specify multiple pdb_mysql.so entries in passdb backend, you also need to use different identifiers!

    Additional options can be given through the smb.conf file in the [global] section.

    -

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    mysql hosthost name, defaults to 'localhost'
    mysql password 
    mysql userdefaults to 'samba'
    mysql databasedefaults to 'samba'
    mysql portdefaults to 3306
    tableName of the table containing users

    +

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    mysql hosthost name, defaults to 'localhost'
    mysql password 
    mysql userdefaults to 'samba'
    mysql databasedefaults to 'samba'
    mysql portdefaults to 3306
    tableName of the table containing users

    Warning

    Since the password for the MySQL user is stored in the smb.conf file, you should make the smb.conf file readable only to the user that runs Samba This is considered a security bug and will be fixed soon.

    Names of the columns in this table (I've added column types those columns should have first):

    -

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    logon time columnint(9) 
    logoff time columnint(9) 
    kickoff time columnint(9) 
    pass last set time columnint(9) 
    pass can change time columnint(9) 
    pass must change time columnint(9) 
    username columnvarchar(255)unix username
    domain columnvarchar(255)NT domain user is part of
    nt username columnvarchar(255)NT username
    fullname columnvarchar(255)Full name of user
    home dir columnvarchar(255)UNIX homedir path
    dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    logon script columnvarchar(255)Batch file to run on client side when logging on
    profile path columnvarchar(255)Path of profile
    acct desc columnvarchar(255)Some ASCII NT user data
    workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    unknown string columnvarchar(255)unknown string
    munged dial columnvarchar(255)?
    user sid columnvarchar(255)NT user SID
    group sid columnvarchar(255)NT group ID
    lanman pass columnvarchar(255)encrypted lanman password
    nt pass columnvarchar(255)encrypted nt passwd
    plain pass columnvarchar(255)plaintext password
    acct control columnint(9)nt user data
    unknown 3 columnint(9)unknown
    logon divs columnint(9)?
    hours len columnint(9)?
    unknown 5 columnint(9)unknown
    unknown 6 columnint(9)unknown

    +

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    logon time columnint(9) 
    logoff time columnint(9) 
    kickoff time columnint(9) 
    pass last set time columnint(9) 
    pass can change time columnint(9) 
    pass must change time columnint(9) 
    username columnvarchar(255)unix username
    domain columnvarchar(255)NT domain user is part of
    nt username columnvarchar(255)NT username
    fullname columnvarchar(255)Full name of user
    home dir columnvarchar(255)UNIX homedir path
    dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    logon script columnvarchar(255)Batch file to run on client side when logging on
    profile path columnvarchar(255)Path of profile
    acct desc columnvarchar(255)Some ASCII NT user data
    workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    unknown string columnvarchar(255)unknown string
    munged dial columnvarchar(255)?
    user sid columnvarchar(255)NT user SID
    group sid columnvarchar(255)NT group ID
    lanman pass columnvarchar(255)encrypted lanman password
    nt pass columnvarchar(255)encrypted nt passwd
    plain pass columnvarchar(255)plaintext password
    acct control columnint(9)nt user data
    unknown 3 columnint(9)unknown
    logon divs columnint(9)?
    hours len columnint(9)?
    unknown 5 columnint(9)unknown
    unknown 6 columnint(9)unknown

    Eventually, you can put a colon (:) after the name of each column, which should specify the column to update when updating the table. You can also specify nothing behind the colon - then the data from the field will not be updated. -

    Using plaintext passwords or encrypted password

    +

    Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    If you would like to use plaintext passwords, set @@ -3800,7 +3798,7 @@ Refer to the logon home parameter in the

    Getting non-column data from the table

    +

    Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    For example, you can set 'identifier:fullname column' to : @@ -3815,7 +3813,7 @@ Refer to the logon home parameter in the $ pdbedit -i xml:filename -

    Common Errors

    Users can not logon

    “I've installed samba, but now I can't log on with my unix account!”

    Make sure your user has been added to the current samba passdb backend. Read the section Account Management Tools for details.

    Users being added to wrong backend database

    +

    Common Errors

    Users can not logon

    “I've installed samba, but now I can't log on with my unix account!”

    Make sure your user has been added to the current samba passdb backend. Read the section Account Management Tools for details.

    Users being added to wrong backend database

    A few complaints have been received from users that just moved to Samba-3. The following smb.conf file entries were causing problems, new accounts were being added to the old smbpasswd file, not to the tdbsam passdb.tdb file: @@ -3826,34 +3824,34 @@ Refer to the logon home parameter in the

    [globals]
    ...
    passdb backend = tdbsam, smbpasswd
    ...

    -

    auth methods does not work

    - If you explicitly set an auth methods parameter, guest must be specified as the first - entry on the line. Eg: auth methods = guest sam. +

    auth methods does not work

    + If you explicitly set an auth methods parameter, guest must be specified as the first + entry on the line. Eg: auth methods = guest sam.

    - This is the exact opposite of the requirement for the passdb backend + This is the exact opposite of the requirement for the passdb backend option, where it must be the LAST parameter on the line. -


    [3] Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD

    Chapter 12. Mapping MS Windows and UNIX Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group

    +


    [3] Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD

    Chapter 12. Mapping MS Windows and UNIX Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group

    Starting with Samba-3, new group mapping functionality is available to create associations between Windows group SIDs and UNIX groups. The groupmap subcommand included with the net tool can be used to manage these associations.

    Warning

    The first immediate reason to use the group mapping on a Samba PDC, is that - + the domain admin group has been removed and should no longer be specified in smb.conf. This parameter was used to give the listed users membership in the Domain Admins Windows group which gave local admin rights on their workstations (in default configurations). -

    Features and Benefits

    +

    Features and Benefits

    Samba allows the administrator to create MS Windows NT4 / 200x group accounts and to arbitrarily associate them with UNIX/Linux group accounts. -

    +

    Group accounts can be managed using the MS Windows NT4 or MS Windows 200x / XP Professional MMC tools. Appropriate interface scripts should be provided in smb.conf if it is desired that UNIX / Linux system accounts should be automatically created when these tools are used. In the absence of these scripts, and so long as winbind is running, Samba accounts group accounts that are created using these tools will be - allocated UNIX UIDs/GIDs from the parameters set by the idmap uid/idmap gid settings + allocated UNIX UIDs/GIDs from the parameters set by the idmap uid/idmap gid settings in the smb.conf file. -

    Figure 12.1. IDMAP groups

    IDMAP groups

    +

    Figure 12.1. IDMAP groups

    IDMAP groups

    Administrators should be aware that where smb.conf group interface scripts make direct calls to the UNIX/Linux system tools (eg: the shadow utilities, groupadd, groupdel, groupmod) then the resulting UNIX/Linux group names will be subject @@ -3861,7 +3859,7 @@ Refer to the logon home parameter in the Engineering Managers will attempt to create an identically named UNIX/Linux group, an attempt that will of course fail! -

    +

    There are several possible work-arounds for the operating system tools limitation. One method is to use a script that generates a name for the UNIX/Linux system group that fits the operating system limits, and that then just passes the UNIX/Linux group id (GID) @@ -3870,18 +3868,18 @@ Refer to the logon home parameter in the net groupmap tool to connect the two to each other. -

    Discussion

    +

    Discussion

    When installing MS Windows NT4 / 200x on a computer, the installation program creates default users and groups, notably the Administrators group, and gives that group privileges necessary privileges to perform essential system tasks. eg: Ability to change the date and time or to kill (or close) any process running on the local machine. -

    +

    The 'Administrator' user is a member of the 'Administrators' group, and thus inherits 'Administrators' group privileges. If a 'joe' user is created to be a member of the 'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    - When an MS Windows NT4 / W200x is made a domain member, the "Domain Admins" group of the + When an MS Windows NT4 / W200x is made a domain member, the "Domain Admins" group of the PDC is added to the local 'Administrators' group of the workstation. Every member of the 'Domain Administrators' group inherits the rights of the local 'Administrators' group when logging on the workstation. @@ -3896,24 +3894,24 @@ Refer to the logon home parameter in the 

    -root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm
+root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm

    -

    - The quotes around "Domain Admins" are necessary due to the space in the group name. +

    + The quotes around "Domain Admins" are necessary due to the space in the group name. Also make sure to leave no whitespace surrounding the equal character (=).

    Now joe, john and mary are domain administrators! -

    +

    It is possible to map any arbitrary UNIX group to any Windows NT4 / 200x group as well as making any UNIX group a Windows domain group. For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine, you would flag that group as a domain group by running the following on the Samba PDC: 

    -root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct
+root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct

    Be aware that the RID parameter is a unsigned 32 bit integer that should @@ -3921,7 +3919,7 @@ Refer to the logon home parameter in the

    Example Configuration

    +

    Example Configuration

    You can list the various groups in the mapping database by executing net groupmap list. Here is an example:

    @@ -3934,20 +3932,20 @@ Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest

    For complete details on net groupmap, refer to the net(8) man page. -

    Configuration Scripts

    +

    Configuration Scripts

    Everyone needs tools. Some of us like to create our own, others prefer to use canned tools (ie: prepared by someone else for general use). -

    Sample smb.conf add group script

    +

    Sample smb.conf add group script

    A script to create complying group names for use by the Samba group interfaces:

    -

    Example 12.1. smbgrpadd.sh

    +
    Example 12.1. smbgrpadd.sh
     
 #!/bin/bash
 
 # Add the group using normal system groupadd tool.
 groupadd smbtmpgrp00
 
-thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3`
+thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3`
 
 # Now change the name to what we want for the MS Windows networking end
 cp /etc/group /etc/group.bak
@@ -3960,45 +3958,45 @@ exit 0
 
    
 		The smb.conf entry for the above script would look like:
 		
    add group script = /path_to_tool/smbgrpadd.sh %g
    
-		
    Script to configure Group Mapping
    
+		
    Script to configure Group Mapping
    
 		In our example we have created a UNIX/Linux group called ntadmin.
 		Our script will create the additional groups Orks, Elves, Gnomes:
 	
    
 
     #!/bin/bash
 
-net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin
-net groupmap modify ntgroup="Domain Users" unixgroup=users
-net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
-net groupmap modify ntgroup="Administrators" unixgroup=root
-net groupmap modify ntgroup="Users" unixgroup=users
-net groupmap modify ntgroup="Guests" unixgroup=nobody
-net groupmap modify ntgroup="System Operators" unixgroup=sys
-net groupmap modify ntgroup="Account Operators" unixgroup=root
-net groupmap modify ntgroup="Backup Operators" unixgroup=bin
-net groupmap modify ntgroup="Print Operators" unixgroup=lp
-net groupmap modify ntgroup="Replicators" unixgroup=daemon
-net groupmap modify ntgroup="Power Users" unixgroup=sys
+net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin
+net groupmap modify ntgroup="Domain Users" unixgroup=users
+net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
+net groupmap modify ntgroup="Administrators" unixgroup=root
+net groupmap modify ntgroup="Users" unixgroup=users
+net groupmap modify ntgroup="Guests" unixgroup=nobody
+net groupmap modify ntgroup="System Operators" unixgroup=sys
+net groupmap modify ntgroup="Account Operators" unixgroup=root
+net groupmap modify ntgroup="Backup Operators" unixgroup=bin
+net groupmap modify ntgroup="Print Operators" unixgroup=lp
+net groupmap modify ntgroup="Replicators" unixgroup=daemon
+net groupmap modify ntgroup="Power Users" unixgroup=sys
 
 groupadd Orks
 groupadd Elves
 groupadd Gnomes
 
-net groupmap add ntgroup="Orks"       unixgroup=Orks         type=d
-net groupmap add ntgroup="Elves"      unixgroup=Elves        type=d
-net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d
+net groupmap add ntgroup="Orks"       unixgroup=Orks         type=d
+net groupmap add ntgroup="Elves"      unixgroup=Elves        type=d
+net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d
 
    
 
    
 	Of course it is expected that the administrator will modify this to suit local needs.
 	For information regarding the use of the net groupmap tool please
 	refer to the man page.
-

    Common Errors

    +

    Common Errors

    At this time there are many little surprises for the unwary administrator. In a real sense it is imperative that every step of automated control scripts must be carefully tested manually before putting them into active service. -

    Adding Groups Fails

    +

    Adding Groups Fails

    This is a common problem when the groupadd is called directly - by the Samba interface script for the add group script in + by the Samba interface script for the add group script in the smb.conf file.

    The most common cause of failure is an attempt to add an MS Windows group account @@ -4010,9 +4008,9 @@ manually before putting them into active service. third option is to manually create a UNIX/Linux group account that can substitute for the MS Windows group name, then use the procedure listed above to map that group to the MS Windows group. -

    Adding MS Windows Groups to MS Windows Groups Fails

    +

    Adding MS Windows Groups to MS Windows Groups Fails

    Samba-3 does NOT support nested groups from the MS Windows control environment. -

    Adding Domain Users to the Power Users group

    “ +

    Adding Domain Users to the Power Users group

    “ What must I do to add Domain Users to the Power Users group? ”

    The Power Users group is a group that is local to each Windows @@ -4020,15 +4018,15 @@ manually before putting them into active service. group automatically, this must be done on each workstation by logging in as the local workstation administrator and then using click on Start / Control Panel / Users and Passwords now click on the 'Advanced' tab, then on the 'Advanced' Button. -

    +

    Now click on 'Groups', then double click on 'Power Users'. This will launch the panel to add users or groups to the local machine 'Power Uses' group. Click on the 'Add' button, select the domain from which the 'Domain Users' group is to be added, double click on the 'Domain Users' group, then click on the 'Ok' button. Note: If a logon box is presented during this process please remember to enter the connect as DOMAIN\UserName. ie: For the domain MIDEARTH and the user 'root' enter MIDEARTH\root. -

    Chapter 13. File, Directory and Share Access Controls

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    drawing
    The Samba Team

    May 10, 2003

    Table of Contents

    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User and Group Based Controls
    File and Directory Permissions Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing file ownership
    Viewing File or Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask - parameters
    Interaction with the standard Samba file attribute mapping
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file

    +

    Chapter 13. File, Directory and Share Access Controls

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    drawing
    The Samba Team

    May 10, 2003

    Table of Contents

    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User and Group Based Controls
    File and Directory Permissions Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing file ownership
    Viewing File or Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute mapping
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file

    Advanced MS Windows users are frequently perplexed when file, directory and share manipulation of resources shared via Samba do not behave in the manner they might expect. MS Windows network administrators are often confused regarding network access controls and how to @@ -4041,7 +4039,7 @@ and directory access permissions. The problem lies in the differences in how file and directory permissions and controls work between the two environments. This difference is one that Samba can not completely hide, even though it does try to bridge the chasm to a degree. -

    +

    POSIX Access Control List technology has been available (along with Extended Attributes) for UNIX for many years, yet there is little evidence today of any significant use. This explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows @@ -4057,7 +4055,7 @@ and interchange of data between differing operating environments. Samba has no i UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient level of exchange of data between the two environments. What is available today extends well beyond early plans and expectations, yet the gap continues to shrink. -

    Features and Benefits

    +

    Features and Benefits

    Samba offers a lot of flexibility in file system access management. These are the key access control facilities present in Samba today:

    Samba Access Control Facilities

    • @@ -4097,12 +4095,12 @@ beyond early plans and expectations, yet the gap continues to shrink. this also. Sadly, few Linux platforms ship today with native ACLs and Extended Attributes enabled. This chapter has pertinent information for users of platforms that support them. -

    File System Access Controls

    +

    File System Access Controls

    Perhaps the most important recognition to be made is the simple fact that MS Windows NT4 / 200x / XP implement a totally divergent file system technology from what is provided in the UNIX operating system environment. Firstly we should consider what the most significant differences are, then we shall look at how Samba helps to bridge the differences. -

    MS Windows NTFS Comparison with UNIX File Systems

    +

    MS Windows NTFS Comparison with UNIX File Systems

    Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions and permissions. It also means that if the MS Windows networking environment requires file system behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating @@ -4119,7 +4117,7 @@ at how Samba helps to bridge the differences.

    What MS Windows calls a Folder, UNIX calls a directory.

    Case Sensitivity

    - + MS Windows file names are generally upper case if made up of 8.3 (ie: 8 character file name and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case Insensitive. @@ -4155,11 +4153,11 @@ at how Samba helps to bridge the differences. either start up files for various UNIX applications, or they may be files that contain start-up configuration data.

    Links and Short-Cuts

    - - - + + + - MS Windows make use of "links and Short-Cuts" that are actually special types of files that will + MS Windows make use of "links and Short-Cuts" that are actually special types of files that will redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory links, but they are entirely different from what MS Windows users are used to.

    @@ -4171,10 +4169,10 @@ at how Samba helps to bridge the differences. There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the purpose of UNIX/Linux training/education. -

    Managing Directories

    +

    Managing Directories

    There are three basic operations for managing directories, create, delete, rename. -

    Table 13.1. Managing directories with unix and windows

    ActionMS Windows CommandUNIX Command
    createmd foldermkdir folder
    deleterd folderrmdir folder
    renamerename oldname newnamemv oldname newname

    -

    File and Directory Access Control

    +

    Table 13.1. Managing directories with unix and windows

    ActionMS Windows CommandUNIX Command
    createmd foldermkdir folder
    deleterd folderrmdir folder
    renamerename oldname newnamemv oldname newname

    +

    File and Directory Access Control

    The network administrator is strongly advised to read foundational training manuals and reference materials regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions without having to resort to more complex facilities like POSIX Access Control Lists (ACLs) or Extended @@ -4207,7 +4205,7 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08

    Figure 13.1. Overview of unix permissions field

    Overview of unix permissions field

    Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character. -

    Example 13.1. Example File

    +	
    Example 13.1. Example File
     		-rwxr-x---   Means: The owner (user) can read, write, execute
 		                    the group can read and execute
 		                    everyone else can NOT do anything with it
@@ -4233,101 +4231,101 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the
 	directory but can NOT create new files. NOTE: If files in the directory are set to be readable and writable for the group, then
 	group members will be able to write to (or delete) them.
-

    Share Definition Access Controls

    +

    Share Definition Access Controls

    The following parameters in the smb.conf file sections that define a share control or affect access controls. Before using any of the following options please refer to the man page for smb.conf. -

    User and Group Based Controls

    +

    User and Group Based Controls

    User and group based controls can prove very useful. In some situations it is distinctly desirable to affect all - file system operations as if a single user is doing this, the use of the force user and - force group behaviour will achieve this. In other situations it may be necessary to affect a + file system operations as if a single user is doing this, the use of the force user and + force group behaviour will achieve this. In other situations it may be necessary to affect a paranoia level of control to ensure that only particular authorised persons will be able to access a share or - it's contents, here the use of the valid users or the invalid users may + it's contents, here the use of the valid users or the invalid users may be most useful.

    As always, it is highly advisable to use the least difficult to maintain and the least ambiguous method for controlling access. Remember, that when you leave the scene someone else will need to provide assistance and if that person finds too great a mess, or if they do not understand what you have done then there is risk of Samba being removed and an alternative solution being adopted. -

    Table 13.2. User and Group Based Controls

    Control ParameterDescription - Action - Notes
    admin users

    +

    Table 13.2. User and Group Based Controls

    Control ParameterDescription - Action - Notes
    admin users

    List of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). Any user in this list will be able to do anything they like on the share, irrespective of file permissions. -

    force group

    +

    force group

    Specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. -

    force user

    +

    force user

    Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. Incorrect use can cause security problems. -

    guest ok

    +

    guest ok

    If this parameter is set for a service, then no password is required to connect to the service. Privileges will be those of the guest account. -

    invalid users

    +

    invalid users

    List of users that should not be allowed to login to this service. -

    only user

    +

    only user

    Controls whether connections with usernames not in the user list will be allowed. -

    read list

    +

    read list

    List of users that are given read-only access to a service. Users in this list will not be given write access, no matter what the read only option is set to. -

    username

    +

    username

    Refer to the smb.conf man page for more information - this is a complex and potentially misused parameter. -

    valid users

    +

    valid users

    List of users that should be allowed to login to this service. -

    write list

    +

    write list

    List of users that are given read-write access to a service. -

    File and Directory Permissions Based Controls

    +

    File and Directory Permissions Based Controls

    The following file and directory permission based controls, if misused, can result in considerable difficulty to diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually re-introduce them in a controlled fashion. -

    Table 13.3. File and Directory Permission Based Controls

    Control ParameterDescription - Action - Notes
    create mask

    +

    Table 13.3. File and Directory Permission Based Controls

    Control ParameterDescription - Action - Notes
    create mask

    Refer to the smb.conf man page. -

    directory mask

    +

    directory mask

    The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories. See also: directory security mask. -

    dos filemode

    +

    dos filemode

    Enabling this parameter allows a user who has write access to the file to modify the permissions on it. -

    force create mode

    +

    force create mode

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. -

    force directory mode

    +

    force directory mode

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. -

    force directory security mode

    +

    force directory security mode

    Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory -

    force security mode

    +

    force security mode

    Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions. -

    hide unreadable

    +

    hide unreadable

    Prevents clients from seeing the existence of files that cannot be read. -

    hide unwriteable files

    +

    hide unwriteable files

    Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. -

    nt acl support

    +

    nt acl support

    This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists. -

    security mask

    +

    security mask

    Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file. -

    Miscellaneous Controls

    +

    Miscellaneous Controls

    The following are documented because of the prevalence of administrators creating inadvertent barriers to file access by not understanding the full implications of smb.conf file settings. -

    Table 13.4. Other Controls

    Control ParameterDescription - Action - Notes
    case sensitive, default case, short preserve case

    +

    Table 13.4. Other Controls

    Control ParameterDescription - Action - Notes
    case sensitive, default case, short preserve case

    This means that all file name lookup will be done in a case sensitive manner. Files will be created with the precise filename Samba received from the MS Windows client. -

    csc policy

    +

    csc policy

    Client Side Caching Policy - parallels MS Windows client side file caching capabilities. -

    dont descend

    +

    dont descend

    Allows to specify a comma-delimited list of directories that the server should always show as empty. -

    dos filetime resolution

    +

    dos filetime resolution

    This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. -

    dos filetimes

    +

    dos filetimes

    DOS and Windows allows users to change file time stamps if they can write to the file. POSIX semantics prevent this. This options allows DOS and Windows behaviour. -

    fake oplocks

    +

    fake oplocks

    Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data. -

    hide dot files, hide files, veto files

    +

    hide dot files, hide files, veto files

    Note: MS Windows Explorer allows over-ride of files marked as hidden so they will still be visible. -

    read only

    +

    read only

    If this parameter is yes, then users of a service may not create or modify files in the service's directory. -

    veto files

    +

    veto files

    List of files and directories that are neither visible nor accessible. -

    Access Controls on Shares

    +

    Access Controls on Shares

    This section deals with how to configure Samba per share access control restrictions. By default, Samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can @@ -4344,9 +4342,9 @@ Before using any of the following options please refer to the man page for /usr/local/samba/var. If the tdbdump utility has been compiled and installed on your system, then you can examine the contents of this file by: tdbdump share_info.tdb. -

    Share Permissions Management

    +

    Share Permissions Management

    The best tool for the task is platform dependant. Choose the best tool for your environment. -

    Windows NT4 Workstation/Server

    +

    Windows NT4 Workstation/Server

    The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below. @@ -4356,7 +4354,7 @@ Before using any of the following options please refer to the man page for

  • Now click on the share that you wish to manage, then click on the Properties tab, next click on the Permissions tab. Now you can add or change access control settings as you wish. -

    • Windows 200x/XP

    +

    Windows 200x/XP

    On MS Windows NT4/200x/XP system access control lists on the share itself are set using native tools, usually from file manager. For example, in Windows 200x: right click on the shared folder, then select Sharing, then click on Permissions. The default @@ -4385,7 +4383,7 @@ Before using any of the following options please refer to the man page for no access means that MaryK who is part of the group Everyone will have no access even if this user is given explicit full control access. -

    MS Windows Access Control Lists and UNIX Interoperability

    Managing UNIX permissions Using NT Security Dialogs

    +

    MS Windows Access Control Lists and UNIX Interoperability

    Managing UNIX permissions Using NT Security Dialogs

    Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions.

    @@ -4399,7 +4397,7 @@ Before using any of the following options please refer to the man page for

    Viewing File Security on a Samba Share

    +

    Viewing File Security on a Samba Share

    From an NT4/2000/XP client, single-click with the right mouse button on any file or directory in a Samba mounted drive letter or UNC path. When the menu pops-up, click on the Properties entry at the bottom of the menu. This brings up the file properties dialog box. Click on the tab @@ -4410,19 +4408,19 @@ Before using any of the following options please refer to the man page for Add button will not currently allow a list of users to be seen. -

    Viewing file ownership

    +

    Viewing file ownership

    Clicking on the Ownership button brings up a dialog box telling you who owns the given file. The owner name will be of the form:

    - "SERVER\user (Long name)" + "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of the Samba server, user is the user name of the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). Click on the Close button to remove this dialog.

    - If the parameter nt acl support is set to false - then the file owner will be shown as the NT user "Everyone". + If the parameter nt acl support is set to false + then the file owner will be shown as the NT user "Everyone".

    The Take Ownership button will not allow you to change the ownership of this file to yourself (clicking on it will display a dialog box complaining that the user you are currently logged onto @@ -4433,23 +4431,23 @@ Before using any of the following options please refer to the man page for Seclib NT security library written - by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.

    Viewing File or Directory Permissions

    + by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.

    Viewing File or Directory Permissions

    The third button is the Permissions button. Clicking on this brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed in the form: -

    "SERVER\ +

    "SERVER\ user - (Long name)"

    Where SERVER is the NetBIOS name of the Samba server, + (Long name)"

    Where SERVER is the NetBIOS name of the Samba server, user is the user name of the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).

    - If the parameter nt acl support is set to false - then the file owner will be shown as the NT user "Everyone" and the permissions will be - shown as NT "Full Control". + If the parameter nt acl support is set to false + then the file owner will be shown as the NT user "Everyone" and the permissions will be + shown as NT "Full Control".

    The permissions field is displayed differently for files and directories, so I'll describe the way file permissions are displayed first. -

    File Permissions

    The standard UNIX user/group/world triplet and - the corresponding "read", "write", "execute" permissions +

    File Permissions

    The standard UNIX user/group/world triplet and + the corresponding "read", "write", "execute" permissions triplets are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into @@ -4460,20 +4458,20 @@ Before using any of the following options please refer to the man page for icon respectively followed by the list of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common NT names such as read, - "change" or full control then + "change" or full control then usually the permissions will be prefixed by the words - "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed + "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed for a particular UNIX user group or world component? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute + to allow "no permissions" to be seen and modified then Samba + overloads the NT "Take Ownership" ACL attribute (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. + no permissions as having the NT "O" bit set. This was chosen of course to make it look like a zero, meaning zero permissions. More details on the decision behind this will - be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two + be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" + in the first set of parentheses in the normal "RW" NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described above, and is displayed in the same way.

    The second set of directory permissions has no real meaning @@ -4481,15 +4479,15 @@ Before using any of the following options please refer to the man page for permissions that any file created within this directory would inherit.

    Samba synthesises these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple + created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and clicking the OK button. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.

    If the parameter nt acl support + attributes that need to also be taken into account.

    If the parameter nt acl support is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

    The first thing to note is that the "Add" + security permissions will fail with an "Access Denied" + message.

    The first thing to note is that the "Add" button will not return a list of users in Samba (it will give an error message of The remote procedure call failed and did not execute). This means that you can only @@ -4498,13 +4496,13 @@ Before using any of the following options please refer to the man page for

    If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT dialog box, then when the OK button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT "O" flag, as described above. This allows you to add permissions back to a file or directory once - you have removed them from a triplet component.

    As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on + you have removed them from a triplet component.

    As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on the Samba server.

    When setting permissions on a directory the second set of permissions (in the second set of parentheses) is by default applied to all files within that directory. If this @@ -4514,58 +4512,58 @@ Before using any of the following options please refer to the man page for Remove button, or set the component to only have the special Take - Ownership permission (displayed as "O" - ) highlighted.

    Interaction with the standard Samba create mask + Ownership permission (displayed as "O" + ) highlighted.

    Interaction with the standard Samba create mask parameters

    There are four parameters to control interaction with the standard Samba create mask parameters. These are : -

    • security mask

    • force security mode

    • directory security mask

    • force directory security mode

    +

    • security mask

    • force security mode

    • directory security mask

    • force directory security mode

    Once a user clicks OK to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triplet set, and then will check the changed permissions for a file against the bits set in the - security mask parameter. Any bits that + security mask parameter. Any bits that were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask + in the file permissions.

    Essentially, zero bits in the security mask mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change.

    If not set explicitly this parameter is set to the same value as - the create mask parameter. To allow a user to modify all the + the create mask parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter to 0777.

    Next Samba checks the changed permissions for a file against the bits set in the - force security mode parameter. Any bits + force security mode parameter. Any bits that were changed that correspond to bits set to '1' in this parameter are forced to be set.

    Essentially, bits set in the force security mode parameter may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value - as the force create mode parameter. + as the force create mode parameter. To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force + with no restrictions set this parameter to 000.

    The security mask and force security mode parameters are applied to the change request in that order.

    For a directory Samba will perform the same operations as described above for a file except using the parameter directory security mask instead of security mask, and force directory security mode parameter instead of force security mode - .

    The directory security mask parameter + .

    The directory security mask parameter by default is set to the same value as the directory mask parameter and the force directory security mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't force any particular bits to be set 'on', then set the following parameters in the smb.conf file in that share specific section : -

    security mask = 0777
    force security mode = 0
    directory security mask = 0777
    force directory security mode = 0

    Interaction with the standard Samba file attribute mapping

    Note

    Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can +

    security mask = 0777
    force security mode = 0
    directory security mask = 0777
    force directory security mode = 0

    Interaction with the standard Samba file attribute mapping

    Note

    Samba maps some of the DOS attribute bits (such as "read + only") into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security dialog and the permission bits set by the file attribute mapping.

    One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard + for the owner it will show up as "read only" in the standard file attributes tabbed dialog. Unfortunately this dialog is the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions to allow themselves read access using the security dialog, clicks @@ -4576,10 +4574,10 @@ Before using any of the following options please refer to the man page for OK to get back to the attributes dialog you should always hit Cancel rather than OK to ensure that your changes - are not overridden.

    Common Errors

    + are not overridden.

    Common Errors

    File, Directory and Share access problems are very common on the mailing list. The following are examples taken from the mailing list in recent times. -

    Users can not write to a public share

    +

    Users can not write to a public share

    “ We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root), and there's a public share, on which everyone needs to have permission to create / modify files, but only @@ -4645,10 +4643,10 @@ drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar

    An alternative is to set in the smb.conf entry for the share:

    force user = jack
    force group = engr

    -

    I have set force user but Samba still makes root the owner of all the files I touch!

    - When you have a user in admin users, samba will always do file operations for - this user as root, even if force user has been set. -

    MS Word with Samba changes owner of file

    +

    I have set force user but Samba still makes root the owner of all the files I touch!

    + When you have a user in admin users, samba will always do file operations for + this user as root, even if force user has been set. +

    MS Word with Samba changes owner of file

    Question: “When userB saves a word document that is owned by userA the updated file is now owned by userB. Why is Samba doing this? How do I fix this?”

    @@ -4667,10 +4665,10 @@ drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar

    These two settings will ensure that all directories and files that get created in the share will be read/writable by the owner and group set on the directory itself. -

    Chapter 14. File and Record Locking

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Eric Roseme

    HP Oplocks Usage Recommendations Whitepaper

    Table of Contents

    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Problems saving files in MS Office on Windows XP
    Long delays deleting files over network with XP SP1
    Additional Reading

    +

    Chapter 14. File and Record Locking

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Eric Roseme

    HP Oplocks Usage Recommendations Whitepaper

    Table of Contents

    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Problems saving files in MS Office on Windows XP
    Long delays deleting files over network with XP SP1
    Additional Reading

    One area which causes trouble for many network administrators is locking. The extent of the problem is readily evident from searches over the internet. -

    Features and Benefits

    +

    Features and Benefits

    Samba provides all the same locking semantics that MS Windows clients expect and that MS Windows NT4 / 200x servers provide also.

    @@ -4692,7 +4690,7 @@ settings on the MS Windows client.

    Note

    Sometimes it is necessary to disable locking control settings BOTH on the Samba server as well as on each MS Windows client! -

    Discussion

    +

    Discussion

    There are two types of locking which need to be performed by a SMB server. The first is record locking which allows a client to lock a range of bytes in a open file. The second is the deny modes @@ -4717,10 +4715,10 @@ a file. Unfortunately with the way fcntl() works this can be slow and may over-s the rpc.lockd. It is also almost always unnecessary as clients are supposed to independently make locking calls before reads and writes anyway if locking is important to them. By default Samba only makes locking calls when explicitly asked -to by a client, but if you set strict locking = yes then it +to by a client, but if you set strict locking = yes then it will make lock checking calls on every read and write.

    -You can also disable byte range locking completely using locking = no. +You can also disable byte range locking completely using locking = no. This is useful for those shares that don't support locking or don't need it (such as cdroms). In this case Samba fakes the return codes of locking calls to tell clients that everything is OK. @@ -4731,7 +4729,7 @@ access should be allowed simultaneously with its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS. -

    Opportunistic Locking Overview

    +

    Opportunistic Locking Overview

    Opportunistic locking (Oplocks) is invoked by the Windows file system (as opposed to an API) via registry entries (on the server AND client) for the purpose of enhancing network performance when accessing a file @@ -4757,7 +4755,7 @@ other processes. operations on the cached local file.

    If a second process attempts to open the file, the open - is deferred while the redirector "breaks" the original + is deferred while the redirector "breaks" the original oplock. The oplock break signals the caching client to write the local file back to the server, flush the local locks, and discard read-ahead data. The break is @@ -4797,12 +4795,12 @@ The actual decision that a user or administrator should consider is whether it is sensible to share amongst multiple users data that will be cached locally on a client. In many cases the answer is no. Deciding when to cache or not cache data is the real question, and thus -"opportunistic locking" should be treated as a toggle for client-side -caching. Turn it "ON" when client-side caching is desirable and -reliable. Turn it "OFF" when client-side caching is redundant, +"opportunistic locking" should be treated as a toggle for client-side +caching. Turn it "ON" when client-side caching is desirable and +reliable. Turn it "OFF" when client-side caching is redundant, unreliable, or counter-productive.

    -Opportunistic locking is by default set to "on" by Samba on all +Opportunistic locking is by default set to "on" by Samba on all configured shares, so careful attention should be given to each case to determine if the potential benefit is worth the potential for delays. The following recommendations will help to characterize the environment @@ -4854,7 +4852,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Exclusively Accessed Shares

    +

    Exclusively Accessed Shares

    Opportunistic locking is most effective when it is confined to shares that are exclusively accessed by a single user, or by only one user at a time. Because the true value of opportunistic locking is the local @@ -4863,7 +4861,7 @@ mechanism will cause a delay.

    Home directories are the most obvious examples of where the performance benefit of opportunistic locking can be safely realized. -

    Multiple-Accessed Shares or Files

    +

    Multiple-Accessed Shares or Files

    As each additional user accesses a file in a share with opportunistic locking enabled, the potential for delays and resulting perceived poor performance increases. When multiple users are accessing a file on a @@ -4875,7 +4873,7 @@ of the caching user. As each additional client attempts to access a file with oplocks set, the potential performance improvement is negated and eventually results in a performance bottleneck. -

    UNIX or NFS Client Accessed Files

    +

    UNIX or NFS Client Accessed Files

    Local UNIX and NFS clients access files without a mandatory file locking mechanism. Thus, these client platforms are incapable of initiating an oplock break request from the server to a Windows client @@ -4885,7 +4883,7 @@ exposes the file to likely data corruption.

    If files are shared between Windows clients, and either local UNIX or NFS users, then turn opportunistic locking off. -

    Slow and/or Unreliable Networks

    +

    Slow and/or Unreliable Networks

    The biggest potential performance improvement for opportunistic locking occurs when the client-side caching of reads and writes delivers the most differential over sending those reads and writes over the wire. @@ -4900,7 +4898,7 @@ the most advantageous scenario to utilize opportunistic locking. If the network is slow, unreliable, or a WAN, then do not configure opportunistic locking if there is any chance of multiple users regularly opening the same file. -

    Multi-User Databases

    +

    Multi-User Databases

    Multi-user databases clearly pose a risk due to their very nature - they are typically heavily accessed by numerous users at random intervals. Placing a multi-user database on a share with opportunistic @@ -4908,7 +4906,7 @@ locking enabled will likely result in a locking management bottleneck on the Samba server. Whether the database application is developed in-house or a commercially available product, ensure that the share has opportunistic locking disabled. -

    PDM Data Shares

    +

    PDM Data Shares

    Process Data Management (PDM) applications such as IMAN, Enovia, and Clearcase, are increasing in usage with Windows client platforms, and therefore SMB data stores. PDM applications manage multi-user @@ -4921,8 +4919,8 @@ application and PDM server to negotiate and maintain. It is appropriate to eliminate the client OS from any caching tasks, and the server from any oplock management, by disabling opportunistic locking on the share. -

    Beware of Force User

    -Samba includes an smb.conf parameter called force user that changes +

    Beware of Force User

    +Samba includes an smb.conf parameter called force user that changes the user accessing a share from the incoming user to whatever user is defined by the smb.conf variable. If opportunistic locking is enabled on a share, the change in user access causes an oplock break to be sent @@ -4934,26 +4932,26 @@ to overcome the lost oplock break.

    Avoid the combination of the following:

    • - force user in the smb.conf share configuration. + force user in the smb.conf share configuration.

    • Slow or unreliable networks

    • Opportunistic Locking Enabled -

    Advanced Samba Opportunistic Locking Parameters

    +

    Advanced Samba Opportunistic Locking Parameters

    Samba provides opportunistic locking parameters that allow the administrator to adjust various properties of the oplock mechanism to account for timing and usage levels. These parameters provide good versatility for implementing oplocks in environments where they would likely cause problems. The parameters are: -oplock break wait time, -oplock contention limit. +oplock break wait time, +oplock contention limit.

    For most users, administrators, and environments, if these parameters are required, then the better option is to simply turn oplocks off. -The samba SWAT help text for both parameters reads "DO NOT CHANGE THIS -PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." +The samba SWAT help text for both parameters reads "DO NOT CHANGE THIS +PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." This is good advice. -

    Mission Critical High Availability

    +

    Mission Critical High Availability

    In mission critical high availability environments, data integrity is often a priority. Complex and expensive configurations are implemented to ensure that if a client loses connectivity with a file server, a @@ -4983,7 +4981,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Samba Opportunistic Locking Control

    +

    Samba Opportunistic Locking Control

    Opportunistic Locking is a unique Windows file locking feature. It is not really file locking, but is included in most discussions of Windows file locking, so is considered a de facto locking feature. @@ -5005,7 +5003,7 @@ file, the first client receives a break and must synchronise the file back to th This can give significant performance gains in some cases; some programs insist on synchronising the contents of the entire file back to the server for a single change.

    -Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. +Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking.

    Level2 Oplocks provides opportunistic locking for a file that will be treated as read only. Typically this is used on files that are read-only or @@ -5033,9 +5031,9 @@ of your client sending oplock breaks and will instead want to disable oplocks fo

    Another factor to consider is the perceived performance of file access. If oplocks provide no measurable speed benefit on your network, it might not be worth the hassle of dealing with them. -

    Example Configuration

    +

    Example Configuration

    In the following we examine two distinct aspects of Samba locking controls. -

    Disabling Oplocks

    +

    Disabling Oplocks

    You can disable oplocks on a per-share basis with the following:

    [acctdata]
    oplocks = False
    level2 oplocks = False

    @@ -5049,7 +5047,7 @@ Alternately, you could disable oplocks on a per-file basis within the share:

    If you are experiencing problems with oplocks as apparent from Samba's log entries, you may want to play it safe and disable oplocks and level2 oplocks. -

    Disabling Kernel OpLocks

    +

    Disabling Kernel OpLocks

    Kernel OpLocks is an smb.conf parameter that notifies Samba (if the UNIX kernel has the capability to send a Windows client an oplock break) when a UNIX process is attempting to open the file that is @@ -5063,7 +5061,7 @@ to send the oplock break. Kernel oplocks are enabled on a per-server basis in the smb.conf file.

    kernel oplocks = yes

    -The default is "no". +The default is "no".

    Veto OpLocks is an smb.conf parameter that identifies specific files for which Oplocks are disabled. When a Windows client opens a file that @@ -5077,12 +5075,12 @@ caching without the risk of data corruption. Veto Oplocks can be enabled on a per-share basis, or globally for the entire server, in the smb.conf file:

    -

    Example 14.1. Share with some files oplocked

    [global]
    veto oplock files = /filename.htm/*.txt/
    [share_name]
    veto oplock files = /*.exe/filename.ext/

    +

    Example 14.1. Share with some files oplocked

    [global]
    veto oplock files = /filename.htm/*.txt/
    [share_name]
    veto oplock files = /*.exe/filename.ext/

    - oplock break wait time is an smb.conf parameter that adjusts the time + oplock break wait time is an smb.conf parameter that adjusts the time interval for Samba to reply to an oplock break request. Samba -recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND -UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Wait Time can only be +recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND +UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Wait Time can only be configured globally in the smb.conf file:

    oplock break wait time = 0 (default)

    @@ -5090,13 +5088,13 @@ configured globally in the smb.conf file: Oplock break contention limit is an smb.conf parameter that limits the response of the Samba server to grant an oplock if the configured number of contending clients reaches the limit specified by the -parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU -HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break +parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU +HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Contention Limit can be enable on a per-share basis, or globally for the entire server, in the smb.conf file:

    -

    Example 14.2. 

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)

    -

    MS Windows Opportunistic Locking and Caching Controls

    +

    Example 14.2. 

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)

    +

    MS Windows Opportunistic Locking and Caching Controls

    There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP workstation computer that can affect any application attempting to access shared database files across a network. This is a result of a default setting configured in the Windows 2000/XP @@ -5188,7 +5186,7 @@ An illustration of how level II oplocks work: station holds any oplock on the file. Because the workstations can have no cached writes or locks at this point, they need not respond to the break-to-none advisory; all they need do is invalidate locally cashed read-ahead data. -

    Workstation Service Entries

    +

    Workstation Service Entries

     	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanWorkstation\Parameters
 
@@ -5197,7 +5195,7 @@ An illustration of how level II oplocks work:

    Indicates whether the redirector should use opportunistic-locking (oplock) performance enhancement. This parameter should be disabled only to isolate problems. -

    Server Service Entries

    +

    Server Service Entries

     	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanServer\Parameters
 
@@ -5226,7 +5224,7 @@ the server disables raw I/O and opportunistic locking for this connection.
 Specifies the time that the server waits for a client to respond to an oplock break
 request. Smaller values can allow detection of crashed clients more quickly but can
 potentially cause loss of cached data.
-

    Persistent Data Corruption

    +

    Persistent Data Corruption

    If you have applied all of the settings discussed in this chapter but data corruption problems and other symptoms persist, here are some additional things to check out:

    @@ -5237,7 +5235,7 @@ rebuild the data files in question. This involves creating a new data file with same definition as the file to be rebuilt and transferring the data from the old file to the new one. There are several known methods for doing this that can be found in our Knowledge Base. -

    Common Errors

    +

    Common Errors

    In some sites locking problems surface as soon as a server is installed, in other sites locking problems may not surface for a long time. Almost without exception, when a locking problem does surface it will cause embarrassment and potential data corruption. @@ -5267,7 +5265,7 @@ so far: report on https://bugzilla.samba.org without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow reproduction of the problem (an essential step in problem isolation and correction). -

    locking.tdb error messages

    +

    locking.tdb error messages

    “ We are seeing lots of errors in the samba logs like: ” @@ -5280,10 +5278,10 @@ tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic ”

    Corrupted tdb. Stop all instances of smbd, delete locking.tdb, restart smbd. -

    Problems saving files in MS Office on Windows XP

    This is a bug in Windows XP. More information can be - found in Microsoft Knowledge Base article 812937.

    Long delays deleting files over network with XP SP1

    “It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied”

    This is a bug in Windows XP. More information can be +

    Problems saving files in MS Office on Windows XP

    This is a bug in Windows XP. More information can be + found in Microsoft Knowledge Base article 812937.

    Long delays deleting files over network with XP SP1

    “It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied”

    This is a bug in Windows XP. More information can be found in - Microsoft Knowledge Base article 811492.

    Additional Reading

    + Microsoft Knowledge Base article 811492.

    Additional Reading

    You may want to check for an updated version of this white paper on our Web site from time to time. Many of our white papers are updated as information changes. For those papers, the Last Edited date is always at the top of the paper. @@ -5295,27 +5293,27 @@ Windows Base Services > Files and I/O > SDK Documentation > File Storag > About File Systems > Opportunistic Locks, Microsoft Corporation. http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp

    -Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", +Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", Microsoft Corporation, April 1999, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992.

    -Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", +Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", Microsoft Corporation, April 2001, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264.

    -Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", +Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", Microsoft Corporation, April 1995, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202. -

    Chapter 15. Securing Samba

    Andrew Tridgell

    Samba Team

    John H. Terpstra

    Samba Team

    May 26, 2003

    Table of Contents

    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using host based protection
    User based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    +

    Chapter 15. Securing Samba

    Andrew Tridgell

    Samba Team

    John H. Terpstra

    Samba Team

    May 26, 2003

    Table of Contents

    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using host based protection
    User based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba installations in general.

    -A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, -if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning -on it!" +A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, +if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning +on it!"

    Security concerns are just like that: You need to know a little about the subject to appreciate how obvious most of it really is. The challenge for most of us is to discover that first morsel of knowledge with which we may unlock the secrets of the masters. -

    Features and Benefits

    +

    Features and Benefits

    There are three level at which security principals must be observed in order to render a site at least moderately secure. These are: the perimeter firewall, the configuration of the host server that is running Samba, and Samba itself. @@ -5325,7 +5323,7 @@ the latest protocols to permit more secure MS Windows file and print operations.

    Samba may be secured from connections that originate from outside the local network. This may be done using host based protection (using samba's implementation of a technology -known as "tcpwrappers", or it may be done be using interface based exclusion +known as "tcpwrappers", or it may be done be using interface based exclusion so that smbd will bind only to specifically permitted interfaces. It is also possible to set specific share or resource based exclusions, eg: on the [IPC$] auto-share. The [IPC$] share is used for browsing purposes as well as to establish @@ -5334,21 +5332,21 @@ TCP/IP connections. Another method by which Samba may be secured is by way of setting Access Control Entries in an Access Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access Control. -

    Technical Discussion of Protective Measures and Issues

    +

    Technical Discussion of Protective Measures and Issues

    The key challenge of security is the fact that protective measures suffice at best only to close the door on known exploits and breach techniques. Never assume that because you have followed these few measures that the Samba server is now an impenetrable fortress! Given the history of information systems so far, it is only a matter of time before someone will find yet another vulnerability. -

    Using host based protection

    +

    Using host based protection

    In many installations of Samba the greatest threat comes for outside your immediate network. By default Samba will accept connections from any host, which means that if you run an insecure version of Samba on a host that is directly connected to the Internet you can be especially vulnerable.

    - One of the simplest fixes in this case is to use the hosts allow and - hosts deny options in the Samba smb.conf configuration file to only + One of the simplest fixes in this case is to use the hosts allow and + hosts deny options in the Samba smb.conf configuration file to only allow access to your server from a specific range of hosts. An example might be:

    hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
    hosts deny = 0.0.0.0/0

    @@ -5357,13 +5355,13 @@ before someone will find yet another vulnerability. 192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as a not listening on called name error. -

    User based protection

    +

    User based protection

    If you want to restrict access to your server to valid users only then the following method may be of use. In the smb.conf [global] section put:

    valid users = @smbusers, jacko

    What this does is, it restricts all server access to either the user jacko or to members of the system group smbusers. -

    Using interface protection

    +

    Using interface protection

    By default Samba will accept connections on any network interface that it finds on your system. That means if you have a ISDN line or a PPP connection to the Internet then Samba will accept connections on those @@ -5382,7 +5380,7 @@ before someone will find yet another vulnerability. connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that interface to any samba process. -

    Using a firewall

    +

    Using a firewall

    Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above @@ -5395,7 +5393,7 @@ before someone will find yet another vulnerability. The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years. -

    Using a IPC$ share deny

    +

    Using a IPC$ share deny

    If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that is used in the recently discovered security hole. This allows you to offer access to other @@ -5418,12 +5416,12 @@ before someone will find yet another vulnerability.

    This is not recommended unless you cannot use one of the other methods listed above for some reason. -

    NTLMv2 Security

    +

    NTLMv2 Security

    To configure NTLMv2 authentication the following registry keys are worth knowing about: 

     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
-		"lmcompatibilitylevel"=dword:00000003
+		"lmcompatibilitylevel"=dword:00000003

    0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication, @@ -5432,30 +5430,30 @@ before someone will find yet another vulnerability. 

     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
-		"NtlmMinClientSec"=dword:00080000
+		"NtlmMinClientSec"=dword:00080000

    0x80000 - NTLMv2 session security. If either NtlmMinClientSec or NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2 session security is not negotiated. -

    Upgrading Samba

    +

    Upgrading Samba

    Please check regularly on http://www.samba.org/ for updates and important announcements. Occasionally security releases are made and it is highly recommended to upgrade Samba when a security vulnerability is discovered. Check with your OS vendor for OS specific upgrades. -

    Common Errors

    +

    Common Errors

    If all of samba and host platform configuration were really as intuitive as one might like then this section would not be necessary. Security issues are often vexing for a support person to resolve, not because of the complexity of the problem, but for reason that most administrators who post what turns out to be a security problem request are totally convinced that the problem is with Samba. -

    Smbclient works on localhost, but the network is dead

    +

    Smbclient works on localhost, but the network is dead

    This is a very common problem. Red Hat Linux (as do others) will install a default firewall. With the default firewall in place only traffic on the loopback adapter (IP address 127.0.0.1) will be allowed through the firewall.

    The solution is either to remove the firewall (stop it) or to modify the firewall script to allow SMB networking traffic through. See section above in this chapter. -

    Why can users access home directories of other users?

    +

    Why can users access home directories of other users?

    “ We are unable to keep individual users from mapping to any other user's home directory once they have supplied a valid password! They only need @@ -5484,7 +5482,7 @@ out to be a security problem request are totally convinced that the problem is w the policies and permissions he or she desires.

    Samba does allow the setup you require when you have set the - only user = yes option on the share, is that you have not set the + only user = yes option on the share, is that you have not set the valid users list for the share.

    Note that only user works in conjunction with the users= list, @@ -5494,14 +5492,14 @@ out to be a security problem request are totally convinced that the problem is w

    valid users = %S

    to the definition of the [homes] share, as recommended in the smb.conf man page. -

    Chapter 16. Interdomain Trust Relationships

    John H. Terpstra

    Samba Team

    Rafal Szczesniak

    Samba Team

    Jelmer R. Vernooij

    drawing
    The Samba Team

    Stephen Langasek

    April 3, 2003

    Table of Contents

    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Inter-Domain Trust Facilities
    Configuring Samba NT-style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-style Domain Trusts with Windows 2000
    Common Errors

    +

    Chapter 16. Interdomain Trust Relationships

    John H. Terpstra

    Samba Team

    Rafal Szczesniak

    Samba Team

    Jelmer R. Vernooij

    drawing
    The Samba Team

    Stephen Langasek

    April 3, 2003

    Table of Contents

    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Inter-Domain Trust Facilities
    Configuring Samba NT-style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-style Domain Trusts with Windows 2000
    Common Errors

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba3-to-Samba3 trusts. -

    Features and Benefits

    +

    Features and Benefits

    Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4 style trust relationships. This imparts to Samba similar scalability as is possible with MS Windows NT4. @@ -5511,7 +5509,7 @@ database such as LDAP, and given it's ability to run in Primary as well as Backu modes, the administrator would be well advised to consider alternatives to the use of Interdomain trusts simply because by the very nature of how this works it is fragile. That was, after all, a key reason for the development and adoption of Microsoft Active Directory. -

    Trust Relationship Background

    +

    Trust Relationship Background

    MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking in large organisations is well known. Additionally, the flat namespace that results from @@ -5547,13 +5545,13 @@ domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 style Interdomain trusts and interoperates with MS Windows 200x ADS security domains in similar manner to MS Windows NT4 style domains. -

    Native MS Windows NT4 Trusts Configuration

    +

    Native MS Windows NT4 Trusts Configuration

    There are two steps to creating an interdomain trust relationship. To effect a two-way trust relationship it is necessary for each domain administrator to create a trust account for the other domain to use in verifying security credentials. - -

    Creating an NT4 Domain Trust

    + +

    Creating an NT4 Domain Trust

    For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. This is done from the Domain User Manager Policies entry on the menu bar. From the Policy menu, select @@ -5564,15 +5562,15 @@ to enter the name of the remote domain that will be able to assign access rights your domain. You will also need to enter a password for this trust relationship, which the trusting domain will use when authenticating users from the trusted domain. The password needs to be typed twice (for standard confirmation). -

    Completing an NT4 Domain Trust

    - +

    Completing an NT4 Domain Trust

    + A trust relationship will work only when the other (trusting) domain makes the appropriate connections with the trusted domain. To consummate the trust relationship the administrator will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the Add button that is next to the box that is labelled Trusted Domains. A panel will open in which must be entered the name of the remote domain as well as the password assigned to that trust. -

    Inter-Domain Trust Facilities

    +

    Inter-Domain Trust Facilities

    A two-way trust relationship is created when two one-way trusts are created, one in each direction. Where a one-way trust has been established between two MS Windows NT4 domains (let's call them DomA and DomB) the following facilities are created: @@ -5612,7 +5610,7 @@ DomA and DomB) the following facilities are created:

  • Global Groups from the trusted domain CAN be made members in Local Groups on MS Windows domain member machines. -

    • Configuring Samba NT-style Domain Trusts

    +

    Configuring Samba NT-style Domain Trusts

    This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba is in its early stage, so lot of things don't work yet. @@ -5650,7 +5648,7 @@ After the command returns successfully, you can look at the entry for the new ac (in the standard way as appropriate for your configuration) and see that account's name is really RUMBA$ and it has the 'I' flag set in the flags field. Now you're ready to confirm the trust by establishing it from Windows NT Server. -

    +

    Open User Manager for Domains and from the Policies menu, select Trust Relationships.... Right beside the Trusted domains list box press the @@ -5660,12 +5658,12 @@ the name of the remote domain, and the password used at the time of account crea Press OK and, if everything went without incident, you will see Trusted domain relationship successfully established message. -

    Samba as the Trusting Domain

    +

    Samba as the Trusting Domain

    This time activities are somewhat reversed. Again, we'll assume that your domain controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.

    The very first step is to add an account for the SAMBA domain on RUMBA's PDC. -

    +

    Launch the Domain User Manager, then from the menu select Policies, Trust Relationships. Now, next to the Trusted Domains box press the Add @@ -5691,7 +5689,7 @@ Congratulations! Your trust relationship has just been established.

    Note

    Note that you have to run this command as root because you must have write access to the secrets.tdb file. -

    NT4-style Domain Trusts with Windows 2000

    +

    NT4-style Domain Trusts with Windows 2000

    Although Domain User Manager is not present in Windows 2000, it is also possible to establish an NT4-style trust relationship with a Windows 2000 domain controller running in mixed mode as the trusting server. It should also be possible for @@ -5712,13 +5710,13 @@ will be prompted for the trusted domain name and the relationship password. Pre after a moment, Active Directory will respond with The trusted domain has been added and the trust has been verified. Your Samba users can now be granted acess to resources in the AD domain. -

    Common Errors

    +

    Common Errors

    Interdomain trust relationships should NOT be attempted on networks that are unstable or that suffer regular outages. Network stability and integrity are key concerns with distributed trusted domains.

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software



    -

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    +

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    The Distributed File System (or DFS) provides a means of separating the logical view of files and directories that users see from the actual physical locations of these resources on the network. It allows for higher availability, smoother @@ -5732,9 +5730,9 @@ distributed trusted domains.

    To enable SMB-based DFS for Samba, configure it with the --with-msdfs option. Once built, a Samba server can be made a DFS server by setting the global - boolean host msdfs + boolean host msdfs parameter in the smb.conf file. You designate a share as a DFS - root using the share level boolean msdfs root parameter. A DFS root directory on Samba hosts DFS + root using the share level boolean msdfs root parameter. A DFS root directory on Samba hosts DFS links in the form of symbolic links that point to other servers. For example, a symbolic link junction->msdfs:storage1\share1 in the share directory acts as the DFS junction. When DFS-aware clients attempt to access the junction link, @@ -5743,7 +5741,7 @@ distributed trusted domains. DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.

    Here's an example of setting up a DFS tree on a Samba server. -

    Example 17.1. smb.conf with DFS configured

    [global]
    netbios name = GANDALF
    host msdfs = yes
    [dfs]
    path = /export/dfsroot
    msdfs root = yes

    In the /export/dfsroot directory we set up our DFS links to +

    Example 17.1. smb.conf with DFS configured

    [global]
    netbios name = GANDALF
    host msdfs = yes
    [dfs]
    path = /export/dfsroot
    msdfs root = yes

    In the /export/dfsroot directory we set up our DFS links to other servers on the network.

     root# cd /export/dfsroot
 root# chown root /export/dfsroot
@@ -5759,16 +5757,16 @@ distributed trusted domains.
 	network shares you want, and start Samba.
    Users on DFS-aware clients can now browse the DFS tree 
 	on the Samba server at \\samba\dfs. Accessing 
 	links linka or linkb (which appear as directories to the client) 
-	takes users directly to the appropriate shares on the network.

    Common Errors

    • Windows clients need to be rebooted + takes users directly to the appropriate shares on the network.

    Common Errors

    • Windows clients need to be rebooted if a previously mounted non-dfs share is made a DFS root or vice versa. A better way is to introduce a new share and make it the DFS root.

    • Currently there's a restriction that msdfs symlink names should all be lowercase.

    • For security purposes, the directory acting as the root of the DFS tree should have ownership and permissions set so that only designated users can - modify the symbolic links in the directory.

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost

    Features and Benefits

    + modify the symbolic links in the directory.

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost

    Features and Benefits

    Printing is often a mission-critical service for the users. Samba can provide this service reliably and seamlessly for a client network consisting of Windows workstations. @@ -5781,10 +5779,10 @@ authentication schemes are essentially the same as described for file services in previous chapters. Overall, Samba's printing support is now able to replace an NT or Windows 2000 print server full-square, with additional benefits in many cases. Clients may download and -install drivers and printers through their familiar "Point'n'Print" -mechanism. Printer installations executed by "Logon Scripts" are no +install drivers and printers through their familiar "Point'n'Print" +mechanism. Printer installations executed by "Logon Scripts" are no problem. Administrators can upload and manage drivers to be used by -clients through the familiar "Add Printer Wizard". As an additional +clients through the familiar "Add Printer Wizard". As an additional benefit, driver and printer management may be run from the command line or through scripts, making it more efficient in case of large numbers of printers. If a central accounting of print jobs (tracking every @@ -5804,17 +5802,17 @@ Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 2000 clients are very similar, but may differ in details. Windows NT is somewhat different again. -

    Technical Introduction

    +

    Technical Introduction

    Samba's printing support always relies on the installed print -subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes +subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes printfiles from Windows (or other SMB) clients and passes them to the real printing system for further processing. Therefore it needs to -"talk" to two sides: to the Windows print clients and to the UNIX +"talk" to two sides: to the Windows print clients and to the UNIX printing system. Hence we must differentiate between the various client OS types each of which behave differently, as well as the various UNIX print subsystems, which themselves have different features and are accessed differently. This part of the Samba HOWTO -Collection deals with the "traditional" way of UNIX printing first; +Collection deals with the "traditional" way of UNIX printing first; the next chapter covers in great detail the more modern Common UNIX Printing System (CUPS). @@ -5822,7 +5820,7 @@ the next chapter covers in great detail the more modern

    Important

    CUPS users, be warned: don't just jump on to the next chapter. You might miss important information contained only here!

    -

    What happens if you send a Job from a Client

    +

    What happens if you send a Job from a Client

    To successfully print a job from a Windows client via a Samba print server to a UNIX printer, there are 6 (potentially 7) stages: @@ -5830,57 +5828,57 @@ stages: into Samba's spooling area

  • Windows closes the connection again

  • Samba invokes the print command to hand the file over to the UNIX print subsystem's spooling area

  • The UNIX print subsystem processes the print job

  • The printfile may need to be explicitly deleted -from the Samba spooling area.

    • Printing Related Configuration Parameters

    +from the Samba spooling area.

    Printing Related Configuration Parameters

    There are a number of configuration parameters in controlling Samba's printing behaviour. Please also refer to the man page for smb.conf to acquire an overview about these. As with other parameters, there are -Global Level (tagged with a "G" in the listings) and -Service Level ("S") parameters. +Global Level (tagged with a "G" in the listings) and +Service Level ("S") parameters.

    Service Level Parameters

    These may go into the [global] section of smb.conf. In this case they define the default behaviour of all individual or service level shares (provided those don't have a different setting defined for the same parameter, thus overriding the global default).

    Global Parameters

    These may not go into individual -shares. If they go in by error, the "testparm" utility can discover -this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly +shares. If they go in by error, the "testparm" utility can discover +this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly related to printing are used in Samba. See also the smb.conf man page for detailed explanations: -

    Global level parameters: addprinter command, -deleteprinter command, -disable spoolss, -enumports command, -load printers, -lpq cache time, -os2 driver map, -printcap name, printcap, -show add printer wizard, -total print jobs, -use client driver. -

    Service level parameters: hosts allow, -hosts deny, -lppause command, -lpq command, -lpresume command, -lprm command, -max print jobs, -min print space, -print command, -printable, print ok , -printer name, printer, -printer admin, -printing = [cups|bsd|lprng...], -queuepause command, -queueresume command, -total print jobs. +

    Global level parameters: addprinter command, +deleteprinter command, +disable spoolss, +enumports command, +load printers, +lpq cache time, +os2 driver map, +printcap name, printcap, +show add printer wizard, +total print jobs, +use client driver. +

    Service level parameters: hosts allow, +hosts deny, +lppause command, +lpq command, +lpresume command, +lprm command, +max print jobs, +min print space, +print command, +printable, print ok , +printer name, printer, +printer admin, +printing = [cups|bsd|lprng...], +queuepause command, +queueresume command, +total print jobs.

    Samba's printing support implements the Microsoft Remote Procedure Calls (MS-RPC) methods for printing. These are used by Windows NT (and -later) print servers. The old "LanMan" protocol is still supported as +later) print servers. The old "LanMan" protocol is still supported as a fallback resort, and for older clients to use. More details will follow further beneath. -

    A simple Configuration to Print

    +

    A simple Configuration to Print

    Here is a very simple example configuration for print related settings in the file. If you compare it with your own system's , you probably find some additional parameters included there (as pre-configured by your OS @@ -5888,7 +5886,7 @@ vendor). Further below is a discussion and explanation of the parameters. Note, that this example doesn't use many parameters. However, in many environments these are enough to provide a valid smb.conf file which enables all clients to print. -

    Example 18.1. Simple configuration with BSD printing

    [global]
    printing = bsd
    load printers = yes
    [printers]
    path = /var/spool/samba
    printable = yes
    public = yes
    writable = no

    +

    Example 18.1. Simple configuration with BSD printing

    [global]
    printing = bsd
    load printers = yes
    [printers]
    path = /var/spool/samba
    printable = yes
    public = yes
    writable = no

    This is only an example configuration. Samba assigns default values to all configuration parameters. On the whole the defaults are conservative and sensible. When a parameter is specified in the smb.conf file this overwrites @@ -5901,25 +5899,25 @@ to pipe it through a pager program. The syntax for the configuration file is easy to grasp. You should know that is not very picky about its syntax. It has been explained elsewhere in this document. A short -reminder: It even tolerates some spelling errors (like "browsable" -instead of "browseable"). Most spelling is case-insensitive. Also, you -can use "Yes|No" or "True|False" for boolean settings. Lists of names +reminder: It even tolerates some spelling errors (like "browsable" +instead of "browseable"). Most spelling is case-insensitive. Also, you +can use "Yes|No" or "True|False" for boolean settings. Lists of names may be separated by commas, spaces or tabs. -

    Verification of "Settings in Use" with testparm

    +

    Verification of "Settings in Use" with testparm

    To see all (or at least most) printing related settings in Samba, including the implicitly used ones, try the command outlined below -(hit "ENTER" twice!). It greps for all occurrences of "lp", "print", -"spool", "driver", "ports" and "[" in testparm's output and gives you +(hit "ENTER" twice!). It greps for all occurrences of "lp", "print", +"spool", "driver", "ports" and "[" in testparm's output and gives you a nice overview about the running smbd's print configuration. (Note that this command does not show individually created printer shares, or the spooling paths in each case). Here is the output of my Samba setup, with exactly the same settings in as shown above: 

    -root# testparm -v | egrep "(lp|print|spool|driver|ports|\[)"
+root# testparm -v | egrep "(lp|print|spool|driver|ports|\[)"
  Load smb config files from /etc/samba/smb.conf.simpleprinting
- Processing section "[homes]"
- Processing section "[printers]"
+ Processing section "[homes]"
+ Processing section "[printers]"
  
  [global]
         smb ports = 445 139
@@ -5957,20 +5955,20 @@ You can easily verify which settings were implicitly added by Samba's
 default behaviour. Don't forget about this point: it may
 be important in your future dealings with Samba.
 
    Note
     testparm in samba 3 behaves differently from 2.2.x: used
-without the "-v" switch it only shows you the settings actually
+without the "-v" switch it only shows you the settings actually
 written into ! To see the complete
-configuration used, add the "-v" parameter to testparm.

    A little Experiment to warn you

    +configuration used, add the "-v" parameter to testparm.

    A little Experiment to warn you

    Should you need to troubleshoot at any stage, please always come back -to this point first and verify if "testparm" shows the parameters you +to this point first and verify if "testparm" shows the parameters you expect! To give you an example from personal experience as a warning, -try to just "comment out" the load printers" +try to just "comment out" the load printers" parameter. If your 2.2.x system behaves like mine, you'll see this: 

    -root# grep "load printers" /etc/samba/smb.conf
+root# grep "load printers" /etc/samba/smb.conf
  #      load printers = Yes
  # This setting is commented ooouuuuut!!
  
-root# testparm -v /etc/samba/smb.conf | egrep "(load printers)"
+root# testparm -v /etc/samba/smb.conf | egrep "(load printers)"
         load printers = Yes

    @@ -5979,20 +5977,20 @@ prevent Samba from publishing my printers, it still did! Oh Boy -- it cost me quite some time to find out the reason. But I am not fooled any more... at least not by this ;-) 

    -root# grep -A1 "load printers" /etc/samba/smb.conf
+root# grep -A1 "load printers" /etc/samba/smb.conf
         load printers = No
         # This setting is what I mean!!
  #      load printers = Yes
         # This setting is commented ooouuuuut!!
 
-root# testparm -v smb.conf.simpleprinting | egrep "(load printers)"
+root# testparm -v smb.conf.simpleprinting | egrep "(load printers)"
         load printers = No

    Only when setting the parameter explicitly to -"load printers = No" +"load printers = No" would Samba recognize my intentions. So my strong advice is: -

    • Never rely on "commented out" parameters!

    • Always set it up explicitly as you intend it to +

      • Never rely on "commented out" parameters!

      • Always set it up explicitly as you intend it to behave.

      • Use testparm to uncover hidden settings which might not reflect your intentions.

      You can have a working Samba print configuration with this @@ -6016,8 +6014,8 @@ ask testparm what the Samba print configuration would be, if you used this minimalistic file as your real : 

      -root# testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
- Processing section "[printers]"
+root# testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
+ Processing section "[printers]"
  WARNING: [printers] service MUST be printable!
  No path in service printers - using /tmp
 
@@ -6062,11 +6060,11 @@ comment sign at the front). At first I regarded this as a bug in my
 Samba version(s). But the man page states: “Internal whitespace
 in a parameter value is retained verbatim.” This means that a
 line consisting of, for example,
-
      # This defines LPRng as the printing system"
      printing = lprng
      
-will regard the whole of the string after the "="
+
      # This defines LPRng as the printing system"
      printing = lprng
      
+will regard the whole of the string after the "="
 sign as the value you want to define. And this is an invalid value
 that will be ignored, and a default value used instead.]
-

    Extended Sample Configuration to Print

    +

    Extended Sample Configuration to Print

    In the extended BSD configuration example we show a more verbose example configuration for print related settings in BSD-printing style environment . Below is a discussion and explanation of the various parameters. We chose to use BSD-style @@ -6085,32 +6083,32 @@ default, because these have been compiled in. To see all settings, let root use the testparm utility. testparm also gives warnings if you have mis-configured certain things.. -

    Detailed Explanation of the Example's Settings

    +

    Detailed Explanation of the Example's Settings

    Following is a discussion of the settings from above shown example. -

    The [global] Section

    +

    The [global] Section

    The [global] section is one of 4 special sections (along with [[homes], [printers] and [print$]...) It contains all parameters which apply to the server as a whole. It is the place for parameters which -have only a "global" meaning. It may also contain service level +have only a "global" meaning. It may also contain service level parameters which then define default settings for all other sections and shares. This way you can simplify the configuration and avoid setting the same value repeatedly. (Within each individual -section or share you may however override these globally set "share -level" settings and specify other values). -

    printing = bsd

    this causes Samba to use default print commands +section or share you may however override these globally set "share +level" settings and specify other values). +

    printing = bsd

    this causes Samba to use default print commands applicable for the BSD (a.k.a. RFC 1179 style or LPR/LPD) printing -system. In general, the "printing" parameter informs Samba about the +system. In general, the "printing" parameter informs Samba about the print subsystem it should expect. Samba supports CUPS, LPD, LPRNG, SYSV, HPUX, AIX, QNX and PLP. Each of these systems defaults to a -different print command (and other queue control -commands).

    Caution

    The printing parameter is +different print command (and other queue control +commands).

    Caution

    The printing parameter is normally a service level parameter. Since it is included here in the [global] section, it will take effect for all printer shares that are not defined differently. Samba 3 no longer -supports the SOFTQ printing system.

    load printers = yes

    this tells Samba to create automatically all -available printer shares. "Available" printer shares are discovered by +supports the SOFTQ printing system.

    load printers = yes

    this tells Samba to create automatically all +available printer shares. "Available" printer shares are discovered by scanning the printcap file. All created printer shares are also loaded for browsing. If you use this parameter, you do not need to specify separate shares for each printer. Each automatically created printer @@ -6118,7 +6116,7 @@ share will clone the configuration options found in the [printers] section. (A load printers = no setting will allow you to specify each UNIX printer you want to share separately, leaving out some you don't want to be -publicly visible and available).

    show add printer wizard = yes

    this setting is normally +publicly visible and available).

    show add printer wizard = yes

    this setting is normally enabled by default (even if the parameter is not written into the ). It makes the Add Printer Wizard icon show up in the Printers folder of the Samba host's @@ -6129,38 +6127,38 @@ will not suffice!). The Add Printer Wizard lets you upload printer drivers to the [print$] share and associate it with a printer (if the respective queue exists there before the action), or exchange a printer's driver against any other previously -uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs +uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client submit a job which exceeds this number, a “no more space available on server” type of error message will be returned by -Samba to the client. A setting of "0" (the default) means there is +Samba to the client. A setting of "0" (the default) means there is no limit at all! -

    printcap name = /etc/printcap

    this tells Samba where to look for a list of +

    printcap name = /etc/printcap

    this tells Samba where to look for a list of available printer names. (If you use CUPS, make sure that a printcap -file is written: this is controlled by the "Printcap" directive of +file is written: this is controlled by the "Printcap" directive of cupsd.conf). -

    printer admin = @ntadmin

    members of the ntadmin group should be able to add -drivers and set printer properties ("ntadmin" is only an example name, +

    printer admin = @ntadmin

    members of the ntadmin group should be able to add +drivers and set printer properties ("ntadmin" is only an example name, it needs to be a valid UNIX group name); root is implicitly always a -printer admin. The "@" sign precedes group names in +printer admin. The "@" sign precedes group names in . A printer admin can do anything to printers via the remote administration interfaces offered by MS-RPC -(see below). Note that the printer admin +(see below). Note that the printer admin parameter is normally a share level parameter, so you may associate different groups to different printer shares in larger installations, -if you use the printer admin parameter on the +if you use the printer admin parameter on the share levels). -

    lpq cache time = 20

    this controls the cache time for the results of the +

    lpq cache time = 20

    this controls the cache time for the results of the lpq command. It prevents the lpq command being called too often and reduces load on a heavily used print server. -

    use client driver = no

    if set to yes, this setting only +

    use client driver = no

    if set to yes, this setting only takes effect for Win NT/2k/XP clients (and not for Win 95/98/ME). Its default value is No (or False). It must not be enabled on print shares (with a yes or true setting) which have valid drivers installed on the Samba server! For more detailed explanations see the man page of smb.conf. -

    The [printers] Section

    +

    The [printers] Section

    This is the second special section. If a section with this name appears in the smb.conf, users are able to connect to any printer specified in the Samba host's printcap file, @@ -6171,57 +6169,57 @@ minimal configuration. It is also a container for settings which should apply as default to all printers. (For more details see the smb.conf man page.) Settings inside this container must be share level parameters. -

    comment = All printers

    the comment is shown next to +

    comment = All printers

    the comment is shown next to the share if a client queries the server, either via Network Neighbourhood or with the net view command to list available shares. -

    printable = yes

    please note well, that the +

    printable = yes

    please note well, that the [printers] service must be declared as printable. If you specify otherwise, smbd will refuse to load at startup. This parameter allows connected clients to open, write to and submit spool files into the -directory specified with the path parameter for +directory specified with the path parameter for this service. It is used by Samba to differentiate printer shares from -file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool +file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool incoming print files. It must not be the same as the spool directory specified in the configuration of your UNIX print subsystem! The path would typically point to a directory -which is world writeable, with the "sticky" bit set to it. -

    browseable = no

    this is always set to no if -printable = yes. It makes the +which is world writeable, with the "sticky" bit set to it. +

    browseable = no

    this is always set to no if +printable = yes. It makes the [printer] share itself invisible in the list of available shares in a net view command or in the Explorer browse list. (Note that you will of course see the individual printers). -

    guest ok = yes

    +

    guest ok = yes

    if set to yes, then no password is required to connect to the printers service. Access will be granted with the -privileges of the guest account. On many systems the -guest account will map to a user named "nobody". This user is in the UNIX +privileges of the guest account. On many systems the +guest account will map to a user named "nobody". This user is in the UNIX passwd file with an empty password, but with no valid UNIX login. (Note: on some systems the guest account might not have the privilege to be able to print. Test this by logging in as your guest user using su - guest and run a system print command like -

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = yes. Since we have guest ok = yes, +

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = yes. Since we have guest ok = yes, it really doesn't need to be here! (This leads to the interesting question: “What, if I by accident have to contradictory settings for the same share?” The answer is: the last one encountered by -Samba wins. The "winner" is shown by testparm. Testparm doesn't +Samba wins. The "winner" is shown by testparm. Testparm doesn't complain about different settings of the same parameter for the same -share! You can test this by setting up multiple lines for the "guest -account" parameter with different usernames, and then run testparm to +share! You can test this by setting up multiple lines for the "guest +account" parameter with different usernames, and then run testparm to see which one is actually used by Samba.) -

    read only = yes

    this normally (for other types of shares) prevents +

    read only = yes

    this normally (for other types of shares) prevents users creating or modifying files in the service's directory. However, -in a "printable" service, it is always allowed to +in a "printable" service, it is always allowed to write to the directory (if user privileges allow the connection), but -only via print spooling operations. "Normal" write operations are not -allowed.

    writeable = no

    -synonym for read only = yes -

    Any [my_printer_name] Section

    +only via print spooling operations. "Normal" write operations are not +allowed.

    writeable = no

    +synonym for read only = yes +

    Any [my_printer_name] Section

    If a section appears in the , which is -tagged as printable = yes, Samba presents it as +tagged as printable = yes, Samba presents it as a printer share to its clients. Note, that Win95/98/ME clients may have problems with connecting or loading printer drivers if the share name has more than 8 characters! Also be very careful if you give a @@ -6230,65 +6228,65 @@ client's connection request to a certain sharename, Samba always tries to find file shares with that name first; if it finds one, it will connect to this and will never ultimately connect to a printer with the same name! -

    comment = Printer with Restricted Access

    the comment says it all. -

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to +

    comment = Printer with Restricted Access

    the comment says it all. +

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to another directory than the default. It is not a requirement to set it differently, but the option is available. -

    printer admin = kurt

    the printer admin definition is different for this +

    printer admin = kurt

    the printer admin definition is different for this explicitly defined printer share from the general [printers] share. It is not a requirement; we did it to show that it is possible if you want it. -

    browseable = yes

    we also made this printer browseable (so that the +

    browseable = yes

    we also made this printer browseable (so that the clients may conveniently find it when browsing the Network Neighbourhood). -

    printable = yes

    see explanation in last subsection. -

    writeable = no

    see explanation in last subsection. -

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control -by using the hosts allow and hosts deny parameters. Note, that +

    printable = yes

    see explanation in last subsection. +

    writeable = no

    see explanation in last subsection. +

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control +by using the hosts allow and hosts deny parameters. Note, that this is not by any means a safe bet. It is not a way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of access control -

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60

    all listed hosts are not allowed here (even if they -belong to the "allowed subnets"). As you can see, you could name IP +

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60

    all listed hosts are not allowed here (even if they +belong to the "allowed subnets"). As you can see, you could name IP addresses as well as NetBIOS hostnames here. -

    guest ok = no

    this printer is not open for the guest account! -

    Print Commands

    +

    guest ok = no

    this printer is not open for the guest account! +

    Print Commands

    In each section defining a printer (or in the [printers] section), a print command parameter may be defined. It sets a command to process the files which have been placed into the Samba print spool directory for that printer. (That spool directory was, if you -remember, set up with the path +remember, set up with the path parameter). Typically, this command will submit the spool file to the Samba host's print subsystem, using the suitable system print command. But there is no requirement that this needs to be the case. For debugging purposes or some other reason you may want to do -something completely different than "print" the file. An example is a +something completely different than "print" the file. An example is a command that just copies the print file to a temporary location for further investigation when you need to debug printing. If you craft your own print commands (or even develop print command shell scripts), make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise your hard disk may soon suffer from shortage of free space. -

    Default Print Commands for various UNIX Print Subsystems

    +

    Default Print Commands for various UNIX Print Subsystems

    You learned earlier on, that Samba in most cases uses its built-in settings for many parameters if it can not find an explicitly stated one in its configuration file. The same is true for the -print command. The default print command varies -depending on the printing parameter +print command. The default print command varies +depending on the printing parameter setting. In the commands listed below, you will notice some parameters of the form %X where X is p, s, J etc. These letters stand for -"printername", "spoolfile" and "job ID" respectively. They are +"printername", "spoolfile" and "job ID" respectively. They are explained in more detail further below. Here is an overview (excluding the special case of CUPS, which is discussed in the next chapter): -

    If this setting is active......this is used in lieu of an explicit command:
    printing = bsd|aix|lprng|plpprint command is lpr -r -P%p %s
    printing = sysv|hpuxprint command is lp -c -P%p %s; rm %s
    printing = qnxprint command is lp -r -P%p -s %s
    printing = bsd|aix|lprng|plplpq command is lpq -P%p
    printing = sysv|hpuxlpq command is lpstat -o%p
    printing = qnxlpq command is lpq -P%p
    printing = bsd|aix|lprng|plplprm command is lprm -P%p %j
    printing = sysv|hpuxlprm command is cancel %p-%j
    printing = qnxlprm command is cancel %p-%j
    printing = bsd|aix|lprng|plplppause command is lp -i %p-%j -H hold
    printing = sysv|hpuxlppause command (...is empty)
    printing = qnxlppause command (...is empty)
    printing = bsd|aix|lprng|plplpresume command is lp -i %p-%j -H resume
    printing = sysv|hpuxlpresume command (...is empty)
    printing = qnxlpresume command (...is empty)

    +

    If this setting is active......this is used in lieu of an explicit command:
    printing = bsd|aix|lprng|plpprint command is lpr -r -P%p %s
    printing = sysv|hpuxprint command is lp -c -P%p %s; rm %s
    printing = qnxprint command is lp -r -P%p -s %s
    printing = bsd|aix|lprng|plplpq command is lpq -P%p
    printing = sysv|hpuxlpq command is lpstat -o%p
    printing = qnxlpq command is lpq -P%p
    printing = bsd|aix|lprng|plplprm command is lprm -P%p %j
    printing = sysv|hpuxlprm command is cancel %p-%j
    printing = qnxlprm command is cancel %p-%j
    printing = bsd|aix|lprng|plplppause command is lp -i %p-%j -H hold
    printing = sysv|hpuxlppause command (...is empty)
    printing = qnxlppause command (...is empty)
    printing = bsd|aix|lprng|plplpresume command is lp -i %p-%j -H resume
    printing = sysv|hpuxlpresume command (...is empty)
    printing = qnxlpresume command (...is empty)

    We excluded the special CUPS case here, because it is discussed in the next chapter. Just a short summary. For printing = CUPS: If SAMBA is compiled against libcups, it uses the CUPS API to submit jobs, etc. (It is a good idea also to set -printcap = cups in case your +printcap = cups in case your cupsd.conf is set to write its autogenerated printcap file to an unusual place). Otherwise Samba maps to the System V printing commands with the -oraw option for printing, i.e. it uses @@ -6299,7 +6297,7 @@ manually set print command will be ignored! Having listed the above mappings here, you should note that there used to be a bug in recent 2.2.x versions which prevented the mapping from taking effect. It lead to the -"bsd|aix|lprng|plp" settings taking effect for all other systems, for +"bsd|aix|lprng|plp" settings taking effect for all other systems, for the most important commands (the print command, the lpq command and the lprm command). The lppause command and the @@ -6311,9 +6309,9 @@ check which command takes effect. Then check that this command is adequate and actually works for your installed print subsystem. It is always a good idea to explicitly set up your configuration files the way you want them to work and not rely on any built-in defaults. -

    Setting up your own Print Commands

    +

    Setting up your own Print Commands

    After a print job has finished spooling to a service, the -print command will be used by Samba via a +print command will be used by Samba via a system() call to process the spool file. Usually the command specified will submit the spool file to the host's printing subsystem. But there is no requirement at all that this must @@ -6324,7 +6322,7 @@ processed.

    There is no difficulty with using your own customized print commands with the traditional printing systems. However, if you don't wish to -"roll your own", you should be well informed about the default +"roll your own", you should be well informed about the default built-in commands that Samba uses for each printing subsystem (see the table above). In all the commands listed in the last paragraphs you see parameters of the form %X These are @@ -6354,7 +6352,7 @@ spool files will be created but not processed! And (most importantly): print files will not be removed, so they will start filling your Samba hard disk.

    -Note that printing may fail on some UNIXes from the "nobody" +Note that printing may fail on some UNIXes from the "nobody" account. If this happens, create an alternative guest account and supply it with the privilege to print. Set up this guest account in the [global] section with the guest @@ -6366,16 +6364,16 @@ expand the included environment variables as usual. (The syntax to include a UNIX environment variable $variable in or in the Samba print command is %$variable.) To give you a working -print command example, the following will log a +print command example, the following will log a print job to /tmp/print.log, print the file, then remove it. Note that ';' is the usual separator for commands in shell scripts:

    print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s

    You may have to vary your own command considerably from this example depending on how you normally print files on your system. The default -for the print command parameter varies depending on the setting of -the printing parameter. Another example is: -

    print command = /usr/local/samba/bin/myprintscript %p %s

    Innovations in Samba Printing since 2.2

    +for the print command parameter varies depending on the setting of +the printing parameter. Another example is: +

    print command = /usr/local/samba/bin/myprintscript %p %s

    Innovations in Samba Printing since 2.2

    Before version 2.2.0, Samba's print server support for Windows clients was limited to the level of LanMan printing calls. This is the same protocol level as Windows 9x PCs offer when @@ -6411,10 +6409,10 @@ rather they can print directly to any printer on another Windows NT host using MS-RPC. This of course assumes that the printing client has the necessary privileges on the remote host serving the printer. The default permissions assigned by Windows NT to a printer gives the -"Print" permissions to the well-known Everyone -group. (The older clients of type Win9x can only print to "shared" +"Print" permissions to the well-known Everyone +group. (The older clients of type Win9x can only print to "shared" printers). -

    Client Drivers on Samba Server for Point'n'Print

    +

    Client Drivers on Samba Server for Point'n'Print

    There is still confusion about what all this means: Is it or is it not a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients? The @@ -6447,12 +6445,12 @@ etc.).

    Please take additional note of the following fact: Samba does not use these uploaded drivers in any way to process spooled files. Drivers are utilized entirely by the clients, who -download and install them via the "Point'n'Print" mechanism supported +download and install them via the "Point'n'Print" mechanism supported by Samba. The clients use these drivers to generate print files in the format the printer (or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing system, which is responsible for all further processing, if needed. -

    The [printer$] Section is removed from Samba 3

    +

    The [printer$] Section is removed from Samba 3

    [print$] vs. [printer$] .  Versions of Samba prior to 2.2 made it possible to use a share @@ -6478,10 +6476,10 @@ access (in the context of its ACLs) in order to support printer driver down- and uploads. Don't fear -- this does not mean Windows 9x clients are thrown aside now. They can use Samba's [print$] share support just fine. -

    Creating the [print$] Share

    +

    Creating the [print$] Share

    In order to support the up- and downloading of printer driver files, you must first configure a file share named -[print$]. The "public" name of this share is +[print$]. The "public" name of this share is hard coded in Samba's internals (because it is hard coded in the MS Windows clients too). It cannot be renamed since Windows clients are programmed to search for a service of exactly this name if they want @@ -6492,25 +6490,25 @@ add the global parameters and create the [print$] file share (of course, some of the parameter values, such as 'path' are arbitrary and should be replaced with appropriate values for your site): -

    Example 18.3. [print\$] example

    [global]
    # members of the ntadmin group should be able to add drivers and set
    # printer properties. root is implicitly always a 'printer admin'.
    printer admin = @ntadmin
    ...
    [printers]
    ...
    [print$]
    comment = Printer Driver Download Area
    path = /etc/samba/drivers
    browseable = yes
    guest ok = yes
    read only = yes
    write list = @ntadmin, root

    +

    Example 18.3. [print\$] example

    [global]
    # members of the ntadmin group should be able to add drivers and set
    # printer properties. root is implicitly always a 'printer admin'.
    printer admin = @ntadmin
    ...
    [printers]
    ...
    [print$]
    comment = Printer Driver Download Area
    path = /etc/samba/drivers
    browseable = yes
    guest ok = yes
    read only = yes
    write list = @ntadmin, root

    Of course, you also need to ensure that the directory named by the -path parameter exists on the UNIX file system. -

    Parameters in the [print$] Section

    +path parameter exists on the UNIX file system. +

    Parameters in the [print$] Section

    [print$] is a special section in . It contains settings relevant to potential printer driver download and local installation by clients. -

    comment = Printer Driver +

    comment = Printer Driver Download Area

    the comment appears next to the share name if it is listed in a share list (usually Windows clients won't see it often but it will also appear up in a smbclient -L sambaserver - output).

    path = /etc/samba/printers

    this is the path to the location of the Windows + output).

    path = /etc/samba/printers

    this is the path to the location of the Windows driver file deposit from the UNIX point of -view.

    browseable = no

    this makes the [print$] share -"invisible" in Network Neighbourhood to clients. However, you can -still "mount" it from any client using the net use -g:\\sambaserver\print$ command in a "DOS box" or the -"Connect network drive" menu from Windows -Explorer.

    guest ok = yes

    this gives read only access to this share for all +view.

    browseable = no

    this makes the [print$] share +"invisible" in Network Neighbourhood to clients. However, you can +still "mount" it from any client using the net use +g:\\sambaserver\print$ command in a "DOS box" or the +"Connect network drive" menu from Windows +Explorer.

    guest ok = yes

    this gives read only access to this share for all guest users. Access may be used to download and install printer drivers on clients. The requirement for guest ok = yes depends upon how your site is configured. If users @@ -6523,28 +6521,28 @@ validated by the Domain Controller in order to logon to the Windows NT session), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share -for guest access. You'll probably want to add map to guest = Bad User in the +for guest access. You'll probably want to add map to guest = Bad User in the [global] section as well. Make sure you understand what this parameter does before using it. -

    read only = yes

    as we don't want everybody to upload driver files (or +

    read only = yes

    as we don't want everybody to upload driver files (or even change driver settings) we tagged this share as not -writeable.

    write list = @ntadmin,root

    since the [print$] was made -read only by the previous setting, we need to create a "write list" -also. UNIX groups (denoted with a leading "@" character) and users +writeable.

    write list = @ntadmin,root

    since the [print$] was made +read only by the previous setting, we need to create a "write list" +also. UNIX groups (denoted with a leading "@" character) and users listed here are allowed write access (as an exception to the general -public's "read-only" access), which they need to update files on the +public's "read-only" access), which they need to update files on the share. Normally you will want to only name administrative level user accounts in this setting. Check the file system permissions to make sure these accounts can copy files to the share. If this is a non-root account, then the account should also be mentioned in the global -printer admin parameter. See the +printer admin parameter. See the man page for more information on -configuring file shares.

    Subdirectory Structure in [print$]

    +configuring file shares.

    Subdirectory Structure in [print$]

    In order for a Windows NT print server to support the downloading of driver files by multiple client architectures, you must create several subdirectories within the [print$] service -(i.e. the UNIX directory named by the path +(i.e. the UNIX directory named by the path parameter). These correspond to each of the supported client architectures. Samba follows this model as well. Just like the name of the [print$] share itself, the subdirectories @@ -6556,11 +6554,11 @@ Therefore, create a directory tree below the to support. 

     [print$]--+--
-          |--W32X86           # serves drivers to "Windows NT x86"
-          |--WIN40            # serves drivers to "Windows 95/98"
-          |--W32ALPHA         # serves drivers to "Windows NT Alpha_AXP"
-          |--W32MIPS          # serves drivers to "Windows NT R4000"
-          |--W32PPC           # serves drivers to "Windows NT PowerPC"
+          |--W32X86           # serves drivers to "Windows NT x86"
+          |--WIN40            # serves drivers to "Windows 95/98"
+          |--W32ALPHA         # serves drivers to "Windows NT Alpha_AXP"
+          |--W32MIPS          # serves drivers to "Windows NT R4000"
+          |--W32PPC           # serves drivers to "Windows NT PowerPC"

    Required permissions

    In order to add a new driver to your Samba host, one of two conditions must hold true: @@ -6579,7 +6577,7 @@ client workstation. Open Network Neighbourhood or Once you have located the server, navigate to its Printers and Faxes folder. You should see an initial listing of printers that matches the printer shares defined on your Samba host. -

    Installing Drivers into [print$]

    +

    Installing Drivers into [print$]

    You have successfully created the [print$] share in ? And Samba has re-read its configuration? Good. But you are not yet ready to take off. The @@ -6597,7 +6595,7 @@ Properties and Add Printer Wizard

    The latter option is probably the easier one (even if the only entrance to this realm seems a little bit weird at first). -

    Setting Drivers for existing Printers with a Client GUI

    +

    Setting Drivers for existing Printers with a Client GUI

    The initial listing of printers in the Samba host's Printers folder accessed from a client's Explorer will have no real printer driver assigned to them. By default @@ -6632,18 +6630,18 @@ Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure your connection is in fact setup as a user with -printer admin privileges (if in doubt, use +printer admin privileges (if in doubt, use smbstatus to check for this). If you wish to install printer drivers for client operating systems other than Windows NT x86, you will need to use the Sharing tab of the printer properties dialog.

    Assuming you have connected with an administrative (or root) account -(as named by the printer admin parameter), +(as named by the printer admin parameter), you will also be able to modify other printer properties such as ACLs and default device settings using this dialog. For the default device settings, please consider the advice given further below. -

    Setting Drivers for existing Printers with +

    Setting Drivers for existing Printers with rpcclient

    The second way to install printer drivers into [print$] and set them up in a valid way can be @@ -6658,7 +6656,7 @@ time with the setdriver subcommand.

    We will provide detailed hints for each of these steps in the next few paragraphs. -

    Identifying the Driver Files

    +

    Identifying the Driver Files

    To find out about the driver files, you have two options: you could investigate the driver CD which comes with your printer. Study the *.inf file on the CD, if it is contained. This @@ -6707,8 +6705,8 @@ printers and drivers. Note the different quotes used to overcome the different spaces in between words: 

     root# rpcclient -U'Danka%xxxx' -c \
-	'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
-cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
+	'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
+cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
 
 [Windows NT x86]
 Printer Driver Info 3:
@@ -6751,17 +6749,17 @@ can also host the Win9x drivers, even if itself runs on Windows NT,
 Since the [print$] share is usually accessible
 through the Network Neighbourhood, you can also use the UNC notation
 from Windows Explorer to poke at it. The Win9x driver files will end
-up in subdirectory "0" of the "WIN40" directory. The full path to
+up in subdirectory "0" of the "WIN40" directory. The full path to
 access them will be
 \\WINDOWSHOST\print$\WIN40\0\.
 
    Note
     more recent drivers on Windows 2000 and Windows XP are
-installed into the "3" subdirectory instead of the "2". The version 2
+installed into the "3" subdirectory instead of the "2". The version 2
 of drivers, as used in Windows NT, were running in Kernel Mode.
 Windows 2000 changed this. While it still can use the Kernel Mode
 drivers (if this is enabled by the Admin), its native mode for printer
 drivers is User Mode execution. This requires drivers designed for
-this. These type of drivers install into the "3" subdirectory.
-

    Collecting the Driver Files from a Windows Host's +this. These type of drivers install into the "3" subdirectory. +

    Collecting the Driver Files from a Windows Host's [print$] Share

    Now we need to collect all the driver files we identified. in our previous step. Where do we get them from? Well, why not retrieve them @@ -6797,7 +6795,7 @@ files for these architectures are in the WIN40/0/ subdir. Once we are complete, we can run smbclient ... put to store the collected files on the Samba server's [print$] share. -

    Depositing the Driver Files into [print$]

    +

    Depositing the Driver Files into [print$]

    So, now we are going to put the driver files into the [print$] share. Remember, the UNIX path to this share has been defined previously in your @@ -6808,9 +6806,9 @@ your [print$] share maps to the UNIX path go here:

    • for all Windows NT, 2000 and XP clients into /etc/samba/drivers/W32X86/ but -*not*(yet) into the "2" subdir!

    • for all Windows 95, 98 and ME clients into +*not*(yet) into the "2" subdir!

    • for all Windows 95, 98 and ME clients into /etc/samba/drivers/WIN40/ -- but *not* -(yet) into the "0" subdir!

    +(yet) into the "0" subdir!

    We again use smbclient to transfer the driver files across the network. We specify the same files and paths as were leaked to us by running getdriver against the original @@ -6850,15 +6848,15 @@ putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF

    Phewww -- that was a lot of typing! Most drivers are a lot smaller -- many only having 3 generic PostScript driver files plus 1 PPD. Note, -that while we did retrieve the files from the "2" subdirectory of the -"W32X86" directory from the Windows box, we don't +that while we did retrieve the files from the "2" subdirectory of the +"W32X86" directory from the Windows box, we don't put them (for now) in this same subdirectory of the Samba box! This re-location will automatically be done by the adddriver command which we will run shortly (and don't forget to also put the files for the Win95/98/ME architecture into the WIN40/ subdirectory should you need them). -

    Check if the Driver Files are there (with smbclient)

    +

    Check if the Driver Files are there (with smbclient)

    For now we verify that our files are there. This can be done with smbclient too (but of course you can log in via SSH also and do this through a standard UNIX shell access too): @@ -6911,7 +6909,7 @@ Point'n'Print. The reason is: Samba doesn't know yet that these files are something special, namely printer driver files and it doesn't know yet to which print queue(s) these driver files belong. -

    Running rpcclient with +

    Running rpcclient with adddriver

    So, next you must tell Samba about the special category of the files you just uploaded into the [print$] share. This @@ -6920,8 +6918,8 @@ prompt Samba to register the driver files into its internal TDB database files. The following command and its output has been edited, again, for readability: 

    -		root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
-"dm9110:HDNIS01_de.DLL: \
+		root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL: \
 Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
@@ -6929,12 +6927,12 @@ Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
  HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
  Hddm91c1_de_reg.HLP' SAMBA-CUPS
 
-cmd = adddriver "Windows NT x86" \
-"dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
+cmd = adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
  HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
- HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
 
 Printer Driver dm9110 successfully installed.
 
@@ -6948,7 +6946,7 @@ files successfully, but render the driver unworkable. So take care!
 Hints about the syntax of the adddriver command are in the man
 page. The CUPS printing chapter of this HOWTO collection provides a
 more detailed description, if you should need it.
-

    Check how Driver Files have been moved after +

    Check how Driver Files have been moved after adddriver finished

    One indication for Samba's recognition of the files as driver files is the successfully installed message. @@ -6996,7 +6994,7 @@ subdirectory. You can check this again with

    Another verification is that the timestamp of the printing TDB files is now updated (and possibly their filesize has increased). -

    Check if the Driver is recognized by Samba

    +

    Check if the Driver is recognized by Samba

    Now the driver should be registered with Samba. We can easily verify this, and will do so in a moment. However, this driver is not yet associated with a particular @@ -7021,13 +7019,13 @@ right-click the white background (with no printer highlighted). Select Drivers tab you will see the new driver listed now. This view enables you to also inspect the list of files belonging to that driver (this doesn't work on Windows NT, but only on -Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" +Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" tab).. An alternative, much quicker method for Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the name to your Samba server instead of SAMBA-CUPS):

    rundll32 printui.dll,PrintUIEntry /s /t2 /n\\SAMBA-CUPS

  • from a UNIX prompt run this command (or a variant thereof), where SAMBA-CUPS is the name of the Samba -host and "xxxx" represents the actual Samba password assigned to root: +host and "xxxx" represents the actual Samba password assigned to root:

    rpcclient -U'root%xxxx' -c 'enumdrivers' SAMBA-CUPS

    You will see a listing of all drivers Samba knows about. Your new one should be amongst them. But it is only listed under the [Windows NT @@ -7040,14 +7038,14 @@ time. Our new driver only shows up for Windows NT 4.0 or 2000. To have it present for Windows 95, 98 and ME you'll have to repeat the whole procedure with the WIN40 architecture and subdirectory. -

    • A side note: you are not bound to specific driver names

    +

    A side note: you are not bound to specific driver names

    You can name the driver as you like. If you repeat the adddriver step, with the same files as before, but with a different driver name, it will work the same: 

     root# rpcclient -Uroot%xxxx                                        \
-  -c 'adddriver "Windows NT x86"                     \
-  "myphantasydrivername:HDNIS01_de.DLL:              \
+  -c 'adddriver "Windows NT x86"                     \
+  "myphantasydrivername:HDNIS01_de.DLL:              \
   Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
   NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
   Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
@@ -7055,12 +7053,12 @@ with a different driver name, it will work the same:
   HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
   
 
- cmd = adddriver "Windows NT x86" 
-                 "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
+ cmd = adddriver "Windows NT x86" 
+                 "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
                   HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,           \
                   Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,                    \
                   Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,                  \
-                  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+                  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
 
  Printer Driver myphantasydrivername successfully installed.
 
@@ -7069,16 +7067,16 @@ You will also be able to bind that driver to any print queue (however,
 you are responsible yourself that you associate drivers to queues
 which make sense to the target printer). Note, that you can't run the
 rpcclient adddriver command
-repeatedly. Each run "consumes" the files you had put into the
+repeatedly. Each run "consumes" the files you had put into the
 [print$] share by moving them into the
 respective subdirectories. So you must precede an
 smbclient ... put command before each
-rpcclient ...  adddriver" command.
-

    Running rpcclient with +rpcclient ... adddriver" command. +

    Running rpcclient with setdriver

    Samba still needs to know which printer's driver this is. It needs to create a mapping of the driver to a printer, and -store this info in its "memory", the TDB files. The rpcclient +store this info in its "memory", the TDB files. The rpcclient setdriver command achieves exactly this: 

     root# rpcclient -U'root%xxxx' -c 'setdriver dm9110 myphantasydrivername' SAMBA-CUPS
@@ -7094,8 +7092,8 @@ name I intended:

    The syntax of the command is rpcclient -U'root%sambapassword' -c 'setdriver -"printername" -"drivername' +"printername" +"drivername' SAMBA-Hostname . -- Now we have done *most* of the work. But not yet all....

    Note

    @@ -7104,25 +7102,25 @@ known to Samba already. A bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba, or at least send a HUP signal to all running smbd processes to work around this: -kill -HUP `pidof smbd`.

    Client Driver Install Procedure

    +kill -HUP `pidof smbd`.

    Client Driver Install Procedure

    A famous philosopher said once: “The Proof of the Pudding lies in the Eating”. The proof for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is not as straightforward as it may seem. Read on. -

    The first Client Driver Installation

    +

    The first Client Driver Installation

    Especially important is the installation onto the first client PC (for each architectural platform separately). Once this is done correctly, all further clients are easy to setup and shouldn't need further attention. What follows is a description for the recommended first procedure. You work now from a client workstation. First you should guarantee that your connection is not unwittingly mapped to -bad user "nobody". In a DOS box type: +bad user "nobody". In a DOS box type:

    net use \\SAMBA-SERVER\print$ /user:root

    Replace root, if needed, by another valid printer admin user as given in the definition. Should you already be connected as a different user, you'll get an error message. There is no easy way to get rid of that connection, because -Windows doesn't seem to know a concept of "logging off" from a share +Windows doesn't seem to know a concept of "logging off" from a share connection (don't confuse this with logging off from the local workstation; that is a different matter). You can try to close all Windows file explorer and Internet Explorer @@ -7143,16 +7141,16 @@ samba-server) should now have appeared in your -- Printers and Faxes).

    Most likely you are now tempted to try and print a test page. After -all, you now can open the printer properties and on the "General" tab, +all, you now can open the printer properties and on the "General" tab, there is a button offering to do just that. But chances are that you get an error message saying Unable to print Test Page. The reason might be that there is not yet a -valid Device Mode set for the driver, or that the "Printer Driver -Data" set is still incomplete. +valid Device Mode set for the driver, or that the "Printer Driver +Data" set is still incomplete.

    -You must now make sure that a valid "Device Mode" is set for the +You must now make sure that a valid "Device Mode" is set for the driver. Don't fear -- we will explain now what that means. -

    IMPORTANT! Setting Device Modes on new Printers

    +

    IMPORTANT! Setting Device Modes on new Printers

    In order for a printer to be truly usable by a Windows NT/2K/XP client, it must possess:

    • a valid Device Mode generated by @@ -7179,7 +7177,7 @@ This can be achieved by accessing the drivers remotely from an NT (or 2k/XP) client, as is discussed in the next paragraphs.

      Be aware, that a valid Device Mode can only be initiated by a -printer admin, or root (the reason should be +printer admin, or root (the reason should be obvious). Device Modes can only correctly be set by executing the printer driver program itself. Since Samba can not execute this Win32 platform driver code, it sets this field initially to NULL (which is @@ -7189,9 +7187,9 @@ are uploaded to the [print$] share with the help of the APW or rpcclient.

      The generation and setting of a first valid Device Mode however -requires some "tickling" from a client, to set it on the Samba +requires some "tickling" from a client, to set it on the Samba server. The easiest means of doing so is to simply change the page -orientation on the server's printer. This "executes" enough of the +orientation on the server's printer. This "executes" enough of the printer driver program on the client for the desired effect to happen, and feeds back the new Device Mode to our Samba server. You can use the native Windows NT/2K/XP printer properties page from a Window client @@ -7203,7 +7201,7 @@ followed the last section's description)

    • At the bottom of the con Connect... entry further above, you need to click that one first to achieve the driver installation as shown in the last section)

    • Go to the Advanced tab; click on -Printing Defaults...

    • Change the "Portrait" page setting to "Landscape" (and +Printing Defaults...

    • Change the "Portrait" page setting to "Landscape" (and back)

    • (Oh, and make sure to apply changes between swapping the page orientation to cause the change to actually take effect...).

    • While you're at it, you may optionally also want to @@ -7224,7 +7222,7 @@ properties. Others may crash the client's spooler service. So use this parameter with caution. It is always better to have the client generate a valid device mode for the printer and store it on the server for you. -

    Further Client Driver Install Procedures

    +

    Further Client Driver Install Procedures

    Every further driver may be done by any user, along the lines described above: Browse network, open printers folder on Samba server, right-click printer and choose Connect.... Once @@ -7244,12 +7242,12 @@ rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2 You can enter the commands either inside a DOS box window or in the Run command... field from the Start menu. -

    Always make first Client Connection as root or "printer admin"

    +

    Always make first Client Connection as root or "printer admin"

    After you installed the driver on the Samba server (in its [print$] share, you should always make sure that your first client installation completes correctly. Make it a habit for yourself to build that the very first connection from a client as -printer admin. This is to make sure that: +printer admin. This is to make sure that:

    • a first valid Device Mode is really initialized (see above for more explanation details), and that

    • the default print settings of your printer for all @@ -7264,32 +7262,32 @@ set to Letter, when you are all using To connect as root to a Samba printer, try this command from a Windows 2K/XP DOS box command prompt: 

      -C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
-	\\SAMBA-SERVER\printername"
+C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
+	\\SAMBA-SERVER\printername"

      You will be prompted for root's Samba-password; type it, wait a few seconds, click on Printing Defaults... and proceed to set the job options as should be used as defaults by all clients. Alternatively, instead of root you can name one other member -of the printer admin from the setting. +of the printer admin from the setting.

      Now all the other users downloading and installing the driver the same way (called Point'n'Print) will have the same defaults set for them. If you miss this step you'll get a lot of helpdesk calls from your users. But maybe you like to talk to people.... ;-) -

    Other Gotchas

    +

    Other Gotchas

    Your driver is installed. It is ready for Point'n'Print installation by the clients now. You may have tried to download and use it onto your first client machine now. But wait... let's make you acquainted first with a few tips and tricks you may find useful. For -example, suppose you didn't manage to "set the defaults" on the +example, suppose you didn't manage to "set the defaults" on the printer, as advised in the preceding paragraphs? And your users complain about various issues (such as “We need to set the paper size for each job from Letter to A4 and it won't store it!”) -

    Setting Default Print Options for the Client Drivers

    +

    Setting Default Print Options for the Client Drivers

    The last sentence might be viewed with mixed feelings by some users and admins. They have struggled for hours and hours and couldn't arrive at a point were their settings seemed to be saved. It is not their @@ -7297,8 +7295,8 @@ fault. The confusing thing is this: in the multi-tabbed dialog that pops up when you right-click the printer name and select Properties..., you can arrive at two identically looking dialogs, each claiming that they help you to set printer options, -in three different ways. Here is the definite answer to the "Samba -Default Driver Setting FAQ": +in three different ways. Here is the definite answer to the "Samba +Default Driver Setting FAQ":

    “I can't set and save default print options for all users on Win2K/XP! Why not?”  How are you doing it? I bet the wrong way.... (it is not very @@ -7310,7 +7308,7 @@ dialogs look the same. Only one of them Administrator to do this for all users. Here is how I reproduce it in on XP Professional: -

    1. The first "wrong" way: +

      1. The first "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer @@ -7318,7 +7316,7 @@ folder.

        3. Right-click on the printer select in context menu Printing Preferences...

        4. Look at this dialog closely and remember what it looks like.

        -

      2. The second "wrong" way: +

      3. The second "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer (remoteprinter on @@ -7327,16 +7325,16 @@ cupshost) and select in the context menu tab

        3. Click on the button Printing Preferences...

        4. A new dialog opens. Keep this dialog open and go back to the parent dialog.

        -

      4. The third, the "correct" way: (should you do +

      5. The third, the "correct" way: (should you do this from the beginning, just carry out steps 1. and 2. from second -"way" above) +"way" above)

        1. Click on the Advanced -tab. (Hmmm... if everything is "Grayed Out", then you are not logged +tab. (Hmmm... if everything is "Grayed Out", then you are not logged in as a user with enough privileges).

        2. Click on the Printing Defaults... button.

        3. On any of the two new tabs, click on the Advanced... button.

        4. A new dialog opens. Compare this one to the other, -identical looking one from "B.5" or A.3".

        +identical looking one from "B.5" or A.3".

    Do you see any difference in the two settings dialogs? I don't @@ -7344,24 +7342,24 @@ either. However, only the last one, which you arrived at with steps C.1.-6. will permanently save any settings which will then become the defaults for new users. If you want all clients to have the same defaults, you need to conduct these steps as administrator -(printer admin in ) +(printer admin in ) before a client downloads the driver (the clients can later set their own per-user defaults by following the procedures A. or B. above...). (This is new: Windows 2000 and Windows XP allow per-user default settings and the ones the administrator gives them, before they set up their own). -The "parents" of the identically looking dialogs have a slight +The "parents" of the identically looking dialogs have a slight difference in their window names: one is called Default Print Values for Printer Foo on Server -Bar" (which is the one you need) and the other is -called "Print Settings for Printer Foo on Server -Bar". The last one is the one you arrive at when you +Bar" (which is the one you need) and the other is +called "Print Settings for Printer Foo on Server +Bar". The last one is the one you arrive at when you right-click on the printer and select Print Settings.... This is the one what you were taught to use back in the days of Windows NT! So it is only natural to try the same way with Win2k or WinXP. You wouldn't dream -that there is now a different "clicking path" to arrive at an +that there is now a different "clicking path" to arrive at an identically looking, but functionally different dialog to set defaults for all users!

    Tip

    Try (on Win2000 and WinXP) to run this command (as a user @@ -7376,9 +7374,9 @@ rundll32 printui.dll,PrintUIEntry /p /t0 /n\\SAMBA-SE

    to see the tab with the Printing Preferences... button (the one which doesn't set system-wide defaults). You can -start the commands from inside a DOS box" or from the Start +start the commands from inside a DOS box" or from the Start -- Run... menu. -

    Supporting large Numbers of Printers

    +

    Supporting large Numbers of Printers

    One issue that has arisen during the recent development phase of Samba is the need to support driver downloads for 100's of printers. Using Windows NT APW here is somewhat awkward (to say the least). If you @@ -7429,7 +7427,7 @@ following is an example of how this could be accomplished: 

     root# rpcclient SAMBA-CUPS -U root%secret -c \
-  'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
+  'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
  cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
  Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).

    @@ -7462,13 +7460,13 @@ following is an example of how this could be accomplished: [....]

    It may be not easy to recognize: but the first call to -enumprinters showed the "dm9110" printer with an +enumprinters showed the "dm9110" printer with an empty string where the driver should have been listed (between the 2 -commas in the "description" field). After the +commas in the "description" field). After the setdriver command succeeded, all is well. (The CUPS Printing chapter has more info about the installation of printer drivers with the help of rpcclient). -

    Adding new Printers with the Windows NT APW

    +

    Adding new Printers with the Windows NT APW

    By default, Samba exhibits all printer shares defined in smb.conf in the Printers... folder. Also located in this folder @@ -7476,27 +7474,27 @@ is the Windows NT Add Printer Wizard icon. The APW will be shown only if:

    • ...the connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative -privileges (i.e. root or printer admin). +privileges (i.e. root or printer admin).

      Tip

      Try this from a Windows 2K/XP DOS box command prompt:

      runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\SAMBA-SERVER\printersharename

      and click on Printing Preferences...

    • ... contains the setting -show add printer wizard = yes (the +show add printer wizard = yes (the default).

    The APW can do various things:

    • upload a new driver to the Samba [print$] share;

    • associate an uploaded driver with an existing (but -still "driverless") print queue;

    • exchange the currently used driver for an existing +still "driverless") print queue;

    • exchange the currently used driver for an existing print queue with one that has been uploaded before;

    • add an entirely new printer to the Samba host (only in -conjunction with a working add printer command; -a corresponding delete printer command for +conjunction with a working add printer command; +a corresponding delete printer command for removing entries from the Printers... folder may be provided too)

    The last one (add a new printer) requires more effort than the previous ones. In order to use the APW to successfully add a printer -to a Samba server, the add printer command must +to a Samba server, the add printer command must have a defined value. The program hook must successfully add the printer to the UNIX print system (i.e. to /etc/printcap, @@ -7508,11 +7506,11 @@ exist, smbd will execute the add printer command and reparse to the to attempt to locate the new printer share. If the share is still not defined, an error of Access Denied is -returned to the client. Note that the add printer command is executed under the context of the connected -user, not necessarily a root account. A map to guest = bad user may have connected you unwittingly under the wrong +returned to the client. Note that the add printer command is executed under the context of the connected +user, not necessarily a root account. A map to guest = bad user may have connected you unwittingly under the wrong privilege; you should check it by using the smbstatus command. -

    Weird Error Message Cannot connect under a +

    Weird Error Message Cannot connect under a different Name

    Once you are connected with the wrong credentials, there is no means to reverse the situation other than to close all Explorer windows, and @@ -7522,7 +7520,7 @@ perhaps reboot. connections to a server or a shared resource by the same user utilizing the several user names are not allowed. Disconnect all previous connections to the server, resp. the shared resource, and try -again.

  • Every attempt to "connect a network drive" to +again.

  • Every attempt to "connect a network drive" to \\SAMBASERVER\\print$ to z: is countered by the pertinacious message. This network folder is currently connected under different credentials (username and password). @@ -7542,20 +7540,20 @@ message. You close all Explorer Windows and start it again. You try to connect - and this times it works! Windows seems to cache connection info somewhere and doesn't keep it up to date (if you are unlucky you might need to reboot to get rid of the error message). -

    • Be careful when assembling Driver Files

    +

    Be careful when assembling Driver Files

    You need to be very careful when you take notes about the files and belonging to a particular driver. Don't confuse the files for driver -version "0" (for Win95/98/ME, going into -[print$]/WIN/0/), driver version "2" (Kernel Mode +version "0" (for Win95/98/ME, going into +[print$]/WIN/0/), driver version "2" (Kernel Mode driver for WinNT, going into [print$]/W32X86/2/ may be used on Win2K/XP too), and driver version -"3" (non-Kernel Mode driver going into +"3" (non-Kernel Mode driver going into [print$]/W32X86/3/ can not be used on WinNT). Very often these different driver versions contain files carrying the same name; but still the files are very different! Also, if you look at them from the Windows Explorer (they reside in %WINDOWS%\system32\spool\drivers\W32X86\) you -will probably see names in capital letters, while an "enumdrivers" +will probably see names in capital letters, while an "enumdrivers" command from Samba would show mixed or lower case letters. So it is easy to confuse them. If you install them manually using rpcclient and subcommands, you may even succeed @@ -7628,7 +7626,7 @@ reasons: Defaultdatatype: []

    -If we write the "version 2" files and the "version 3" files +If we write the "version 2" files and the "version 3" files into different text files and compare the result, we see this picture: 

    @@ -7666,7 +7664,7 @@ comparison:
 
     root# for i in cns3g.hlp cns3gui.dll cns3g.dll; do                  \
            smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \
-           -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i";      \
+           -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i";      \
 		   done
 
   CNS3G.HLP               A   122981  Thu May 30 02:31:00 2002
@@ -7683,35 +7681,35 @@ In my example were even more differences than shown here.  Conclusion:
 you must be very careful to select the correct driver files for each
 driver version. Don't rely on the names alone. Don't interchange files
 belonging to different driver versions.
-

    Samba and Printer Ports

    +

    Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc. Samba must also support the concept of ports associated with a printer. By -default, only one printer port, named "Samba Printer Port", exists on -a system. Samba does not really need such a "port" in order to print; +default, only one printer port, named "Samba Printer Port", exists on +a system. Samba does not really need such a "port" in order to print; it rather is a requirement of Windows clients. They insist on being told about an available port when they request this info, otherwise they throw an error message at you. So Samba fakes the port information to keep the Windows clients happy.

    -Note that Samba does not support the concept of "Printer Pooling" +Note that Samba does not support the concept of "Printer Pooling" internally either. Printer Pooling assigns a logical printer to multiple ports as a form of load balancing or fail over.

    If you require that multiple ports be defined for some reason or another (“My users and my Boss should not know that they are working with Samba”), possesses a -enumports command which can be used to define +enumports command which can be used to define an external program that generates a listing of ports on a system. -

    Avoiding the most common Misconfigurations of the Client Driver

    +

    Avoiding the most common Misconfigurations of the Client Driver

    So - printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, which don't look good at all. Some jobs print fast, and some are dead-slow. We can't cover it all; but we want to encourage you to read -the little paragraph about "Avoiding the wrong PostScript Driver -Settings" in the CUPS Printing part of this document. -

    The Imprints Toolset

    +the little paragraph about "Avoiding the wrong PostScript Driver +Settings" in the CUPS Printing part of this document. +

    The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please refer to the Imprints web site @@ -7728,20 +7726,20 @@ coordinate your efforts on the samba-technical mailing list. The toolset is still in usable form; but only for a series of older printer models, where there are prepared packages to use. Packages for more up to date print devices are needed if Imprints should have a -future.

    What is Imprints?

    +future.

    What is Imprints?

    Imprints is a collection of tools for supporting these goals:

    • Providing a central repository information regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating the Imprints printer driver packages.

    • Providing an installation client which will obtain printer drivers from a central internet (or intranet) Imprints Server repository and install them on remote Samba and Windows NT4 print -servers.

    Creating Printer Driver Packages

    +servers.

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included with the Samba distribution for more information). In short, an Imprints driver package is a gzipped tarball containing the driver files, related INF files, and a control file needed by the installation client. -

    The Imprints Server

    +

    The Imprints Server

    The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer entry in the database has an associated URL for the actual downloading of the package. Each @@ -7749,7 +7747,7 @@ package is digitally signed via GnuPG which can be used to verify that package downloaded is actually the one referred in the Imprints database. It is strongly recommended that this security check not be disabled. -

    The Installation Client

    +

    The Installation Client

    More information regarding the Imprints installation client is available in the Imprints-Client-HOWTO.ps file included with the imprints source package. @@ -7770,9 +7768,9 @@ wrapped around smbclient and rpcclient

  • rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer

    • One of the problems encountered when implementing the Imprints tool set was the name space issues between various supported client -architectures. For example, Windows NT includes a driver named "Apple -LaserWriter II NTX v51.8" and Windows 95 calls its version of this -driver "Apple LaserWriter II NTX" +architectures. For example, Windows NT includes a driver named "Apple +LaserWriter II NTX v51.8" and Windows 95 calls its version of this +driver "Apple LaserWriter II NTX"

    The problem is how to know what client drivers have been uploaded for a printer. An astute reader will remember that the Windows NT Printer @@ -7790,7 +7788,7 @@ if is has not already been installed? The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that NT driver is installed first. -

    Add Network Printers at Logon without User Interaction

    +

    Add Network Printers at Logon without User Interaction

    The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients: How to Add Printers with No User Interaction in Windows 2000. ( http://support.microsoft.com/default.aspx?scid=kb;en-us;189105 @@ -7800,7 +7798,7 @@ The ideas sketched out below are inspired by this article. It describes a commandline method which can be applied to install network and local printers and their drivers. This is most useful if integrated in Logon Scripts. You can see what options are -available by typing in a command prompt ("DOS box") this: +available by typing in a command prompt ("DOS box") this:

    rundll32 printui.dll,PrintUIEntry /?

    A window pops up which shows you all of the commandline switches available. An extensive list of examples is also provided. This is @@ -7810,16 +7808,16 @@ what a client logon script might contain, with a short explanation of what the lines actually do (it works if 2k/XP Windows clients access printers via Samba, but works for Windows-based print servers too): 

    -rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q
-rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"
-rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"
+rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q
+rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"
+rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"

    Here is a list of the used commandline parameters:

    /dn

    deletes a network printer

    /q

    quiet modus

    /n

    names a printer

    /in

    adds a network printer connection

    /y

    sets printer as default printer

    • Line 1 deletes a possibly existing previous network printer infotec2105-IPDS (which had used native Windows drivers with LPRng that were removed from the server which was converted to CUPS). The /q at the end eliminates -"Confirm" or error dialog boxes popping up. They should not be +"Confirm" or error dialog boxes popping up. They should not be presented to the user logging on.

    • Line 2 adds the new printer infotec2105-PS (which actually is same physical device but is now run by the new CUPS printing system and associated @@ -7835,7 +7833,7 @@ default printer). The default printer selection may of course be different for different users.

    Note that the second line only works if the printer infotec2105-PS has an already working print queue -on "sambacupsserver", and if the printer drivers have successfully been +on "sambacupsserver", and if the printer drivers have successfully been uploaded (via APW , smbclient/rpcclient or cupsaddsmb) into the @@ -7851,7 +7849,7 @@ every time a user logs in; it's really quick anyway (1 to 2 seconds).

    The additional benefits for this are:

    • It puts in place any printer default setup changes -automatically at every user logon.

    • It allows for "roaming" users' login into the domain from +automatically at every user logon.

    • It allows for "roaming" users' login into the domain from different workstations.

    Since network printers are installed per user this much simplifies the process of keeping the installation up-to-date. The extra few seconds @@ -7859,7 +7857,7 @@ at logon time will not really be noticeable. Printers can be centrally added, changed, and deleted at will on the server with no user intervention required on the clients (you just need to keep the logon scripts up to date). -

    The addprinter command

    +

    The addprinter command

    The addprinter command can be configured to be a shell script or program executed by Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks the @@ -7871,13 +7869,13 @@ on legacy systems, or execute the lpadmin command on more modern systems) and create the associated share in , then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! -

    Migration of "Classical" printing to Samba

    -The basic "NT-style" printer driver management has not changed +

    Migration of "Classical" printing to Samba

    +The basic "NT-style" printer driver management has not changed considerably in 3.0 over the 2.2.x releases (apart from many small improvements). Here migration should be quite easy, especially if you followed previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x setup, or if you -continued "Win9x-style" printing in your Samba 2.2 installations, it +continued "Win9x-style" printing in your Samba 2.2 installations, it is more of an effort. Please read the appropriate release notes and the HOWTO Collection for 2.2. You can follow several paths. Here are possible scenarios for migration: @@ -7896,7 +7894,7 @@ used to do) drop down to using a printers.def (and all associated parameters). The make_printerdef tool is removed and there is no backwards compatibility for this.

  • You need to install a Windows 9x driver into the [print$] share for a printer on your Samba -host. The driver files will be stored in the "WIN40/0" subdirectory of +host. The driver files will be stored in the "WIN40/0" subdirectory of [print$], and some other settings and info go into the printing-related TDBs.

  • If you want to migrate an existing printers.def file into the new setup, the current @@ -7907,9 +7905,9 @@ rpcclient. See the Imprints installation client at: http://imprints.sourceforge.net/

    for an example. See also the discussion of rpcclient usage in the -"CUPS Printing" section.

    • Publishing Printer Information in Active Directory or LDAP

    +"CUPS Printing" section.

    Publishing Printer Information in Active Directory or LDAP

    We will publish an update to this section shortly. -

    Common Errors

    I give my root password but I don't get access

    +

    Common Errors

    I give my root password but I don't get access

    Don't confuse the root password which is valid for the UNIX system (and in most cases stored in the form of a one-way hash in a file named /etc/shadow) with the password used to @@ -7917,47 +7915,47 @@ authenticate against Samba!. Samba doesn't know the UNIX password; for root to access Samba resources via Samba-type access, a Samba account for root must be created first. This is often done with the smbpasswd command. -

    My printjobs get spooled into the spooling directory, but then get lost

    +

    My printjobs get spooled into the spooling directory, but then get lost

    Don't use the existing UNIX print system spool directory for the Samba spool directory. It may seem convenient and a saving of space, but it only leads to problems. The two must be separate. -

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    Jelmer R. Vernooij

    drawings
    The Samba Team

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download
    GDI on Windows -- PostScript on UNIX
    Windows Drivers, GDI and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript -- the Software RIP for non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    CUPS can use all Windows-formatted Vendor PPDs
    CUPS also uses PPDs for non-PostScript Printers
    The CUPS Filtering Architecture
    MIME types and CUPS Filters
    MIME type Conversion Rules
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -native CUPS printing
    Examples for filtering Chains
    Sources of CUPS drivers / PPDs
    Printing with Interface Scripts
    Network printing (purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows clients -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    PPDs for non-PS Printers on UNIX
    PPDs for non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers running in "Kernel Mode" cause many -Problems
    Workarounds impose Heavy Limitations
    CUPS: a "Magical Stone"?
    PostScript Drivers with no major problems -- even in Kernel -Mode
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsmb completed successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding critical PostScript Driver Settings on the -Client
    Installing PostScript Driver Files manually (using -rpcclient)
    A Check of the rpcclient man Page
    Understanding the rpcclient man page
    Producing an Example by querying a Windows Box
    What is required for adddriver and setdriver to succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting revisited
    The printing *.tdb Files
    Trivial DataBase Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic explained
    foomatic-rip and Foomatic-PPD Download and Installation
    Page Accounting with CUPS
    Setting up Quotas
    Correct and incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in - neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." - message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account - from Win2K/XP
    Avoid being connected to the Samba server as the - "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on - NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is - a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security - Policies"
    WinXP clients: "Administrator can not install - printers for all local users"
    "Print Change Notify" functions on - NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/XP
    Most common blunders in driver - settings on Windows clients
    cupsaddsmb does not work - with newly installed printer
    Permissions on +

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    Jelmer R. Vernooij

    drawings
    The Samba Team

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download
    GDI on Windows -- PostScript on UNIX
    Windows Drivers, GDI and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript -- the Software RIP for non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    CUPS can use all Windows-formatted Vendor PPDs
    CUPS also uses PPDs for non-PostScript Printers
    The CUPS Filtering Architecture
    MIME types and CUPS Filters
    MIME type Conversion Rules
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +native CUPS printing
    Examples for filtering Chains
    Sources of CUPS drivers / PPDs
    Printing with Interface Scripts
    Network printing (purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows clients -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    PPDs for non-PS Printers on UNIX
    PPDs for non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers running in "Kernel Mode" cause many +Problems
    Workarounds impose Heavy Limitations
    CUPS: a "Magical Stone"?
    PostScript Drivers with no major problems -- even in Kernel +Mode
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsmb completed successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding critical PostScript Driver Settings on the +Client
    Installing PostScript Driver Files manually (using +rpcclient)
    A Check of the rpcclient man Page
    Understanding the rpcclient man page
    Producing an Example by querying a Windows Box
    What is required for adddriver and setdriver to succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting revisited
    The printing *.tdb Files
    Trivial DataBase Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic explained
    foomatic-rip and Foomatic-PPD Download and Installation
    Page Accounting with CUPS
    Setting up Quotas
    Correct and incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/XP
    Most common blunders in driver + settings on Windows clients
    cupsaddsmb does not work + with newly installed printer
    Permissions on /var/spool/samba/ get reset after each -reboot
    Printer named "lp" +reboot
    Printer named "lp" intermittently swallows jobs and spits out completely different -ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    +ones

    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    The Common UNIX Print System (CUPS) has become very popular. All major Linux distributions now ship it as their default printing system. To many it is still a very mystical tool. Mostly, it - "just works" (TM). People tend to regard it as a "black box" + "just works" (TM). People tend to regard it as a "black box" which they don't want to look into, as long as it works. But once there is a little problem, they are in trouble to find out where to - start debugging it. Refer to the "Classical Printing" chapter also, it + start debugging it. Refer to the "Classical Printing" chapter also, it contains a lot of information that is relevant for CUPS.

    CUPS sports quite a few unique and powerful features. While their @@ -7968,7 +7966,7 @@ ones

    Location of Adobe PostScript driver files from the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most basic things first. -

    Overview

    +

    Overview

    CUPS is more than just a print spooling system. It is a complete printer management system that complies with the new IPP (Internet Printing Protocol). IPP is an industry @@ -7980,18 +7978,18 @@ ones

    Location of Adobe PostScript driver files (GUI interfaces developed by 3rd parties, like KDE's overwhelming KDEPrint).

    - CUPS allows creation of "raw" printers (ie: NO print file - format translation) as well as "smart" printers (i.e. CUPS does + CUPS allows creation of "raw" printers (ie: NO print file + format translation) as well as "smart" printers (i.e. CUPS does file format conversion as required for the printer). In many ways this gives CUPS similar capabilities to the MS Windows print monitoring system. Of course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now move on to explore how one may configure CUPS for interfacing with MS Windows print clients via Samba. -

    Basic Configuration of CUPS support

    +

    Basic Configuration of CUPS support

    Printing with CUPS in the most basic smb.conf setup in Samba 3.0 (as was true for 2.2.x) only needs two - settings: printing = cups and - printcap = cups. CUPS does not need a printcap file. + settings: printing = cups and + printcap = cups. CUPS does not need a printcap file. However, the cupsd.conf configuration file knows of two related directives that control how such a file will be automatically created and maintained by CUPS for the convenience of third party applications (example: Printcap /etc/printcap and PrintcapFormat BSD). @@ -7999,7 +7997,7 @@ ones

    Location of Adobe PostScript driver files print. Make sure CUPS is set to generate and maintain a printcap file! For details see man cupsd.conf and other CUPS-related documentation, like the wealth of documents on your CUPS server itself: http://localhost:631/documentation.html. -

    Linking of smbd with libcups.so

    +

    Linking of smbd with libcups.so

    Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support. Most recent installations have this support enabled. Per default CUPS linking is compiled into smbd and other Samba binaries. Of course, you can use CUPS even @@ -8007,7 +8005,7 @@ ones

    Location of Adobe PostScript driver files there are some differences in required or supported configuration then.

    - When Samba is compiled against libcups, printcap = cups + When Samba is compiled against libcups, printcap = cups uses the CUPS API to list printers, submit jobs, query queues, etc. Otherwise it maps to the System V commands with an additional -oraw option for printing. On a Linux system, you can use the ldd utility to find out details (ldd may not be present on @@ -8024,17 +8022,17 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) is set, then any otherwise manually set print command in smb.conf is ignored. This is an important point to remember!

    Tip

    Should it be necessary, for any reason, to set your own print commands, you can do this by setting - printing = sysv. However, you will loose all the benefits + printing = sysv. However, you will loose all the benefits of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands - (most important: print command; other commands are - lppause command, - lpresume command, - lpq command, - lprm command, - queuepause command and - queue resume command).

    Simple smb.conf Settings for CUPS

    + (most important: print command; other commands are + lppause command, + lpresume command, + lpq command, + lprm command, + queuepause command and + queue resume command).

    Simple smb.conf Settings for CUPS

    To summarize, here is the simplest printing-related setup for smb.conf to enable basic CUPS support: -

    Example 19.1. Simplest printing-related smb.conf

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins

    +

    Example 19.1. Simplest printing-related smb.conf

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins

    This is all you need for basic printing setup for CUPS. It will print all Graphic, Text, PDF and PostScript file submitted from Windows clients. However, most of your Windows users would not know how to @@ -8044,31 +8042,31 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) driver. Your users also very rarely send files from the command line. Unlike UNIX clients, they hardly submit graphic, text or PDF formatted files directly to the spooler. They nearly exclusively print - from GUI applications, with a "printer driver" hooked in between the + from GUI applications, with a "printer driver" hooked in between the applications native format and the print data stream. If the backend - printer is not a PostScript device, the print data stream is "binary", + printer is not a PostScript device, the print data stream is "binary", sensible only for the target printer. Read on to learn which problem this may cause and how to avoid it. -

    More complex smb.conf Settings for +

    More complex smb.conf Settings for CUPS

    Here is a slightly more complex printing-related setup for smb.conf. It enables general CUPS printing support for all printers, but defines one printer share which is set up differently. -

    Example 19.2. Overriding global CUPS settings for one printer

    [global]
    printing = cups
    printcap name = cups
    load printers = yes
    [printers]
    comment = All Printers
    path = /var/spool/samba
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins
    [special_printer]
    comment = A special printer with his own settings
    path = /var/spool/samba-special
    printing = sysv
    printcap = lpstat
    print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; \
    echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; \
    echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log : rm %f
    public = no
    guest ok = no
    writeable = no
    printable = yes
    printer admin = kurt
    hosts deny = 0.0.0.0
    hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

    +

    Example 19.2. Overriding global CUPS settings for one printer

    [global]
    printing = cups
    printcap name = cups
    load printers = yes
    [printers]
    comment = All Printers
    path = /var/spool/samba
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins
    [special_printer]
    comment = A special printer with his own settings
    path = /var/spool/samba-special
    printing = sysv
    printcap = lpstat
    print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; \
    echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; \
    echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log : rm %f
    public = no
    guest ok = no
    writeable = no
    printable = yes
    printer admin = kurt
    hosts deny = 0.0.0.0
    hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

    This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters known to Samba into the /tmp/smbprn.log file and deletes the jobfile. Moreover, the -printer admin of this share is "kurt" (not the "@ntadmins" group); +printer admin of this share is "kurt" (not the "@ntadmins" group); guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set -printing = sysv and -printcap = lpstat. -

    Advanced Configuration

    +printing = sysv and +printcap = lpstat. +

    Advanced Configuration

    Before we delve into all the configuration options, let us clarify a few points. Network printing needs to be organized and setup correctly. Often this is not done correctly. Legacy systems or small business LAN environments often lack design and good housekeeping. -

    Central spooling vs. "Peer-to-Peer" printing

    +

    Central spooling vs. "Peer-to-Peer" printing

    Many small office or home networks, as well as badly organized larger environments, allow each client a direct access to available network printers. This is generally a bad idea. It often blocks one client's @@ -8076,15 +8074,15 @@ access to the printer when another client's job is printing. It also might freeze the first client's application while it is waiting to get rid of the job. Also, there are frequent complaints about various jobs being printed with their pages mixed with each other. A better concept -is the usage of a "print server": it routes all jobs through one +is the usage of a "print server": it routes all jobs through one central system, which responds immediately, takes jobs from multiple concurrent clients at the same time and in turn transfers them to the printer(s) in the correct order. -

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients

    +

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients

    Most traditionally configured UNIX print servers acting on behalf of Samba's Windows clients represented a really simple setup. Their only -task was to manage the "raw" spooling of all jobs handed to them by +task was to manage the "raw" spooling of all jobs handed to them by Samba. This approach meant that the Windows clients were expected to prepare the print job file that it s ready to be sent to the printing device. Here a native (vendor-supplied) Windows printer @@ -8099,26 +8097,26 @@ sent in a format that is suitable for direct delivery to the printer. Clients need to run the vendor-provided drivers to do this. In this case CUPS will NOT do any print file format conversion work. -

    Driver Installation Methods on Windows Clients

    +

    Driver Installation Methods on Windows Clients

    The printer drivers on the Windows clients may be installed in two functionally different ways:

    • manually install the drivers locally on each client, one by one; this yields the old LanMan style printing; it uses a \\sambaserver\printershare type of connection.

    • - + deposit and prepare the drivers (for later download) on the print server (Samba); this enables the clients to use -"Point and Print" to get drivers semi-automatically installed the +"Point and Print" to get drivers semi-automatically installed the first time they access the printer; with this method NT/2K/XP clients use the SPOOLSS/MS-RPC type printing calls.

    The second method is recommended for use over the first. -

    Explicitly enable "raw" printing for -application/octet-stream!

    +

    Explicitly enable "raw" printing for +application/octet-stream!

    If you use the first option (drivers are installed on the client side), there is one setting to take care of: CUPS needs to be told -that it should allow "raw" printing of deliberate (binary) file +that it should allow "raw" printing of deliberate (binary) file formats. The CUPS files that need to be correctly set for RAW mode printers to work are:

    • /etc/cups/mime.types @@ -8132,7 +8130,7 @@ present:

      In /etc/cups/mime.convs, have this line: -

      +
        application/octet-stream   application/vnd.cups-raw   0   - 
 
      
 If these two files are not set up correctly for raw Windows client
@@ -8140,54 +8138,54 @@ printing, you may encounter the dreaded Unable to
 convert file 0 in your CUPS error_log file. 
 
      Note
      editing the mime.convs and the
 mime.types file does not
-enforce "raw" printing, it only
+enforce "raw" printing, it only
 allows it.
-
      Background. 
+

    Background.  CUPS being a more security-aware printing system than traditional ones does not by default allow a user to send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a -"Denial of Service" attack on your printer(s), causing at the least -the loss of a lot of paper and ink. "Unknown" data are tagged by CUPS +"Denial of Service" attack on your printer(s), causing at the least +the loss of a lot of paper and ink. "Unknown" data are tagged by CUPS as MIME type: application/octet-stream and not allowed to go to the printer. By default, you can only send other -(known) MIME types "raw". Sending data "raw" means that CUPS does not +(known) MIME types "raw". Sending data "raw" means that CUPS does not try to convert them and passes them to the printer untouched (see next chapter for even more background explanations).

    This is all you need to know to get the CUPS/Samba combo printing -"raw" files prepared by Windows clients, which have vendor drivers +"raw" files prepared by Windows clients, which have vendor drivers locally installed. If you are not interested in background information about more advanced CUPS/Samba printing, simply skip the remaining sections of this chapter. -

    Three familiar Methods for driver upload plus a new one

    +

    Three familiar Methods for driver upload plus a new one

    If you want to use the MS-RPC type printing, you must upload the drivers onto the Samba server first ([print$] share). For a discussion on how to deposit printer drivers on the Samba host (so that the Windows clients can download and use them via -"Point'n'Print") please also refer to the previous chapter of this +"Point'n'Print") please also refer to the previous chapter of this HOWTO Collection. There you will find a description or reference to three methods of preparing the client drivers on the Samba server: -

    • the GUI, "Add Printer Wizard" +

      • the GUI, "Add Printer Wizard" upload-from-a-Windows-client -method;

      • the commandline, "smbclient/rpcclient" +method;

      • the commandline, "smbclient/rpcclient" upload-from-a-UNIX-workstation method;

      • - + the Imprints Toolset method.

      These 3 methods apply to CUPS all the same. A new and more convenient way to load the Windows drivers into Samba is provided if you use CUPS: -

      • the cupsaddsmb +

        • the cupsaddsmb utility.

        cupsaddsmb is discussed in much detail further below. But we will first explore the CUPS filtering system and compare the Windows and UNIX printing architectures. -

    Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download

    +

    Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download

    Are you still following this? Good. Let's go into more detail then. We now know -how to set up a "dump" printserver, that is, a server which is spooling -printjobs "raw", leaving the print data untouched. +how to set up a "dump" printserver, that is, a server which is spooling +printjobs "raw", leaving the print data untouched.

    Possibly you need to setup CUPS in a more smart way. The reasons could be manifold: @@ -8198,9 +8196,9 @@ peaks in printing? Which departments prints how much?

  • Maybe you are asked to setup a print quota system: users should not be able to print more jobs, once they have surpassed a given limit per period?

  • Maybe your previous network printing setup is a mess -and shall be re-organized from a clean beginning?

  • Maybe you have experiencing too many "Blue Screens", -originating from poorly debugged printer drivers running in NT "kernel -mode"?

    • +and shall be re-organized from a clean beginning?

  • Maybe you have experiencing too many "Blue Screens", +originating from poorly debugged printer drivers running in NT "kernel +mode"?

    • These goals cannot be achieved by a raw print server. To build a server meeting these requirements, you'll first need to learn about how CUPS works and how you can enable its features. @@ -8208,23 +8206,23 @@ how CUPS works and how you can enable its features. What follows is the comparison of some fundamental concepts for Windows and UNIX printing; then is the time for a description of the CUPS filtering system, how it works and how you can tweak it. -

    GDI on Windows -- PostScript on UNIX

    +

    GDI on Windows -- PostScript on UNIX

    Network printing is one of the most complicated and error-prone day-to-day tasks any user or an administrator may encounter. This is true for all OS platforms. And there are reasons for this. -

    +

    You can't expect for most file formats to just throw them towards printers and they get printed. There needs to be a file format conversion in between. The problem is: there is no common standard for print file formats across all manufacturers and printer types. While PostScript (trademark held by Adobe), and, to an extent, PCL (trademark held by HP), have developed -into semi-official "standards", by being the most widely used PDLs +into semi-official "standards", by being the most widely used PDLs (Page Description Languages), there are still -many manufacturers who "roll their own" (their reasons may be +many manufacturers who "roll their own" (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, etc.). -

    Windows Drivers, GDI and EMF

    +

    Windows Drivers, GDI and EMF

    In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all application programmers have at their disposal a built-in API, the GDI (Graphical Device @@ -8234,14 +8232,14 @@ all Windows programs, to draw pictures, fonts and documents on screen as well as on paper (=print). Therefore printer driver developers can standardize on a well-defined GDI output for their own driver -input. Achieving WYSIWYG ("What You See Is What You Get") is +input. Achieving WYSIWYG ("What You See Is What You Get") is relatively easy, because the on-screen graphic primitives, as well as the on-paper drawn objects, come from one common source. This source, the GDI, produces often a file format called EMF (Enhanced MetaFile). The EMF is processed by the printer driver and converted to the printer-specific file format.

    Note

    - + To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation for their (BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating @@ -8250,7 +8248,7 @@ Systems. Their Core Graphic Engine uses a

    Figure 19.1. Windows Printing to a local Printer

    Windows Printing to a local Printer

    -

    UNIX Printfile Conversion and GUI Basics

    +

    UNIX Printfile Conversion and GUI Basics

    In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server. Every application is responsible for itself to create its print output. Fortunately, most @@ -8261,17 +8259,17 @@ the same document is displayed on screen and how it is presented on paper. WYSIWYG is more difficult to achieve. This goes back to the time decades ago, when the predecessors of X.org, designing the UNIX foundations and protocols for Graphical User -Interfaces refused to take over responsibility for "paper output" +Interfaces refused to take over responsibility for "paper output" also, as some had demanded at the time, and restricted itself to -"on-screen only". (For some years now, the "Xprint" project has been +"on-screen only". (For some years now, the "Xprint" project has been under development, attempting to build printing support into the X framework, including a PostScript and a PCL driver, but it is not yet ready for prime time.) You can see this unfavorable inheritance up to -the present day by looking into the various "font" directories on your +the present day by looking into the various "font" directories on your system; there are separate ones for fonts used for X display and fonts to be used on paper. -

    Background.  -The PostScript programming language is an "invention" by Adobe Inc., +

    Background.  +The PostScript programming language is an "invention" by Adobe Inc., but its specifications have been published to the full. Its strength lies in its powerful abilities to describe graphical objects (fonts, shapes, patterns, lines, curves, dots...), their attributes (color, @@ -8280,18 +8278,18 @@ shift...) them. Because of its open specification, anybody with the skill can start writing his own implementation of a PostScript interpreter and use it to display PostScript files on screen or on paper. Most graphical output devices are based on the concept of -"raster images" or "pixels" (one notable exception are pen +"raster images" or "pixels" (one notable exception are pen plotters). Of course, you can look at a PostScript file in its textual form and you will be reading its PostScript code, the language instructions which need to be interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer program or on paper by a printer. -

    PostScript and Ghostscript

    +

    PostScript and Ghostscript

    So, UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable legacy for UNIX, basic printing is fairly easy: if you have PostScript printers at your disposal! The reason is: these devices have a built-in PostScript -language "interpreter", also called a Raster Image +language "interpreter", also called a Raster Image Processor (RIP), (which makes them more expensive than other types of printers); throw PostScript towards them, and they will spit out your printed pages. Their RIP is doing all the hard work of @@ -8299,17 +8297,17 @@ converting the PostScript drawing commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no different to PostScript printing of a file from a Windows origin.

    Note

    - + Traditional UNIX programs and printing systems -- while -using PostScript -- are largely not PPD-aware. PPDs are "PostScript -Printer Description" files. They enable you to specify and control all +using PostScript -- are largely not PPD-aware. PPDs are "PostScript +Printer Description" files. They enable you to specify and control all options a printer supports: duplexing, stapling, punching... Therefore UNIX users for a long time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now there is CUPS....

    Figure 19.2. Printing to a Postscript Printer

    Printing to a Postscript Printer

    -

    +

    However, there are other types of printers out there. These don't know how to print PostScript. They use their own Page Description Language (PDL, often proprietary). To print to them is much @@ -8317,7 +8315,7 @@ more demanding. Since your UNIX applications mostly produce PostScript, and since these devices don't understand PostScript, you need to convert the printfiles to a format suitable for your printer on the host, before you can send it away. -

    Ghostscript -- the Software RIP for non-PostScript Printers

    +

    Ghostscript -- the Software RIP for non-PostScript Printers

    Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter used on UNIX platforms. It is a RIP in software, capable to do a @@ -8328,23 +8326,23 @@ to non-PostScript hardware.

    Figure 19.3. Ghostscript as a RIP for non-postscript printers

    Ghostscript as a RIP for non-postscript printers

    Tip

    -Use the "gs -h" command to check for all built-in "devices" of your +Use the "gs -h" command to check for all built-in "devices" of your Ghostscript version. If you specify e.g. a parameter of -sDEVICE=png256 on your Ghostscript command line, you are asking Ghostscript to convert the input into a PNG -file. Naming a "device" on the commandline is the most important +file. Naming a "device" on the commandline is the most important single parameter to tell Ghostscript how exactly it should render the input. New Ghostscript versions are released at fairly regular intervals, now by artofcode LLC. They are initially put under the -"AFPL" license, but re-released under the GNU GPL as soon as the next +"AFPL" license, but re-released under the GNU GPL as soon as the next AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has got some -deficiencies. Therefore ESP Ghostscript was developed as an +deficiencies. Therefore ESP Ghostscript was developed as an enhancement over GNU Ghostscript, with lots of bug-fixes, additional devices and improvements. It is jointly maintained by developers from CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes -the "cups" device (essential to print to non-PS printers from CUPS). -

    PostScript Printer Description (PPD) Specification

    +the "cups" device (essential to print to non-PS printers from CUPS). +

    PostScript Printer Description (PPD) Specification

    While PostScript in essence is a Page Description Language (PDL) to represent the page layout in a device independent way, real world print jobs are @@ -8370,13 +8368,13 @@ user selections are somehow written (in the form of special PostScript, PJL, JCL or vendor-dependent commands) into the PostScript file created by the driver.

    Warning

    - + A PostScript file that was created to contain device-specific commands for achieving a certain print job output (e.g. duplexed, stapled and punched) on a specific target machine, may not print as expected, or may not be printable at all on other models; it also may not be fit for further processing by software (e.g. by a PDF distilling program). -

    CUPS can use all Windows-formatted Vendor PPDs

    +

    CUPS can use all Windows-formatted Vendor PPDs

    CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if a UNIX/Linux-illiterate vendor might not have mentioned our favorite @@ -8391,8 +8389,8 @@ immediately. CUPS in all versions after 1.1.19 has a much more strict internal PPD parsing and checking code enabled; in case of printing trouble this online resource should be one of your first pitstops.

    Warning

    - - + + For real PostScript printers don't use the Foomatic or cupsomatic PPDs from Linuxprinting.org. With these devices the original @@ -8405,7 +8403,7 @@ your LAN has the PostScript driver installed, just use access the Windows directory where all printer driver files are stored. First look in the W32X86/2 subdir for the PPD you are seeking. -

    CUPS also uses PPDs for non-PostScript Printers

    +

    CUPS also uses PPDs for non-PostScript Printers

    CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available from the vendors (and no, you can't just take the PPD of a Postscript printer with the same @@ -8413,7 +8411,7 @@ model name and hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers we first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned. -

    The CUPS Filtering Architecture

    +

    The CUPS Filtering Architecture

    The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some other filters of its own. You (or your OS vendor) may have @@ -8429,37 +8427,37 @@ given input data format.

    If CUPS rasterizes a PostScript file natively to a bitmap, this is done in 2 stages: -

    • the first stage uses a Ghostscript device named "cups" +

      • the first stage uses a Ghostscript device named "cups" (this is since version 1.1.15) and produces a generic raster format -called "CUPS raster". -

      • the second stage uses a "raster driver" which converts +called "CUPS raster". +

      • the second stage uses a "raster driver" which converts the generic CUPS raster to a device specific raster.

      -Make sure your Ghostscript version has the "cups" device compiled in +Make sure your Ghostscript version has the "cups" device compiled in (check with gs -h | grep cups). Otherwise you may encounter the dreaded Unable to convert file -0 in your CUPS error_log file. To have "cups" as a +0 in your CUPS error_log file. To have "cups" as a device in your Ghostscript, you either need to patch GNU -Ghostscript and re-compile or use ESP Ghostscript. The +Ghostscript and re-compile or use ESP Ghostscript. The superior alternative is ESP Ghostscript: it supports not just CUPS, but 300 other devices too (while GNU Ghostscript supports only about 180). Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers too. It is now recommended by Linuxprinting.org for all spoolers.

      - - + + CUPS printers may be setup to use external rendering paths. One of the most common ones is provided by the Foomatic/cupsomatic concept, from Linuxprinting.org. This uses the classical Ghostscript approach, doing everything in one -step. It doesn't use the "cups" device, but one of the many +step. It doesn't use the "cups" device, but one of the many others. However, even for Foomatic/cupsomatic usage, best results and - + broadest printer model support is provided by ESP Ghostscript (more about cupsomatic/Foomatic, particularly the new version called now foomatic-rip, follows below). -

      MIME types and CUPS Filters

      - +

      MIME types and CUPS Filters

      + CUPS reads the file /etc/cups/mime.types (and all other files carrying a *.types suffix in the same directory) upon startup. These files contain the MIME @@ -8469,7 +8467,7 @@ for mime.types and in the comments section of the mime.types file itself. A simple rule reads like this:

      - + 

        application/pdf         pdf string(0,%PDF)

      @@ -8510,7 +8508,7 @@ CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, PNM, PBM, SGI-RGB and some more) and their associated MIME types with its filters. -

      MIME type Conversion Rules

      +

      MIME type Conversion Rules

      CUPS reads the file /etc/cups/mime.convs (and all other files named with a *.convs suffix in the same directory) upon startup. These files contain @@ -8526,24 +8524,24 @@ This means that the pdftops filter will t application/postscript as output, the virtual cost of this operation is 33 CUPS-$. The next filter is more expensive, costing 66 CUPS-$: -

      +
        application/vnd.hp-HPGL application/postscript   66   hpgltops
 
      
 This is the hpgltops, which processes HP-GL
 plotter files to PostScript.
-
      +
        application/octet-stream
 
      
 Here are two more examples: 
-
      +
        application/x-shell     application/postscript   33    texttops
  text/plain              application/postscript   33    texttops
 
      
 The last two examples name the texttops filter
-to work on "text/plain" as well as on "application/x-shell". (Hint:
+to work on "text/plain" as well as on "application/x-shell". (Hint:
 this differentiation is needed for the syntax highlighting feature of
-"texttops").
-

      Filter Requirements

      +"texttops"). +

      Filter Requirements

      There are many more combinations named in mime.convs. However, you are not limited to use the ones pre-defined there. You can plug in any filter you like into the CUPS framework. It must meet, or must be made @@ -8553,7 +8551,7 @@ needs, and put in the right lines in mime.types and mime.convs, then it will work seamlessly inside CUPS!

      Tip

      -The mentioned "CUPS requirements" for filters are simple. Take +The mentioned "CUPS requirements" for filters are simple. Take filenames or stdin as input and write to stdout. They should take these 5 or 6 arguments: printer job user title copies options [filename] @@ -8564,13 +8562,13 @@ attribute

      title

      The string from attribute

      options

      The job options

      filename

      (Optionally) The print request file (if missing, filters expected data fed through stdin). In most cases it is very easy to write a simple wrapper script around existing -filters to make them work with CUPS.

      Prefilters

      +filters to make them work with CUPS.

    Prefilters

    As was said, PostScript is the central file format to any UNIX based printing system. From PostScript, CUPS generates raster data to feed non-PostScript printers.

    But what is happening if you send one of the supported non-PS formats -to print? Then CUPS runs "pre-filters" on these input formats to +to print? Then CUPS runs "pre-filters" on these input formats to generate PostScript first. There are pre-filters to create PS from ASCII text, PDF, DVI or HP-GL. The outcome of these filters is always of MIME type application/postscript (meaning that @@ -8583,7 +8581,7 @@ MIME type application/vnd.cups-postscript print options already embedded into the file.

    Figure 19.4. Prefiltering in CUPS to form Postscript

    Prefiltering in CUPS to form Postscript

    -

    pstops

    +

    pstops

    pstopsis the filter to convert application/postscript to application/vnd.cups-postscript. It was said @@ -8596,14 +8594,14 @@ stapling an punching it, etc.) into the PostScript file. This is not all: other tasks performed by it are:

    • selecting the range of pages to be printed (if you choose to -print only pages "3, 6, 8-11, 16, 19-21", or only the odd numbered +print only pages "3, 6, 8-11, 16, 19-21", or only the odd numbered ones)

    • putting 2 or more logical pages on one sheet of paper (the -so-called "number-up" function) +so-called "number-up" function)

    • counting the pages of the job to insert the accounting information into the /var/log/cups/page_log -

    pstoraster

    +

    pstoraster

    pstoraster is at the core of the CUPS filtering system. It is responsible for the first stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; @@ -8628,18 +8626,18 @@ than one vendor financing the development of CUPS raster drivers).

    Figure 19.7. CUPS-raster production using Ghostscript

    CUPS-raster production using Ghostscript

    CUPS versions before version 1.1.15 were shipping a binary (or source -code) standalone filter, named "pstoraster". pstoraster was derived +code) standalone filter, named "pstoraster". pstoraster was derived from GNU Ghostscript 5.50, and could be installed besides and in addition to any GNU or AFPL Ghostscript package without conflicting.

    From version 1.1.15, this has changed. The functions for this has been integrated back into Ghostscript (now based on GNU Ghostscript version -7.05). The "pstoraster" filter is now a simple shell script calling +7.05). The "pstoraster" filter is now a simple shell script calling gs with the -sDEVICE=cups parameter. If your Ghostscript doesn't show a success on asking for gs -h |grep cups, you might not be able to print. Update your Ghostscript then! -

    imagetops and imagetoraster

    +

    imagetops and imagetoraster

    Above in the section about prefilters, we mentioned the prefilter that generates PostScript from image formats. The imagetoraster filter is used to convert directly from image to raster, without the @@ -8648,7 +8646,7 @@ mentioned prefilters. Here is a summarizing flowchart of image file filtering:

    Figure 19.8. Image format to CUPS-raster format conversion

    Image format to CUPS-raster format conversion

    -

    rasterto [printers specific]

    +

    rasterto [printers specific]

    CUPS ships with quite some different raster drivers processing CUPS raster. On my system I find in /usr/lib/cups/filter/ these: rastertoalps, rastertobj, rastertoepson, rastertoescp, @@ -8662,12 +8660,12 @@ development projects (such as Gimp-Print) wanting to cooperate as closely as possible with CUPS.

    Figure 19.9. Raster to Printer Specific formats

    Raster to Printer Specific formats

    -

    CUPS Backends

    -The last part of any CUPS filtering chain is a "backend". Backends +

    CUPS Backends

    +The last part of any CUPS filtering chain is a "backend". Backends are special programs that send the print-ready file to the final device. There is a separate backend program for any transfer -"protocol" of sending printjobs over the network, or for every local -interface. Every CUPS printqueue needs to have a CUPS "device-URI" +"protocol" of sending printjobs over the network, or for every local +interface. Every CUPS printqueue needs to have a CUPS "device-URI" associated with it. The device URI is the way to encode the backend used to send the job to its destination. Network device-URIs are using two slashes in their syntax, local device URIs only one, as you can @@ -8694,8 +8692,8 @@ This backend sends printfiles to LPR/LPD connected network printers. An example for the CUPS device-URI to use is: lpd://remote_host_name/remote_queue_name

    AppSocket/HP JetDirect

    -This backend sends printfiles to AppSocket (a.k.a. "HP -JetDirect") connected network printers. An example for the CUPS +This backend sends printfiles to AppSocket (a.k.a. "HP +JetDirect") connected network printers. An example for the CUPS device-URI to use is: socket://10.11.12.13:9100

    ipp

    @@ -8730,11 +8728,11 @@ root user create it: ln -s `which smbspool`

    It is easy to write your own backends as Shell or Perl scripts, if you need any modification or extension to the CUPS print system. One -reason could be that you want to create "special" printers which send -the printjobs as email (through a "mailto:/" backend), convert them to -PDF (through a "pdfgen:/" backend) or dump them to "/dev/null" (In +reason could be that you want to create "special" printers which send +the printjobs as email (through a "mailto:/" backend), convert them to +PDF (through a "pdfgen:/" backend) or dump them to "/dev/null" (In fact I have the system-wide default printer set up to be connected to -a "devnull:/" backend: there are just too many people sending jobs +a "devnull:/" backend: there are just too many people sending jobs without specifying a printer, or scripts and programs which don't name a printer. The system-wide default deletes the job and sends a polite mail back to the $USER asking him to always specify a correct @@ -8747,21 +8745,21 @@ utility. Used with the -v parameter, it lists all available backends: 

     $ lpinfo -v
-

    cupsomatic/Foomatic -- how do they fit into the Picture?

    -"cupsomatic" filters may be the most widely used on CUPS +

    cupsomatic/Foomatic -- how do they fit into the Picture?

    +"cupsomatic" filters may be the most widely used on CUPS installations. You must be clear about the fact that these were not -developed by the CUPS people. They are a "Third Party" add-on to +developed by the CUPS people. They are a "Third Party" add-on to CUPS. They utilize the traditional Ghostscript devices to render jobs for CUPS. When troubleshooting, you should know about the difference. Here the whole rendering process is done in one stage, -inside Ghostscript, using an appropriate "device" for the target -printer. cupsomatic uses PPDs which are generated from the "Foomatic" +inside Ghostscript, using an appropriate "device" for the target +printer. cupsomatic uses PPDs which are generated from the "Foomatic" Printer & Driver Database at Linuxprinting.org.

    You can recognize these PPDs from the line calling the cupsomatic filter: 

    - *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"
+ *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"

    This line you may find amongst the first 40 or so lines of the PPD file. If you have such a PPD installed, the printer shows up in the @@ -8770,18 +8768,18 @@ the driver description. cupsomatic is a Perl script that runs Ghostscript, with all the complicated commandline options auto-constructed from the selected PPD and commandline options give to the printjob. -

    +

    However, cupsomatic is now deprecated. Its PPDs (especially the first generation of them, still in heavy use out there) are not meeting the Adobe specifications. You might also suffer difficulties when you try -to download them with "Point'n'Print" to Windows clients. A better, +to download them with "Point'n'Print" to Windows clients. A better, and more powerful successor is now in a very stable Beta-version available: it is called foomatic-rip. To use foomatic-rip as a filter with CUPS, you need the new-type PPDs. These have a similar, but different line: 

     
- *cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"
+ *cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"

    The PPD generating engine at Linuxprinting.org has been revamped. @@ -8795,11 +8793,11 @@ print-options from page to page, in the middle of a job. And the best thing is: the new foomatic-rip now works seamlessly with all legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing for them access to use PPDs for their printing! -

    The Complete Picture

    +

    The Complete Picture

    If you want to see an overview over all the filters and how they relate to each other, the complete picture of the puzzle is at the end of this document. -

    mime.convs

    +

    mime.convs

    CUPS auto-constructs all possible filtering chain paths for any given MIME type, and every printer installed. But how does it decide in favor or against a specific alternative? (There may often be cases, @@ -8807,37 +8805,37 @@ where there is a choice of two or more possible filtering chains for the same target printer). Simple: you may have noticed the figures in the 3rd column of the mime.convs file. They represent virtual costs assigned to this filter. Every possible filtering chain will sum up to -a total "filter cost". CUPS decides for the most "inexpensive" route. +a total "filter cost". CUPS decides for the most "inexpensive" route.

    Tip

    The setting of FilterLimit 1000 in cupsd.conf will not allow more filters to run concurrently than will consume a total of 1000 virtual filter cost. This is a very efficient way to limit the load of any CUPS -server by setting an appropriate "FilterLimit" value. A FilterLimit of +server by setting an appropriate "FilterLimit" value. A FilterLimit of 200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows approximately 5 jobs maximum at a time. -

    "Raw" printing

    -You can tell CUPS to print (nearly) any file "raw". "Raw" means it -will not be filtered. CUPS will send the file to the printer "as is" +

    "Raw" printing

    +You can tell CUPS to print (nearly) any file "raw". "Raw" means it +will not be filtered. CUPS will send the file to the printer "as is" without bothering if the printer is able to digest it. Users need to take care themselves that they send sensible data formats only. Raw -printing can happen on any queue if the "-o raw" option is specified +printing can happen on any queue if the "-o raw" option is specified on the command line. You can also set up raw-only queues by simply not associating any PPD with it. This command: 

     $ lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E

    -sets up a queue named "rawprinter", connected via the "socket" -protocol (a.k.a. "HP JetDirect") to the device at IP address +sets up a queue named "rawprinter", connected via the "socket" +protocol (a.k.a. "HP JetDirect") to the device at IP address 11.12.1.3.14, using port 9100. (If you had added a PPD with -P /path/to/PPD to this command line, you would -have installed a "normal" printqueue. +have installed a "normal" printqueue.

    -CUPS will automatically treat each job sent to a queue as a "raw" one, +CUPS will automatically treat each job sent to a queue as a "raw" one, if it can't find a PPD associated with the queue. However, CUPS will only send known MIME types (as defined in its own mime.types file) and refuse others. -

    "application/octet-stream" printing

    +

    "application/octet-stream" printing

    Any MIME type with no rule in the /etc/cups/mime.types file is regarded as unknown or application/octet-stream and will not be @@ -8848,14 +8846,14 @@ message in your CUPS logs like: 

      Unable to convert file 0 to printable format for job

    -To enable the printing of "application/octet-stream" files, edit +To enable the printing of "application/octet-stream" files, edit these two files:

    • /etc/cups/mime.convs

    • /etc/cups/mime.types

    Both contain entries (at the end of the respective files) which must be uncommented to allow RAW mode operation for application/octet-stream. In /etc/cups/mime.types make sure this line is present: -

    +
      application/octet-stream
 
    
 This line (with no specific auto-typing rule set) makes all files
@@ -8864,32 +8862,32 @@ not otherwise auto-typed a member of application/octet-stream. In
 line: 
 
      application/octet-stream   application/vnd.cups-raw   0   -
-
    
+

    This line tells CUPS to use the Null Filter -(denoted as "-", doing... nothing at all) on +(denoted as "-", doing... nothing at all) on application/octet-stream, and tag the result as application/vnd.cups-raw. This last one is always a green light to the CUPS scheduler to now hand the file over -to the "backend" connecting to the printer and sending it over. +to the "backend" connecting to the printer and sending it over.

    Note

    Editing the mime.convs and the mime.types file does not -enforce "raw" printing, it only +enforce "raw" printing, it only allows it.

    Background.  CUPS being a more security-aware printing system than traditional ones does not by default allow one to send deliberate (possibly binary) data to printing devices. (This could be easily abused to launch a Denial of Service attack on your printer(s), causing at least the loss -of a lot of paper and ink...) "Unknown" data are regarded by CUPS +of a lot of paper and ink...) "Unknown" data are regarded by CUPS as MIME type application/octet-stream. While you -can send data "raw", the MIME type for these must +can send data "raw", the MIME type for these must be one that is known to CUPS and an allowed one. The file -/etc/cups/mime.types defines the "rules" how CUPS +/etc/cups/mime.types defines the "rules" how CUPS recognizes MIME types. The file /etc/cups/mime.convs decides which file conversion filter(s) may be applied to which MIME types. -

    PostScript Printer Descriptions (PPDs) for non-PS Printers

    +

    PostScript Printer Descriptions (PPDs) for non-PS Printers

    Originally PPDs were meant to be used for PostScript printers only. Here, they help to send device-specific commands and settings to the RIP which processes the jobfile. CUPS has extended this @@ -8902,16 +8900,16 @@ printers the Ghostscript RIP runs on the host computer.

    PPDs for a non-PS printer have a few lines that are unique to CUPS. The most important one looks similar to this: -

    +
      *cupsFilter: application/vnd.cups-raster  66   rastertoprinter
 
    
 It is the last piece in the CUPS filtering puzzle. This line tells the
-CUPS daemon to use as a last filter "rastertoprinter".  This filter
-should be served as input an "application/vnd.cups-raster" MIME type
+CUPS daemon to use as a last filter "rastertoprinter".  This filter
+should be served as input an "application/vnd.cups-raster" MIME type
 file. Therefore CUPS should auto-construct a filtering chain, which
 delivers as its last output the specified MIME type. This is then
-taken as input to the specified "rastertoprinter" filter. After this
-the last filter has done its work ("rastertoprinter" is a Gimp-Print
+taken as input to the specified "rastertoprinter" filter. After this
+the last filter has done its work ("rastertoprinter" is a Gimp-Print
 filter), the file should go to the backend, which sends it to the
 output device.
 
    
@@ -8919,15 +8917,15 @@ CUPS by default ships only a few generic PPDs, but they are good for
 several hundred printer models. You may not be able to control
 different paper trays, or you may get larger margins than your
 specific model supports):
-
    Table 19.1. PPD's shipped with CUPS
    PPD filePrinter type
    deskjet.ppdolder HP inkjet printers and compatible
    deskjet2.ppdnewer HP inkjet printers and compatible 
    dymo.ppdlabel printers 
    epson9.ppdEpson 24pin impact printers and compatible 
    epson24.ppdEpson 24pin impact printers and compatible 
    okidata9.ppdOkidata 9pin impact printers and compatible 
    okidat24.ppdOkidata 24pin impact printers and compatible 
    stcolor.ppdolder Epson Stylus Color printers 
    stcolor2.ppdnewer Epson Stylus Color printers 
    stphoto.ppdolder Epson Stylus Photo printers 
    stphoto2.ppdnewer Epson Stylus Photo printers 
    laserjet.ppdall PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.

    Difference between cupsomatic/foomatic-rip and -native CUPS printing

    +

    Table 19.1. PPD's shipped with CUPS

    PPD filePrinter type
    deskjet.ppdolder HP inkjet printers and compatible
    deskjet2.ppdnewer HP inkjet printers and compatible
    dymo.ppdlabel printers
    epson9.ppdEpson 24pin impact printers and compatible
    epson24.ppdEpson 24pin impact printers and compatible
    okidata9.ppdOkidata 9pin impact printers and compatible
    okidat24.ppdOkidata 24pin impact printers and compatible
    stcolor.ppdolder Epson Stylus Color printers
    stcolor2.ppdnewer Epson Stylus Color printers
    stphoto.ppdolder Epson Stylus Photo printers
    stphoto2.ppdnewer Epson Stylus Photo printers
    laserjet.ppdall PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.

    Difference between cupsomatic/foomatic-rip and +native CUPS printing

    Native CUPS rasterization works in two steps.

    • -First is the "pstoraster" step. It uses the special "cups" - +First is the "pstoraster" step. It uses the special "cups" + device from ESP Ghostscript 7.05.x as its tool

    • -Second comes the "rasterdriver" step. It uses various +Second comes the "rasterdriver" step. It uses various device-specific filters; there are several vendors who provide good quality filters for this step, some are Free Software, some are Shareware/Non-Free, some are proprietary.

    @@ -8948,8 +8946,8 @@ other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly advised, especially if you are upgrading to a recent version of CUPS too.

    - - + + Both the cupsomatic (old) and the foomatic-rip (new) methods from Linuxprinting.org use the traditional Ghostscript print file processing, doing everything in a single step. It therefore relies on @@ -8962,22 +8960,22 @@ Of course, you can use both methods side by side on one system (and even for one printer, if you set up different queues), and find out which works best for you.

    -cupsomatic "kidnaps" the printfile after the +cupsomatic "kidnaps" the printfile after the application/vnd.cups-postscript stage and deviates it through the CUPS-external, system wide Ghostscript -installation: Therefore the printfile bypasses the "pstoraster" filter +installation: Therefore the printfile bypasses the "pstoraster" filter (and thus also bypasses the CUPS-raster-drivers -"rastertosomething"). After Ghostscript finished its rasterization, +"rastertosomething"). After Ghostscript finished its rasterization, cupsomatic hands the rendered file directly to the CUPS backend. The flowchart above illustrates the difference between native CUPS rendering and the Foomatic/cupsomatic method. -

    Examples for filtering Chains

    +

    Examples for filtering Chains

    Here are a few examples of commonly occurring filtering chains to illustrate the workings of CUPS.

    Assume you want to print a PDF file to a HP JetDirect-connected PostScript printer, but you want to print the pages 3-5, 7, 11-13 -only, and you want to print them "2-up" and "duplex": +only, and you want to print them "2-up" and "duplex":

    • your print options (page selection as required, 2-up, duplex) are passed to CUPS on the commandline;

    • the (complete) PDF file is sent to CUPS and autotyped as application/pdf;

    • the file therefore first must pass the @@ -8985,8 +8983,8 @@ duplex) are passed to CUPS on the commandline;

    • the (complete) PDF MIME type application/postscript (a preview here would still show all pages of the original PDF);

    • the file then passes the pstops filter which applies the commandline options: it selects the pages -2-5, 7 and 11-13, creates and imposed layout "2 pages on 1 sheet" and -inserts the correct "duplex" command (as is defined in the printer's +2-5, 7 and 11-13, creates and imposed layout "2 pages on 1 sheet" and +inserts the correct "duplex" command (as is defined in the printer's PPD) into the new PostScript file; the file now is of PostScript MIME type application/vnd.cups-postscript;

    • the file goes to the socket @@ -9002,10 +9000,10 @@ duplex) are passed to CUPS on the commandline;

    • the (complete) PDF application/pdf;

    • the file therefore first must pass the pdftops pre-filter, which produces PostScript MIME type application/postscript (a preview here -would still show all pages of the original PDF);

    • the file then passes the "pstops" filter which applies +would still show all pages of the original PDF);

    • the file then passes the "pstops" filter which applies the commandline options: it selects the pages 2-5, 7 and 11-13, -creates and imposed layout "2 pages on 1 sheet" and inserts the -correct "duplex" command... (OOoops -- this printer and his PPD +creates and imposed layout "2 pages on 1 sheet" and inserts the +correct "duplex" command... (OOoops -- this printer and his PPD don't support duplex printing at all -- this option will be ignored then) into the new PostScript file; the file now is of PostScript MIME type @@ -9017,14 +9015,14 @@ printer-specific raster data and embedding any user-selected print-options into the print data stream;

    • the file goes to the usb backend, which transfers the job to the printers.

    The resulting filter chain therefore is as drawn in the image below. -

    Figure 19.12. PDF to USB chain

    PDF to USB chain

    Sources of CUPS drivers / PPDs

    +

    Figure 19.12. PDF to USB chain

    PDF to USB chain

    Sources of CUPS drivers / PPDs

    On the internet you can find now many thousand CUPS-PPD files (with their companion filters), in many national languages, supporting more than 1000 non-PostScript models. -

    • ESP +

      • ESP PrintPro (commercial, non-Free) is packaged with more than 3000 PPDs, ready for -successful use "out of the box" on Linux, Mac OS X, IBM-AIX, +successful use "out of the box" on Linux, Mac OS X, IBM-AIX, HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX and some more commercial Unices (it is written by the CUPS developers themselves and its sales help finance the further development of @@ -9052,8 +9050,8 @@ HPIJS).

      Printing with Interface Scripts

      -CUPS also supports the usage of "interface scripts" as known from +

    Printing with Interface Scripts

    +CUPS also supports the usage of "interface scripts" as known from System V AT&T printing systems. These are often used for PCL printers, from applications that generate PCL print jobs. Interface scripts are specific to printer models. They have a similar role as @@ -9068,38 +9066,38 @@ the -i option: root# lpadmin -p pclprinter -v socket://11.12.13.14:9100 \ -i /path/to/interface-script

    -Interface scripts might be the "unknown animal" to many. However, +Interface scripts might be the "unknown animal" to many. However, with CUPS they provide the most easy way to plug in your own custom-written filtering script or program into one specific print queue (some information about the traditional usage of interface scripts is to be found at http://playground.sun.com/printing/documentation/interface.html). -

    Network printing (purely Windows)

    +

    Network printing (purely Windows)

    Network printing covers a lot of ground. To understand what exactly goes on with Samba when it is printing on behalf of its Windows -clients, let's first look at a "purely Windows" setup: Windows clients +clients, let's first look at a "purely Windows" setup: Windows clients with a Windows NT print server. -

    From Windows Clients to an NT Print Server

    +

    From Windows Clients to an NT Print Server

    Windows clients printing to an NT-based print server have two options. They may -

    • execute the driver locally and render the GDI output +

      • execute the driver locally and render the GDI output (EMF) into the printer specific format on their own, or

      • send the GDI output (EMF) to the server, where the driver is executed to render the printer specific output.

      Both print paths are shown in the flowcharts below. -

    Driver Execution on the Client

    -In the first case the print server must spool the file as "raw", +

    Driver Execution on the Client

    +In the first case the print server must spool the file as "raw", meaning it shouldn't touch the jobfile and try to convert it in any way. This is what traditional UNIX-based print server can do too; and at a better performance and more reliably than NT print server. This is what most Samba administrators probably are familiar with. One -advantage of this setup is that this "spooling-only" print server may +advantage of this setup is that this "spooling-only" print server may be used even if no driver(s) for UNIX are available it is sufficient to have the Windows client drivers available and installed on the clients.

    Figure 19.13. Print Driver execution on the Client

    Print Driver execution on the Client

    -

    Driver Execution on the Server

    +

    Driver Execution on the Server

    The other path executes the printer driver on the server. The clients transfers print files in EMF format to the server. The server uses the PostScript, PCL, ESC/P or other driver to convert the EMF file into @@ -9111,14 +9109,14 @@ understand.

    Figure 19.14. Print Driver execution on the Server

    Print Driver execution on the Server

    However, there is something similar possible with CUPS. Read on... -

    Network Printing (Windows clients -- UNIX/Samba Print +

    Network Printing (Windows clients -- UNIX/Samba Print Servers)

    Since UNIX print servers cannot execute the Win32 program code on their platform, the picture is somewhat different. However, this doesn't limit your options all that much. In the contrary, you may have a way here to implement printing features which are not possible otherwise. -

    From Windows Clients to a CUPS/Samba Print Server

    +

    From Windows Clients to a CUPS/Samba Print Server

    Here is a simple recipe showing how you can take advantage of CUPS powerful features for the benefit of your Windows network printing clients: @@ -9127,14 +9125,14 @@ server.

  • Let the CUPS server render the PostScript into device specific raster format.

    • This requires the clients to use a PostScript driver (even if the printer is a non-PostScript model. It also requires that you have a -"driver" on the CUPS server. +"driver" on the CUPS server.

    Firstly, to enable CUPS based printing through Samba the following options should be set in your smb.conf file [global] section: -

    • printing = cups

    • printcap = cups

    +

    • printing = cups

    • printcap = cups

    When these parameters are specified, all manually set print directives -(like print command, or lppause command) in smb.conf (as well as +(like print command, or lppause command) in smb.conf (as well as in samba itself) will be ignored. Instead, Samba will directly interface with CUPS through it's application program interface (API) - as long as Samba has been compiled with CUPS library (libcups) @@ -9143,12 +9141,12 @@ other print commands are set up, then printing will use the System V AT&T command set, with the -oraw option automatically passing through (if you want your own defined print commands to work with a Samba that has CUPS support compiled in, -simply use printing = sysv). +simply use printing = sysv).

    Figure 19.15. Printing via CUPS/samba server

    Printing via CUPS/samba server

    -

    Samba receiving Jobfiles and passing them to CUPS

    +

    Samba receiving Jobfiles and passing them to CUPS

    Samba must use its own spool directory (it is set -by a line similar to path = /var/spool/samba, +by a line similar to path = /var/spool/samba, in the [printers] or [printername] section of smb.conf). Samba receives the job in its own @@ -9158,14 +9156,14 @@ directive, in a line that defaults to RequestRoot /var/spool/cups). CUPS checks the access rights of its spool dir and resets it to healthy values with every re-start. We have seen quite some people who had used a common spooling space for Samba -and CUPS, and were struggling for weeks with this "problem". +and CUPS, and were struggling for weeks with this "problem".

    A Windows user authenticates only to Samba (by whatever means is configured). If Samba runs on the same host as CUPS, you only need to -allow "localhost" to print. If they run on different machines, you +allow "localhost" to print. If they run on different machines, you need to make sure the Samba host gets access to printing on CUPS. -

    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs

    +

    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs

    PPDs can control all print device options. They are usually provided by the manufacturer; if you own a PostScript printer, that is. PPD files (PostScript Printer Descriptions) are always a component of @@ -9173,7 +9171,7 @@ PostScript printer drivers on MS Windows or Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate PostScript, PCL or PJL commands for the target printer. Printer driver GUI dialogs translate these options -"on-the-fly" into buttons and drop-down lists for the user to select. +"on-the-fly" into buttons and drop-down lists for the user to select.

    CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver and handle the options. There is @@ -9184,8 +9182,8 @@ or see if you have lphelp on your system). There are also some different GUI frontends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant to be evaluated by the PostScript RIP on the real PostScript printer. -

    PPDs for non-PS Printers on UNIX

    -CUPS doesn't limit itself to "real" PostScript printers in its usage +

    PPDs for non-PS Printers on UNIX

    +CUPS doesn't limit itself to "real" PostScript printers in its usage of PPDs. The CUPS developers have extended the scope of the PPD concept, to also describe available device and driver options for non-PostScript printers through CUPS-PPDs. @@ -9201,10 +9199,10 @@ the supplied PostScript. Thus CUPS lets all its printers appear as PostScript devices to its clients, because it can act as a PostScript RIP for those printers, processing the received PostScript code into a proper raster print format. -

    PPDs for non-PS Printers on Windows

    +

    PPDs for non-PS Printers on Windows

    CUPS-PPDs can also be used on Windows-Clients, on top of a -"core" PostScript driver (now recommended is the "CUPS PostScript -Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with +"core" PostScript driver (now recommended is the "CUPS PostScript +Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with limitations). This feature enables CUPS to do a few tricks no other spooler can do:

    • act as a networked PostScript RIP (Raster Image @@ -9212,27 +9210,27 @@ Processor), handling printfiles from all client platforms in a uniform way;

    • act as a central accounting and billing server, since all files are passed through the pstops filter and are therefore logged in the CUPS page_log file. -NOTE: this can not happen with "raw" print jobs, +NOTE: this can not happen with "raw" print jobs, which always remain unfiltered per definition;

    • enable clients to consolidate on a single PostScript driver, even for many different target printers.

    Using CUPS PPDs on Windows clients enables these to control all print job settings just as a UNIX client can do too. -

    Windows Terminal Servers (WTS) as CUPS Clients

    +

    Windows Terminal Servers (WTS) as CUPS Clients

    This setup may be of special interest to people experiencing major problems in WTS environments. WTS need often a multitude of non-PostScript drivers installed to run their clients' variety of different printer models. This often imposes the price of much increased instability. -

    Printer Drivers running in "Kernel Mode" cause many +

    Printer Drivers running in "Kernel Mode" cause many Problems

    -The reason is that in Win NT printer drivers run in "Kernel -Mode", this introduces a high risk for the stability of the system +The reason is that in Win NT printer drivers run in "Kernel +Mode", this introduces a high risk for the stability of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out there! Especially notorious is the example of the PCL printer driver that had an additional sound module running, to notify users via soundcard of their finished jobs. Do I -need to say that this one was also reliably causing "Blue Screens -of Death" on a regular basis? +need to say that this one was also reliably causing "Blue Screens +of Death" on a regular basis?

    PostScript drivers generally are very well tested. They are not known to cause any problems, even though they run in Kernel Mode too. This @@ -9240,7 +9238,7 @@ might be because there have so far only been 2 different PostScript drivers: the ones from Adobe and the one from Microsoft. Both are very well tested and are as stable as you ever can imagine on Windows. The CUPS driver is derived from the Microsoft one. -

    Workarounds impose Heavy Limitations

    +

    Workarounds impose Heavy Limitations

    In many cases, in an attempt to work around this problem, site administrators have resorted to restrict the allowed drivers installed on their WTS to one generic PCL- and one PostScript driver. This @@ -9248,7 +9246,7 @@ however restricts the clients in the amount of printer options available for them; often they can't get out more than simplex prints from one standard paper tray, while their devices could do much better, if driven by a different driver! ) -

    CUPS: a "Magical Stone"?

    +

    CUPS: a "Magical Stone"?

    Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these shortcomings. There are, depending on the version of Windows OS you use, up to 3 different PostScript @@ -9258,14 +9256,14 @@ used with many different PPDs). The clients will be able to (again) chose paper trays, duplex printing and other settings. However, there is a certain price for this too: a CUPS server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as -a "raw spooling" device. Plus, this setup is not yet widely tested, +a "raw spooling" device. Plus, this setup is not yet widely tested, although the first feedbacks look very promising. -

    PostScript Drivers with no major problems -- even in Kernel -Mode

    +

    PostScript Drivers with no major problems -- even in Kernel +Mode

    More recent printer drivers on W2K and XP don't run in Kernel mode (unlike Win NT) any more. However, both operating systems can still use the NT drivers, running in Kernel mode (you can roughly tell which -is which as the drivers in subdirectory "2" of "W32X86" are "old" +is which as the drivers in subdirectory "2" of "W32X86" are "old" ones). As was said before, the Adobe as well as the Microsoft PostScript drivers are not known to cause any stability problems. The CUPS driver is derived from the Microsoft one. There is a simple @@ -9275,16 +9273,16 @@ includes the source code of the Microsoft driver, and licensees of Visual Studio are allowed to use and modify it for their own driver development efforts. This is what the CUPS people have done. The license doesn't allow them to publish the whole of the source code. -However, they have released the "diff" under the GPL, and if you are -owner of an "MS DDK for Win NT", you can check the driver yourself. -

    Setting up CUPS for driver Download

    +However, they have released the "diff" under the GPL, and if you are +owner of an "MS DDK for Win NT", you can check the driver yourself. +

    Setting up CUPS for driver Download

    As we have said before: all previously known methods to prepare client -printer drivers on the Samba server for download and "Point'n'Print" +printer drivers on the Samba server for download and "Point'n'Print" convenience of Windows workstations are working with CUPS too. These methods were described in the previous chapter. In reality, this is a pure Samba business, and only relates to the Samba/Win client relationship. -

    cupsaddsmb: the unknown Utility

    +

    cupsaddsmb: the unknown Utility

    The cupsaddsmb utility (shipped with all current CUPS versions) is an alternative method to transfer printer drivers into the Samba [print$] share. Remember, this share is where @@ -9309,10 +9307,10 @@ job-billing)

    However, currently only Windows NT, 2000, and XP are supported by the CUPS drivers. You will need to get the respective part of Adobe driver too if you need to support Windows 95, 98, and ME clients. -

    Prepare your smb.conf for cupsaddsmb

    +

    Prepare your smb.conf for cupsaddsmb

    Prior to running cupsaddsmb, you need the following settings in smb.conf: -

    Example 19.3. smb.conf for cupsaddsmb usage

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    # setting depends on your requirements
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root
    [print$]
    comment = Printer Drivers
    path = /etc/samba/drivers
    browseable = yes
    guest ok = no
    read only = yes
    write list = root

    CUPS Package of "PostScript Driver for WinNT/2k/XP"

    +

    Example 19.3. smb.conf for cupsaddsmb usage

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    # setting depends on your requirements
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root
    [print$]
    comment = Printer Drivers
    path = /etc/samba/drivers
    browseable = yes
    guest ok = no
    read only = yes
    write list = root

    CUPS Package of "PostScript Driver for WinNT/2k/XP"

    CUPS users may get the exactly same packages from http://www.cups.org/software.html. It is a separate package from the CUPS base software files, tagged as CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba @@ -9327,13 +9325,13 @@ cups-samba.readme cups-samba.remove cups-samba.ss

    - - + + These have been packaged with the ESP meta packager software -"EPM". The *.install and +"EPM". The *.install and *.remove files are simple shell scripts, which untars the *.ss (the *.ss is -nothing else but a tar-archive, which can be untar-ed by "tar" +nothing else but a tar-archive, which can be untar-ed by "tar" too). Then it puts the content into /usr/share/cups/drivers/. This content includes 3 files: @@ -9365,17 +9363,17 @@ copy/move the file (after running the right place. 

     root# cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-

    +

    This new CUPS PostScript driver is currently binary-only, but free of charge. No complete source code is provided (yet). The reason is this: it has been developed with the help of the Microsoft Driver Developer Kit (DDK) and compiled with Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of the source code as Free Software. However, CUPS developers released -the "diff" in source code under the GPL, so anybody with a license of +the "diff" in source code under the GPL, so anybody with a license of Visual Studio and a DDK will be able to compile for him/herself. -

    Recognize the different Driver Files

    -The CUPS drivers don't support the "older" Windows 95/98/ME, but only +

    Recognize the different Driver Files

    +The CUPS drivers don't support the "older" Windows 95/98/ME, but only the Windows NT/2000/XP client:

    Windows NT, 2000, and XP are supported by:

    • cups.hlp

    • cupsdrvr.dll

    • cupsui.dll

    @@ -9394,7 +9392,7 @@ support of WinNT/2k/XP are present in , the Adobe ones will be ignored and the CUPS ones will be used. If you prefer -- for whatever reason -- to use Adobe-only drivers, move away the 3 CUPS driver files. The Win95/98/ME clients use the Adobe drivers in any case. -

    Acquiring the Adobe Driver Files

    +

    Acquiring the Adobe Driver Files

    Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on the Adobe website as single files and the self-extracting and/or self-installing Windows-exe is @@ -9407,13 +9405,13 @@ Generic PostScript printer. After this, the client's where you can get them with smbclient from the CUPS host. A more detailed description about this is in the next (the CUPS printing) chapter. -

    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"

    -Users of the ESP Print Pro software are able to install their "Samba -Drivers" package for this purpose with no problem. Retrieve the driver +

    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"

    +Users of the ESP Print Pro software are able to install their "Samba +Drivers" package for this purpose with no problem. Retrieve the driver files from the normal download area of the ESP Print Pro software at http://www.easysw.com/software.html. -You need to locate the link labelled "SAMBA" amongst the +You need to locate the link labelled "SAMBA" amongst the Download Printer Drivers for ESP Print Pro 4.x area and download the package. Once installed, you can prepare any driver by simply highlighting the printer in the Printer Manager GUI @@ -9423,7 +9421,7 @@ driver files; i.e. mainly setup the [print$] share, etc. The ESP Print Pro package includes the CUPS driver files as well as a (licensed) set of Adobe drivers for the Windows 95/98/ME client family. -

    Caveats to be considered

    +

    Caveats to be considered

    Once you have run the install script (and possibly manually moved the cups.hlp file to /usr/share/cups/drivers/), the driver is @@ -9431,10 +9429,10 @@ ready to be put into Samba's [print$] share (w /etc/samba/drivers/ and contains a subdir tree with WIN40 and W32X86 branches): You do this by running -"cupsaddsmb" (see also man cupsaddsmb for +"cupsaddsmb" (see also man cupsaddsmb for CUPS since release 1.1.16).

    Tip

    - + You may need to put root into the smbpasswd file by running smbpasswd; this is especially important if you should run this whole procedure for the first time, and are not @@ -9454,42 +9452,42 @@ It is not harmful if you still have the ADOBE*.* driver files from previous installations in the /usr/share/cups/drivers/ directory. The new cupsaddsmb (from 1.1.16) will -automatically prefer "its own" drivers if it finds both. +automatically prefer "its own" drivers if it finds both.

  • - + Should your Win clients have had the old ADOBE*.* files for the Adobe PostScript driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/2k/XP will fail at first. You need to wipe the old driver from the clients -first. It is not enough to "delete" the printer, as the driver files +first. It is not enough to "delete" the printer, as the driver files will still be kept by the clients and re-used if you try to re-install the printer. To really get rid of the Adobe driver files on the -clients, open the "Printers" folder (possibly via Start, Settings, Control Panel, Printers), +clients, open the "Printers" folder (possibly via Start, Settings, Control Panel, Printers), right-click onto the folder background and select Server Properties. When the new dialog opens, select the Drivers tab. On the list select the driver you want to delete and click on the Delete button. This will only work if there is not one single printer left -which uses that particular driver. You need to "delete" all printers -using this driver in the "Printers" folder first. You will need +which uses that particular driver. You need to "delete" all printers +using this driver in the "Printers" folder first. You will need Administrator privileges to do this.

  • - + Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all printers to this one by proceeding as described in the printing chapter: either change -a driver for an existing printer by running the "Printer Properties" +a driver for an existing printer by running the "Printer Properties" dialog, or use rpcclient with the setdriver sub-command.

    • -

    Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver

    +

    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver

    You are interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes these are the most important items which weigh in favor of the CUPS ones:

    • no hassle with the Adobe EULA

    • no hassle with the question “Where do I get the ADOBE*.* driver files from?”

    • - + the Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the main PostScript part of the print file. Thus the printfile starts with @@ -9497,24 +9495,24 @@ PostScript part of the print file. Thus the printfile starts with <escape>%-12345X instead of %!PS). This leads to the CUPS daemon auto-typing the incoming file as a print-ready file, -not initiating a pass through the "pstops" filter (to speak more +not initiating a pass through the "pstops" filter (to speak more technically, it is not regarded as the generic MIME type - + application/postscript, but as the more special MIME type - + application/cups.vnd-postscript), which therefore also leads to the page accounting in /var/log/cups/page_log not receiving the exact number of pages; instead the dummy page number -of "1" is logged in a standard setup)

    • the Adobe driver has more options to "mis-configure" the +of "1" is logged in a standard setup)

    • the Adobe driver has more options to "mis-configure" the PostScript generated by it (like setting it inadvertently to Optimize for Speed, instead of Optimize for Portability, which could lead to CUPS being unable to process it)

    • the CUPS PostScript driver output sent by Windows clients to the CUPS server will be guaranteed to be auto-typed always as generic MIME type application/postscript, -thusly passing through the CUPS "pstops" filter and logging the +thusly passing through the CUPS "pstops" filter and logging the correct number of pages in the page_log for accounting and quota purposes

    • the CUPS PostScript driver supports the sending of additional standard (IPP) print options by Win NT/2k/XP clients. Such @@ -9532,7 +9530,7 @@ not disturb any other applications as they will regard it as a comment and simply ignore it).

    • the CUPS PostScript driver will be the heart of the fully fledged CUPS IPP client for Windows NT/2K/XP to be released soon (probably alongside the first Beta release for CUPS -1.2).

    Run "cupsaddsmb" (quiet Mode)

    +1.2).

    Run "cupsaddsmb" (quiet Mode)

    The cupsaddsmb command copies the needed files into your [print$] share. Additionally, the PPD associated with this printer is copied from @@ -9541,7 +9539,7 @@ associated with this printer is copied from Windows client installations via Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate towards Samba. If you have a small network you are probably using user -level security (security = user). +level security (security = user).

    Here is an example of a successfully run cupsaddsmb command. 

    @@ -9550,18 +9548,18 @@ Password for root required to access localhost via Samba: <

    To share all printers and drivers, use the -a parameter instead of a printer name. Since -cupsaddsmb "exports" the printer drivers to Samba, it should be +cupsaddsmb "exports" the printer drivers to Samba, it should be obvious that it only works for queues with a CUPS driver associated. -

    Run "cupsaddsmb" with verbose Output

    +

    Run "cupsaddsmb" with verbose Output

    Probably you want to see what's going on. Use the -v parameter to get a more verbose output. The -output below was edited for better readability: all "\" at the end of +output below was edited for better readability: all "\" at the end of a line indicate that I inserted an artificial line break plus some indentation here:

    Warning

    You will see the root password for the Samba account printed on screen. -

    +
     root# cupsaddsmb -U root -v infotec_2105
 Password for root required to access localhost via GANDALF:
 Running command: smbclient //localhost/print\$ -N -U'root%secret' \
@@ -9579,11 +9577,11 @@ putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
 putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
   
 Running command: rpcclient localhost -N -U'root%secret' 
-   -c 'adddriver "Windows NT x86"   \
-   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
-    RAW:NULL"'
-cmd = adddriver "Windows NT x86" \
-    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
 Printer Driver infotec_2105 successfully installed.
   
 Running command: smbclient //localhost/print\$ -N -U'root%secret' \
@@ -9607,13 +9605,13 @@ Running command: smbclient //localhost/print\$ -N -U'root%secret' \
   putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
   
   Running command: rpcclient localhost -N -U'root%secret' \
-   -c 'adddriver "Windows 4.0"      \
-   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
    PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
-    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-  cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+  cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
     ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
-                   PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+                   PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
   Printer Driver infotec_2105 successfully installed.
   
   Running command: rpcclient localhost -N -U'root%secret'  \
@@ -9628,11 +9626,11 @@ you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in
 between. They occur, because the directories WIN40 and W32X86 already
 existed in the [print$] driver download share
 (from a previous driver installation). They are harmless here.
-

    Understanding cupsaddsmb

    +

    Understanding cupsaddsmb

    What has happened? What did cupsaddsmb do? There are five stages of the procedure

    1. - + call the CUPS server via IPP and request the driver files and the PPD file for the named printer;

    2. store the files temporarily in the local TEMPDIR (as defined in @@ -9640,13 +9638,13 @@ TEMPDIR (as defined in [print$] share and put the files into the share's WIN40 (for Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub directories;

    3. - + connect via rpcclient to the Samba server and -execute the "adddriver" command with the correct +execute the "adddriver" command with the correct parameters;

    4. - + connect via rpcclient to the Samba server a second -time and execute the "setdriver" command.

    +time and execute the "setdriver" command.

    Note, that you can run the cupsaddsmb utility with parameters to specify one remote host as Samba host and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a @@ -9655,7 +9653,7 @@ life most people will have their CUPS and Samba servers run on the same host): 

     root# cupsaddsmb -H sambaserver -h cupsserver -v printername
-

    How to recognize if cupsaddsmb completed successfully

    +

    How to recognize if cupsaddsmb completed successfully

    You must always check if the utility completed successfully in all fields. You need as a minimum these 3 messages amongst the output: @@ -9676,7 +9674,7 @@ It is impossible to see any diagnostic output if you don't run cupsaddsmb in verbose mode. Therefore we strongly recommend to not use the default quiet mode. It will hide any problems from you which might occur. -

    cupsaddsmb with a Samba PDC

    +

    cupsaddsmb with a Samba PDC

    You can't get the standard cupsaddsmb command to run on a Samba PDC? You are asked for the password credential all over again and again and the command just will not take off at all? Try one of these @@ -9687,34 +9685,34 @@ variations: root# cupsaddsmb -H SAURON -U MIDEARTH\\root -h cups-server -v printername

    (Note the two backslashes: the first one is required to -"escape" the second one). -

    cupsaddsmb Flowchart

    +"escape" the second one). +

    cupsaddsmb Flowchart

    Here is a chart about the procedures, commandflows and -dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is -not intended to, and does not work with, "raw" queues! +dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is +not intended to, and does not work with, "raw" queues!

    Figure 19.16. cupsaddsmb flowchart

    cupsaddsmb flowchart

    -

    Installing the PostScript Driver on a Client

    +

    Installing the PostScript Driver on a Client

    After cupsaddsmb completed, your driver is prepared for the clients to use. Here are the steps you must perform to download and install it -via "Point'n'Print". From a Windows client, browse to the CUPS/Samba +via "Point'n'Print". From a Windows client, browse to the CUPS/Samba server; -

    • open the Printers +

      • open the Printers share of Samba in Network Neighbourhood;

      • right-click on the printer in question;

      • from the opening context-menu select Install... or Connect... (depending on the Windows version you use).

      After a few seconds, there should be a new printer in your -client's local "Printers" folder: On Windows +client's local "Printers" folder: On Windows XP it will follow a naming convention of PrinterName on -SambaServer. (In my current case it is "infotec_2105 on -kde-bitshop"). If you want to test it and send your first job from +SambaServer. (In my current case it is "infotec_2105 on +kde-bitshop"). If you want to test it and send your first job from an application like Winword, the new printer will appears in a \\SambaServer\PrinterName entry in the dropdown list of available printers.

      Note

      - + cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher and Samba from 2.2.4. If it doesn't work, or if the automatic printer driver download to the clients doesn't succeed, you can still manually @@ -9725,11 +9723,11 @@ share for a UNC type of connection: C:\> net use lpt1: \\sambaserver\printershare /user:ntadmin

      should you desire to use the CUPS networked PostScript RIP -functions. (Note that user "ntadmin" needs to be a valid Samba user +functions. (Note that user "ntadmin" needs to be a valid Samba user with the required privileges to access the printershare) This would set up the printer connection in the traditional LanMan way (not using MS-RPC). -

      Avoiding critical PostScript Driver Settings on the +

      Avoiding critical PostScript Driver Settings on the Client

      Soooo: printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, @@ -9755,7 +9753,7 @@ get a printout at all) (Adobe)

    • Sometimes you can choose : in case of problems try 2 instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well) (Adobe).

    • Say Yes to PostScript -Error Handler (Adobe)

    Installing PostScript Driver Files manually (using +Error Handler (Adobe)

    Installing PostScript Driver Files manually (using rpcclient)

    Of course you can run all the commands which are embedded into the cupsaddsmb convenience utility yourself, one by one, and hereby upload @@ -9764,18 +9762,18 @@ and prepare the driver files for future client downloads. printer should be there. We are providing the driver now);

  • copy all files to [print$]

  • - + run rpcclient adddriver (for each client architecture you want to support):

  • - + run rpcclient setdriver.

    • - - - - - -We are going to do this now. First, read the man page on "rpcclient" + + + + + +We are going to do this now. First, read the man page on "rpcclient" to get a first idea. Look at all the printing related sub-commands. enumprinters, enumdrivers, enumports, @@ -9783,9 +9781,9 @@ sub-commands. enumprinters, the most interesting ones. rpcclient implements an important part of the MS-RPC protocol. You can use it to query (and command) a Win NT (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other -things, to benefit from the "Point'n'Print" features. Samba can now +things, to benefit from the "Point'n'Print" features. Samba can now mimic this too. -

    A Check of the rpcclient man Page

    +

    A Check of the rpcclient man Page

    First let's have a little check of the rpcclient man page. Here are two relevant passages:

    @@ -9805,9 +9803,9 @@ Help File Name:\ Language Monitor Name:\ Default Data Type:\ Comma Separated list of Files -

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors +

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of -a bi-directional link for communication. This field should be "NULL". +a bi-directional link for communication. This field should be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail @@ -9818,32 +9816,32 @@ printer driver associated with an installed printer. The printer driver must already be correctly installed on the print server.

    See also the enumprinters and enumdrivers commands for obtaining a list of installed printers and drivers. -

    Understanding the rpcclient man page

    +

    Understanding the rpcclient man page

    The exact format isn't made too clear by the man page, since you have to deal with some parameters containing spaces. Here is a better description for it. We have line-broken the -command and indicated the breaks with "\". Usually you would type the +command and indicated the breaks with "\". Usually you would type the command in one line without the linebreaks: -

    - adddriver "Architecture" \
-           "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
-           LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
+
    + adddriver "Architecture" \
+           "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
+           LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
 
    
 What the man pages denotes as a simple <config>
 keyword, does in reality consist of 8 colon-separated fields. The
 last field may take multiple (in some, very insane, cases, even
 20 different additional files. This might sound confusing at first.
-Note, that what the man pages names the "LongPrinterName" in
-reality should rather be called the "Driver Name". You can name it
+Note, that what the man pages names the "LongPrinterName" in
+reality should rather be called the "Driver Name". You can name it
 anything you want, as long as you use this name later in the
 rpcclient ... setdriver command. For
 practical reasons, many name the driver the same as the
 printer.
 
    
 True: it isn't simple at all. I hear you asking:
-How do I know which files are "Driver
-File", "Data File", "Config File", "Help File" and "Language
-Monitor File" in each case? -- For an answer you may
+How do I know which files are "Driver
+File", "Data File", "Config File", "Help File" and "Language
+Monitor File" in each case? -- For an answer you may
 want to have a look at how a Windows NT box with a shared printer
 presents the files to us. Remember, that this whole procedure has
 to be developed by the Samba Team by overhearing the traffic caused
@@ -9852,9 +9850,9 @@ box now, and access it from a UNIX workstation. We will query it
 with rpcclient to see what it tells us and
 try to understand the man page more clearly which we've read just
 now.
-

    Producing an Example by querying a Windows Box

    - - +

    Producing an Example by querying a Windows Box

    + + We could run rpcclient with a getdriver or a getprinter subcommand (in level 3 verbosity) against it. Just sit down at UNIX or @@ -9865,10 +9863,10 @@ following command:

    From the result it should become clear which is which. Here is an example from my installation: -

    +
     root# rpcclient -U'Danka%xxxx' W2KSERVER \
-	-c'getdriver "DANKA InfoStream Virtual Printer" 3'
- cmd = getdriver "DANKA InfoStream Virtual Printer" 3
+	-c'getdriver "DANKA InfoStream Virtual Printer" 3'
+ cmd = getdriver "DANKA InfoStream Virtual Printer" 3
 
  [Windows NT x86]
  Printer Driver Info 3:
@@ -9893,37 +9891,37 @@ example from my installation:
 
 
    
 Some printer drivers list additional files under the label
-"Dependentfiles": these would go into the last field
+"Dependentfiles": these would go into the last field
 ListOfFiles,Comma-separated. For the CUPS
 PostScript drivers we don't need any (nor would we for the Adobe
-PostScript driver): therefore the field will get a "NULL" entry.
-

    What is required for adddriver and setdriver to succeed

    +PostScript driver): therefore the field will get a "NULL" entry. +

    What is required for adddriver and setdriver to succeed

    From the manpage (and from the quoted output of cupsaddsmb, above) it becomes clear that you need to have certain conditions in order to make the manual uploading and initializing of the driver files succeed. The two rpcclient - + subcommands (adddriver and setdriver) need to encounter the following pre-conditions to complete successfully: -

    • you are connected as printer admin, or root (note, -that this is not the "Printer Operators" group in +

      • you are connected as printer admin, or root (note, +that this is not the "Printer Operators" group in NT, but the printer admin group, as defined in the [global] section of smb.conf);

      • copy all required driver files to \\sambaserver\print$\w32x86 and \\sambaserver\print$\win40 as appropriate. They -will end up in the "0" respective "2" subdirectories later -- for now +will end up in the "0" respective "2" subdirectories later -- for now don't put them there, they'll be automatically used by the adddriver subcommand.! (if you use -"smbclient" to put the driver files into the share, note that you need -to escape the "$": smbclient //sambaserver/print\$ -U +"smbclient" to put the driver files into the share, note that you need +to escape the "$": smbclient //sambaserver/print\$ -U root);

      • the user you're connecting as must be able to write to the [print$] share and create subdirectories;

      • the printer you are going to setup for the Windows clients, needs to be installed in CUPS already;

      • - - + + the CUPS printer must be known to Samba, otherwise the setdriver subcommand fails with an NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by @@ -9932,7 +9930,7 @@ rpcclient. A long-standing bug prevented a proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember this in case you've created the CUPS printer just shortly ago and encounter problems: try restarting -Samba.

    Manual Driver Installation in 15 Steps

    +Samba.

    Manual Driver Installation in 15 Steps

    We are going to install a printer driver now by manually executing all required commands. As this may seem a rather complicated process at first, we go through the procedure step by step, explaining every @@ -9945,7 +9943,7 @@ to the CUPS system. The printer is accessed via a socket (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root for this step

  • (optional) Check if the Printer is recognized by -Samba

    +Samba
     root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
 flags:[0x800000]
 name:[\\kde-bitshop\mysmbtstprn]
@@ -9955,15 +9953,15 @@ comment:[mysmbtstprn]
 This should show the printer in the list. If not, stop and re-start
 the Samba daemon (smbd), or send a HUP signal: kill -HUP
 `pidof smbd`. Check again.  Troubleshoot and repeat until
-success. Note the "empty" field between the two commas in the
-"description" line. Here would the driver name appear if there was one
+success. Note the "empty" field between the two commas in the
+"description" line. Here would the driver name appear if there was one
 already. You need to know root's Samba password (as set by the
 smbpasswd command) for this step and most of the
 following steps. Alternatively you can authenticate as one of the
-users from the "write list" as defined in smb.conf for
+users from the "write list" as defined in smb.conf for
 [print$].

  • (optional) Check if Samba knows a Driver for the -Printer

    +Printer
     root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
 			| grep driver 
 drivername:[]
@@ -9987,8 +9985,8 @@ printprocessor:[winprint]
 Neither method of the three commands shown above should show a driver.
 This step was done for the purpose of demonstrating this condition. An
 attempt to connect to the printer at this stage will prompt the
-message along the lines: "The server has not the required printer
-driver installed".
+message along the lines: "The server has not the required printer
+driver installed".

  • Put all required Driver Files into Samba's [print$]

     root# smbclient //localhost/print\$ -U 'root%xxxx' \
@@ -9999,13 +9997,13 @@ driver installed".
 	put /usr/share/cups/drivers/cups.hlp cups.hlp'

    (Note that this command should be entered in one long single -line. Line-breaks and the line-end indicating "\" has been inserted +line. Line-breaks and the line-end indicating "\" has been inserted for readability reasons.) This step is required for the next one to succeed. It makes the driver files physically present in the [print$] share. However, clients would still not be able to install them, because Samba does not yet treat them as driver files. A client asking for the driver would still -be presented with a "not installed here" message. +be presented with a "not installed here" message.

  • Verify where the Driver Files are now

     root# ls -l /etc/samba/drivers/W32X86/
 total 669
@@ -10016,20 +10014,20 @@ drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
 -rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
 -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD

    -The driver files now are in the W32X86 architecture "root" of +The driver files now are in the W32X86 architecture "root" of [print$].

  • Tell Samba that these are Driver Files -(adddriver)

    -root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
+(adddriver)
    +root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
   cupsdrvr.dll:mysmbtstprn.PPD: \
-  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
   localhost
 Printer Driver mydrivername successfully installed.
 
    
 Note that your cannot repeat this step if it fails. It could fail even
 as a result of a simple typo. It will most likely have moved a part of
-the driver files into the "2" subdirectory. If this step fails, you
+the driver files into the "2" subdirectory. If this step fails, you
 need to go back to the fourth step and repeat it, before you can try
 this one again. In this step you need to choose a name for your
 driver. It is normally a good idea to use the same name as is used for
@@ -10053,7 +10051,7 @@ total 5039
 Notice how step 6 did also move the driver files to the appropriate
 subdirectory. Compare with the situation after step 5.

  • (optional) Verify if Samba now recognizes the -Driver

    +Driver
     root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
 	| grep -B2 -A5 mydrivername
 Printer Driver Info 3:
@@ -10068,7 +10066,7 @@ Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 Remember, this command greps for the name you did choose for the
 driver in step Six. This command must succeed before you can proceed.

  • Tell Samba which Printer should use these Driver -Files (setdriver)

    +Files (setdriver)
     root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
 Successfully set mysmbtstprn to driver mydrivername
 
    
@@ -10079,7 +10077,7 @@ setdriver command to succeed. The only pre-conditions are:
 enumdrivers must find the driver and
 enumprinters must find the printer.

  • (optional) Verify if Samba has this Association -recognized

    +recognized
     root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
   | grep driver
 drivername:[mydrivername]
@@ -10117,56 +10115,56 @@ Printer Driver Info 3:
      comment:[mysmbtstprn]
 
 
    
-
+
 Compare these results with the ones from steps 2 and 3. Note that
 every single of these commands show the driver is installed.  Even
 the enumprinters command now lists the driver
-on the "description" line.
+on the "description" line.

  • (optional) Tickle the Driver into a correct Device Mode

    - + You certainly know how to install the driver on the client. In case you are not particularly familiar with Windows, here is a short recipe: browse the Network Neighbourhood, go to the Samba server, look for the shares. You should see all shared Samba printers. Double-click on the one in question. The driver should get installed, and the network connection set up. An alternative way is to -open the "Printers (and Faxes)" folder, right-click on the printer in -question and select "Connect" or "Install". As a result, a new printer -should have appeared in your client's local "Printers (and Faxes)" -folder, named something like "printersharename on Sambahostname". +open the "Printers (and Faxes)" folder, right-click on the printer in +question and select "Connect" or "Install". As a result, a new printer +should have appeared in your client's local "Printers (and Faxes)" +folder, named something like "printersharename on Sambahostname".

    It is important that you execute this step as a Samba printer admin (as defined in smb.conf). Here is another method to do this on Windows XP. It uses a commandline, which you may type -into the "DOS box" (type root's smbpassword when prompted): +into the "DOS box" (type root's smbpassword when prompted): 

    -C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
-			\\sambacupsserver\mysmbtstprn"
+C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
+			\\sambacupsserver\mysmbtstprn"

    -Change any printer setting once (like changing "portrait" to - "landscape"), click Apply; change the setting +Change any printer setting once (like changing "portrait" to + "landscape"), click Apply; change the setting back.

  • Install the Printer on a Client -("Point'n'Print")

    -C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
+("Point'n'Print")
    +C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
 
    
 If it doesn't work it could be a permission problem with the
 [print$] share.

  • Thirteenth Step (optional): Print a Test Page

    -C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
+C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"

    Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again and march to the printer.

  • Fourteenth Step (recommended): Study the Test Page

    Hmmm.... just kidding! By now you know everything about printer installations and you don't need to read a word. Just put it in a -frame and bolt it to the wall with the heading "MY FIRST -RPCCLIENT-INSTALLED PRINTER" - why not just throw it away! +frame and bolt it to the wall with the heading "MY FIRST +RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!

  • Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your Success

    -root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
-

    • Troubleshooting revisited

    +root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd +

    Troubleshooting revisited

    The setdriver command will fail, if in Samba's mind the queue is not already there. You had promising messages about the: 

    @@ -10174,14 +10172,14 @@ already there. You had promising messages about the:
  Printer Driver ABC successfully installed.

    -after the "adddriver" parts of the procedure? But you are also seeing +after the "adddriver" parts of the procedure? But you are also seeing a disappointing message like this one beneath? 

     
  result was NT_STATUS_UNSUCCESSFUL

    - + It is not good enough that you can see the queue in CUPS, using the lpstat -p ir85wm command. A @@ -10189,14 +10187,14 @@ bug in most recent versions of Samba prevents the proper update of the queuelist. The recognition of newly installed CUPS printers fails unless you re-start Samba or send a HUP to all smbd processes. To verify if this is the reason why Samba doesn't -execute the setdriver command successfully, check if Samba "sees" +execute the setdriver command successfully, check if Samba "sees" the printer: -

    +
     root# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
         printername:[ir85wm]
 
    
 An alternative command could be this: 
-
    +
     root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
         cmd = getprinter ir85wm
         flags:[0x800000]
@@ -10206,20 +10204,20 @@ An alternative command could be this:
 
    
 BTW, you can use these commands, plus a few more, of course,
 to install drivers on remote Windows NT print servers too!
-

    The printing *.tdb Files

    - - - - - - - - - - - - - +

    The printing *.tdb Files

    + + + + + + + + + + + + + Some mystery is associated with the series of files with a tdb-suffix appearing in every Samba installation. They are connections.tdb, @@ -10234,10 +10232,10 @@ tdb-suffix appearing in every Samba installation. They are ntprinters.tdb, sessionid.tdb and secrets.tdb. What is their purpose? -

    Trivial DataBase Files

    +

    Trivial DataBase Files

    A Windows NT (Print) Server keeps track of all information needed to serve its duty toward its clients by storing entries in the Windows -"Registry". Client queries are answered by reading from the registry, +"Registry". Client queries are answered by reading from the registry, Administrator or user configuration settings are saved by writing into the Registry. Samba and UNIX obviously don't have such a kind of Registry. Samba instead keeps track of all client related information in a @@ -10247,10 +10245,10 @@ or /var/lock/samba/ . The printing related files are ntprinters.tdb, printing.tdb,ntforms.tdb and ntdrivers.tdb. -

    Binary Format

    +

    Binary Format

    *.tdb files are not human readable. They are -written in a binary format. "Why not ASCII?", you may ask. "After all, -ASCII configuration files are a good and proofed tradition on UNIX." +written in a binary format. "Why not ASCII?", you may ask. "After all, +ASCII configuration files are a good and proofed tradition on UNIX." -- The reason for this design decision by the Samba Team is mainly performance. Samba needs to be fast; it runs a separate smbd process for each client connection, in some @@ -10260,7 +10258,7 @@ same time. The file format of Samba's *.tdb files allows for this provision. Many smbd processes may write to the same *.tdb file at the same time. This wouldn't be possible with pure ASCII files. -

    Losing *.tdb Files

    +

    Losing *.tdb Files

    It is very important that all *.tdb files remain consistent over all write and read accesses. However, it may happen that these files do get corrupted. (A @@ -10270,7 +10268,7 @@ etc.). In cases of trouble, a deletion of the old printing-related *.tdb files may be the only option. You need to re-create all print related setup after that. Or you have made a backup of the *.tdb files in time. -

    Using tdbbackup

    +

    Using tdbbackup

    Samba ships with a little utility which helps the root user of your system to back up your *.tdb files. If you run it with no argument, it prints a little usage message: @@ -10299,10 +10297,10 @@ ntprinters.tdb sessionid.tdb -rw------- 1 root root 40960 May 2 03:44 printing.tdb -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak -

    CUPS Print Drivers from Linuxprinting.org

    +

    CUPS Print Drivers from Linuxprinting.org

    CUPS ships with good support for HP LaserJet type printers. You can install the generic driver as follows: -

    +
     root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
 
    
 The -m switch will retrieve the
@@ -10312,8 +10310,8 @@ not-yet-installed-PPDs, which CUPS typically stores in
 -P /path/to/your.ppd.
 
    
 The generic laserjet.ppd however does not support every special option
-for every LaserJet-compatible model. It constitutes a sort of "least
-denominator" of all the models. If for some reason it is ruled out to
+for every LaserJet-compatible model. It constitutes a sort of "least
+denominator" of all the models. If for some reason it is ruled out to
 you to pay for the commercially available ESP Print Pro drivers, your
 first move should be to consult the database on http://www.linuxprinting.org/printer_list.cgi.
 Linuxprinting.org has excellent recommendations about which driver is
@@ -10321,9 +10319,9 @@ best used for each printer. Its database is kept current by the
 tireless work of Till Kamppeter from MandrakeSoft, who is also the
 principal author of the foomatic-rip utility.
 
    Note
    
-
-The former "cupsomatic" concept is now be replaced by the new, much
-more powerful "foomatic-rip". foomatic-rip is the successor of
+
+The former "cupsomatic" concept is now be replaced by the new, much
+more powerful "foomatic-rip". foomatic-rip is the successor of
 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
 to the Foomatic-3.0 database:http://www.linuxprinting.org/driver_list.cgi.
 If you upgrade to foomatic-rip, don't forget to also upgrade to the
@@ -10332,7 +10330,7 @@ not work with PPDs generated for the old cupsomatic. The new-style
 PPDs are 100% compliant to the Adobe PPD specification. They are
 intended to be used by Samba and the cupsaddsmb utility also, to
 provide the driver files for the Windows clients also!
-
    foomatic-rip and Foomatic explained
    
+
    foomatic-rip and Foomatic explained
    
 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
 to create their printing related software (which, BTW, works on all
 UNIXes and on Mac OS X or Darwin too). It is not known as well as it
@@ -10349,63 +10347,63 @@ its Foomatic<
 database. Currently there are 245 drivers
 in the database: many drivers support various models, and many models
 may be driven by different drivers; it's your choice!
-
    690 "perfect" Printers
    
-At present there are 690 devices dubbed as working "perfectly", 181
-"mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
+
    690 "perfect" Printers
    
+At present there are 690 devices dubbed as working "perfectly", 181
+"mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
 that most of these are non-PostScript models (PostScript printers are
 automatically supported supported by CUPS to perfection, by using
 their own manufacturer-provided Windows-PPD...), and that a
-multifunctional device never qualifies as working "perfectly" if it
+multifunctional device never qualifies as working "perfectly" if it
 doesn't also scan and copy and fax under GNU/Linux: then this is a
 truly astonishing achievement. Three years ago the number was not
-more than 500, and Linux or UNIX "printing" at the time wasn't
+more than 500, and Linux or UNIX "printing" at the time wasn't
 anywhere near the quality it is today!
-
    How the "Printing HOWTO" started it all
    
+
    How the "Printing HOWTO" started it all
    
 A few years ago Grant Taylor
 started it all. The roots of today's Linuxprinting.org are in the
 first Linux Printing
 HOWTO which he authored. As a side-project to this document,
 which served many Linux users and admins to guide their first steps in
 this complicated and delicate setup (to a scientist, printing is
-"applying a structured deposition of distinct patterns of ink or toner
-particles on paper substrates" ;-), he started to
+"applying a structured deposition of distinct patterns of ink or toner
+particles on paper substrates" ;-), he started to
 build in a little Postgres database with information about the
 hardware and driver zoo that made up Linux printing of the time. This
 database became the core component of today's Foomatic collection of
 tools and data. In the meantime it has moved to an XML representation
 of the data.
-
    Foomatic's strange Name
    
-"Why the funny name?", you ask. When it really took off, around spring
+
    Foomatic's strange Name
    
+"Why the funny name?", you ask. When it really took off, around spring
 2000, CUPS was far less popular than today, and most systems used LPD,
-LPRng or even PDQ to print. CUPS shipped with a few generic "drivers"
+LPRng or even PDQ to print. CUPS shipped with a few generic "drivers"
 (good for a few hundred different printer models). These didn't
 support many device-specific options. CUPS also shipped with its own
-built-in rasterization filter ("pstoraster", derived from
+built-in rasterization filter ("pstoraster", derived from
 Ghostscript). On the other hand, CUPS provided brilliant support for
 controlling all printer options through
-standardized and well-defined "PPD files" (PostScript Printers
+standardized and well-defined "PPD files" (PostScript Printers
 Description files). Plus, CUPS was designed to be easily extensible.
 
    
 Grant already had in his database a respectable compilation
-of facts about a many more printers, and the Ghostscript "drivers"
+of facts about a many more printers, and the Ghostscript "drivers"
 they run with. His idea, to generate PPDs from the database info
 and use them to make standard Ghostscript filters work within CUPS,
-proved to work very well. It also "killed several birds with one
-stone":
+proved to work very well. It also "killed several birds with one
+stone":
 
    • It made all current and future Ghostscript filter
 developments available for CUPS;
    • It made available a lot of additional printer models
-to CUPS users (because often the "traditional" Ghostscript way of
+to CUPS users (because often the "traditional" Ghostscript way of
 printing was the only one available);
    • It gave all the advanced CUPS options (web interface,
 GUI driver configurations) to users wanting (or needing) to use
-Ghostscript filters.
    cupsomatic, pdqomatic, lpdomatic, directomatic
    
+Ghostscript filters.
    cupsomatic, pdqomatic, lpdomatic, directomatic
    
 CUPS worked through a quickly-hacked up filter script named cupsomatic.
 cupsomatic ran the printfile through Ghostscript, constructing
 automatically the rather complicated command line needed. It just
 required to be copied into the CUPS system to make it work. To
-"configure" the way cupsomatic controls the Ghostscript rendering
+"configure" the way cupsomatic controls the Ghostscript rendering
 process, it needs a CUPS-PPD. This PPD is generated directly from the
 contents of the database. For CUPS and the respective printer/filter
-combo another Perl script named "CUPS-O-Matic" did the PPD
+combo another Perl script named "CUPS-O-Matic" did the PPD
 generation. After that was working, Grant implemented within a few
 days a similar thing for two other spoolers. Names chosen for the
 config-generator scripts were PDQ-O-Matic
@@ -10423,25 +10421,25 @@ printers. He also developed the support for other spoolers, like
 PPR (via ppromatic),
 GNUlpr and
 LPRng (both via an extended
-lpdomatic) and "spoolerless" printing (directomatic)....
+lpdomatic) and "spoolerless" printing (directomatic)....
 
    
-So, to answer your question: "Foomatic" is the general name for all
-the overlapping code and data behind the "*omatic" scripts.... --
+So, to answer your question: "Foomatic" is the general name for all
+the overlapping code and data behind the "*omatic" scripts.... --
 Foomatic up to versions 2.0.x required (ugly) Perl data structures
 attached the Linuxprinting.org PPDs for CUPS. It had a different
-"*omatic" script for every spooler, as well as different printer
+"*omatic" script for every spooler, as well as different printer
 configuration files..
-
    The Grand Unification
-achieved...
    
+
    The Grand Unification
+achieved...
    
 This all has changed in Foomatic versions 2.9 (Beta) and released as
-"stable" 3.0. This has now achieved the convergence of all *omatic
+"stable" 3.0. This has now achieved the convergence of all *omatic
 scripts: it is called the foomatic-rip.
 This single script is the unification of the previously different
 spooler-specific *omatic scripts. foomatic-rip is used by all the
 different spoolers alike. Because foomatic-rip can read PPDs (both the
 original PostScript printer PPDs and the Linuxprinting.org-generated
 ones), all of a sudden all supported spoolers can have the power of
-PPDs at their disposal; users only need to plug "foomatic-rip" into
+PPDs at their disposal; users only need to plug "foomatic-rip" into
 their system.... For users there is improved media type and source
 support; paper sizes and trays are easier to configure.
 
    
@@ -10467,7 +10465,7 @@ sizes for many printers; and it will support printing on media drawn
 from different paper trays within the same job (in both cases: even
 where there is no support for this from Windows-based vendor printer
 drivers).
-
    Driver Development outside
    
+
    Driver Development outside
    
 Most driver development itself does not happen within
 Linuxprinting.org. Drivers are written by independent maintainers.
 Linuxprinting.org just pools all the information, and stores it in its
@@ -10490,9 +10488,9 @@ effort, started by Michael Sweet (also lead developer for CUPS), now
 directed by Robert Krawitz, which has achieved an amazing level of
 photo print quality (many Epson users swear that its quality is
 better than the vendor drivers provided by Epson for the Microsoft
-platforms). This currently supports 522 models.
    Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
+platforms). This currently supports 522 models.
    Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
 commercial UNIX
    
-Linuxprinting.org today is the one-stop "shop" to download printer
+Linuxprinting.org today is the one-stop "shop" to download printer
 drivers. Look for printer information and tutorials
 or solve printing problems in its popular forums.  But
 it's not just for GNU/Linux: users and admins of commercial UNIX
@@ -10511,17 +10509,17 @@ of the Foomatic project.
 Till Kamppeter from MandrakeSoft is doing an excellent job in his
 spare time to maintain Linuxprinting.org and Foomatic. So if you use
 it often, please send him a note showing your appreciation.
-
    Foomatic Database generated PPDs
    
+
    Foomatic Database generated PPDs
    
 The Foomatic database is an amazing piece of ingenuity in itself. Not
 only does it keep the printer and driver information, but it is
-organized in a way that it can generate "PPD" files "on the fly" from
+organized in a way that it can generate "PPD" files "on the fly" from
 its internal XML-based datasets. While these PPDs are modelled to the
-Adobe specification of "PostScript Printer Descriptions" (PPDs), the
+Adobe specification of "PostScript Printer Descriptions" (PPDs), the
 Linuxprinting.org/Foomatic-PPDs don't normally drive PostScript
 printers: they are used to describe all the bells and whistles you
 could ring or blow on an Epson Stylus inkjet, or a HP Photosmart or
-what-have-you. The main "trick" is one little additional line, not
-envisaged by the PPD specification, starting with the "*cupsFilter"
+what-have-you. The main "trick" is one little additional line, not
+envisaged by the PPD specification, starting with the "*cupsFilter"
 keyword: it tells the CUPS daemon how to proceed with the PostScript
 print file (old-style Foomatic-PPDs named the
 cupsomatic filter script, while the new-style
@@ -10532,12 +10530,12 @@ filter or internal device setting it should ask from Ghostscript to
 convert the PostScript printjob into a raster format ready for the
 target device. This usage of PPDs to describe the options of non-PS
 printers was the invention of the CUPS developers. The rest is easy:
-GUI tools (like KDE's marvellous "kprinter",
-or the GNOME "gtklp", "xpp" and the CUPS
+GUI tools (like KDE's marvellous "kprinter",
+or the GNOME "gtklp", "xpp" and the CUPS
 web interface) read the PPD too and use this information to present
 the available settings to the user as an intuitive menu selection.
-

    foomatic-rip and Foomatic-PPD Download and Installation

    -Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus" +

    foomatic-rip and Foomatic-PPD Download and Installation

    +Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus" compatible printer in CUPS (note that recent distributions of SuSE, UnitedLinux and Mandrake may ship with a complete package of Foomatic-PPDs plus the foomatic-rip utility. going directly to @@ -10549,11 +10547,11 @@ Linuxprinting.org ensures you to get the latest driver/PPD files): link.

  • You'll arrive at a page listing all drivers working with this model (for all printers, there will always be one recommended driver. Try this one -first).

  • In our case ("HP LaserJet 4 Plus"), we'll arrive here: +first).

  • In our case ("HP LaserJet 4 Plus"), we'll arrive here: http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus -

  • The recommended driver is "ljet4".

  • There are several links provided here. You should +

  • The recommended driver is "ljet4".

  • There are several links provided here. You should visit them all, if you are not familiar with the Linuxprinting.org -database.

  • There is a link to the database page for the "ljet4": +database.

  • There is a link to the database page for the "ljet4": http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 On the driver's page, you'll find important and detailed information about how to use that driver within the various available @@ -10563,7 +10561,7 @@ setup instructions for CUPS (http://www.linuxprinting.org/pdq-doc.html), LPD, LPRng and GNUlpr (http://www.linuxprinting.org/lpd-doc.html) as well as PPR (http://www.linuxprinting.org/ppr-doc.html) -or "spooler-less" printing (http://www.linuxprinting.org/direct-doc.html +or "spooler-less" printing (http://www.linuxprinting.org/direct-doc.html ).

  • You can view the PPD in your browser through this link: http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1

  • You can also (most importantly) @@ -10573,18 +10571,18 @@ model and the driver; this is, once installed, working transparently for the user. Later you'll only need to choose resolution, paper size etc. from the web-based menu, or from the print dialog GUI, or from the commandline.

  • Should you have ended up on the driver's page (http://www.linuxprinting.org/show_driver.cgi?driver=ljet4), -you can choose to use the "PPD-O-Matic" online PPD generator -program.

  • Select the exact model and check either "download" or -"display PPD file" and click on "Generate PPD file".

  • If you save the PPD file from the browser view, please -don't use "cut'n'past" (since it could possibly damage line endings -and tabs, which makes the PPD likely to fail its duty), but use "Save -as..." in your browser's menu. (Best is to use the "download" option +you can choose to use the "PPD-O-Matic" online PPD generator +program.

  • Select the exact model and check either "download" or +"display PPD file" and click on "Generate PPD file".

  • If you save the PPD file from the browser view, please +don't use "cut'n'past" (since it could possibly damage line endings +and tabs, which makes the PPD likely to fail its duty), but use "Save +as..." in your browser's menu. (Best is to use the "download" option from the web page directly).

  • Another very interesting part on each driver page is the Show execution details button. If you select your printer model and click that button, you will get displayed a complete Ghostscript command line, enumerating all options available for that driver/printermodel combo. This is a great way to -"Learn Ghostscript By Doing". It is also an excellent "cheat sheet" +"Learn Ghostscript By Doing". It is also an excellent "cheat sheet" for all experienced users who need to re-construct a good command line for that damn printing script, but can't remember the exact syntax. ;-)

  • Some time during your visit to Linuxprinting.org, save @@ -10596,9 +10594,9 @@ cupsd).

  • Then install the printer with a suitable commandline, e.g.: 

     root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-

  • Note again this: for all the new-style "Foomatic-PPDs" -from Linuxprinting.org, you also need a special "CUPS filter" named -"foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0 +

  • Note again this: for all the new-style "Foomatic-PPDs" +from Linuxprinting.org, you also need a special "CUPS filter" named +"foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0

  • The foomatic-rip Perlscript itself also makes some interesting reading (http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1), because it is very well documented by Till's inline comments (even @@ -10606,8 +10604,8 @@ non-Perl hackers will learn quite a bit about printing by reading it... ;-)

  • Save foomatic-rip either directly in /usr/lib/cups/filter/foomatic-rip or somewhere in your $PATH (and don't forget to make it world-executable). Again, -don't save by "copy'n'paste" but use the appropriate link, or the -"Save as..." menu item in your browser.

  • If you save foomatic-rip in your $PATH, create a symlink: +don't save by "copy'n'paste" but use the appropriate link, or the +"Save as..." menu item in your browser.

  • If you save foomatic-rip in your $PATH, create a symlink: cd /usr/lib/cups/filter/ ; ln -s `which foomatic-rip`. For CUPS to discover this new available filter at startup, you need to re-start @@ -10623,18 +10621,18 @@ data should look like and which printer commands to embed into the data stream.

    You need: -

    • A "foomatic+something" PPD -- but it this not enough +

      • A "foomatic+something" PPD -- but it this not enough to print with CUPS (it is only one important -component)

      • The "foomatic-rip" filter script (Perl) in +component)

      • The "foomatic-rip" filter script (Perl) in /usr/lib/cups/filters/

      • Perl to make foomatic-rip run

      • Ghostscript (because it is doing the main work, controlled by the PPD/foomatic-rip combo) to produce the raster data fit for your printermodel's consumption

      • Ghostscript must (depending on -the driver/model) contain support for a certain "device", representing -the selected "driver" for your model (as shown by "gs --h")

      • foomatic-rip needs a new version of PPDs (PPD versions +the driver/model) contain support for a certain "device", representing +the selected "driver" for your model (as shown by "gs +-h")

      • foomatic-rip needs a new version of PPDs (PPD versions produced for cupsomatic don't work with -foomatic-rip).

    • Page Accounting with CUPS

    -Often there are questions regarding "print quotas" wherein Samba users +foomatic-rip).

    Page Accounting with CUPS

    +Often there are questions regarding "print quotas" wherein Samba users (that is, Windows clients) should not be able to print beyond a certain amount of pages or data volume per day, week or month. This feature is dependent on the real print subsystem you're using. @@ -10642,28 +10640,28 @@ Samba's part is always to receive the job files from the clients (filtered or unfiltered) and hand it over to this printing subsystem.

    -Of course one could "hack" things with one's own scripts. But then -there is CUPS. CUPS supports "quotas" which can be based on sizes of +Of course one could "hack" things with one's own scripts. But then +there is CUPS. CUPS supports "quotas" which can be based on sizes of jobs or on the number of pages or both, and are spanning any time period you want. -

    Setting up Quotas

    +

    Setting up Quotas

    This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter": -

    +assuming an existing printer named "quotaprinter":
+
     root# lpadmin -p quotaprinter -o job-quota-period=604800 \
 	-o job-k-limit=1024 -o job-page-limit=100
 
    
 This would limit every single user to print 100 pages or 1024 KB of
 data (whichever comes first) within the last 604,800 seconds ( = 1
 week).
-

    Correct and incorrect Accounting

    +

    Correct and incorrect Accounting

    For CUPS to count correctly, the printfile needs to pass the CUPS -"pstops" filter, otherwise it uses a "dummy" count of "1". Some +"pstops" filter, otherwise it uses a "dummy" count of "1". Some printfiles don't pass it (eg: image files) but then those are mostly 1 page jobs anyway. This also means that proprietary drivers for the target printer running on the client computers and CUPS/Samba, which -then spool these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too! +then spool these files as "raw" (i.e. leaving them untouched, not +filtering them), will be counted as "1-pagers" too!

    You need to send PostScript from the clients (i.e. run a PostScript driver there) to have the chance to get accounting done. If the @@ -10671,28 +10669,28 @@ printer is a non-PostScript model, you need to let CUPS do the job to convert the file to a print-ready format for the target printer. This will be working for currently about 1,000 different printer models, see the driver list at linuxprinting.org/. -

    Adobe and CUPS PostScript Drivers for Windows Clients

    +

    Adobe and CUPS PostScript Drivers for Windows Clients

    Before CUPS-1.1.16 your only option was to use the Adobe PostScript Driver on the Windows clients. The output of this driver was not -always passed through the "pstops" filter on the CUPS/Samba side, and +always passed through the "pstops" filter on the CUPS/Samba side, and therefore was not counted correctly (the reason is that it often, -depending on the "PPD" being used, wrote a "PJL"-header in front of +depending on the "PPD" being used, wrote a "PJL"-header in front of the real PostScript which caused CUPS to skip pstops and go directly -to the "pstoraster" stage). +to the "pstoraster" stage).

    -From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for -Windows NT/2K/XP clients" (which is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). It does +From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for +Windows NT/2K/XP clients" (which is tagged in the download area of +http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). It does not work for Win9x/ME clients. But it guarantees: -

    • to not write an PJL-header

    • to still read and support all PJL-options named in the -driver PPD with its own means

    • that the file will pass through the "pstops" filter +

      • to not write an PJL-header

      • to still read and support all PJL-options named in the +driver PPD with its own means

      • that the file will pass through the "pstops" filter on the CUPS/Samba server

      • to page-count correctly the printfile

      You can read more about the setup of this combination in the manpage -for "cupsaddsmb" (which is only present with CUPS installed, and only +for "cupsaddsmb" (which is only present with CUPS installed, and only current from CUPS 1.1.16). -

    The page_log File Syntax

    -These are the items CUPS logs in the "page_log" for every +

    The page_log File Syntax

    +These are the items CUPS logs in the "page_log" for every single page of a job:

    • Printer name

    • User name

    • Job ID

    • Time of printing

    • the page number

    • the number of copies

    • a billing information string (optional)

    • the host which sent the job (included since version @@ -10706,64 +10704,64 @@ infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13 infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13 DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33

      -This was job ID "401", printed on "infotec_IS2027" by user "kurt", a -64-page job printed in 3 copies and billed to "#marketing", sent -from IP address 10.160.50.13. The next job had ID "402", was sent by -user "boss" from IP address 10.160.51.33,printed from one page 440 -copies and is set to be billed to "finance-dep". -

    Possible Shortcomings

    +This was job ID "401", printed on "infotec_IS2027" by user "kurt", a +64-page job printed in 3 copies and billed to "#marketing", sent +from IP address 10.160.50.13. The next job had ID "402", was sent by +user "boss" from IP address 10.160.51.33,printed from one page 440 +copies and is set to be billed to "finance-dep". +

    Possible Shortcomings

    What flaws or shortcomings are there with this quota system?

    • the ones named above (wrongly logged job in case of printer hardware failure, etc.)

    • in reality, CUPS counts the job pages that are being processed in software (that is, going through the -"RIP") rather than the physical sheets successfully leaving the +"RIP") rather than the physical sheets successfully leaving the printing device. Thus if there is a jam while printing the 5th sheet out -of 1000 and the job is aborted by the printer, the "page count" will +of 1000 and the job is aborted by the printer, the "page count" will still show the figure of 1000 for that job

    • all quotas are the same for all users (no flexibility to give the boss a higher quota than the clerk), no support for groups

    • no means to read out the current balance or the -"used-up" number of current quota

    • a user having used up 99 sheets of 100 quota will +"used-up" number of current quota

    • a user having used up 99 sheets of 100 quota will still be able to send and print a 1,000 sheet job

    • a user being denied a job because of a filled-up quota doesn't get a meaningful error message from CUPS other than -"client-error-not-possible".

    Future Developments

    +"client-error-not-possible".

    Future Developments

    This is the best system currently available, and there are huge improvements under development for CUPS 1.2: -

    • page counting will go into the "backends" (these talk +

      • page counting will go into the "backends" (these talk directly to the printer and will increase the count in sync with the actual printing process: thus a jam at the 5th sheet will lead to a stop in the counting)

      • quotas will be handled more flexibly

      • probably there will be support for users to inquire -their "accounts" in advance

      • probably there will be support for some other tools -around this topic

    Other Accounting Tools

    +their "accounts" in advance

  • probably there will be support for some other tools +around this topic

    • Other Accounting Tools

    PrintAnalyzer, pyKota, printbill, LogReport. -

    Additional Material

    +

    Additional Material

    A printer queue with no PPD associated to it is a -"raw" printer and all files will go directly there as received by the -spooler. The exceptions are file types "application/octet-stream" -which need "passthrough feature" enabled. "Raw" queues don't do any +"raw" printer and all files will go directly there as received by the +spooler. The exceptions are file types "application/octet-stream" +which need "passthrough feature" enabled. "Raw" queues don't do any filtering at all, they hand the file directly to the CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation: lpd://, socket://, +(as in the "device URI" notation: lpd://, socket://, smb://, ipp://, http://, parallel:/, serial:/, usb:/ etc.)

    -"cupsomatic"/Foomatic are not native CUPS drivers +"cupsomatic"/Foomatic are not native CUPS drivers and they don't ship with CUPS. They are a Third Party add-on, developed at Linuxprinting.org. As such, they are a brilliant hack to make all models (driven by Ghostscript drivers/filters in traditional spoolers) also work via CUPS, with the same (good or bad!) quality as -in these other spoolers. "cupsomatic" is only a vehicle to execute a +in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript commandline at that stage in the CUPS filtering chain, -where "normally" the native CUPS "pstoraster" filter would kick -in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS +where "normally" the native CUPS "pstoraster" filter would kick +in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS away and re-directs it to go through Ghostscript. CUPS accepts this, because the associated CUPS-O-Matic-/Foomatic-PPD specifies: 

    -  *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
+  *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"

    This line persuades CUPS to hand the file to cupsomatic, once it has successfully converted it to the MIME type -"application/vnd.cups-postscript". This conversion will not happen for +"application/vnd.cups-postscript". This conversion will not happen for Jobs arriving from Windows which are auto-typed -"application/octet-stream", with the according changes in +"application/octet-stream", with the according changes in /etc/cups/mime.types in place.

    CUPS is widely configurable and flexible, even regarding its filtering @@ -10775,7 +10773,7 @@ mechanism. Another workaround in some situations would be to have in

    This would prevent all Postscript files from being filtered (rather, they will through the virtual nullfilter -denoted with "-"). This could only be useful for PS printers. If you +denoted with "-"). This could only be useful for PS printers. If you want to print PS code on non-PS printers (provided they support ASCII text printing) an entry as follows could be useful: 

    @@ -10795,38 +10793,38 @@ unwanted PJL. This would need to conform to CUPS filter design
 username, jobtitle, copies, print options and possibly the
 filename). It would be installed as world executable into
 /usr/lib/cups/filters/ and will be called by CUPS
-if it encounters a MIME type "application/vnd.cups-postscript".
+if it encounters a MIME type "application/vnd.cups-postscript".
 
    
 CUPS can handle -o job-hold-until=indefinite.
-This keeps the job in the queue "on hold". It will only be printed
+This keeps the job in the queue "on hold". It will only be printed
 upon manual release by the printer operator. This is a requirement in
-many "central reproduction departments", where a few operators manage
+many "central reproduction departments", where a few operators manage
 the jobs of hundreds of users on some big machine, where no user is
 allowed to have direct access (such as when the operators often need
 to load the proper paper type before running the 10,000 page job
 requested by marketing for the mailing, etc.).
-

    Auto-Deletion or Preservation of CUPS Spool Files

    -Samba print files pass through two "spool" directories. One is the -incoming directory managed by Samba, (set in the path = /var/spool/samba directive in the +

    Auto-Deletion or Preservation of CUPS Spool Files

    +Samba print files pass through two "spool" directories. One is the +incoming directory managed by Samba, (set in the path = /var/spool/samba directive in the [printers] section of smb.conf). The other is the spool directory of your UNIX print subsystem. For CUPS it is normally /var/spool/cups/, as set by the cupsd.conf directive RequestRoot /var/spool/cups. -

    CUPS Configuration Settings explained

    +

    CUPS Configuration Settings explained

    Some important parameter settings in the CUPS configuration file cupsd.conf are:

    PreserveJobHistory Yes

    This keeps some details of jobs in cupsd's mind (well it keeps the -"c12345", "c12346" etc. files in the CUPS spool directory, which do a +"c12345", "c12346" etc. files in the CUPS spool directory, which do a similar job as the old-fashioned BSD-LPD control files). This is set -to "Yes" as a default. +to "Yes" as a default.

    PreserveJobFiles Yes

    This keeps the job files themselves in cupsd's mind -(well it keeps the "d12345", "d12346" etc. files in the CUPS spool -directory...). This is set to "No" as the CUPS +(well it keeps the "d12345", "d12346" etc. files in the CUPS spool +directory...). This is set to "No" as the CUPS default. -

    "MaxJobs 500"

    +

    "MaxJobs 500"

    This directive controls the maximum number of jobs that are kept in memory. Once the number of jobs reaches the limit, the oldest completed job is automatically purged from the system to @@ -10835,42 +10833,42 @@ pending or active then the new job will be rejected. Setting the maximum to 0 disables this functionality. The default setting is 0.

    -(There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...) -

    Pre-conditions

    +(There are also additional settings for "MaxJobsPerUser" and +"MaxJobsPerPrinter"...) +

    Pre-conditions

    For everything to work as announced, you need to have three things: -

    • a Samba-smbd which is compiled against "libcups" (Check -on Linux by running "ldd `which smbd`")

    • a Samba-smb.conf setting of - printing = cups

    • another Samba-smb.conf setting of - printcap = cups

    Note

    +

    • a Samba-smbd which is compiled against "libcups" (Check +on Linux by running "ldd `which smbd`")

    • a Samba-smb.conf setting of + printing = cups

    • another Samba-smb.conf setting of + printcap = cups

    Note

    In this case all other manually set printing-related commands (like -print command, -lpq command, -lprm command, -lppause command or -lpresume command) are ignored and they should normally have no +print command, +lpq command, +lprm command, +lppause command or +lpresume command) are ignored and they should normally have no influence what-so-ever on your printing. -

    Manual Configuration

    -If you want to do things manually, replace the printing = cups -by printing = bsd. Then your manually set commands may work -(haven't tested this), and a print command = lp -d %P %s; rm %s" +

    Manual Configuration

    +If you want to do things manually, replace the printing = cups +by printing = bsd. Then your manually set commands may work +(haven't tested this), and a print command = lp -d %P %s; rm %s" may do what you need. -

    In Case of Trouble.....

    +

    In Case of Trouble.....

    If you have more problems, post the output of these commands to the CUPS or Samba mailing lists (choose the one which seems more relevant to your problem): 

     $ grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
+$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    (adapt paths as needed). These commands leave out the empty -lines and lines with comments, providing the "naked settings" in a +lines and lines with comments, providing the "naked settings" in a compact way. Don't forget to name the CUPS and Samba versions you are using! This saves bandwidth and makes for easier readability for experts (and you are expecting experts to read them, right? ;-) -

    Printing from CUPS to Windows attached +

    Printing from CUPS to Windows attached Printers

    From time to time the question arises, how you can print to a Windows attached printer @@ -10878,12 +10876,12 @@ From time to time the question arises, how you can print from Windows host to printer would be done by USB or parallel cable, but this doesn't matter to Samba. From here only an SMB connection needs to be opened to the Windows host. Of course, this -printer must be "shared" first. As you have learned by now, CUPS uses +printer must be "shared" first. As you have learned by now, CUPS uses backends to talk to printers and other servers. To talk to Windows shared printers you need to use the smb (surprise, surprise!) backend. Check if this is in the CUPS backend directory. This resides usually in -/usr/lib/cups/backend/. You need to find a "smb" +/usr/lib/cups/backend/. You need to find a "smb" file there. It should be a symlink to smbspool which file must exist and be executable: 

    @@ -10914,7 +10912,7 @@ If this symlink doesn't exist, create it:
 smbspool has been written by Mike Sweet from the CUPS folks.  It is
 included and ships with Samba. It may also be used with print
 subsystems other than CUPS, to spool jobs to Windows printer shares. To
-set up printer "winprinter" on CUPS, you need to have a "driver" for
+set up printer "winprinter" on CUPS, you need to have a "driver" for
 it. Essentially this means to convert the print data on the CUPS/Samba
 host to a format that the printer can digest (the Windows host is
 unable to convert any files you may send).  This also means you should
@@ -10947,41 +10945,41 @@ doesn't require a password! Printing will only work if you have a
 working netbios name resolution up and running. Note that this is a
 feature of CUPS and you don't necessarily need to have smbd running
 (but who wants that? :-).
-

    More CUPS filtering Chains

    +

    More CUPS filtering Chains

    The following diagrams reveal how CUPS handles print jobs.

    Figure 19.17. Filtering chain 1

    Filtering chain 1

    Figure 19.18. Filtering chain with cupsomatic

    Filtering chain with cupsomatic

    Note

    Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to CUPS and ESP PrintPro plug-in where rastertosomething is noted. -

    Common Errors

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 -chars (or "8 plus 3 chars suffix") max; otherwise the driver files +

    Common Errors

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 +chars (or "8 plus 3 chars suffix") max; otherwise the driver files won't get transferred when you want to download them from -Samba.

    "cupsaddsmb" keeps asking for root password in - neverending loop

    Have you security = user? Have +Samba.

    "cupsaddsmb" keeps asking for root password in + neverending loop

    Have you security = user? Have you used smbpasswd to give root a Samba account? You can do 2 things: open another terminal and execute smbpasswd -a root to create the account, and continue with entering the password into the first terminal. Or break out of the loop by hitting ENTER twice (without trying to type a -password).

    "cupsaddsmb" gives "No PPD file for printer..." +password).

    "cupsaddsmb" gives "No PPD file for printer..." message while PPD file is present

    Have you enabled printer sharing on CUPS? This means: do you have a <Location /printers>....</Location> section in CUPS server's cupsd.conf which doesn't deny access to -the host you run "cupsaddsmb" from? It could be +the host you run "cupsaddsmb" from? It could be an issue if you use cupsaddsmb remotely, or if you use it with a -h parameter: cupsaddsmb -H sambaserver -h cupsserver -v printername.

    Is your -"TempDir" directive in +"TempDir" directive in cupsd.conf set to a valid value and is it writeable? -

    Client can't connect to Samba printer

    Use smbstatus to check which user +

    Client can't connect to Samba printer

    Use smbstatus to check which user you are from Samba's point of view. Do you have the privileges to write into the [print$] -share?

    Can't reconnect to Samba under new account - from Win2K/XP

    Once you are connected as the "wrong" user (for -example as "nobody", which often occurs if you have -map to guest = bad user), Windows Explorer will not accept an +share?

    Can't reconnect to Samba under new account + from Win2K/XP

    Once you are connected as the "wrong" user (for +example as "nobody", which often occurs if you have +map to guest = bad user), Windows Explorer will not accept an attempt to connect again as a different user. There won't be any byte transfered on the wire to Samba, but still you'll see a stupid error message which makes you think that Samba has denied access. Use @@ -10989,56 +10987,56 @@ message which makes you think that Samba has denied access. Use PIDs. You still can't re-connect and get the dreaded You can't connect with a second account from the same machine message, as soon as you are trying? And you -don't see any single byte arriving at Samba (see logs; use "ethereal") +don't see any single byte arriving at Samba (see logs; use "ethereal") indicating a renewed connection attempt? Shut all Explorer Windows. This makes Windows forget what it has cached in its memory as established connections. Then re-connect as the right user. Best method is to use a DOS terminal window and first do net use z: \\GANDALF\print$ /user:root. Check with smbstatus that you are connected under a -different account. Now open the "Printers" folder (on the Samba server +different account. Now open the "Printers" folder (on the Samba server in the Network Neighbourhood), right-click the printer in question and select -Connect...

    Avoid being connected to the Samba server as the - "wrong" user

    You see per smbstatus that you are -connected as user "nobody"; while you wanted to be "root" or -"printeradmin"? This is probably due to -map to guest = bad user, which silently connects you under the guest account, +Connect...

    Avoid being connected to the Samba server as the + "wrong" user

    You see per smbstatus that you are +connected as user "nobody"; while you wanted to be "root" or +"printeradmin"? This is probably due to +map to guest = bad user, which silently connects you under the guest account, when you gave (maybe by accident) an incorrect username. Remove -map to guest, if you want to prevent -this.

    Upgrading to CUPS drivers from Adobe drivers on - NT/2K/XP clients gives problems

    First delete all "old" Adobe-using printers. Then -delete all "old" Adobe drivers. (On Win2K/XP, right-click in -background of "Printers" folder, select "Server Properties...", select -tab "Drivers" and delete here).

    Can't use "cupsaddsmb" on Samba server which is - a PDC

    Do you use the "naked" root user name? Try to do it +map to guest, if you want to prevent +this.

    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems

    First delete all "old" Adobe-using printers. Then +delete all "old" Adobe drivers. (On Win2K/XP, right-click in +background of "Printers" folder, select "Server Properties...", select +tab "Drivers" and delete here).

    Can't use "cupsaddsmb" on Samba server which is + a PDC

    Do you use the "naked" root user name? Try to do it this way: cupsaddsmb -U DOMAINNAME\\root -v printername> (note the two backslashes: the first one is -required to "escape" the second one).

    Deleted Win2K printer driver is still shown

    Deleting a printer on the client won't delete the +required to "escape" the second one).

    Deleted Win2K printer driver is still shown

    Deleting a printer on the client won't delete the driver too (to verify, right-click on the white background of the -"Printers" folder, select "Server Properties" and click on the -"Drivers" tab). These same old drivers will be re-used when you try to +"Printers" folder, select "Server Properties" and click on the +"Drivers" tab). These same old drivers will be re-used when you try to install a printer with the same name. If you want to update to a new driver, delete the old ones first. Deletion is only possible if no -other printer uses the same driver.

    Win2K/XP "Local Security - Policies"

    Local Security Policies may not -allow the installation of unsigned drivers. "Local Security Policies" +other printer uses the same driver.

    Win2K/XP "Local Security + Policies"

    Local Security Policies may not +allow the installation of unsigned drivers. "Local Security Policies" may not allow the installation of printer drivers at -all.

    WinXP clients: "Administrator can not install - printers for all local users"

    Windows XP handles SMB printers on a "per-user" basis. +all.

    WinXP clients: "Administrator can not install + printers for all local users"

    Windows XP handles SMB printers on a "per-user" basis. This means every user needs to install the printer himself. To have a printer available for everybody, you might want to use the built-in IPP client capabilities of WinXP. Add a printer with the print path of http://cupsserver:631/printers/printername. -Still looking into this one: maybe a "logon script" could +Still looking into this one: maybe a "logon script" could automatically install printers for all -users.

    "Print Change Notify" functions on - NT-clients

    For "print change notify" functions on NT++ clients, -these need to run the "Server" service first (re-named to +users.

    "Print Change Notify" functions on + NT-clients

    For "print change notify" functions on NT++ clients, +these need to run the "Server" service first (re-named to File & Print Sharing for MS Networks in -XP).

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print +XP).

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print Restriction Policy (this restriction doesn't apply to -"Administrator" or "Power User" groups of users). In Group Policy +"Administrator" or "Power User" groups of users). In Group Policy Object Editor: go to User Configuration, Administrative Templates, Control Panel, Printers. The policy is automatically set to @@ -11046,14 +11044,14 @@ Printers. The policy is automatically set to and Print to machines in their Forest . You probably need to change it to Disabled or Users can only Point and Print to these servers in order to make -driver downloads from Samba possible.

    Print options for all users can't be set on Win2K/XP

    How are you doing it? I bet the wrong way (it is not +driver downloads from Samba possible.

    Print options for all users can't be set on Win2K/XP

    How are you doing it? I bet the wrong way (it is not very easy to find out, though). There are 3 different ways to bring you to a dialog that seems to set everything. All three dialogs look the same. Only one of them does what you intend. You need to be Administrator or Print Administrator to do this for all users. Here is how I do in on XP: -

    1. The first "wrong" way: +

      1. The first "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer @@ -11061,7 +11059,7 @@ folder.

        3. Right-click on the printer select in context menu Printing Preferences...

        4. Look at this dialog closely and remember what it looks like.

        -

      2. The second "wrong" way: +

      3. The second "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer (remoteprinter on @@ -11070,28 +11068,28 @@ cupshost) and select in the context menu tab

        3. Click on the button Printing Preferences...

        4. A new dialog opens. Keep this dialog open and go back to the parent dialog.

        -

      4. The third, the "correct" way: (should you do +

      5. The third, the "correct" way: (should you do this from the beginning, just carry out steps 1. and 2. from second -"way" above) +"way" above)

        1. Click on the Advanced -tab. (Hmmm... if everything is "Grayed Out", then you are not logged +tab. (Hmmm... if everything is "Grayed Out", then you are not logged in as a user with enough privileges).

        2. Click on the Printing Defaults... button.

        3. On any of the two new tabs, click on the Advanced... button.

        4. A new dialog opens. Compare this one to the other, -identical looking one from "B.5" or A.3".

        +identical looking one from "B.5" or A.3".

    Do you see any difference? I don't either... However, only the last -one, which you arrived at with steps "C.1.-6." will save any settings +one, which you arrived at with steps "C.1.-6." will save any settings permanently and be the defaults for new users. If you want all clients to get the same defaults, you need to conduct these steps as -Administrator (printer admin in +Administrator (printer admin in smb.conf) before a client downloads the driver (the clients can later set their own per-user defaults by following the procedures A. or B. -above).

    Most common blunders in driver +above).

    Most common blunders in driver settings on Windows clients

    Don't use Optimize for Speed: use Optimize for Portability instead (Adobe PS Driver) Don't use @@ -11104,63 +11102,63 @@ printer (Adobe PS Driver). For TrueType Download Options choose Outline. Use PostScript Level 2, if you are having trouble with a non-PS printer, and if -there is a choice.

    cupsaddsmb does not work +there is a choice.

    cupsaddsmb does not work with newly installed printer

    Symptom: the last command of cupsaddsmb doesn't complete successfully: cmd = setdriver printername printername result was NT_STATUS_UNSUCCESSFUL then possibly the printer was not yet -"recognized" by Samba. Did it show up in Network +"recognized" by Samba. Did it show up in Network Neighbourhood? Did it show up in rpcclient hostname -c 'enumprinters'? Restart smbd (or send a kill -HUP to all processes listed by smbstatus and try -again.

    Permissions on +again.

    Permissions on /var/spool/samba/ get reset after each reboot

    Have you by accident set the CUPS spool directory to the same location? (RequestRoot /var/spool/samba/ in cupsd.conf or the other way round: /var/spool/cups/ is set as -path> in the [printers] +path> in the [printers] section). These must be different. Set RequestRoot /var/spool/cups/ in -cupsd.conf and path = +cupsd.conf and path = /var/spool/samba in the [printers] section of smb.conf. Otherwise cupsd will sanitize permissions to its spool directory with each restart, and -printing will not work reliably.

    Printer named "lp" +printing will not work reliably.

    Printer named "lp" intermittently swallows jobs and spits out completely different -ones

    It is a very bad idea to name any printer "lp". This +ones

    It is a very bad idea to name any printer "lp". This is the traditional UNIX name for the default printer. CUPS may be set -up to do an automatic creation of "Implicit Classes". This means, to +up to do an automatic creation of "Implicit Classes". This means, to group all printers with the same name to a pool of devices, and loadbalancing the jobs across them in a round-robin fashion. Chances -are high that someone else has an "lp" named printer too. You may +are high that someone else has an "lp" named printer too. You may receive his jobs and send your own to his device unwittingly. To have tight control over the printer names, set BrowseShortNames -No. It will present any printer as "printername@cupshost" +No. It will present any printer as "printername@cupshost" then, giving you a better control over what may happen in a large -networked environment.

    Location of Adobe PostScript driver files necessary for "cupsaddsmb"

    Use smbclient to connect to any +networked environment.

    Location of Adobe PostScript driver files necessary for "cupsaddsmb"

    Use smbclient to connect to any Windows box with a shared PostScript printer: smbclient //windowsbox/print\$ -U guest. You can navigate to the W32X86/2 subdir to mget ADOBE* and other files or to WIN40/0 to do the same. -- Another option is to download the *.exe packaged -files from the Adobe website.

    An Overview of the CUPS Printing Processes

    Figure 19.19. CUPS Printing Overview

    CUPS Printing Overview

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan

    Features and Benefits

    +files from the Adobe website.

    An Overview of the CUPS Printing Processes

    Figure 19.19. CUPS Printing Overview

    CUPS Printing Overview

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan

    Features and Benefits

    Since Samba-3, there is support for stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. This chapter covers all the modules that come with the samba source and references to some external modules. -

    Discussion

    +

    Discussion

    If not supplied with your platform distribution binary Samba package you may have problems to compile these modules, as shared libraries are compiled and linked in different ways on different systems. They currently have been tested against GNU/Linux and IRIX.

    To use the VFS modules, create a share similar to the one below. The -important parameter is the vfs objects parameter where +important parameter is the vfs objects parameter where you can list one or more VFS modules by name. For example, to log all access to files and put deleted files in a recycle bin: -

    Example 20.1. smb.conf with VFS modules

    [audit]
    comment = Audited /data directory
    path = /data
    vfs objects = audit recycle
    writeable = yes
    browseable = yes

    +

    Example 20.1. smb.conf with VFS modules

    [audit]
    comment = Audited /data directory
    path = /data
    vfs objects = audit recycle
    writeable = yes
    browseable = yes

    The modules are used in the order in which they are specified.

    @@ -11172,29 +11170,29 @@ directory in the root directory of the samba installation (usually Some modules can be used twice for the same share. This can be done using a configuration similar to the one below. -

    Example 20.2. smb.conf with multiple VFS modules

    [test]
    comment = VFS TEST
    path = /data
    writeable = yes
    browseable = yes
    vfs objects = example:example1 example example:test
    example1: parameter = 1
    example: parameter = 5
    test: parameter = 7

    -

    Included modules

    audit

    +

    Example 20.2. smb.conf with multiple VFS modules

    [test]
    comment = VFS TEST
    path = /data
    writeable = yes
    browseable = yes
    vfs objects = example:example1 example example:test
    example1: parameter = 1
    example: parameter = 5
    test: parameter = 7

    +

    Included modules

    audit

    A simple module to audit file access to the syslog facility. The following operations are logged:

    • share

    • connect/disconnect

    • directory opens/create/remove

    • file open/close/rename/unlink/chmod

    -

    extd_audit

    +

    extd_audit

    This module is identical with the audit module above except that it sends audit logs to both syslog as well as the smbd log file/s. The loglevel for this module is set in the smb.conf file.

    The logging information that will be written to the smbd log file is controlled by - the log level parameter in smb.conf. The + the log level parameter in smb.conf. The following information will be recorded: -

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    fake_perms

    +

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    fake_perms

    This module was created to allow Roaming Profile files and directories to be set (on the Samba server under Unix) as read only. This module will if installed on the Profiles share will report to the client that the Profile files and directories are writable. This satisfies the client even though the files will never be overwritten as the client logs out or shuts down. -

    recycle

    +

    recycle

    A recycle-bin like module. When used any unlink call will be intercepted and files moved to the recycle directory instead of being deleted. This gives the same - effect as the "Recycle Bin" on Windows computers. + effect as the "Recycle Bin" on Windows computers.

    Supported options:

    recycle:repository

    Relative path of the directory where deleted files should be moved to

    recycle:keeptree

    Specifies whether the directory structure should be kept or if the files in the directory that is being @@ -11202,7 +11200,7 @@ This can be done using a configuration similar to the one below.

    recycle:versions

    If this option is set, two files with the same name that are deleted will both be kept in the recycle bin. Newer deleted versions - of a file will be called "Copy #x of filename".

    recycle:touch

    Specifies whether a file's access + of a file will be called "Copy #x of filename".

    recycle:touch

    Specifies whether a file's access date should be touched when the file is moved to the recycle bin.

    recycle:maxsize

    Files that are larger than the number of bytes specified by this parameter will @@ -11212,12 +11210,12 @@ This can be done using a configuration similar to the one below. these directories are deleted, they are not put into the recycle bin, but deleted in the regular way.

    recycle:noversions

    Opposite of recycle:versions. If both options are specified, this one takes precedence.

    -

    netatalk

    +

    netatalk

    A netatalk module, that will ease co-existence of samba and netatalk file sharing services.

    Advantages compared to the old netatalk module:

    • it doesn't care about creating of .AppleDouble forks, just keeps them in sync

    • if a share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    -

    VFS modules available elsewhere

    +

    VFS modules available elsewhere

    This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS tree for one reason or another (e.g. it is easy for the maintainer @@ -11225,14 +11223,14 @@ to have his or her own CVS tree).

    No statements about the stability or functionality of any module should be implied due to its presence here. -

    DatabaseFS

    +

    DatabaseFS

    URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    By Eric Lorimer.

    I have created a VFS module which implements a fairly complete read-only filesystem. It presents information from a database as a filesystem in a modular and generic way to allow different databases to be used (originally designed for organizing MP3s under directories such as - "Artists," "Song Keywords," etc... I have since applied it to a student + "Artists," "Song Keywords," etc... I have since applied it to a student roster database very easily). The directory structure is stored in the database itself and the module makes no assumptions about the database structure beyond the table it requires to run. @@ -11240,15 +11238,15 @@ should be implied due to its presence here. Any feedback would be appreciated: comments, suggestions, patches, etc... If nothing else, hopefully it might prove useful for someone else who wishes to create a virtual filesystem. -

    vscan

    URL: http://www.openantivirus.org/

    +

    vscan

    URL: http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which uses the VFS (virtual file system) features of Samba 2.2.x/3.0 alphaX. Of course, Samba has to be compiled with VFS support. samba-vscan supports various virus scanners and is maintained by Rainer Link. -

    Chapter 21. Winbind: Use of Domain Accounts

    Tim Potter

    Samba Team

    Andrew Tridgell

    Samba Team

    Naag Mummaneni

    Notes for Solaris

    John Trostel

    SNAP

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    27 June 2002

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning

    Features and Benefits

    +

    Chapter 21. Winbind: Use of Domain Accounts

    Tim Potter

    Samba Team

    Andrew Tridgell

    Samba Team

    Naag Mummaneni

    Notes for Solaris

    John Trostel

    SNAP

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    27 June 2002

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning

    Features and Benefits

    Integration of UNIX and Microsoft Windows NT through a unified logon has - been considered a "holy grail" in heterogeneous computing environments for + been considered a "holy grail" in heterogeneous computing environments for a long time.

    There is one other facility without which UNIX and Microsoft Windows network @@ -11280,7 +11278,7 @@ should be implied due to its presence here. If winbindd is not running, then smbd (which calls winbindd) will fall back to using purely local information from /etc/passwd and /etc/group and no dynamic mapping will be used. -

    Introduction

    It is well known that UNIX and Microsoft Windows NT have +

    Introduction

    It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and use different technologies for implementing them. This fact has made it difficult to integrate the two systems in a satisfactory @@ -11301,7 +11299,7 @@ should be implied due to its presence here. tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple and elegant solution to all three components of the unified logon - problem.

    What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by + problem.

    What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once this is done the UNIX box will see NT users and groups as if they were native UNIX users and groups, allowing the NT domain @@ -11314,7 +11312,7 @@ should be implied due to its presence here. (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely transparent.

    Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files + names as they would use "native" UNIX names. They can chown files so that they are owned by NT domain users or even login to the UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is that user and group names take the form DOMAIN\user and @@ -11325,7 +11323,7 @@ should be implied due to its presence here. to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing passwords between systems since all passwords are stored in a single - location (on the domain controller).

    Target Uses

    Winbind is targeted at organizations that have an + location (on the domain controller).

    Target Uses

    Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to @@ -11335,12 +11333,12 @@ should be implied due to its presence here. be used is as a central part of UNIX based appliances. Appliances that provide file and print services to Microsoft based networks will be able to use Winbind to provide seamless integration of - the appliance into the domain.

    How Winbind Works

    The winbind system is designed around a client/server + the appliance into the domain.

    How Winbind Works

    The winbind system is designed around a client/server architecture. A long running winbindd daemon listens on a UNIX domain socket waiting for requests to arrive. These requests are generated by the NSS and PAM clients and processed sequentially.

    The technologies used to implement winbind are described - in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway + in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -11353,7 +11351,7 @@ should be implied due to its presence here. users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user passwords. By directly querying a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.

    Microsoft Active Directory Services

    + NT account information onto UNIX user and group names.

    Microsoft Active Directory Services

    Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its 'Native Mode' protocols, rather than the NT4 RPC services. @@ -11362,7 +11360,7 @@ should be implied due to its presence here. same way as a Win2k client would, and in so doing provide a much more efficient and effective winbind implementation. -

    Name Service Switch

    The Name Service Switch, or NSS, is a feature that is +

    Name Service Switch

    The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information to be resolved from different sources. For example, a standalone @@ -11383,7 +11381,7 @@ should be implied due to its presence here. When a UNIX application makes a request to do a lookup the C library looks in /etc/nsswitch.conf for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names + example the "passwd" service type is used when user or group names are looked up. This config line specifies which implementations of that service should be tried and in what order. If the passwd config line is:

    @@ -11397,9 +11395,9 @@ passwd: files example
 		result to the application.
    This NSS interface provides a very easy way for Winbind 
 		to hook into the operating system. All that needs to be done 
 		is to put libnss_winbind.so in /lib/ 
-		then add "winbind" into /etc/nsswitch.conf at 
+		then add "winbind" into /etc/nsswitch.conf at 
 		the appropriate place. The C library will then call Winbind to 
-		resolve user and group names.

    Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, + resolve user and group names.

    Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different authentication methods for different system applications without @@ -11424,7 +11422,7 @@ passwd: files example is copied to /lib/security/ and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT + for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify @@ -11437,7 +11435,7 @@ passwd: files example time, winbind will have mapped all Windows NT users and groups to UNIX user ids and group ids.

    The results of this mapping are stored persistently in an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.

    Result Caching

    An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.

    Result Caching

    An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind uses a caching scheme based on the SAM sequence number supplied by NT domain controllers. User or group information returned @@ -11448,7 +11446,7 @@ passwd: files example the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information is discarded and up to date information is requested directly - from the PDC.

    Installation and Configuration

    Introduction

    + from the PDC.

    Installation and Configuration

    Introduction

    This section describes the procedures used to get winbind up and running. Winbind is capable of providing access and authentication control for Windows Domain users through an NT @@ -11469,7 +11467,7 @@ well for SAMBA services. SAMBA server, this HOWTO is for you. That said, I am no NT or PAM expert, so you may find a better or easier way to accomplish these tasks. -

    Requirements

    +

    Requirements

    If you have a Samba configuration file that you are currently using... BACK IT UP! If your system already uses PAM, back up the /etc/pam.d directory @@ -11496,7 +11494,7 @@ winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that means pam-0.74-22. For best results, it is helpful to also install the development packages in pam-devel-0.74-22. -

    Testing Things Out

    +

    Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all smbd, nmbd, and winbindd processes that may @@ -11507,7 +11505,7 @@ services, several pam libraries, and the /usr/doc and /usr/man entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. -

    Configure nsswitch.conf and the +

    Configure nsswitch.conf and the winbind libraries on Linux and Solaris

    The libraries needed to run the winbindd daemon through nsswitch need to be copied to their proper locations, so @@ -11542,7 +11540,7 @@ is faster (and you don't need to reboot) if you do it manually:

    This makes libnss_winbind available to winbindd and echos back a check to you. -

    NSS Winbind on AIX

    (This section is only for those running AIX)

    +

    NSS Winbind on AIX

    (This section is only for those running AIX)

    The winbind AIX identification module gets built as libnss_winbind.so in the nsswitch directory of the samba source. This file can be copied to /usr/lib/security, and the AIX naming convention would indicate that it @@ -11557,19 +11555,19 @@ supports identification, but there have been success reports using the standard winbind pam module for authentication. Use caution configuring loadable authentication modules as it is possible to make it impossible to logon to the system. More information about the AIX authentication -module API can be found at "Kernel Extensions and Device Support -Programming Concepts for AIX": +module API can be found at "Kernel Extensions and Device Support +Programming Concepts for AIX": Chapter 18. Loadable Authentication Module Programming Interface and more information on administering the modules at -"System Management Guide: Operating System and Devices". -

    Configure smb.conf

    +"System Management Guide: Operating System and Devices". +

    Configure smb.conf

    Several parameters are needed in the smb.conf file to control the behavior of winbindd. Configure smb.conf These are described in more detail in the winbindd(8) man page. My smb.conf file was modified to include the following entries in the [global] section: -

    Example 21.1. smb.conf for winbind set-up

    [global]
    ...
    # separate domain and username with '+', like DOMAIN+username
    winbind separator = +
    # use uids from 10000 to 20000 for domain users
    idmap uid = 10000-20000
    # use gids from 10000 to 20000 for domain groups
    winbind gid = 10000-20000
    # allow enumeration of winbind users and groups
    winbind enum users = yes
    winbind enum groups = yes
    # give winbind users a real shell (only needed if they have telnet access)
    template homedir = /home/winnt/%D/%U
    template shell = /bin/bash

    Join the SAMBA server to the PDC domain

    +

    Example 21.1. smb.conf for winbind set-up

    [global]
    ...
    # separate domain and username with '+', like DOMAIN+username
    winbind separator = +
    # use uids from 10000 to 20000 for domain users
    idmap uid = 10000-20000
    # use gids from 10000 to 20000 for domain groups
    winbind gid = 10000-20000
    # allow enumeration of winbind users and groups
    winbind enum users = yes
    winbind enum groups = yes
    # give winbind users a real shell (only needed if they have telnet access)
    template homedir = /home/winnt/%D/%U
    template shell = /bin/bash

    Join the SAMBA server to the PDC domain

    Enter the following command to make the SAMBA server join the PDC domain, where DOMAIN is the name of your Windows domain and Administrator is @@ -11577,10 +11575,10 @@ a domain user who has administrative privileges in the domain.

    root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator

    -The proper response to the command should be: "Joined the domain -DOMAIN" where DOMAIN +The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN is your DOMAIN name. -

    Start up the winbindd daemon and test it!

    +

    Start up the winbindd daemon and test it!

    Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of SAMBA start, but it is possible to test out just the winbind @@ -11622,7 +11620,7 @@ your PDC. For example, I get the following response: CEO+krbtgt CEO+TsInternetUser

    - Obviously, I have named my domain 'CEO' and my winbind separator is '+'. + Obviously, I have named my domain 'CEO' and my winbind separator is '+'.

    You can do the same sort of thing to get group information from the PDC: @@ -11651,7 +11649,7 @@ directories and default shells. The same thing can be done for groups with the command

    root# getent group -

    Fix the init.d startup scripts

    Linux

    +

    Fix the init.d startup scripts

    Linux

    The winbindd daemon needs to start up after the smbd and nmbd daemons are running. To accomplish this task, you need to modify the startup scripts of your system. @@ -11663,18 +11661,18 @@ startup script starts up smbd, 

     stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
         killproc smbd
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
         killproc nmbd
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Shutting down $KIND services: "
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
         killproc winbindd
         RETVAL3=$?
         [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
 		 rm -f /var/lock/subsys/smb
-        echo ""
+        echo ""
         return $RETVAL
 }
-
    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter for details.

    On Solaris, you need to modify the +

    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter for details.

    On Solaris, you need to modify the /etc/init.d/samba.server startup script. It usually only starts smbd and nmbd but should now start winbindd too. If you have samba installed in /usr/local/samba/bin, @@ -11736,12 +11734,12 @@ the file could contains something like this: pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server - case "$1" in + case "$1" in 'start') # @@ -11766,7 +11764,7 @@ the file could contains something like this: ;; *) - echo "Usage: /etc/init.d/samba.server { start | stop }" + echo "Usage: /etc/init.d/samba.server { start | stop }" ;; esac

    @@ -11780,11 +11778,11 @@ in the script above with: 

     	/usr/local/samba/bin/winbindd -B

    -

    Restarting

    +

    Restarting

    If you restart the smbd, nmbd, and winbindd daemons at this point, you should be able to connect to the samba server as a domain member just as if you were a local user. -

    Configure Winbind and PAM

    +

    Configure Winbind and PAM

    If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other services, keep reading. The pam configuration files need to be altered in @@ -11804,7 +11802,7 @@ your other pam security modules. On my RedHat system, this was the modules reside in /usr/lib/security.

    root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security -

    Linux/FreeBSD-specific PAM configuration

    +

    Linux/FreeBSD-specific PAM configuration

    The /etc/pam.d/samba file does not need to be changed. I just left this file as it was: 

    @@ -11831,7 +11829,7 @@ have individual directories for the domain users already present on
 the server, or change the home directory template to a general
 directory for all domain users.  These can be easily set using 
 the smb.conf global entry 
-template homedir.
+template homedir.
 
    
 The /etc/pam.d/ftp file can be changed 
 to allow winbind ftp access in a manner similar to the
@@ -11867,7 +11865,7 @@ above it, to disallow root logins over the network.  I also added a
 
    sufficient /lib/security/pam_unix.so use_first_pass
    
 line after the winbind.so line to get rid of annoying 
 double prompts for passwords.
-
    Solaris-specific configuration

    +

    Solaris-specific configuration

    The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but @@ -11875,7 +11873,7 @@ be sure of those changes because in the worst case it will leave your system nearly impossible to boot. 

     	#
-	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
 	#
 	# Copyright (c) 1996-1999, Sun Microsystems, Inc.
 	# All Rights Reserved.
@@ -11939,12 +11937,12 @@ annoying double prompts for passwords.
 
    
 Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.
-

    Conclusion

    The winbind system, through the use of the Name Service +

    Conclusion

    The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate Microsoft RPC calls have allowed us to provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.

    Common Errors

    Winbind has a number of limitations in its current + cost of running a mixed UNIX and NT network.

    Common Errors

    Winbind has a number of limitations in its current released version that we hope to overcome in future releases:

    • Winbind is currently only available for the Linux, Solaris, AIX and IRIX operating systems, although ports to other operating @@ -11959,18 +11957,18 @@ configured in the pam.conf. containing this information is corrupted or destroyed.

    • Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

    NSCD Problem Warning

    Note

    + instead up to the PDC to enforce.

    NSCD Problem Warning

    Note

    Do NOT under ANY circumstances run nscd on any system on which winbind is running.

    If nscd is running on the UNIX/Linux system, then even though NSSWITCH is correctly configured it will NOT be possible to resolve domain users and groups for file and directory controls. -

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    +

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    This section documents peripheral issues that are of great importance to network administrators who want to improve network resource access control, to automate the user environment, and to make their lives a little easier. -

    Features and Benefits

    +

    Features and Benefits

    Often the difference between a working network environment and a well appreciated one can best be measured by the little things that makes everything work more harmoniously. A key part of every network environment solution is the ability to remotely @@ -11980,7 +11978,7 @@ network operations.

    This chapter presents information on each of these area. They are placed here, and not in other chapters, for ease of reference. -

    Remote Server Administration

    +

    Remote Server Administration

    How do I get 'User Manager' and 'Server Manager'?

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', @@ -11994,12 +11992,12 @@ Click here to download the archived file Windows NT 4.0 version of the 'User Manager for Domains' and 'Server Manager' are available from Microsoft via ftp from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE -

    Remote Desktop Management

    +

    Remote Desktop Management

    There are a number of possible remote desktop management solutions that range from free through costly. Do not let that put you off. Sometimes the most costly solutions is the most cost effective. In any case, you will need to draw your own conclusions as to which is the best tool in your network environment. -

    Remote Management from NoMachines.Com

    +

    Remote Management from NoMachines.Com

    The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003. It is presented in slightly edited form (with author details omitted for privacy reasons). The entire answer is reproduced below with some comments removed. @@ -12018,7 +12016,7 @@ is the best tool in your network environment. > Any ideas/experience would be appreciated :)

    - Answer provided: Check out the new offer from NoMachine, "NX" software: + Answer provided: Check out the new offer from NoMachine, "NX" software: http://www.nomachine.com/.

    It implements a very easy-to-use interface to the remote X protocol as @@ -12031,18 +12029,18 @@ is the best tool in your network environment.

    I could test drive their (public) RedHat machine in Italy, over a loaded internet connection, with enabled thumbnail previews in KDE konqueror - which popped up immediately on "mouse-over". From inside that (remote X) + which popped up immediately on "mouse-over". From inside that (remote X) session I started a rdesktop session on another, a Windows XP machine. To test the performance, I played Pinball. I am proud to announce here that my score was 631750 points at first try...

    - NX performs better on my local LAN than any of the other "pure" + NX performs better on my local LAN than any of the other "pure" connection methods I am using from time to time: TightVNC, rdesktop or remote X. It is even faster than a direct crosslink connection between two nodes.

    I even got sound playing from the remote X app to my local boxes, and - had a working "copy'n'paste" from an NX window (running a KDE session + had a working "copy'n'paste" from an NX window (running a KDE session in Italy) to my Mozilla mailing agent... These guys are certainly doing something right!

    @@ -12087,7 +12085,7 @@ is the best tool in your network environment. NoMachine are encouraging and offering help to OSS/Free Software implementations for such a frontend too, even if it means competition to them (they have written to this effect even to the LTSP, KDE and GNOME developer mailing lists) -

    Network Logon Script Magic

    +

    Network Logon Script Magic

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates to John Terpstra.

    @@ -12129,31 +12127,31 @@ This is the genlogon.pl file: # Log client connection #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); - open LOG, ">>/var/log/samba/netlogon.log"; - print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; + open LOG, ">>/var/log/samba/netlogon.log"; + print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; close LOG; # Start generating logon script - open LOGON, ">/shared/netlogon/$ARGV[0].bat"; - print LOGON "\@ECHO OFF\r\n"; + open LOGON, ">/shared/netlogon/$ARGV[0].bat"; + print LOGON "\@ECHO OFF\r\n"; # Connect shares just use by Software Development group - if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") + if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") { - print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; + print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; } # Connect shares just use by Technical Support staff - if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support") + if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support") { - print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n"; + print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n"; } # Connect shares just used by Administration staff - If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin") + If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin") { - print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n"; - print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n"; + print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n"; + print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n"; } # Now connect Printers. We handle just two or three users a little @@ -12163,13 +12161,13 @@ This is the genlogon.pl file: if ($ARGV[0] eq 'jim' || $ARGV[0] eq 'yvonne') { - print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; + print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n"; + print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; } else { - print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; + print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n"; + print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; } # All done! Close the output file. @@ -12177,7 +12175,7 @@ This is the genlogon.pl file:

    Those wishing to use more elaborate or capable logon processing system should check out the following sites: -

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

    +

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

    Printers may be added automatically during logon script processing through the use of: 

    @@ -12185,20 +12183,20 @@ Printers may be added automatically during logon script processing through the u

    See the documentation in the Microsoft knowledgebase article no: 189105. -

    Common Errors

    +

    Common Errors

    The information provided in this chapter has been reproduced from postings on the samba@samba.org mailing list. No implied endorsement or recommendation is offered. Administrators should conduct their own evaluation of alternatives and are encouraged to draw their own conclusions. -

    Chapter 23. System and Account Policies

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    +

    Chapter 23. System and Account Policies

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    This chapter summarises the current state of knowledge derived from personal practice and knowledge from samba mailing list subscribers. Before reproduction of posted information effort has been made to validate the information provided. Where additional information was uncovered through this validation it is provided also. -

    Features and Benefits

    +

    Features and Benefits

    When MS Windows NT3.5 was introduced the hot new topic was the ability to implement Group Policies for users and group. Then along came MS Windows NT4 and a few sites -started to adopt this capability. How do we know that? By way of the number of "booboos" +started to adopt this capability. How do we know that? By way of the number of "booboos" (or mistakes) administrators made and then requested help to resolve.

    By the time that MS Windows 2000 and Active Directory was released, administrators @@ -12216,7 +12214,7 @@ network client workstations.

    A tool new to Samba may become an important part of the future Samba Administrators' arsenal. The editreg tool is described in this document. -

    Creating and Managing System Policies

    +

    Creating and Managing System Policies

    Under MS Windows platforms, particularly those following the release of MS Windows NT4 and MS Windows 95) it is possible to create a type of file that would be placed in the NETLOGON share of a domain controller. As the client logs onto the network @@ -12247,11 +12245,11 @@ advisable to read the documentation available from Microsoft's web site regardin Implementing Profiles and Policies in Windows NT 4.0 available from Microsoft. There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies". +be read and understood. Try searching on the Microsoft web site for "Group Policies".

    What follows is a very brief discussion with some helpful notes. The information provided here is incomplete - you are warned. -

    Windows 9x/Me Policies

    +

    Windows 9x/Me Policies

    You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. It can be found on the Original full product Win98 installation CD under tools/reskit/netadmin/poledit. Install this using the @@ -12277,7 +12275,7 @@ here is incomplete - you are warned. grouppol.inf. Log off and on again a couple of times and see if Win98 picks up group policies. Unfortunately this needs to be done on every Win9x/Me machine that uses group policies. -

    Windows NT4 Style Policy Files

    +

    Windows NT4 Style Policy Files

    To create or edit ntconfig.pol you must use the NT Server Policy Editor, poledit.exe which is included with NT4 Server but not NT Workstation. There is a Policy Editor on a NT4 @@ -12298,14 +12296,14 @@ here is incomplete - you are warned. be extracted as well. It is also possible to downloaded the policy template files for Office97 and get a copy of the policy editor. Another possible location is with the Zero Administration Kit available for download from Microsoft. -

    Registry Spoiling

    +

    Registry Spoiling

    With NT4 style registry based policy changes, a large number of settings are not automatically reversed as the user logs off. Since the settings that were in the NTConfig.POL file were applied to the client machine registry and that apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences down-stream and the administrator must be extremely careful not to lock out the ability to manage the machine at a later date. -

    MS Windows 200x / XP Professional Policies

    +

    MS Windows 200x / XP Professional Policies

    Windows NT4 System policies allows setting of registry parameters specific to users, groups and computers (client workstations) that are members of the NT4 style domain. Such policy file will work with MS Windows 2000 / XP clients also. @@ -12342,7 +12340,7 @@ here is incomplete - you are warned. to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows the administrator to also set filters over the policy settings. No such equivalent capability exists with NT4 style policy files. -

    Administration of Win2K / XP Policies

    +

    Administration of Win2K / XP Policies

    Instead of using the tool called The System Policy Editor, commonly called Poledit (from the executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console (MMC) snap-in as follows:

    1. @@ -12368,7 +12366,7 @@ here is incomplete - you are warned. The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you use this powerful tool. Please refer to the resource kit manuals for specific usage information. -

    Managing Account/User Policies

    +

    Managing Account/User Policies

    Policies can define a specific user's settings or the settings for a group of users. The resulting policy file contains the registry settings for all users, groups, and computers that will be using the policy file. Separate policy files for each user, group, or computer are not necessary. @@ -12395,7 +12393,7 @@ MS Windows NT4/200x/XP allows per domain as well as per user account restriction Common restrictions that are frequently used includes:

    • Logon Hours

    • Password Aging

    • Permitted Logon from certain machines only

    • Account type (Local or Global)

    • User Rights

    -

    Samba Editreg Toolset

    +

    Samba Editreg Toolset

    A new tool called editreg is under development. This tool can be used to edit registry files (called NTUser.DAT) that are stored in user and group profiles. NTConfig.POL files have the same structure as the NTUser.DAT file and can be editted using @@ -12404,17 +12402,17 @@ Common restrictions that are frequently used includes: extended capabilities. It is proving difficult to realise this capability, so do not be surprised if this feature does not materialise. Formal capabilities will be announced at the time that this tool is released for production use. -

    Windows NT4/200x

    +

    Windows NT4/200x

    The tools that may be used to configure these types of controls from the MS Windows environment are: The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). Under MS Windows 200x/XP this is done using the Microsoft Management Console (MMC) with appropriate - "snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. -

    Samba PDC

    + "snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. +

    Samba PDC

    With a Samba Domain Controller, the new tools for managing of user account and policy information includes: smbpasswd, pdbedit, net, rpcclient. The administrator should read the man pages for these tools and become familiar with their use. -

    System Startup and Logon Processing Overview

    +

    System Startup and Logon Processing Overview

    The following attempts to document the order of processing of system and user policies following a system reboot and as part of the user logon:

    1. @@ -12444,10 +12442,10 @@ reboot and as part of the user logon:

    2. The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 Domain) machine (system) policies are applied at start-up, User policies are applied at logon. -

    Common Errors

    +

    Common Errors

    Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following collection demonstrates only basic issues. -

    Policy Does Not Work

    +

    Policy Does Not Work

    “We have created the config.pol file and put it in the NETLOGON share. It has made no difference to our Win XP Pro machines, they just don't see it. IT worked fine with Win 98 but does not work any longer since we upgraded to Win XP Pro. Any hints?” @@ -12455,7 +12453,7 @@ work any longer since we upgraded to Win XP Pro. Any hints?” Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based platforms. You need to use the NT4 Group Policy Editor to create a file called NTConfig.POL so that it is in the correct format for your MS Windows XP Pro clients. -

    Chapter 24. Desktop Profile Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    +

    Chapter 24. Desktop Profile Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for some administrators.

    @@ -12468,7 +12466,7 @@ problem to others. In particular, users of mobile computing tools, where often t be a sustained network connection, are often better served by purely Local Profiles. This chapter provides information to help the Samba administrator to deal with those situations also. -

    Roaming Profiles

    Warning

    +

    Roaming Profiles

    Warning

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how @@ -12481,9 +12479,9 @@ profiles are restricted to being stored in the user's home directory.

    Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, including a separate field for the location of the user's profiles. -

    Samba Configuration for Profile Handling

    +

    Samba Configuration for Profile Handling

    This section documents how to configure Samba for MS Windows client profile support. -

    NT4/200x User Profiles

    +

    NT4/200x User Profiles

    To support Windows NT4/200x clients, in the [global] section of smb.conf set the following (for example):

    @@ -12504,8 +12502,8 @@ semantics of %L and %N, as well as %U and %u. MS Windows NT/2K clients at times do not disconnect a connection to a server between logons. It is recommended to NOT use the homes meta-service name as part of the profile share path. -

    Windows 9x / Me User Profiles

    - To support Windows 9x / Me clients, you must use the logon home parameter. Samba has +

    Windows 9x / Me User Profiles

    + To support Windows 9x / Me clients, you must use the logon home parameter. Samba has now been fixed so that net use /home now works as well, and it, too, relies on the logon home parameter.

    @@ -12519,11 +12517,11 @@ of your home directory called .profiles (thus making t Not only that, but net use /home will also work, because of a feature in Windows 9x / Me. It removes any directory stuff off the end of the home directory area and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for logon home. -

    Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    +specified \\%L\%U for logon home. +

    Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example: -

    logon home = \\%L\%u\.profiles
    logon path = \\%L\profiles\%u

    Disabling Roaming Profile Support

    +logon home and logon path parameters. For example: +

    logon home = \\%L\%u\.profiles
    logon path = \\%L\profiles\%u

    Disabling Roaming Profile Support

    A question often asked is “How may I enforce use of local profiles?” or “How do I disable Roaming Profiles?”

    @@ -12558,15 +12556,15 @@ profiles. The specifics of how to convert a local profile to a roaming profile, or a roaming profile to a local one vary according to the version of MS Windows you are running. Consult the Microsoft MS Windows Resource Kit for your version of Windows for specific information. -

    Windows Client Profile Configuration Information

    Windows 9x / Me Profile Setup

    +

    Windows Client Profile Configuration Information

    Windows 9x / Me Profile Setup

    When a user first logs in on Windows 9X, the file user.DAT is created, as are folders Start Menu, Desktop, Programs and Nethood. These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options preserve case = yes, short preserve case = yes and -case sensitive = no in order to maintain capital letters in shortcuts +options preserve case = yes, short preserve case = yes and +case sensitive = no in order to maintain capital letters in shortcuts in any of the profile folders.

    The user.DAT file contains all the user's preferences. If you wish to @@ -12603,7 +12601,7 @@ will inform you that The user has not logged on befor Do you wish to save the user's preferences?. Select yes.

    Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the logon path +to examine the contents of the directory specified in the logon path on the samba server and verify that the Desktop, Start Menu, Programs and Nethood folders have been created.

    @@ -12623,7 +12621,7 @@ on the samba server.

    If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time". +they will be told that they are logging in "for the first time".

    Warning

    Before deleting the contents of the directory listed in the ProfilePath (this is likely to be @@ -12634,7 +12632,7 @@ they will be told that they are logging in "for the first time".

    This will have the effect of removing the local (read-only hidden system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. + local "desktop", "nethood", "start menu" and "programs" folders.

    1. instead of logging in under the [user, password, domain] dialog, press escape. @@ -12652,7 +12650,7 @@ they will be told that they are logging in "for the first time".

    2. log off the windows 9x / Me client.

    3. - check the contents of the profile path (see logon path described + check the contents of the profile path (see logon path described above), and delete the user.DAT or user.MAN file for the user, making a backup if required.

    @@ -12664,14 +12662,14 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces provided with Windows NT4/200x server, and see what the differences are with the equivalent samba trace. -

    Windows NT4 Workstation

    +

    Windows NT4 Workstation

    When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified -through the logon path parameter. +through the logon path parameter.

    There is a parameter that is now available for use with NT Profiles: -logon drive. This should be set to H: or any other drive, and -should be used in conjunction with the new logon home parameter. +logon drive. This should be set to H: or any other drive, and +should be used in conjunction with the new logon home parameter.

    The entry for the NT4 profile is a _directory_ not a file. The NT help on profiles mentions that a directory is also created with a .PDS @@ -12693,7 +12691,7 @@ turns a profile into a mandatory one.

    The case of the profile is significant. The file must be called NTuser.DAT or, for a mandatory profile, NTuser.MAN. -

    Windows 2000/XP Professional

    +

    Windows 2000/XP Professional

    You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows:

    1. @@ -12709,7 +12707,7 @@ profile on the MS Windows workstation as follows:

    2. In the Permitted to use box, click on the Change button.

    3. - Click on the 'Look in" area that lists the machine name, when you click + Click on the 'Look in" area that lists the machine name, when you click here it will open up a selection box. Click on the domain to which the profile must be accessible.

      Note

      You will need to log on if a logon box opens up. Eg: In the connect as: DOMAIN\root, password: mypassword.

    4. @@ -12739,10 +12737,10 @@ the following (N.B. I don't know for sure that this will work in the same way as a domain group policy):

    5. On the XP workstation log in with an Administrator account. -

    6. Click: Start, Run

    7. Type: mmc

    8. Click: OK

    9. A Microsoft Management Console should appear.

    10. Click: File, Add/Remove Snap-in..., Add

    11. Double-Click: Group Policy

    12. Click: Finish, Close

    13. Click: OK

    14. In the "Console Root" window:

    15. Expand: Local Computer Policy, Computer Configuration, +

    16. Click: Start, Run

    17. Type: mmc

    18. Click: OK

    19. A Microsoft Management Console should appear.

    20. Click: File, Add/Remove Snap-in..., Add

    21. Double-Click: Group Policy

    22. Click: Finish, Close

    23. Click: OK

    24. In the "Console Root" window:

    25. Expand: Local Computer Policy, Computer Configuration, Administrative Templates, System, User Profiles

    26. Double-Click: Do not check for user ownership of Roaming Profile Folders

    27. Select: Enabled

    28. Click: OK

    29. Close the whole console. You do not need to save the settings (this refers to the console settings rather than the policies you have - changed).

    30. Reboot

    Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    + changed).

  • Reboot

    • Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    Sharing of desktop profiles between Windows versions is NOT recommended. Desktop profiles are an evolving phenomenon and profiles for later versions of MS Windows clients add features that may interfere with earlier versions @@ -12754,17 +12752,17 @@ on again with the newer version of MS Windows.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home. +that need to be common are logon path and +logon home.

    If you have this set up correctly, you will find separate user.DAT and NTuser.DAT files in the same profile directory. -

    Profile Migration from Windows NT4/200x Server to Samba

    +

    Profile Migration from Windows NT4/200x Server to Samba

    There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the profile be stored on a samba server, or any other SMB server, as long as that SMB server supports encrypted passwords. -

    Windows NT4 Profile Management Tools

    +

    Windows NT4 Profile Management Tools

    Unfortunately, the Resource Kit information is specific to the version of MS Windows NT4/200x. The correct resource kit is required for each platform.

    @@ -12774,20 +12772,20 @@ On your NT4 Domain Controller, right click on My Computer< select the tab labelled User Profiles.

  • Select a user profile you want to migrate and click on it. -

    Note

    I am using the term "migrate" loosely. You can copy a profile to +

    Note

    I am using the term "migrate" loosely. You can copy a profile to create a group profile. You can give the user 'Everyone' rights to the profile you copy this to. That is what you need to do, since your samba domain is not a member of a trust relationship with your NT4 PDC.

  • Click the Copy To button.

  • In the box labelled Copy Profile to add your new path, eg: c:\temp\foobar

  • Click on the button Change in the Permitted to use box.

  • Click on the group 'Everyone' and then click OK. This closes the 'choose user' box.

  • Now click OK.

    • Follow the above for every profile you need to migrate. -

    Side bar Notes

    +

    Side bar Notes

    You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

    moveuser.exe

    +this. Read the man page.

    moveuser.exe

    The W2K professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account domain to change, and/or the user name to change. -

    Get SID

    +

    Get SID

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.

    @@ -12800,7 +12798,7 @@ users who have logged on to this computer. (To find the profile information for the user whose locally cached profile you want to move, find the SID for the user with the GetSID.exe utility.) Inside of the appropriate user's subkey, you will see a string value named ProfileImagePath. -

    Mandatory profiles

    +

    Mandatory profiles

    A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. During the user's session it may be possible to change the desktop environment, but as the user logs out all changes made will be lost. If it is desired to NOT allow the @@ -12816,7 +12814,7 @@ file in the copied profile and rename it to NTUser.MAN.

    For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to affect a mandatory profile. -

    Creating/Managing Group Profiles

    +

    Creating/Managing Group Profiles

    Most organisations are arranged into departments. There is a nice benefit in this fact since usually most users in a department will require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the @@ -12826,19 +12824,19 @@ profile is assigned access rights for the user group that needs to be given acce to the group profile.

    The next step is rather important. Please note: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned +to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned the now modified profile.

    Note

    Be careful with group profiles, if the user who is a member of a group also has a personal profile, then the result will be a fusion (merge) of the two. -

    Default Profile for Windows Users

    +

    Default Profile for Windows Users

    MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom a profile does not already exist. Armed with a knowledge of where the default profile is located on the Windows workstation, and knowing which registry keys affect the path from which the default profile is created, it is possible to modify the default profile to one that has been optimised for the site. This has significant administrative advantages. -

    MS Windows 9x/Me

    +

    MS Windows 9x/Me

    To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System Policy Editor or change the registry directly.

    @@ -12849,8 +12847,8 @@ select User Profiles, click on the enable box. Do

    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. -

    How User Profiles Are Handled in Windows 9x / Me?

    +"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. +

    How User Profiles Are Handled in Windows 9x / Me?

    When a user logs on to a Windows 9x / Me machine, the local profile path, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked for an existing entry for that user: @@ -12866,7 +12864,7 @@ If a User Profile is not found in either location, the Default User Profile from machine is used and is copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user's local profile. If the user has a roaming profile, the changes are written to the user's profile on the server. -

    MS Windows NT4 Workstation

    +

    MS Windows NT4 Workstation

    On MS Windows NT4 the default user profile is obtained from the location %SystemRoot%\Profiles which in a default installation will translate to C:\WinNT\Profiles. Under this directory on a clean install there will be @@ -12910,7 +12908,7 @@ also remain stored in the same way, unless the following registry key is created 

     HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
-winlogon\"DeleteRoamingCache"=dword:00000001
+winlogon\"DeleteRoamingCache"=dword:00000001

    In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be @@ -12929,7 +12927,7 @@ are controlled by entries on Windows NT4 is:

    The above hive key contains a list of automatically managed folders. The default entries are:

    -

    Table 24.1. User Shell Folder registry keys default values

    NameDefault Value
    AppData%USERPROFILE%\Application Data
    Desktop%USERPROFILE%\Desktop
    Favorites%USERPROFILE%\Favorites
    NetHood%USERPROFILE%\NetHood
    PrintHood%USERPROFILE%\PrintHood
    Programs%USERPROFILE%\Start Menu\Programs
    Recent%USERPROFILE%\Recent
    SendTo%USERPROFILE%\SendTo
    Start Menu %USERPROFILE%\Start Menu
    Startup%USERPROFILE%\Start Menu\Programs\Startup

    +

    Table 24.1. User Shell Folder registry keys default values

    NameDefault Value
    AppData%USERPROFILE%\Application Data
    Desktop%USERPROFILE%\Desktop
    Favorites%USERPROFILE%\Favorites
    NetHood%USERPROFILE%\NetHood
    PrintHood%USERPROFILE%\PrintHood
    Programs%USERPROFILE%\Start Menu\Programs
    Recent%USERPROFILE%\Recent
    SendTo%USERPROFILE%\SendTo
    Start Menu %USERPROFILE%\Start Menu
    Startup%USERPROFILE%\Start Menu\Programs\Startup

    The registry key that contains the location of the default profile settings is:

    @@ -12937,8 +12935,8 @@ The registry key that contains the location of the default profile settings is:

    The default entries are: -

    Table 24.2. Defaults of profile settings registry keys

    Common Desktop%SystemRoot%\Profiles\All Users\Desktop
    Common Programs%SystemRoot%\Profiles\All Users\Programs
    Common Start Menu%SystemRoot%\Profiles\All Users\Start Menu
    Common Startup%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup

    -

    MS Windows 200x/XP

    Note

    +

    Table 24.2. Defaults of profile settings registry keys

    Common Desktop%SystemRoot%\Profiles\All Users\Desktop
    Common Programs%SystemRoot%\Profiles\All Users\Programs
    Common Start Menu%SystemRoot%\Profiles\All Users\Start Menu
    Common Startup%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup

    +

    MS Windows 200x/XP

    Note

    MS Windows XP Home Edition does use default per user profiles, but can not participate in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile only from itself. While there are benefits in doing this the beauty of those MS Windows @@ -12987,9 +12985,9 @@ are controlled by entries on Windows 200x/XP is:

    The above hive key contains a list of automatically managed folders. The default entries are:

    -

    Table 24.3. Defaults of default user profile paths registry keys

    NameDefault Value
    AppData%USERPROFILE%\Application Data
    Cache%USERPROFILE%\Local Settings\Temporary Internet Files
    Cookies%USERPROFILE%\Cookies
    Desktop%USERPROFILE%\Desktop
    Favorites%USERPROFILE%\Favorites
    History%USERPROFILE%\Local Settings\History
    Local AppData%USERPROFILE%\Local Settings\Application Data
    Local Settings%USERPROFILE%\Local Settings
    My Pictures%USERPROFILE%\My Documents\My Pictures
    NetHood%USERPROFILE%\NetHood
    Personal%USERPROFILE%\My Documents
    PrintHood%USERPROFILE%\PrintHood
    Programs%USERPROFILE%\Start Menu\Programs
    Recent%USERPROFILE%\Recent
    SendTo%USERPROFILE%\SendTo
    Start Menu%USERPROFILE%\Start Menu
    Startup%USERPROFILE%\Start Menu\Programs\Startup
    Templates%USERPROFILE%\Templates

    +

    Table 24.3. Defaults of default user profile paths registry keys

    NameDefault Value
    AppData%USERPROFILE%\Application Data
    Cache%USERPROFILE%\Local Settings\Temporary Internet Files
    Cookies%USERPROFILE%\Cookies
    Desktop%USERPROFILE%\Desktop
    Favorites%USERPROFILE%\Favorites
    History%USERPROFILE%\Local Settings\History
    Local AppData%USERPROFILE%\Local Settings\Application Data
    Local Settings%USERPROFILE%\Local Settings
    My Pictures%USERPROFILE%\My Documents\My Pictures
    NetHood%USERPROFILE%\NetHood
    Personal%USERPROFILE%\My Documents
    PrintHood%USERPROFILE%\PrintHood
    Programs%USERPROFILE%\Start Menu\Programs
    Recent%USERPROFILE%\Recent
    SendTo%USERPROFILE%\SendTo
    Start Menu%USERPROFILE%\Start Menu
    Startup%USERPROFILE%\Start Menu\Programs\Startup
    Templates%USERPROFILE%\Templates

    -There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all +There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all the others are of type REG_EXPAND_SZ.

    It makes a huge difference to the speed of handling roaming user profiles if all the folders are @@ -13013,11 +13011,11 @@ A roaming profile will be cached locally unless the following registry key is cr 

     HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
-	winlogon\"DeleteRoamingCache"=dword:00000001

    + winlogon\"DeleteRoamingCache"=dword:00000001

    In which case, the local cache copy will be deleted on logout. -

    Common Errors

    +

    Common Errors

    The following are some typical errors/problems/questions that have been asked. -

    Setting up roaming profiles for just a few user's or group's?

    +

    Setting up roaming profiles for just a few user's or group's?

    With samba-2.2.x the choice you have is to enable or disable roaming profiles support. It is a global only setting. The default is to have roaming profiles and the default path will locate them in the user's home @@ -13035,7 +13033,7 @@ using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).

    In any case, you can configure only one profile per user. That profile can be either: -

    • A profile unique to that user

    • A mandatory profile (one the user can not change)

    • A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    +

    • A profile unique to that user

    • A mandatory profile (one the user can not change)

    • A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    A user requested the following: “ I do not want Roaming profiles to be implemented. I want to give users a local profile alone. ... @@ -13081,7 +13079,7 @@ Exchange Server back-end. This removes the need for a PST file. LOCAL profiles mean:

    • If each machine is used my many users then much local disk storage is needed for local profiles

    • Every workstation the user logs into has it's own profile, these can be very different from machine to machine

    On the other hand, use of roaming profiles means: -

    • The network administrator can control the desktop environment of all users.

    • Use of mandatory profiles drasitcally reduces network management overheads.

    • In the long run users will be experience fewer problems.

    Changing the default profile

    +

    • The network administrator can control the desktop environment of all users.

    • Use of mandatory profiles drasitcally reduces network management overheads.

    • In the long run users will be experience fewer problems.

    Changing the default profile

    Question: “ When the client logs onto the domain controller it searches for a profile to download, @@ -13106,7 +13104,7 @@ they do not interoperate with domain profiles. For roaming profiles add to smb.conf:

    logon path = \\%N\profiles\%U
    # Default logon drive is Z:
    logon drive = H:
    # This requires a PROFILES share that is world writable.

    -

    Chapter 25. PAM based Distributed Authentication

    John H. Terpstra

    Samba Team

    Stephen Langasek

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication using winbindd.so
    Password Synchronization using pam_smbpass.so
    Common Errors
    pam_winbind problem
    Winbind is not resolving users and groups

    +

    Chapter 25. PAM based Distributed Authentication

    John H. Terpstra

    Samba Team

    Stephen Langasek

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication using winbindd.so
    Password Synchronization using pam_smbpass.so
    Common Errors
    pam_winbind problem
    Winbind is not resolving users and groups

    This chapter you should help you to deploy winbind based authentication on any PAM enabled UNIX/Linux system. Winbind can be used to enable user level application access authentication from any MS Windows NT Domain, MS Windows 200x Active Directory based domain, or any Samba @@ -13117,7 +13115,7 @@ In addition to knowing how to configure winbind into PAM, you will learn generic possibilities and in particular how to deploy tools like pam_smbpass.so to your advantage.

    Note

    The use of Winbind require more than PAM configuration alone. Please refer to the Winbind chapter. -

    Features and Benefits

    +

    Features and Benefits

    A number of UNIX systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, authorization and resource control services. Prior to the introduction of PAM, a decision @@ -13175,12 +13173,12 @@ of distributed samba domain controllers that can provide wide are network bandwi efficient authentication services for PAM capable systems. In effect, this allows the deployment of centrally managed and maintained distributed authentication from a single user account database. -

    Technical Discussion

    +

    Technical Discussion

    PAM is designed to provide the system administrator with a great deal of flexibility in configuration of the privilege granting applications of their system. The local configuration of system security controlled by PAM is contained in one of two places: either the single system file, /etc/pam.conf; or the /etc/pam.d/ directory. -

    PAM Configuration Syntax

    +

    PAM Configuration Syntax

    In this section we discuss the correct syntax of and generic options respected by entries to these files. PAM specific tokens in the configuration file are case insensitive. The module paths, however, are case sensitive since they indicate a file's name and reflect the case dependence of typical file-systems. @@ -13198,7 +13196,7 @@ is located outside the default then the path must be specified as: 

     auth  required  /other_path/pam_strange_module.so

    -

    Anatomy of /etc/pam.d Entries

    +

    Anatomy of /etc/pam.d Entries

    The remaining information in this subsection was taken from the documentation of the Linux-PAM project. For more information on PAM, see The Official Linux-PAM home page @@ -13367,13 +13365,13 @@ squid auth required pam_mysql.so user=passwd_query passwd=mada \ Any line in (one of) the configuration file(s), that is not formatted correctly, will generally tend (erring on the side of caution) to make the authentication process fail. A corresponding error is written to the system log files with a call to syslog(3). -

    Example System Configurations

    +

    Example System Configurations

    The following is an example /etc/pam.d/login configuration file. This example had all options been uncommented is probably not usable as it stacks many conditions before allowing successful completion of the login process. Essentially all conditions can be disabled by commenting them out except the calls to pam_pwdb.so. -

    PAM: original login config

    +
    PAM: original login config
     #%PAM-1.0
 # The PAM configuration file for the `login' service
 #
@@ -13388,7 +13386,7 @@ session      required    pam_pwdb.so
 # session    optional    pam_lastlog.so
 # password   required    pam_cracklib.so retry=3
 password     required    pam_pwdb.so shadow md5
-
    PAM: login using pam_smbpass
    
+

    PAM: login using pam_smbpass

    PAM allows use of replaceable modules. Those available on a sample system include:

    $/bin/ls /lib/security 

    @@ -13467,8 +13465,8 @@ authentication to be configured in a single central file. The
 on the basis that it allows for easier administration. As with all issues in 
 life though, every decision makes trade-offs, so you may want examine the 
 PAM documentation for further helpful information.
-

    smb.conf PAM Configuration

    - There is an option in smb.conf called obey pam restrictions. +

    smb.conf PAM Configuration

    + There is an option in smb.conf called obey pam restrictions. The following is from the on-line help for this option in SWAT;

    When Samba is configured to enable PAM support (i.e. @@ -13478,11 +13476,11 @@ and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of -encrypt passwords = yes. +encrypt passwords = yes. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption. -

    Default: obey pam restrictions = no

    Remote CIFS Authentication using winbindd.so

    +

    Default: obey pam restrictions = no

    Remote CIFS Authentication using winbindd.so

    All operating systems depend on the provision of users credentials acceptable to the platform. UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID). These are both simple integer type numbers that are obtained from a password backend such @@ -13508,7 +13506,7 @@ Microsoft Active Directory Service (ADS) in so far as reduction of wide area net The rid to unix id database is the only location where the user and group mappings are stored by winbindd. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids. -

    Password Synchronization using pam_smbpass.so

    +

    Password Synchronization using pam_smbpass.so

    pam_smbpass is a PAM module which can be used on conforming systems to keep the smbpasswd (Samba password) database in sync with the unix password file. PAM (Pluggable Authentication Modules) is an API supported @@ -13521,7 +13519,7 @@ concerned about the presence of suid root binaries on your system, it is recommended that you use pam_winbind instead.

    Options recognized by this module are as follows: -

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    +

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    • Andrew Morgan, for providing the Linux-PAM framework, without which none of this would have happened

    • Christian Gafton and Andrew Morgan again, for the @@ -13532,7 +13530,7 @@ Options recognized by this module are as follows: The following are examples of the use of pam_smbpass.so in the format of Linux /etc/pam.d/ files structure. Those wishing to implement this tool on other platforms will need to adapt this appropriately. -

      Password Synchronisation Configuration

      +

      Password Synchronisation Configuration

      A sample PAM configuration that shows the use of pam_smbpass to make sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow) is changed. Useful when an expired password might be changed by an @@ -13548,7 +13546,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -

      Password Migration Configuration

      +

      Password Migration Configuration

      A sample PAM configuration that shows the use of pam_smbpass to migrate from plaintext to encrypted passwords for Samba. Unlike other methods, this can be used for users who have never connected to Samba shares: @@ -13567,7 +13565,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password optional pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -

      Mature Password Configuration

      +

      Mature Password Configuration

      A sample PAM configuration for a 'mature' smbpasswd installation. private/smbpasswd is fully populated, and we consider it an error if the smbpasswd doesn't exist or doesn't match the UNIX password. @@ -13582,7 +13580,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so use_authtok use_first_pass session required pam_unix.so -

      Kerberos Password Integration Configuration

      +

      Kerberos Password Integration Configuration

      A sample PAM configuration that shows pam_smbpass used together with pam_krb5. This could be useful on a Samba PDC that is also a member of a Kerberos realm. @@ -13598,10 +13596,10 @@ password requisite pam_cracklib.so retry=3 password optional pam_smbpass.so nullok use_authtok try_first_pass password required pam_krb5.so use_authtok try_first_pass session required pam_krb5.so -

    Common Errors

    +

    Common Errors

    PAM can be a very fickle and sensitive to configuration glitches. Here we look at a few cases from the Samba mailing list. -

    pam_winbind problem

    +

    pam_winbind problem

    “ I have the following PAM configuration: ” @@ -13618,8 +13616,8 @@ password required /lib/security/pam_stack.so service=system-auth

    “ - When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie". - I've tried with user "scienceu+pitie" also. + When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie". + I've tried with user "scienceu+pitie" also. ”

    The problem may lie with your inclusion of pam_stack.so @@ -13629,11 +13627,11 @@ password required /lib/security/pam_stack.so service=system-auth /etc/pam.d/system-auth and copy only what you need from it into your /etc/pam.d/login file. Alternatively, if you want all services to use winbind, you can put the winbind-specific stuff in /etc/pam.d/system-auth. -

    Winbind is not resolving users and groups

    +

    Winbind is not resolving users and groups

    “ My smb.conf file is correctly configured. I have specified - idmap uid = 12000, - and idmap gid = 3000-3500 + idmap uid = 12000, + and idmap gid = 3000-3500 and winbind is running. When I do the following it all works fine. ” 

    @@ -13670,7 +13668,7 @@ This is driving me nuts! What can be wrong?
 	
    
 	Your system is likely running nscd, the name service
 	caching daemon. Shut it down, do NOT restart it! You will find your problem resolved.
-

    Chapter 26. Integrating MS Windows networks with Samba

    John H. Terpstra

    Samba Team

    (Jan 01 2001)

    Table of Contents

    Features and Benefits
    Background Information
    Name Resolution in a pure UNIX/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging works only in one way
    Very Slow Network Connections
    Samba server name change problem

    +

    Chapter 26. Integrating MS Windows networks with Samba

    John H. Terpstra

    Samba Team

    (Jan 01 2001)

    Table of Contents

    Features and Benefits
    Background Information
    Name Resolution in a pure UNIX/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging works only in one way
    Very Slow Network Connections
    Samba server name change problem

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this section does not apply to your installation. If your installation involves use of @@ -13681,7 +13679,7 @@ NetBIOS over TCP/IP then this section may help you to resolve networking problem to NOT run NetBEUI at all. Note also that there is NO such thing as NetBEUI over TCP/IP - the existence of such a protocol is a complete and utter mis-apprehension. -

    Features and Benefits

    +

    Features and Benefits

    Many MS Windows network administrators have never been exposed to basic TCP/IP networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP based @@ -13689,7 +13687,7 @@ networking (and may have no desire to be either).

    This chapter gives a short introduction to the basics of how a name can be resolved to it's IP address for each operating system environment. -

    Background Information

    +

    Background Information

    Since the introduction of MS Windows 2000 it is possible to run MS Windows networking without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over @@ -13702,14 +13700,14 @@ Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print

    When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires - + Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). - + Use of DHCP with ADS is recommended as a further means of maintaining central control over client workstation network configuration. -

    Name Resolution in a pure UNIX/Linux world

    +

    Name Resolution in a pure UNIX/Linux world

    The key configuration files covered in this section are: -

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    +

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    Contains a static list of IP addresses and names. eg: 

    @@ -13725,7 +13723,7 @@ layer communicate not via IP addresses but rather using the Media
 Access Control address, or MAC address. IP addresses are currently 
 32 bits in length and are typically presented as four (4) decimal 
 numbers that are separated by a dot (or period). eg: 168.192.1.1.
-
    
+
    
 MAC Addresses use 48 bits (or 6 bytes) and are typically represented 
 as two digit hexadecimal numbers separated by colons. eg: 
 40:8e:0a:12:34:56
@@ -13742,8 +13740,8 @@ be assigned per MAC address. One address must be the primary IP address,
 this is the address that will be returned in the ARP reply.
 
    
 When a user or a process wants to communicate with another machine 
-the protocol implementation ensures that the "machine name" or "host 
-name" is resolved to an IP address in a manner that is controlled 
+the protocol implementation ensures that the "machine name" or "host 
+name" is resolved to an IP address in a manner that is controlled 
 by the TCP/IP configuration control files. The file 
 /etc/hosts is one such file.
 
    
@@ -13758,7 +13756,7 @@ MAC addresses only; their own unique address and the address
 ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will 
 contain the MAC address and the primary IP address for each 
 interface.
-
    
+
    
 The /etc/hosts file is foundational to all 
 UNIX/Linux TCP/IP installations and as a minimum will contain 
 the localhost and local network interface IP addresses and the 
@@ -13766,7 +13764,7 @@ primary names by which they are known within the local machine.
 This file helps to prime the pump so that a basic level of name 
 resolution can exist before any other method of name resolution 
 becomes available.
-

    /etc/resolv.conf

    +

    /etc/resolv.conf

    This file tells the name resolution libraries:

    • The name of the domain to which the machine belongs @@ -13776,7 +13774,7 @@ This file tells the name resolution libraries:

    • The name or IP address of available Domain Name Servers that may be asked to perform name to address translation lookups -

    /etc/host.conf

    +

    /etc/host.conf

    /etc/host.conf is the primary means by which the setting in /etc/resolv.conf may be affected. It is a critical configuration file. This file controls the order by @@ -13787,7 +13785,7 @@ multi on

    then both addresses should be returned. Please refer to the man page for host.conf for further details. -

    /etc/nsswitch.conf

    +

    /etc/nsswitch.conf

    This file controls the actual name resolution targets. The file typically has resolver object specifications as follows: 

    @@ -13818,7 +13816,7 @@ facilities and/or services are correctly configured.
 It should be noted that unless a network request/message must be 
 sent, TCP/IP networks are silent. All TCP/IP communications assumes a 
 principal of speaking only when necessary.
-
    
+
    
 Starting with version 2.2.0 samba has Linux support for extensions to 
 the name service switch infrastructure so that linux clients will 
 be able to obtain resolution of MS Windows NetBIOS names to IP 
@@ -13826,18 +13824,18 @@ Addresses. To gain this functionality Samba needs to be compiled
 with appropriate arguments to the make command (i.e.: make 
 nsswitch/libnss_wins.so). The resulting library should 
 then be installed in the /lib directory and 
-the "wins" parameter needs to be added to the "hosts:" line in 
+the "wins" parameter needs to be added to the "hosts:" line in 
 the /etc/nsswitch.conf file. At this point it 
 will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, so long as that machine is within the workgroup to 
 which both the samba machine and the MS Windows machine belong.
-

    Name resolution as used within MS Windows networking

    +

    Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as -the "computer name", "machine name", "networking name", "netbios name", -or "SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a +the "computer name", "machine name", "networking name", "netbios name", +or "SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a simple name with which the machine is associated. All NetBIOS names are exactly 16 characters in length. The 16th character is reserved. It is used to store a one byte value that indicates service level @@ -13846,14 +13844,14 @@ name is therefore registered for each service type that is provided by the client/server.

    The following are typical NetBIOS name/service type registrations: -

    Table 26.1. Unique NetBIOS names

    MACHINENAME<00>Server Service is running on MACHINENAME
    MACHINENAME<03>Generic Machine Name (NetBIOS name)
    MACHINENAME<20>LanMan Server service is running on MACHINENAME
    WORKGROUP<1b>Domain Master Browser

    Table 26.2. Group Names

    WORKGROUP<03>Generic Name registered by all members of WORKGROUP
    WORKGROUP<1c>Domain Controllers / Netlogon Servers
    WORKGROUP<1d>Local Master Browsers
    WORKGROUP<1e>Internet Name Resolvers

    - +

    Table 26.1. Unique NetBIOS names

    MACHINENAME<00>Server Service is running on MACHINENAME
    MACHINENAME<03>Generic Machine Name (NetBIOS name)
    MACHINENAME<20>LanMan Server service is running on MACHINENAME
    WORKGROUP<1b>Domain Master Browser

    Table 26.2. Group Names

    WORKGROUP<03>Generic Name registered by all members of WORKGROUP
    WORKGROUP<1c>Domain Controllers / Netlogon Servers
    WORKGROUP<1d>Local Master Browsers
    WORKGROUP<1e>Internet Name Resolvers

    + It should be noted that all NetBIOS machines register their own names as per the above. This is in vast contrast to TCP/IP installations where traditionally the system administrator will determine in the /etc/hosts or in the DNS database what names are associated with each IP address. -

    +

    One further point of clarification should be noted, the /etc/hosts file and the DNS records do not provide the NetBIOS name type information that MS Windows clients depend on to locate the type of service that may @@ -13865,9 +13863,9 @@ registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Whichever machine first replies then ends up providing the logon services.

    -The name "workgroup" or "domain" really can be confusing since these +The name "workgroup" or "domain" really can be confusing since these have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates +architecture of the MS Windows network. The term "workgroup" indicates that the primary nature of the network environment is that of a peer-to-peer design. In a WORKGROUP all machines are responsible for their own security, and generally such security is limited to use of @@ -13891,7 +13889,7 @@ NBT or NetBT, the NetBIOS over TCP/IP. MS Windows machines use a complex array of name resolution mechanisms. Since we are primarily concerned with TCP/IP this demonstration is limited to this area. -

    The NetBIOS Name Cache

    +

    The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external machines that that machine has communicated with over the @@ -13905,11 +13903,11 @@ an attempt to exchange a message with that machine will be subject to time-out delays. i.e.: Its name is in the cache, so a name resolution lookup will succeed, but the machine can not respond. This can be frustrating for users - but it is a characteristic of the protocol. -

    +

    The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this +name cache is called "nbtstat". The Samba equivalent of this is called nmblookup. -

    The LMHOSTS file

    +

    The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the machine name in matched pairs. The @@ -13927,7 +13925,7 @@ It typically looks like: # (NetBIOS) names. Each entry should be kept on an individual line. # The IP address should be placed in the first column followed by the # corresponding computername. The address and the computername -# should be separated by at least one space or tab. The "#" character +# should be separated by at least one space or tab. The "#" character # is generally used to denote the start of a comment (see the exceptions # below). # @@ -13941,29 +13939,29 @@ It typically looks like: # #END_ALTERNATE # \0xnn (non-printing character support) # -# Following any entry in the file with the characters "#PRE" will cause +# Following any entry in the file with the characters "#PRE" will cause # the entry to be preloaded into the name cache. By default, entries are # not preloaded, but are parsed only after dynamic name resolution fails. # -# Following an entry with the "#DOM:<domain>" tag will associate the +# Following an entry with the "#DOM:<domain>" tag will associate the # entry with the domain specified by <domain>. This affects how the # browser and logon services behave in TCP/IP environments. To preload # the host name associated with #DOM entry, it is necessary to also add a # #PRE to the line. The <domain> is always preloaded although it will not # be shown when the name cache is viewed. # -# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) +# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) # software to seek the specified <filename> and parse it as if it were # local. <filename> is generally a UNC-based name, allowing a # centralized lmhosts file to be maintained on a server. # It is ALWAYS necessary to provide a mapping for the IP address of the # server prior to the #INCLUDE. This mapping must use the #PRE directive. -# In addition the share "public" in the example below must be in the -# LanManServer list of "NullSessionShares" in order for client machines to +# In addition the share "public" in the example below must be in the +# LanManServer list of "NullSessionShares" in order for client machines to # be able to read the lmhosts file successfully. This key is under # \machine\system\currentcontrolset\services\lanmanserver\ # parameters\nullsessionshares -# in the registry. Simply add "public" to the list found there. +# in the registry. Simply add "public" to the list found there. # # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE # statements to be grouped together. Any single successful include @@ -13976,7 +13974,7 @@ It typically looks like: # The following example illustrates all of these extensions: # # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC -# 102.54.94.102 "appname \0x14" #special app server +# 102.54.94.102 "appname \0x14" #special app server # 102.54.94.123 popular #PRE #source server # 102.54.94.117 localsrv #PRE #needed for the include # @@ -13985,24 +13983,24 @@ It typically looks like: # #INCLUDE \\rhino\public\lmhosts # #END_ALTERNATE # -# In the above example, the "appname" server contains a special -# character in its name, the "popular" and "localsrv" server names are -# preloaded, and the "rhino" server name is specified so it can be used -# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" +# In the above example, the "appname" server contains a special +# character in its name, the "popular" and "localsrv" server names are +# preloaded, and the "rhino" server name is specified so it can be used +# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" # system is unavailable. # # Note that the whole file is parsed including comments on each lookup, # so keeping the number of comments to a minimum will improve performance. # Therefore it is not advisable to simply add lmhosts file entries onto the # end of this file. -

    HOSTS file

    +

    HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the IP hostname in matched pairs. It can be used by the name resolution infrastructure in MS Windows, depending on how the TCP/IP environment is configured. This file is in every way the equivalent of the UNIX/Linux /etc/hosts file. -

    DNS Lookup

    +

    DNS Lookup

    This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled, an elaborate name resolution sequence is followed the precise nature of which is dependant on how the NetBIOS @@ -14013,7 +14011,7 @@ cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast lookup is used. -

    WINS Lookup

    +

    WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivalent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores the names and IP addresses that are registered by a Windows client @@ -14028,11 +14026,11 @@ needed in the smb.conf file: where xxx.xxx.xxx.xxx is the IP address of the WINS server.

    For information about setting up Samba as a WINS server, read - the chapter on network browsing.

    Common Errors

    + the chapter on network browsing.

    Common Errors

    TCP/IP network configuration problems find every network administrator sooner or later. The cause can be anything from keyboard mishaps, forgetfulness, simple mistakes, and carelessness. Of course, no one is every deliberately careless! -

    Pinging works only in one way

    +

    Pinging works only in one way

    “I can ping my samba server from Windows, but I can not ping my Windows machine from the samba server.”

    @@ -14042,9 +14040,9 @@ carelessness. Of course, no one is every deliberately careless!

    Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while the Samba server was on network 192.168.1.128/25 - logically a different network. -

    Very Slow Network Connections

    +

    Very Slow Network Connections

    A common causes of slow network response includes: -

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but remote connection is down

    • Client is configured to use a WINS server, but there is no WINS server

    • Client is NOT configured to use a WINS server, but there is a WINS server

    • Firewall is filtering our DNS or WINS traffic

    Samba server name change problem

    +

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but remote connection is down

    • Client is configured to use a WINS server, but there is no WINS server

    • Client is NOT configured to use a WINS server, but there is a WINS server

    • Firewall is filtering our DNS or WINS traffic

    Samba server name change problem

    “The name of the samba server was changed, samba was restarted, samba server can not be pinged by new name from MS Windows NT4 Workstation, but it does still respond to ping using the old name. Why?” @@ -14084,7 +14082,7 @@ GANDALF <20> UNIQUE 192.168.1.1 240 The first listing shows the contents of the Local Name Table (i.e.: Identity information on the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache. The name cache contains the remote machines known to this workstation. -

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found

    Features and Benefits

    +

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found

    Features and Benefits

    Every industry eventually matures. One of the great areas of maturation is in the focus that has been given over the past decade to make it possible for anyone anywhere to use a computer. It has not always been that way, in fact, not so long @@ -14098,7 +14096,7 @@ special mention. Samba-2.x supported a single locale through a mechanism called codepages. Samba-3 is destined to become a truly trans-global file and printer sharing platform. -

    What are charsets and unicode?

    +

    What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned to a certain number depends on the character set(charset) @@ -14124,46 +14122,46 @@ communicating. negotiating the charset to be used in the smb protocol. Thus, you have to make sure you are using the same charset when talking to an older client. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -

    Samba and charsets

    +

    Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, samba knows of three kinds of character sets: -

    unix charset

    +

    unix charset

    This is the charset used internally by your operating system. The default is UTF-8, which is fine for most systems. The default in previous samba releases was ASCII. -

    display charset

    This is the charset samba will use to print messages +

    display charset

    This is the charset samba will use to print messages on your screen. It should generally be the same as the unix charset. -

    dos charset

    This is the charset samba uses when communicating with +

    dos charset

    This is the charset samba uses when communicating with DOS and Windows 9x clients. It will talk unicode to all newer clients. The default depends on the charsets you have installed on your system. - Run testparm -v | grep "dos charset" to see + Run testparm -v | grep "dos charset" to see what the default is on your system. -

    Conversion from old names

    Because previous samba versions did not do any charset conversion, +

    Conversion from old names

    Because previous samba versions did not do any charset conversion, characters in filenames are usually not correct in the unix charset but only for the local charset used by the DOS/Windows clients.

    Bjoern Jacke has written a utility named convm that can convert whole directory structures to different charsets with one single command. -

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are -points of attention when setting it up:

    • You should set mangling method = hash

    • There are various iconv() implementations around and not +

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are +points of attention when setting it up:

    • You should set mangling method = hash

    • There are various iconv() implementations around and not all of them work equally well. glibc2's iconv() has a critical problem in CP932. libiconv-1.8 works with CP932 but still has some problems and -does not work with EUC-JP.

    • You should set dos charset = CP932, not -Shift_JIS, SJIS...

    • Currently only unix charset = CP932 +does not work with EUC-JP.

    • You should set dos charset = CP932, not +Shift_JIS, SJIS...

    • Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. -unix charset = EUC-JP doesn't work well because of -iconv() issues.

    • Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    Common errors

    CP850.so can't be found

    “Samba is complaining about a missing CP850.so file”.

    CP850 is the default dos charset. The dos charset is used to convert data to the codepage used by your dos clients. If you don't have any dos clients, you can safely ignore this message.

    CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    +unix charset = EUC-JP doesn't work well because of +iconv() issues.

  • Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    • More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    Common errors

    CP850.so can't be found

    “Samba is complaining about a missing CP850.so file”.

    CP850 is the default dos charset. The dos charset is used to convert data to the codepage used by your dos clients. If you don't have any dos clients, you can safely ignore this message.

    CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Features and Benefits

    +

    Features and Benefits

    We need feedback from people who are backing up samba servers. We would like to know what software tools you are using to backup your samba server/s.

    In particular, if you have any success and / or failure stories you could share with other users this would be appreciated. -

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    June 30, 2003

    Table of Contents

    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP

    New Features in Samba-3

    +

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    June 30, 2003

    Table of Contents

    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP

    New Features in Samba-3

    Major new features:

    1. Active Directory support. This release is able to join a ADS realm @@ -14181,10 +14179,10 @@ Major new features: completely rewritten. An internal database now stores mangling maps persistently. This needs lots of testing.

    2. - New "net" command. A new "net" command has been added. It is - somewhat similar to the "net" command in windows. Eventually we + New "net" command. A new "net" command has been added. It is + somewhat similar to the "net" command in windows. Eventually we plan to replace a bunch of other utilities (such as smbpasswd) - with subcommands in "net", at the moment only a few things are + with subcommands in "net", at the moment only a few things are implemented.

    3. Samba now negotiates NT-style status32 codes on the wire. This @@ -14209,20 +14207,20 @@ Major new features: Major updates to the Samba documentation tree.

    Plus lots of other improvements! -

    Configuration Parameter Changes

    +

    Configuration Parameter Changes

    This section contains a brief listing of changes to smb.conf options in the 3.0.0 release. Please refer to the smb.conf(5) man page for complete descriptions of new or modified parameters. -

    Removed Parameters

    (order alphabetically):

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • force unknown acl user

    • nt smb support

    • post script

    • printer driver

    • printer driver file

    • printer driver location

    • status

    • total print jobs

    • use rhosts

    • valid chars

    • vfs options

    New Parameters

    (new parameters have been grouped by function):

    Remote management

    • abort shutdown script

    • shutdown script

    User and Group Account Management

    • add group script

    • add machine script

    • add user to group script

    • algorithmic rid base

    • delete group script

    • delete user from group script

    • passdb backend

    • set primary group script

    Authentication

    • auth methods

    • ads server

    • realm

    Protocol Options

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • disable netbios

    • ntlm auth

    • paranoid server security

    • server schannel

    • smb ports

    • use spnego

    File Service

    • get quota command

    • hide special files

    • hide unwriteable files

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • msdfs proxy

    • set quota command

    • use sendfile

    • vfs objects

    Printing

    • max reported print jobs

    UNICODE and Character Sets

    • display charset

    • dos charset

    • unicode

    • unix charset

    SID to uid/gid Mappings

    • idmap backend

    • idmap gid

    • idmap only

    • idmap uid

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap trust ids

    • ldap user suffix

    General Configuration

    • preload modules

    • privatedir

    Modified Parameters (changes in behavior):

    • encrypt passwords (enabled by default)

    • mangling method (set to 'hash2' by default)

    • passwd chat

    • passwd program

    • restrict anonymous (integer value)

    • security (new 'ads' value)

    • strict locking (enabled by default)

    • winbind cache time (increased to 5 minutes)

    • winbind uid (deprecated in favor of 'idmap uid')

    • winbind gid (deprecated in favor of 'idmap gid')

    New Functionality

    Databases

    +

    Removed Parameters

    (order alphabetically):

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • force unknown acl user

    • nt smb support

    • post script

    • printer driver

    • printer driver file

    • printer driver location

    • status

    • total print jobs

    • use rhosts

    • valid chars

    • vfs options

    New Parameters

    (new parameters have been grouped by function):

    Remote management

    • abort shutdown script

    • shutdown script

    User and Group Account Management

    • add group script

    • add machine script

    • add user to group script

    • algorithmic rid base

    • delete group script

    • delete user from group script

    • passdb backend

    • set primary group script

    Authentication

    • auth methods

    • ads server

    • realm

    Protocol Options

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • disable netbios

    • ntlm auth

    • paranoid server security

    • server schannel

    • smb ports

    • use spnego

    File Service

    • get quota command

    • hide special files

    • hide unwriteable files

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • msdfs proxy

    • set quota command

    • use sendfile

    • vfs objects

    Printing

    • max reported print jobs

    UNICODE and Character Sets

    • display charset

    • dos charset

    • unicode

    • unix charset

    SID to uid/gid Mappings

    • idmap backend

    • idmap gid

    • idmap only

    • idmap uid

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap trust ids

    • ldap user suffix

    General Configuration

    • preload modules

    • privatedir

    Modified Parameters (changes in behavior):

    • encrypt passwords (enabled by default)

    • mangling method (set to 'hash2' by default)

    • passwd chat

    • passwd program

    • restrict anonymous (integer value)

    • security (new 'ads' value)

    • strict locking (enabled by default)

    • winbind cache time (increased to 5 minutes)

    • winbind uid (deprecated in favor of 'idmap uid')

    • winbind gid (deprecated in favor of 'idmap gid')

    New Functionality

    Databases

    This section contains brief descriptions of any new databases introduced in Samba 3.0. Please remember to backup your existing ${lock directory}/*tdb before upgrading to Samba 3.0. Samba will upgrade databases as they are opened (if necessary), but downgrading from 3.0 to 2.2 is an unsupported path. -

    Table 30.1. TDB File Descriptions

    NameDescriptionBackup?
    account_policyUser policy settingsyes
    gencacheGeneric caching dbno
    group_mapping

    Mapping table from Windows groups/SID to unix groups

    		yes
    idmap

    new ID map table from SIDS to UNIX uids/gids

    		yes
    namecacheName resolution cache entriesno
    netlogon_unigrp

    Cache of universal group membership obtained when operating +

    Table 30.1. TDB File Descriptions

    NameDescriptionBackup?
    account_policyUser policy settingsyes
    gencacheGeneric caching dbno
    group_mapping

    Mapping table from Windows groups/SID to unix groups

    		yes
    idmap

    new ID map table from SIDS to UNIX uids/gids

    		yes
    namecacheName resolution cache entriesno
    netlogon_unigrp

    Cache of universal group membership obtained when operating as a member of a Windows domain

    		no
    printing/*.tdb

    Cached output from 'lpq command' created on a per print service basis

    		no
    registry

    Read-only samba registry skeleton that provides support for - exporting various db tables via the winreg RPCs

    		no

    Changes in Behavior

    + exporting various db tables via the winreg RPCs

    		no

    Changes in Behavior

    The following issues are known changes in behavior between Samba 2.2 and Samba 3.0 that may affect certain installations of Samba.

    1. @@ -14238,11 +14236,11 @@ complete descriptions of new or modified parameters. script' that must be specified for this purpose. Samba 3.0 will not fall back to using the 'add user script' in the absence of an 'add machine script' -

    Charsets

    +

    Charsets

    You might experience problems with special characters when communicating with old DOS clients. Codepage support has changed in samba 3.0. Read the chapter Unicode support for details. -

    Passdb Backends and Authentication

    +

    Passdb Backends and Authentication

    There have been a few new changes that Samba administrators should be aware of when moving to Samba 3.0.

    1. @@ -14252,15 +14250,15 @@ complete descriptions of new or modified parameters. must be created for each user, or (b) 'encrypt passwords = no' must be explicitly defined in smb.conf.

    2. - Inclusion of new security = ads option for integration + Inclusion of new security = ads option for integration with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols.

    Samba 3.0 also includes the possibility of setting up chains of authentication methods - (auth methods) and account + (auth methods) and account storage backends - (passdb backend). + (passdb backend). Please refer to the smb.conf man page and the chapter about account information databases for details. While both parameters assume sane default values, it is likely that you will need to understand what the @@ -14269,13 +14267,13 @@ complete descriptions of new or modified parameters. Certain functions of the smbpasswd(8) tool have been split between the new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8) utility. See the respective man pages for details. -

    Charsets

    +

    Charsets

    You might experience problems with special characters when communicating with old DOS clients. Codepage support has changed in samba 3.0. Read the chapter Unicode support for details. -

    LDAP

    +

    LDAP

    This section outlines the new features affecting Samba / LDAP integration. -

    New Schema

    +

    New Schema

    A new object class (sambaSamAccount) has been introduced to replace the old sambaAccount. This change aids us in the renaming of attributes to prevent clashes with attributes from other vendors. There is a @@ -14284,14 +14282,14 @@ complete descriptions of new or modified parameters.

    Example: 

    -		$ ldapsearch .... -b "ou=people,dc=..." > old.ldif
+		$ ldapsearch .... -b "ou=people,dc=..." > old.ldif
 		$ convertSambaAccount <DOM SID> old.ldif new.ldif

    The <DOM SID> can be obtained by running 'net getlocalsid <DOMAINNAME> on the Samba PDC as root.

    The old sambaAccount schema may still be used by specifying the - "ldapsam_compat" passdb backend. However, the sambaAccount and + "ldapsam_compat" passdb backend. However, the sambaAccount and associated attributes have been moved to the historical section of the schema file and must be uncommented before use if needed. The 2.2 object class declaration for a sambaAccount has not changed @@ -14317,7 +14315,7 @@ complete descriptions of new or modified parameters. sambaIdmapEntry - object storing a mapping between a SID and a UNIX uid/gid. These objects are created by the idmap_ldap module as needed. -

    New Suffix for Searching

    +

    New Suffix for Searching

    The following new smb.conf parameters have been added to aid in directing certain LDAP queries when 'passdb backend = ldapsam://...' has been specified. @@ -14329,19 +14327,19 @@ complete descriptions of new or modified parameters.

    Due to a limitation in Samba's smb.conf parsing, you should not surround the DN's with quotation marks. -

    IdMap LDAP support

    +

    IdMap LDAP support

    Samba 3.0 supports an ldap backend for the idmap subsystem. The following options would inform Samba that the idmap table should be - stored on the directory server onterose in the "ou=idmap,dc=plainjoe, - dc=org" partition. + stored on the directory server onterose in the "ou=idmap,dc=plainjoe, + dc=org" partition.

    [global]
    ...
    idmap backend = ldap:ldap://onterose/
    ldap idmap suffix = ou=idmap,dc=plainjoe,dc=org
    idmap uid = 40000-50000
    idmap gid = 40000-50000

    This configuration allows winbind installations on multiple servers to share a uid/gid number space, thus avoiding the interoperability problems with NFS that were present in Samba 2.2. -

    Chapter 31. Migration from NT4 PDC to Samba-3 PDC

    John H. Terpstra

    Samba Team

    April 3, 2003

    Table of Contents

    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices

    +

    Chapter 31. Migration from NT4 PDC to Samba-3 PDC

    John H. Terpstra

    Samba Team

    April 3, 2003

    Table of Contents

    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices

    This is a rough guide to assist those wishing to migrate from NT4 domain control to Samba-3 based domain control. -

    Planning and Getting Started

    +

    Planning and Getting Started

    In the IT world there is often a saying that all problems are encountered because of poor planning. The corollary to this saying is that not all problems can be anticipated and planned for. Then again, good planning will anticipate most show stopper type situations. @@ -14349,7 +14347,7 @@ and planned for. Then again, good planning will anticipate most show stopper typ Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control environment would do well to develop a detailed migration plan. So here are a few pointers to help migration get under way. -

    Objectives

    +

    Objectives

    The key objective for most organisations will be to make the migration from MS Windows NT4 to Samba-3 domain control as painless as possible. One of the challenges you may experience in your migration process may well be one of convincing management that the new environment @@ -14375,7 +14373,7 @@ Before migrating a network from MS Windows NT4 to Samba-3 consider all necessary should be educated about changes they may experience so that the change will be a welcome one and not become an obstacle to the work they need to do. The following are factors that will help ensure a successful migration: -

    Domain Layout

    +

    Domain Layout

    Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called a secondary controller), a domain member, or as a stand-alone server. The Windows network security domain context should be sized and scoped before implementation. Particular attention needs to be @@ -14395,7 +14393,7 @@ serve multiple routed network segments may result in severe performance problems response time (eg: ping timing) between the remote segment and the PDC. If long (more than 100 ms) locate a backup controller (BDC) on the remote segmanet to serve as the local authentication and access control server. -

    Server Share and Directory Layout

    +

    Server Share and Directory Layout

    There are cardinal rules to effective network design. These can not be broken with impunity. The most important rule: Simplicity is king in every well controlled network. Every part of the infrastructure must be managed, the more complex it is, the greater will be the demand @@ -14409,7 +14407,7 @@ maintenance. Leave nothing to chance in your design, above all, do not leave bac Backup and test, validate every backup, create a disaster recovery plan and prove that it works.

    Users should be grouped according to data access control needs. File and directory access -is best controlled via group permissions and the use of the "sticky bit" on group controlled +is best controlled via group permissions and the use of the "sticky bit" on group controlled directories may substantially avoid file access complaints from samba share users.

    Inexperienced network administrators often attempt elaborate techniques to set access @@ -14420,32 +14418,32 @@ Remember, job security through complex design and implementation may cause loss and downtime to users as the new administrator learns to untangle your knots. Keep access controls simple and effective and make sure that users will never be interrupted by stupid complexity. -

    Logon Scripts

    +

    Logon Scripts

    Logon scripts can help to ensure that all users gain share and printer connections they need.

    Logon scripts can be created 'on-the-fly' so that all commands executed are specific to the rights and priviliges granted to the user. The preferred controls should be affected through group membership so that group information can be used to custom create a logon script using -the root preexec parameters to the NETLOGON share. +the root preexec parameters to the NETLOGON share.

    Some sites prefer to use a tool such as kixstart to establish a controlled user environment. In any case you may wish to do a google search for logon script process controls. In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that deals with how to add printers without user intervention via the logon script process. -

    Profile Migration/Creation

    +

    Profile Migration/Creation

    User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile Management.

    Profiles may also be managed using the Samba-3 tool profiles. This tool allows the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file to be changed to the SID of the Samba-3 domain. -

    User and Group Accounts

    +

    User and Group Accounts

    It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the groups that are present on the MS Windows NT4 domain AND to map these to suitable Unix/Linux groups. By following this simple advice all user and group attributes should migrate painlessly. -

    Steps In Migration Process

    +

    Steps In Migration Process

    The approximate migration process is described below.

    • You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated @@ -14461,21 +14459,21 @@ to fucntion as a BDC. ie: domain master = No. #### Keep this as a shell script for future re-use # First assign well known domain global groups -net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmins -net groupmap modify ntgroup="Domain Guests" unixgroup=nobody -net groupmap modify ntgroup="Domain Users" unixgroup=users +net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmins +net groupmap modify ntgroup="Domain Guests" unixgroup=nobody +net groupmap modify ntgroup="Domain Users" unixgroup=users # Now for our added domain global groups -net groupmap add ntgroup="Designers" unixgroup=designers type=d rid=3200 -net groupmap add ntgroup="Engineers" unixgroup=engineers type=d rid=3210 -net groupmap add ntgroup="QA Team" unixgroup=qateam type=d rid=3220 +net groupmap add ntgroup="Designers" unixgroup=designers type=d rid=3200 +net groupmap add ntgroup="Engineers" unixgroup=engineers type=d rid=3210 +net groupmap add ntgroup="QA Team" unixgroup=qateam type=d rid=3220

    • net groupmap list

      1. Now check that all groups are recognised

    Now migrate all the profiles, then migrate all policy files. -

    Migration Options

    +

    Migration Options

    Sites that wish to migrate from MS Windows NT4 Domain Control to a Samba based solution generally fit into three basic categories. -

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas

    Planning for Success

    +

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas

    Planning for Success

    There are three basic choices for sites that intend to migrate from MS Windows NT4 to Samba-3.

    • @@ -14494,7 +14492,7 @@ Minimise down-stream problems by: Test ALL assumptions

    • Test full roll-out program, including workstation deployment -

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck all accounts from NT4 into Samba-3

    Copy and improve:

    Authentication Regime (database location and access)

    Make least number of operational changes

    Make progressive improvements

    Desktop Management Methods

    Take least amount of time to migrate

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

    Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)

    Take advantage of lower maintenance opportunity

    Samba-3 Implementation Choices

    Authentication database/back end:

    +

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck all accounts from NT4 into Samba-3

    Copy and improve:

    Authentication Regime (database location and access)

    Make least number of operational changes

    Make progressive improvements

    Desktop Management Methods

    Take least amount of time to migrate

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

    Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)

    Take advantage of lower maintenance opportunity

    Samba-3 Implementation Choices

    Authentication database/back end:

    Samba-3 can use an external authentication backend:

    • Winbind (external Samba or NT4/200x server)

    • External server could use Active Directory or NT4 Domain

    • Can use pam_mkhomedir.so to auto-create home dirs

    @@ -14515,7 +14513,7 @@ Minimise down-stream problems by: Linux limit is 16 char, no spaces and no upper case chars (groupadd)

    Migration Tools:

    Domain Control (NT4 Style) Profiles, Policies, Access Controls, Security

    • Samba: net, rpcclient, smbpasswd, pdbedit, profiles

    • Windows: NT4 Domain User Manager, Server Manager (NEXUS)

    -

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    +

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    There are many and varied opinions regarding the usefulness or otherwise of SWAT. No matter how hard one tries to produce the perfect configuration tool it remains an object of personal taste. SWAT is a tool that will allow web based configuration @@ -14523,7 +14521,7 @@ of samba. It has a wizard that may help to get samba configured quickly, it has sensitive help on each smb.conf parameter, it provides for monitoring of current state of connection information, and it allows network wide MS Windows network password management. -

    Features and Benefits

    +

    Features and Benefits

    There are network administrators who believe that it is a good idea to write systems documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT does not store the configuration file in any intermediate form, rather, it stores only the @@ -14535,7 +14533,7 @@ internal ordering. So before using SWAT please be warned - SWAT will completely replace your smb.conf with a fully optimised file that has been stripped of all comments you might have placed there and only non-default settings will be written to the file. -

    Enabling SWAT for use

    +

    Enabling SWAT for use

    SWAT should be installed to run via the network super daemon. Depending on which system your UNIX/Linux system has you will have either an inetd or xinetd based system. @@ -14589,7 +14587,7 @@ So long as you log onto SWAT as the user rootHOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD. -

    Securing SWAT through SSL

    +

    Securing SWAT through SSL

    Lots of people have asked about how to setup SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger

    @@ -14614,10 +14612,10 @@ Modifications to the swat setup are as following:

    afterwords simply contact to swat by using the URL https://myhost:901, accept the certificate and the SSL connection is up. -

    The SWAT Home Page

    +

    The SWAT Home Page

    The SWAT title page provides access to the latest Samba documentation. The manual page for each samba component is accessible from this page as are the Samba-HOWTO-Collection (this -document) as well as the O'Reilly book "Using Samba". +document) as well as the O'Reilly book "Using Samba".

    Administrators who wish to validate their samba configuration may obtain useful information from the man pages for the diagnostic utilities. These are available from the SWAT home page @@ -14629,7 +14627,7 @@ as it runs SWAT without authentication and with full administrative ability. ie: changes to smb.conf as well as general operation with root privileges. The option that creates this ability is the -a flag to swat. Do not use this in any production environment. -

    Global Settings

    +

    Global Settings

    The Globals button will expose a page that allows configuration of the global parameters in smb.conf. There are three levels of exposure of the parameters:

    • @@ -14651,7 +14649,7 @@ your changes will be immediately lost.

      Note

      SWAT has context sensitive help. To find out what each parameter is for simply click the Help link to the left of the configuration parameter. -

    Share Settings

    +

    Share Settings

    To affect a currently configured share, simply click on the pull down button between the Choose Share and the Delete Share buttons, select the share you wish to operate on, then to edit the settings click on the @@ -14661,7 +14659,7 @@ select the share you wish to operate on, then to edit the settings click on the To create a new share, next to the button labelled Create Share enter into the text field the name of the share to be created, then click on the Create Share button. -

    Printers Settings

    +

    Printers Settings

    To affect a currently configured printer, simply click on the pull down button between the Choose Printer and the Delete Printer buttons, select the printer you wish to operate on, then to edit the settings click on the @@ -14671,7 +14669,7 @@ select the printer you wish to operate on, then to edit the settings click on th To create a new printer, next to the button labelled Create Printer enter into the text field the name of the share to be created, then click on the Create Printer button. -

    The SWAT Wizard

    +

    The SWAT Wizard

    The purpose if the SWAT Wizard is to help the Microsoft knowledgeable network administrator to configure Samba with a minimum of effort.

    @@ -14687,7 +14685,7 @@ Finally, there are a limited set of options that will determine what type of ser will be configured for, whether it will be a WINS server, participate as a WINS client, or operate with no WINS support. By clicking on one button you can elect to expose (or not) user home directories. -

    The Status Page

    +

    The Status Page

    The status page serves a limited purpose. Firstly, it allows control of the samba daemons. The key daemons that create the samba server environment are: smbd, nmbd, winbindd.

    @@ -14698,11 +14696,11 @@ conditions with minimal effort.

    Lastly, the Status page may be used to terminate specific smbd client connections in order to free files that may be locked. -

    The View Page

    +

    The View Page

    This page allows the administrator to view the optimised smb.conf file and, if you are particularly masochistic, will permit you also to see all possible global configuration parameters and their settings. -

    The Password Change Page

    +

    The Password Change Page

    The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation and reactivation of MS Windows networking users on the local machine. Alternatively, you can use this tool to change a local password for a user account. @@ -14713,7 +14711,7 @@ required.

    One popular use for this tool is to change user passwords across a range of remote MS Windows servers. -

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests

    Introduction

    +

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests

    Introduction

    This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem is if it fails any one of these steps. If it passes all these tests @@ -14725,10 +14723,10 @@ the earlier tests. However, do not stop at the first error as there have been some instances when continuing with the tests has helped to solve a problem.

    -If you send one of the samba mailing lists an email saying "it doesn't work" +If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then you should not be surprised if your email is ignored. -

    Assumptions

    +

    Assumptions

    In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    @@ -14738,7 +14736,7 @@ It is also assumed you know the name of an available share in your smb.conf. I will assume this share is called tmp. You can add a tmp share like this by adding the following to smb.conf: -

    Example 33.1. smb.conf with [tmp] share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    +

    Example 33.1. smb.conf with [tmp] share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    Note

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. @@ -14751,7 +14749,7 @@ file points to name servers that really do exist. Also, if you do not have DNS server access for name resolution please check that the settings for your smb.conf file results in dns proxy = no. The best way to check this is with testparm smb.conf. -

    +

    It is helpful to monitor the log files during testing by using the tail -F log_file_name in a separate terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). @@ -14762,7 +14760,7 @@ depending on how or if you specified logging in your smb.co

    If you make changes to your smb.conf file while going through these test, don't forget to restart smbd and nmbd. -

    The tests

    Procedure 33.1. Diagnosing your samba server

    1. +

    The tests

    Procedure 33.1. Diagnosing your samba server

    1. In the directory in which you store your smb.conf file, run the command testparm smb.conf. If it reports any errors then your smb.conf configuration file is faulty. @@ -14775,7 +14773,7 @@ Run the command ping BIGSERVER from the PC and the unix box. If you don't get a valid response then your TCP/IP software is not correctly installed.

      -Note that you will need to start a "dos prompt" window on the PC to +Note that you will need to start a "dos prompt" window on the PC to run ping.

      If you get a message saying host not found or similar then your DNS @@ -14795,7 +14793,7 @@ This is a common problem that is often overlooked. Run the command smbclient -L BIGSERVER on the unix box. You should get a list of available shares back.

      -If you get a error message containing the string "Bad password" then +If you get a error message containing the string "Bad password" then you probably have either an incorrect hosts allow, hosts deny or valid users line in your smb.conf, or your guest account is not @@ -14808,15 +14806,15 @@ that file incorrectly. If you installed it as a daemon then check that it is running, and check that the netbios-ssn port is in a LISTEN state using netstat -a.

      Note

      - - + + Some Unix / Linux systems use xinetd in place of inetd. Check your system documentation for the location of the control file/s for your particular system implementation of this network super daemon.

      If you get a session request failed then the server refused the -connection. If it says "Your server software is being unfriendly" then +connection. If it says "Your server software is being unfriendly" then its probably because you have invalid command line parameters to smbd, or a similar fatal problem with the initial startup of smbd. Also check your config file (smb.conf) for syntax errors with testparm @@ -14831,15 +14829,15 @@ In the above, no allowance has been made for any session requests that will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem change these lines to:

      hosts deny = ALL
      hosts allow = xxx.xxx.xxx.xxx/yy 127.

      -Do not use the bind interfaces only parameter where you +Do not use the bind interfaces only parameter where you may wish to use the samba password change facility, or where smbclient may need to access a local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency +connections. (Note: the bind interfaces only parameter deficiency where it will not allow connections to the loopback address will be fixed soon).

      - + Another common cause of these two errors is having something already running on port 139, such as Samba (ie: smbd is running from inetd already) or @@ -14882,7 +14880,7 @@ messages from several hosts. If this doesn't give a similar result to the previous test then nmblookup isn't correctly getting your broadcast address through its automatic mechanism. In this case you should experiment with the -interfaces option in smb.conf to manually configure your IP +interfaces option in smb.conf to manually configure your IP address, broadcast and netmask.

      If your PC and server aren't on the same subnet then you will need to @@ -14891,7 +14889,7 @@ subnet.

      This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above). -

    2. +

    3. Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with @@ -14905,18 +14903,18 @@ as follows:

    Once you enter the password you should get the smb> prompt. If you don't then look at the error message. If it says invalid network -name then the service "tmp" is not correctly setup in your smb.conf. +name then the service "tmp" is not correctly setup in your smb.conf.

    If it says bad password then the likely causes are:

    1. you have shadow passwords (or some other password system) but didn't compile in support for them in smbd

    2. - your valid users configuration is incorrect + your valid users configuration is incorrect

    3. - you have a mixed case password and you haven't enabled the password level option at a high enough level + you have a mixed case password and you haven't enabled the password level option at a high enough level

    4. - the path line in smb.conf is incorrect. Check it with testparm + the path line in smb.conf is incorrect. Check it with testparm

    5. you enabled password encryption but didn't map unix to samba users. Run 

      smbpasswd -a username

      .

    @@ -14927,7 +14925,7 @@ especially check that the amount of free disk space shown is correct when you type dir.

  • On the PC, type the command net view \\BIGSERVER. You will -need to do this from within a "dos prompt" window. You should get back a +need to do this from within a "dos prompt" window. You should get back a list of available shares on the server.

    If you get a network name not found or similar error then netbios @@ -14968,13 +14966,13 @@ installed or your smb.conf is incorrect. make sure your hosts and other config lines in smb.conf are correct.

    It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = username to the [tmp] section of +connect you as. To see if this is the problem add the line user = username to the [tmp] section of smb.conf where username is the username corresponding to the password you typed. If you find this fixes things you may need the username mapping option.

    It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf +and you have encrypt passwords = no in smb.conf Turn it back on to fix.

  • Run the command nmblookup -M testgroup where @@ -14985,33 +14983,33 @@ master browser for that workgroup. If you don't then the election process has failed. Wait a minute to see if it is just being slow then try again. If it still fails after that then look at the browsing options you have set in smb.conf. Make -sure you have preferred master = yes to ensure that +sure you have preferred master = yes to ensure that an election is held at startup.

  • From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it is refusing to browse a server that has no encrypted password capability and is in user level security mode. In this case either set -security = server AND -password server = Windows_NT_Machine in your -smb.conf file, or make sure encrypt passwords is -set to "yes". -

    • Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

    +security = server AND +password server = Windows_NT_Machine in your +smb.conf file, or make sure encrypt passwords is +set to "yes". +

    Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

    There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of -general SMB topics such as browsing.

    Diagnostics tools

    With SMB networking, it is often not immediately clear what +general SMB topics such as browsing.

    Diagnostics tools

    With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself provides rather useful information, but in some cases you might have to fall back to using a sniffer. A sniffer is a program that listens on your LAN, analyses the data sent on it and displays it -on the screen.

    Debugging with Samba itself

    +on the screen.

    Debugging with Samba itself

    One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specify what -debug level at which to run. See the man pages on smbd, nmbd and +debug level at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords).

    @@ -15032,17 +15030,17 @@ Some useful samba commands worth investigating: 

     $ testparm | more
 $ smbclient -L //{netbios name of server}
-

    Tcpdump

    Tcpdump was the first +

    Tcpdump

    Tcpdump was the first unix sniffer with SMB support. It is a command-line utility and nowadays, it's SMB support is somewhat less then that of ethereal -and tethereal.

    Ethereal

    +and tethereal.

    Ethereal

    Ethereal is a graphical sniffer, available for both unix (Gtk) and Windows. Ethereal's SMB support is very good.

    For details on the use of ethereal, read the well-written ethereal User Guide.

    Listen for data on ports 137, 138, 139 and 445. E.g. use the filter port 137 or port 138 or port 139 or port 445.

    A console version of ethereal is available as well and is called -tethereal.

    The Windows Network Monitor

    +tethereal.

    The Windows Network Monitor

    For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of @@ -15052,7 +15050,7 @@ The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon formatted files. -

    Installing 'Network Monitor' on an NT Workstation

    +

    Installing 'Network Monitor' on an NT Workstation

    Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT @@ -15085,17 +15083,17 @@ Now copy the files from the NT Server in %SYSTEMROOT%\Syste to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set permissions as you deem appropriate for your site. You will need administrative rights on the NT box to run netmon. -

    Installing 'Network Monitor' on an 9x Workstation

    +

    Installing 'Network Monitor' on an 9x Workstation

    To install Netmon on a Windows 9x box install the network monitor agent from the Windows 9x CD (\admin\nettools\netmon). There is a readme file located with the netmon driver files on the CD if you need information on how to do this. Copy the files from a working Netmon installation. -

    Useful URLs

    • See how Scott Merrill simulates a BDC behavior at +

    Useful URLs

    Getting help from the mailing lists

    + ftp://ftp.microsoft.com/developr/drg/CIFS/

    Getting help from the mailing lists

    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror and then click on Support and then click on Samba related mailing lists. @@ -15129,14 +15127,14 @@ error messages.

  • (Possibly) If you have a complete netmon trace ( the pipe to the error ) you can send the *.CAP file as well.

  • Please think carefully before attaching a document to an email. Consider pasting the relevant parts into the body of the message. The samba mailing lists go to a huge number of people, do they all need a copy of your -smb.conf in their attach directory?

    • How to get off the mailing lists

    To have your name removed from a samba mailing list, go to the +smb.conf in their attach directory?

    How to get off the mailing lists

    To have your name removed from a samba mailing list, go to the same place you went to to get on it. Go to http://lists.samba.org, click on your nearest mirror and then click on Support and then click on Samba related mailing lists.

    Please don't post messages to the list asking to be removed, you will just be referred to the above address (unless that process failed in some way...) -

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using +

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using bugzilla.

    Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we @@ -15146,7 +15144,7 @@ Please also do as much as you can yourself to help track down the bug. Samba is maintained by a dedicated group of people who volunteer their time, skills and efforts. We receive far more mail about it than we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets +and a fix if you send us a "developer friendly" bug report that lets us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb @@ -15158,7 +15156,7 @@ that list that may be able to help you. You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba web pages at http://samba.org/samba/. -

    General info

    +

    General info

    Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config @@ -15170,14 +15168,14 @@ This is very important. If you include part of a log file with your bug report then be sure to annotate it with exactly what you were doing on the client at the time, and exactly what the results were. -

    Debug levels

    +

    Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably be very useful. Depending on the problem a log level of between 3 and 10 showing the problem may be appropriate. A higher level gives more detail, but may use too much disk space.

    -To set the debug level use the log level in your +To set the debug level use the log level in your smb.conf. You may also find it useful to set the log level higher for just one machine and keep separate logs for each machine. To do this add the following lines to your main smb.conf file: @@ -15186,22 +15184,22 @@ then create a file /usr/local/samba/lib/smb.conf.machine where machine is the name of the client you wish to debug. In that file put any smb.conf commands you want, for example -log level may be useful. This also allows you to +log level may be useful. This also allows you to experiment with different security systems, protocol levels etc on just one machine.

    -The smb.conf entry log level -is synonymous with the parameter debuglevel that has +The smb.conf entry log level +is synonymous with the parameter debuglevel that has been used in older versions of Samba and is being retained for backwards compatibility of smb.conf files.

    -As the log level value is increased you will record +As the log level value is increased you will record a significantly increasing level of debugging information. For most debugging operations you may not need a setting higher than 3. Nearly all bugs can be tracked at a setting of 10, but be prepared for a VERY large volume of log data. -

    Internal errors

    +

    Internal errors

    If you get a INTERNAL ERROR message in your log files it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless @@ -15214,12 +15212,12 @@ include it in your bug report.

    You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed. -

    +

    You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your samba log files. This file is the most useful tool for tracking down the bug. To use it you do this: -

    +
     $ gdb smbd core
 
    
 adding appropriate paths to smbd and core so gdb can find them. If you
@@ -15234,7 +15232,7 @@ disassemble the routine that called it) and try to work out exactly
 where the problem is by looking at the surrounding code. Even if you
 don't know assembly, including this info in the bug report can be
 useful. 
-

    Attaching to a running process

    +

    Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd does often). To debug with this sort of system you could try to attach @@ -15244,33 +15242,33 @@ to the running process using Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred. -

    Patches

    +

    Patches

    The best sort of bug report is one that includes a fix! If you send us patches please use diff -u format if your version of diff supports it, otherwise use diff -c4. Make sure you do the diff against a clean version of the source and let me know exactly what version you used. -

    Appendixes

    Table of Contents

    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft

    Chapter 36. How to compile Samba

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    +

    Appendixes

    Table of Contents

    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft

    Chapter 36. How to compile Samba

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    You can obtain the samba source from the samba website. To obtain a development version, you can download samba from CVS or using rsync. -

    Access Samba source code via CVS

    Introduction

    +

    Access Samba source code via CVS

    Introduction

    Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can be accessed via anonymous CVS using the instructions detailed in this chapter.

    This chapter is a modified version of the instructions found at http://samba.org/samba/cvs.html -

    CVS Access to samba.org

    +

    CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, including samba, rsync, distcc, ccache and jitterbug. There are two main ways of accessing the CVS server on this host. -

    Access via CVSweb

    +

    Access via CVSweb

    You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision @@ -15278,7 +15276,7 @@ history and commit logs of individual files. You can also ask for a diff listing between any two versions on the repository.

    Use the URL : http://samba.org/cgi-bin/cvsweb -

    Access via cvs

    +

    Access via cvs

    You can also access the source code via a normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees @@ -15318,7 +15316,7 @@ on this system just substitute the correct package name

    CVS branches other then HEAD can be obtained by using the -r and defining a tag name. A list of branch tag names - can be found on the "Development" page of the samba web site. A common + can be found on the "Development" page of the samba web site. A common request is to obtain the latest 3.0 release code. This could be done by using the following command:

    @@ -15328,7 +15326,7 @@ on this system just substitute the correct package name the following command from within the samba directory:

    cvs update -d -P -

    Accessing the samba sources via rsync and ftp

    +

    Accessing the samba sources via rsync and ftp

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. @@ -15337,7 +15335,7 @@ on this system just substitute the correct package name The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

    Verifying Samba's PGP signature

    +

    Verifying Samba's PGP signature

    In these days of insecurity, it's strongly recommended that you verify the PGP signature for any source file before installing it. Even if you're not downloading from a mirror site, verifying PGP signatures should be a @@ -15348,7 +15346,7 @@ With that said, go ahead and download the following files: $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    - + The first file is the PGP signature for the Samba source file; the other is the Samba public PGP key itself. Import the public PGP key with: 

    @@ -15359,29 +15357,29 @@ And verify the Samba source code integrity with:
 $ gzip -d samba-2.2.8a.tar.gz
 $ gpg --verify samba-2.2.8a.tar.asc

    -If you receive a message like, "Good signature from Samba Distribution -Verification Key..." +If you receive a message like, "Good signature from Samba Distribution +Verification Key..." then all is well. The warnings about trust relationships can be ignored. An example of what you would not want to see would be:

    - gpg: BAD signature from "Samba Distribution Verification Key" + gpg: BAD signature from "Samba Distribution Verification Key" -

    Building the Binaries

    +

    Building the Binaries

    To do this, first run the program ./configure in the source directory. This should automatically configure Samba for your operating system. If you have unusual needs then you may wish to run

    root# ./configure --help

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully + Then executing

    root# make

    will create the binaries. Once it's successfully compiled you can use 

    root# make install

    to install the binaries and manual pages. You can separately install the binaries and/or man pages using

    root# make installbin

    and

    root# make installman

    Note that if you are upgrading for a previous version of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You + the binaries will be renamed with a ".old" extension. You can go back to the previous version with

    root# make revert
-

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed +

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed on your system:

    • the MIT kerberos development libraries (either install from the sources or use a package). The Heimdal libraries will not work.

    • the OpenLDAP development libraries.

    If your kerberos libraries are in a non-standard location then @@ -15393,12 +15391,12 @@ example of what you would not want to see would be: #define HAVE_LDAP 1

    If it doesn't then configure did not find your krb5 libraries or your ldap libraries. Look in config.log to figure - out why and fix it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    + out why and fix it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    • libkrb5-dev

    • krb5-user

    -

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    +

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    • krb5-workstation (for kinit)

    • krb5-libs (for linking with)

    • krb5-devel (because you are compiling from source)

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either + to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either as daemons or from inetd. Don't try to do both! Either you can put them in inetd.conf and have them started on demand @@ -15411,7 +15409,7 @@ example of what you would not want to see would be: Samba. In many cases you must be root.

    The main advantage of starting smbd and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection - request.

    Starting from inetd.conf

    Note

    The following will be different if + request.

    Starting from inetd.conf

    Note

    The following will be different if you use NIS, NIS+ or LDAP to distribute services maps.

    Look at your /etc/services. What is defined at port 139/tcp. If nothing is defined then add a line like this:

    netbios-ssn     139/tcp

    similarly for 137/udp you should have an entry like:

    netbios-ns	137/udp

    Next edit your /etc/inetd.conf @@ -15420,13 +15418,13 @@ example of what you would not want to see would be: netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd

    The exact syntax of /etc/inetd.conf varies between unixes. Look at the other entries in inetd.conf - for a guide.

    Some distributions use xinetd instead of inetd. Consult the + for a guide.

    Some distributions use xinetd instead of inetd. Consult the xinetd manual for configuration information.

    Note

    Some unixes already have entries like netbios_ns (note the underscore) in /etc/services. You must either edit /etc/services or /etc/inetd.conf to make them consistent. -

    Note

    On many systems you may need to use the - interfaces option in smb.conf to specify the IP +

    Note

    On many systems you may need to use the + interfaces option in smb.conf to specify the IP address and netmask of your interfaces. Run ifconfig as root if you don't know what the broadcast is for your @@ -15439,7 +15437,7 @@ example of what you would not want to see would be: from inetd.

    Restart inetd, perhaps just send it a HUP. 

     			root# killall -HUP inetd
-

    Alternative: starting it as a daemon

    To start the server as a daemon you should create +

    Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling it startsmb.

     		#!/bin/sh
@@ -15451,9 +15449,9 @@ example of what you would not want to see would be:
 		
    To kill it send a kill signal to the processes 
 			nmbd and smbd.
    Note
    If you use the SVR4 style init system then 
 		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9

    Samba works on a wide range of platforms but the interface all the + script to make Samba fit into that system.

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9

    Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using samba.

    HPUX

    +platform-specific information about compiling and using samba.

    HPUX

    HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but @@ -15473,7 +15471,7 @@ allowed range. On HPUX you must use gcc or the HP ANSI compiler. The free compiler that comes with HP-UX is not ANSI compliant and cannot compile Samba. -

    SCO UNIX

    +

    SCO UNIX

    If you run an old version of SCO UNIX then you may need to get important TCP/IP patches for Samba to work correctly. Without the patch, you may encounter corrupt data transfers using samba. @@ -15481,7 +15479,7 @@ encounter corrupt data transfers using samba. The patch you need is UOD385 Connection Drivers SLS. It is available from SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). -

    DNIX

    +

    DNIX

    DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX C library for some reason. @@ -15540,11 +15538,11 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line: 

     #define NO_EID
-

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    +

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: 

    -	127.0.0.1 loopback "hostname"."domainname"
+	127.0.0.1 loopback "hostname"."domainname"

    This causes Samba to loop back onto the loopback interface. @@ -15554,10 +15552,10 @@ is the master browse list holder and who is the master browser.

    Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1 -

    AIX

    Sequential Read Ahead

    +

    AIX

    Sequential Read Ahead

    Disabling Sequential Read Ahead using vmtune -r 0 improves Samba performance significantly. -

    Solaris

    Locking improvements

    Some people have been experiencing problems with F_SETLKW64/fcntl +

    Solaris

    Locking improvements

    Some people have been experiencing problems with F_SETLKW64/fcntl when running Samba on Solaris. The built in file locking mechanism was not scalable. Performance would degrade to the point where processes would get into loops of trying to lock a file. It would try a lock, then fail, @@ -15578,9 +15576,9 @@ and rebuild samba. Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior is fixed by Sun in patch 113476-05 which as of March 2003 is not in any roll-up packages. -

    Chapter 38. Samba and other CIFS clients

    Jelmer R. Vernooij

    The Samba Team

    Jim McDonough

    OS/2
    IBM

    5 Mar 2001

    Table of Contents

    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1

    This chapter contains client-specific information.

    Macintosh clients?

    +

    Chapter 38. Samba and other CIFS clients

    Jelmer R. Vernooij

    The Samba Team

    Jim McDonough

    OS/2
    IBM

    5 Mar 2001

    Table of Contents

    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1

    This chapter contains client-specific information.

    Macintosh clients?

    Yes. Thursby now has a CIFS Client / Server called DAVE

    They test it against Windows 95, Windows NT and samba for @@ -15600,23 +15598,23 @@ What Samba offers MS Windows users, these packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems) see http://www.eats.com/linux_mac_win.html -

    Newer versions of the Macintosh (Mac OS X) include Samba.

    OS2 Client

    Configuring OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba

    Basically, you need three components:

    • The File and Print Client ('IBM Peer')

    • TCP/IP ('Internet support')

    • The "NetBIOS over TCP/IP" driver ('TCPBEUI')

    Installing the first two together with the base operating +

    Newer versions of the Macintosh (Mac OS X) include Samba.

    OS2 Client

    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba

    Basically, you need three components:

    • The File and Print Client ('IBM Peer')

    • TCP/IP ('Internet support')

    • The "NetBIOS over TCP/IP" driver ('TCPBEUI')

    Installing the first two together with the base operating system on a blank system is explained in the Warp manual. If Warp has already been installed, but you now want to install the - networking support, use the "Selective Install for Networking" - object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described + networking support, use the "Selective Install for Networking" + object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line + MPTS.EXE, click on OK, click on "Configure LAPS" and click + on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this + click on "Change number" and increase it from 0 to 1. Save this configuration.

    If the Samba server(s) is not on your local subnet, you can optionally add IP names and addresses of these servers - to the "Names List", or specify a WINS server ('NetBIOS + to the "Names List", or specify a WINS server ('NetBIOS Nameserver' in IBM and RFC terminology). For Warp Connect you may need to download an update for 'IBM Peer' to bring it on - the same level as Warp 4. See the webpage mentioned above.

    Configuring OS/2 Warp 3 (not Connect), + the same level as Warp 4. See the webpage mentioned above.

    Configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from @@ -15632,12 +15630,12 @@ packages, Samba, and Linux (and other UNIX-based systems) see or NS2000 driver from ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead. -

    Printer driver download for for OS/2 clients?

    First, create a share called [PRINTDRV] that is +

    Printer driver download for for OS/2 clients?

    First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note that the .EA_ files must still be separate, so you will need to use the original install files, and not copy an installed driver from an OS/2 system.

    Install the NT driver first for that printer. Then, - add to your smb.conf a parameter, os2 driver map = filename. Then, in the file + add to your smb.conf a parameter, os2 driver map = filename. Then, in the file specified by filename, map the name of the NT driver name to the OS/2 driver name as follows:

    nt driver name = os2 driver name.device name, e.g.:

    @@ -15647,7 +15645,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see you the driver is not available. On the second attempt, it will work. This is fixed simply by adding the device name to the mapping, after which it will work on the first attempt. -

    Windows for Workgroups

    Latest TCP/IP stack from Microsoft

    Use the latest TCP/IP stack from Microsoft if you use Windows +

    Windows for Workgroups

    Latest TCP/IP stack from Microsoft

    Use the latest TCP/IP stack from Microsoft if you use Windows for Workgroups.

    The early TCP/IP stacks had lots of bugs.

    Microsoft has released an incremental upgrade to their TCP/IP 32-Bit @@ -15662,7 +15660,7 @@ fixed. New files include WINSOCK.DLL, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE. -

    Delete .pwl files after password change

    +

    Delete .pwl files after password change

    WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password. @@ -15671,19 +15669,19 @@ If you don't do this you may find that WfWg remembers and uses the old password, even if you told it a new one.

    Often WfWg will totally ignore a password you give it in a dialog box. -

    Configuring WfW password handling

    +

    Configuring WfW password handling

    There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE. Then add an icon for it via the Program Manager New Menu. This program allows you to control how WFW handles passwords. ie disable Password Caching etc -for use with security = user -

    Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf information on password level to specify what characters samba should try to uppercase when checking.

    Use TCP/IP as default protocol

    To support print queue reporting you may find +for use with security = user +

    Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf information on password level to specify what characters samba should try to uppercase when checking.

    Use TCP/IP as default protocol

    To support print queue reporting you may find that you have to use TCP/IP as the default protocol under WfWg. For some reason if you leave NetBEUI as the default it may break the print queue reporting on some systems. -It is presumably a WfWg bug.

    Speed improvement

    +It is presumably a WfWg bug.

    Speed improvement

    Note that some people have found that setting DefaultRcvWindow in the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a @@ -15694,7 +15692,7 @@ performance with a large value (16384 or larger). Other people have reported that anything over 3072 slows things down enormously. One person even reported a speed drop of a factor of 30 when he went from 3072 to 8192. I don't know why. -

    Windows '95/'98

    +

    Windows '95/'98

    When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these updates have been installed. @@ -15708,11 +15706,11 @@ install the OLEUPD.EXE fix. This fix may stop your machine from hanging for an extended period when exiting Outlook and you may also notice a significant speedup when accessing network neighborhood services. -

    Speed improvement

    +

    Speed improvement

    Configure the win95 TCPIP registry settings to give better performance. I use a program called MTUSPEED.exe which I got off the net. There are various other utilities of this type freely available. -

    Windows 2000 Service Pack 2

    +

    Windows 2000 Service Pack 2

    There are several annoyances with Windows 2000 SP2. One of which only appears when using a Samba server to host user profiles to Windows 2000 SP2 clients in a Windows domain. This assumes @@ -15721,7 +15719,7 @@ likely occur if it is not.

    In order to serve profiles successfully to Windows 2000 SP2 clients (when not operating as a PDC), Samba must have -nt acl support = no +nt acl support = no added to the file share which houses the roaming profiles. If this is not done, then the Windows 2000 SP2 client will complain about not being able to access the profile (Access @@ -15729,11 +15727,11 @@ Denied) and create multiple copies of it on disk (DOMAIN.user.001, DOMAIN.user.002, etc...). See the smb.conf man page for more details on this option. Also note that the -nt acl support parameter was formally a global parameter in +nt acl support parameter was formally a global parameter in releases prior to Samba 2.2.2.

    The following is a minimal profile share: -

    Example 38.1. Minimal profile share

    [profile]
    path = /export/profile
    create mask = 0600
    directory mask = 0700
    nt acl support = no
    read only = no

    +

    Example 38.1. Minimal profile share

    [profile]
    path = /export/profile
    create mask = 0600
    directory mask = 0700
    nt acl support = no
    read only = no

    The reason for this bug is that the Win2k SP2 client copies the security descriptor for the profile which contains the Samba server's SID, and not the domain SID. The client @@ -15741,15 +15739,15 @@ compares the SID for SAMBA\user and realizes it is different that the one assigned to DOMAIN\user. Hence the reason for the access denied message.

    -By disabling the nt acl support parameter, Samba will send +By disabling the nt acl support parameter, Samba will send the Win2k client a response to the QuerySecurityDescriptor trans2 call which causes the client to set a default ACL for the profile. This default ACL includes -

    DOMAIN\user "Full Control">

    Note

    This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.

    Windows NT 3.1

    If you have problems communicating across routers with Windows +

    DOMAIN\user "Full Control">

    Note

    This bug does not occur when using winbind to +create accounts on the Samba host for Domain users.

    Windows NT 3.1

    If you have problems communicating across routers with Windows NT 3.1 workstations, read this Microsoft Knowledge Base article. -

    Chapter 39. Samba Performance Tuning

    Paul Cochrane

    Dundee Limb Fitting Centre

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files

    Comparisons

    +

    Chapter 39. Samba Performance Tuning

    Paul Cochrane

    Dundee Limb Fitting Centre

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files

    Comparisons

    The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to programs that use the same protocol. The most readily available @@ -15771,14 +15769,14 @@ suspect the biggest factor is not Samba vs some other system but the hardware and drivers used on the various systems. Given similar hardware Samba should certainly be competitive in speed with other systems. -

    Socket options

    +

    Socket options

    There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.

    The socket options that Samba uses are settable both on the command line with the -O option, or in the smb.conf file.

    -The socket options section of the smb.conf manual page describes how +The socket options section of the smb.conf manual page describes how to set these and gives recommendations.

    Getting the socket options right can make a big difference to your @@ -15787,11 +15785,11 @@ much. The correct settings are very dependent on your local network.

    The socket option TCP_NODELAY is the one that seems to make the biggest single difference for most networks. Many people report that -adding socket options = TCP_NODELAY doubles the read +adding socket options = TCP_NODELAY doubles the read performance of a Samba drive. The best explanation I have seen for this is that the Microsoft TCP/IP stack is slow in sending tcp ACKs. -

    Read size

    -The option read size affects the overlap of disk +

    Read size

    +The option read size affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing @@ -15807,10 +15805,10 @@ The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is pointless and will cause you to allocate memory unnecessarily. -

    Max xmit

    +

    Max xmit

    At startup the client and server negotiate a maximum transmit size, which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the max xmit option +maximum size that Samba will negotiate using the max xmit option in smb.conf. Note that this is the maximum size of SMB requests that Samba will accept, but not the maximum size that the *client* will accept. The client maximum receive size is sent to Samba by the client and Samba @@ -15821,41 +15819,41 @@ clients may perform better with a smaller transmit unit. Trying values of less than 2048 is likely to cause severe problems.

    In most cases the default is the best option. -

    Log level

    -If you set the log level (also known as debug level) higher than 2 +

    Log level

    +If you set the log level (also known as debug level) higher than 2 then you may suffer a large drop in performance. This is because the server flushes the log file after each operation, which can be very expensive. -

    Read raw

    -The read raw operation is designed to be an optimised, low-latency +

    Read raw

    +The read raw operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, -however. and Samba makes support for read raw optional, with it +however. and Samba makes support for read raw optional, with it being enabled by default.

    -In some cases clients don't handle read raw very well and actually +In some cases clients don't handle read raw very well and actually get lower performance using it than they get using the conventional read operations.

    -So you might like to try read raw = no and see what happens on your +So you might like to try read raw = no and see what happens on your network. It might lower, raise or not affect your performance. Only testing can really tell. -

    Write raw

    -The write raw operation is designed to be an optimised, low-latency +

    Write raw

    +The write raw operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, -however. and Samba makes support for write raw optional, with it +however. and Samba makes support for write raw optional, with it being enabled by default.

    -Some machines may find write raw slower than normal write, in which +Some machines may find write raw slower than normal write, in which case you may wish to change this option. -

    Slow Logins

    +

    Slow Logins

    Slow logins are almost always due to the password checking time. Using -the lowest practical password level will improve things. -

    Client tuning

    +the lowest practical password level will improve things. +

    Client tuning

    Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP performance. Check the sections on the various clients in Samba and Other Clients. -

    Samba performance problem due changing kernel

    +

    Samba performance problem due changing kernel

    Hi everyone. I am running Gentoo on my server and samba 2.2.8a. Recently I changed kernel version from linux-2.4.19-gentoo-r10 to linux-2.4.20-wolk4.0s. And now I have performance issue with samba. Ok @@ -15870,7 +15868,7 @@ Grab mii-tool and check the duplex settings on the NIC. My guess is that it is a link layer issue, not an application layer problem. Also run ifconfig and verify that the framing error, collisions, etc... look normal for ethernet. -

    Corrupt tdb Files

    +

    Corrupt tdb Files

    Well today it happened, Our first major problem using samba. Our samba PDC server has been hosting 3 TB of data to our 500+ users [Windows NT/XP] for the last 3 years using samba, no problem. @@ -15888,12 +15886,12 @@ Q2) What I also would like to mention is that the service latency seems a lot lower then before the locks cleanup, any ideas on keeping it top notch?

    A2) Yes! Same answer as for Q1! -

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Chapter 41. Further Resources

    Jelmer R. Vernooij

    The Samba Team

    May 1, 2003

    Table of Contents

    Websites
    Related updates from Microsoft

    Websites

    • +

    Chapter 41. Further Resources

    Jelmer R. Vernooij

    The Samba Team

    May 1, 2003

    Table of Contents

    Websites
    Related updates from Microsoft

    Websites

    Related updates from Microsoft

    Related updates from Microsoft

    Index

    Symbols

    "Domain Admins" group, Discussion
    "Domain Users" group, Adding Domain Users to the Power Users group
    "Printers" folder, Caveats to be considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    "raw" printing, CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    /etc/host.conf, /etc/host.conf
    /etc/hosts, /etc/hosts
    /etc/nsswitch.conf, /etc/nsswitch.conf
    8.3
    file names, MS Windows NTFS Comparison with UNIX File Systems

    A

    ACLs, File, Directory and Share Access Controls
    Active Directory, Samba ADS Domain Membership
    add group script, Adding Groups Fails
    add machine script, The machine trust account not accessible, Adding Machine to Domain Fails
    add printer command, Adding new Printers with the Windows NT APW
    add printer wizard, Three familiar Methods for driver upload plus a new one
    add user script, Mapping User Identifiers between MS Windows and UNIX
    addprinter command, Parameters Recommended for Use
    admin users, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!
    Administrator, Discussion
    ADS (see Active Directory)
    ads server, Setup your smb.conf
    application/cups.vnd-postscript, Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver
    application/octet-stream, Explicitly enable "raw" printing for -application/octet-stream!, MIME type Conversion Rules, "application/octet-stream" printing
    application/pdf, MIME types and CUPS Filters
    application/postscript, Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver
    application/vnd.cups-raster, PostScript Printer Descriptions (PPDs) for non-PS Printers
    application/vnd.cups-raw, Explicitly enable "raw" printing for -application/octet-stream!
    auth methods, auth methods does not work, Passdb Backends and Authentication

    B

    bind interfaces only, The tests
    brlock.tdb, The printing *.tdb Files
    (see also TDB)
    browse list, What is Browsing?, Technical Overview of browsing
    browseable, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    C

    case sensitive, Miscellaneous Controls, Windows 9x / Me Profile Setup
    chpass, Manual Creation of Machine Trust Accounts
    client use spnego, I can't join a Windows 2003 PDC
    comment, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section
    configure, Building the Binaries
    connections.tdb, The printing *.tdb Files
    (see also TDB)
    core files, Internal errors
    create mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    csc policy, Miscellaneous Controls
    CUPS
    Page Accounting, Page Accounting with CUPS
    quotas, Setting up Quotas
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cupsaddsmb, Three familiar Methods for driver upload plus a new one, cupsaddsmb: the unknown Utility, Caveats to be considered, Run "cupsaddsmb" (quiet Mode), Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, cupsaddsmb with a Samba PDC, cupsaddsmb Flowchart
    cupsomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and -native CUPS printing, cupsomatic, pdqomatic, lpdomatic, directomatic
    CVS, Access Samba source code via CVS
    web, Access via CVSweb

    D

    daemon, Alternative: starting it as a daemon
    DDK, PostScript Drivers with no major problems -- even in Kernel -Mode, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    debug, Internal errors
    debug level, Debugging with Samba itself, Log level
    debuglevel, Debug levels
    default case, Miscellaneous Controls
    delete printer command, Adding new Printers with the Windows NT APW
    deleteprinter command, Parameters Recommended for Use
    DHCP, Background Information
    diff, Patches
    directory mask, File and Directory Permissions Based Controls
    directory security mask, Interaction with the standard Samba create mask - parameters
    disable spoolss, Parameters Recommended for Use
    display charset, Samba and charsets
    DNS, TCP/IP - without NetBIOS, DNS Lookup
    Active Directory, DNS and Active Directory
    Dynamic, Background Information
    dns proxy, What is Browsing?
    domain admin group, Mapping MS Windows and UNIX Groups
    domain logons, Preparing for Domain Control
    domain master, Domain Network Logon Service, Example Configuration, What is Browsing?, Making Samba the domain master
    dont descend, Miscellaneous Controls
    dos charset, Samba and charsets, Japanese charsets, CP850.so can't be found
    dos filemode, File and Directory Permissions Based Controls
    dos filetime resolution, Miscellaneous Controls
    dos filetimes, Miscellaneous Controls

    E

    EMF, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    encrypt passwords, Joining an NT4 type Domain with Samba-3, smbpasswd - Encrypted Password Database, smb.conf PAM Configuration, The tests
    enhanced browsing, What is Browsing?
    enumports command, Parameters Recommended for Use, Samba and Printer Ports
    EPM (see ESP meta packager)
    ESC/P, Driver Execution on the Server
    ESP
    Ghostscript, The CUPS Filtering Architecture, Difference between cupsomatic/foomatic-rip and -native CUPS printing
    meta packager, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Print Pro, Sources of CUPS drivers / PPDs, ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Extended Attributes, File, Directory and Share Access Controls

    F

    fake oplocks, Miscellaneous Controls
    File System, File System Access Controls
    foomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and -native CUPS printing, foomatic-rip and Foomatic explained, Foomatic's strange Name
    foomatic-rip, Difference between cupsomatic/foomatic-rip and -native CUPS printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic explained, The Grand Unification -achieved...
    force create mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    force directory mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    force directory security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    force group, User and Group Based Controls
    force security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    force user, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!, Beware of Force User
    ftp, Accessing the samba sources via rsync and ftp

    G

    gdb, Internal errors
    GDI, GDI on Windows -- PostScript on UNIX, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    GhostScript, PostScript and Ghostscript, Ghostscript -- the Software RIP for non-PostScript Printers
    (see also PostScript)
    Ghostscript
    ESP (see ESP GhostScript)
    GID, Features and Benefits
    GPG, Verifying Samba's PGP signature
    groupadd, Features and Benefits
    groupdel, Features and Benefits
    groups
    domain, Discussion
    mapping, Mapping MS Windows and UNIX Groups
    nested, Adding MS Windows Groups to MS Windows Groups Fails
    guest account, Problem resolution, My client reports "This server is not configured to list shared resources", The [printers] Section
    guest ok, User and Group Based Controls, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    H

    hide dot files, Miscellaneous Controls
    hide files, Miscellaneous Controls
    hide unreadable, File and Directory Permissions Based Controls
    hide unwriteable files, File and Directory Permissions Based Controls
    host msdfs, Features and Benefits
    hosts allow, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section
    hosts deny, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section

    I

    idmap gid, Features and Benefits, Winbind is not resolving users and groups
    idmap uid, Features and Benefits, Winbind is not resolving users and groups
    ifconfig, Starting from inetd.conf
    imprints, Three familiar Methods for driver upload plus a new one
    inetd, The tests, Starting the smbd and nmbd, Starting from inetd.conf
    Interdomain Trusts, Interdomain Trust Relationships
    completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Inter-Domain Trust Facilities
    interfaces, Multiple interfaces, The tests, Starting from inetd.conf
    invalid users, User and Group Based Controls
    IPP, Understanding cupsaddsmb

    K

    KDC, Samba ADS Domain Membership
    Kerberos, Samba ADS Domain Membership
    kinit, Setup your /etc/krb5.conf

    L

    ldap admin dn, Configuring Samba
    ldap delete dn, Configuring Samba
    ldap filter, Configuring Samba
    ldap machine suffix, Configuring Samba
    ldap passwd sync, Configuring Samba, Password synchronisation
    ldap ssl, Configuring Samba, Security and sambaSamAccount
    ldap suffix, Configuring Samba
    ldap trust ids, Configuring Samba
    ldap user suffix, Configuring Samba
    libnss_wins.so, /etc/nsswitch.conf
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linuxprinting.org, CUPS Print Drivers from Linuxprinting.org
    lm announce, What is Browsing?
    lm interval, What is Browsing?
    LMB (see Local Master Browser)
    LMHOSTS, The LMHOSTS file
    load printers, Parameters Recommended for Use, A little Experiment to warn you, The [global] Section
    local master, What is Browsing?, Setting up WORKGROUP Browsing
    Local Master Browser, Use of the Remote Announce parameter
    locking, Discussion
    locking.tdb, The printing *.tdb Files
    (see also TDB)
    log files
    monitoring, Assumptions
    log level, Adding Machine to Domain Fails, extd_audit, Debug levels
    logon drive, Windows NT4 Workstation
    logon home, LDAP special attributes for sambaSamAccounts, Windows 9x / Me User Profiles, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon path, LDAP special attributes for sambaSamAccounts, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows 9x / Me Profile Setup, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon script, LDAP special attributes for sambaSamAccounts
    lpadmin, CUPS Print Drivers from Linuxprinting.org, Setting up Quotas
    lppause command, Parameters Recommended for Use, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    lpq cache time, Parameters Recommended for Use, The [global] Section
    lpq command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpresume command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lprm command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpstat, Troubleshooting revisited

    M

    MAC Addresses, /etc/hosts
    machine trust accounts, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    make, Building the Binaries
    mangling method, Japanese charsets
    map to guest, Parameters in the [print$] Section, Adding new Printers with the Windows NT APW, Can't reconnect to Samba under new account - from Win2K/XP, Avoid being connected to the Samba server as the - "wrong" user
    max print jobs, Parameters Recommended for Use
    max xmit, Max xmit
    messages.tdb, The printing *.tdb Files
    (see also TDB)
    MIME, MIME types and CUPS Filters, MIME type Conversion Rules, Filter Requirements, "application/octet-stream" printing
    min print space, Parameters Recommended for Use
    msdfs root, Features and Benefits

    N

    name resolve order, What is Browsing?
    nbtstat, The NetBIOS Name Cache
    NetBIOS, Features and Benefits, TCP/IP - without NetBIOS, Integrating MS Windows networks with Samba, Name resolution as used within MS Windows networking
    NetBIOS-less, TCP/IP - without NetBIOS
    nmblookup, The NetBIOS Name Cache
    nt acl support, File and Directory Permissions Based Controls, Viewing file ownership, Viewing File or Directory Permissions, Modifying file or directory permissions, Windows 2000 Service Pack 2
    ntdrivers.tdb, The printing *.tdb Files
    (see also TDB)
    ntforms.tdb, The printing *.tdb Files
    (see also TDB)
    NTFS, File System Access Controls
    ntprinters.tdb, The printing *.tdb Files
    (see also TDB)

    O

    obey pam restrictions, smb.conf PAM Configuration
    only user, User and Group Based Controls, Why can users access home directories of other users?
    oplock break wait time, Advanced Samba Opportunistic Locking Parameters, Disabling Kernel OpLocks
    oplock contention limit, Advanced Samba Opportunistic Locking Parameters
    os level, What is Browsing?, Setting up WORKGROUP Browsing, Setting up DOMAIN Browsing, Forcing Samba to be the master, Making Samba the domain master
    os2 driver map, Parameters Recommended for Use, Printer driver download for for OS/2 clients?

    P

    page_log, The page_log File Syntax
    passdb backend, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, Technical Information, The pdbedit Command, Configuring Samba, Configuring, Users can not logon, auth methods does not work, Passdb Backends and Authentication
    password level, Password checking, The tests, Case handling of passwords, Slow Logins
    password server, Server Security (User Level Security), Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, The tests
    patch, Patches
    path, "The network name cannot be found", The [printers] Section, Any [my_printer_name] Section, Print Commands, Creating the [print$] Share, Parameters in the [print$] Section, Subdirectory Structure in [print$], Samba receiving Jobfiles and passing them to CUPS, Auto-Deletion or Preservation of CUPS Spool Files, Permissions on +

    Index

    Symbols

    "Domain Admins" group, Discussion
    "Domain Users" group, Adding Domain Users to the Power Users group
    "Printers" folder, Caveats to be considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    "raw" printing, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    /etc/host.conf, /etc/host.conf
    /etc/hosts, /etc/hosts
    /etc/nsswitch.conf, /etc/nsswitch.conf
    8.3
    file names, MS Windows NTFS Comparison with UNIX File Systems

    A

    ACLs, File, Directory and Share Access Controls
    Active Directory, Samba ADS Domain Membership
    add group script, Adding Groups Fails
    add machine script, The machine trust account not accessible, Adding Machine to Domain Fails
    add printer command, Adding new Printers with the Windows NT APW
    add printer wizard, Three familiar Methods for driver upload plus a new one
    add user script, Mapping User Identifiers between MS Windows and UNIX
    addprinter command, Parameters Recommended for Use
    admin users, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!
    Administrator, Discussion
    ADS (see Active Directory)
    ads server, Setup your smb.conf
    application/cups.vnd-postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    application/octet-stream, Explicitly enable "raw" printing for +application/octet-stream!, MIME type Conversion Rules, "application/octet-stream" printing
    application/pdf, MIME types and CUPS Filters
    application/postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    application/vnd.cups-raster, PostScript Printer Descriptions (PPDs) for non-PS Printers
    application/vnd.cups-raw, Explicitly enable "raw" printing for +application/octet-stream!
    auth methods, auth methods does not work, Passdb Backends and Authentication

    B

    bind interfaces only, The tests
    brlock.tdb, The printing *.tdb Files
    (see also TDB)
    browse list, What is Browsing?, Technical Overview of browsing
    browseable, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    C

    case sensitive, Miscellaneous Controls, Windows 9x / Me Profile Setup
    chpass, Manual Creation of Machine Trust Accounts
    comment, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section
    configure, Building the Binaries
    connections.tdb, The printing *.tdb Files
    (see also TDB)
    core files, Internal errors
    create mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    csc policy, Miscellaneous Controls
    CUPS
    Page Accounting, Page Accounting with CUPS
    quotas, Setting up Quotas
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cupsaddsmb, Three familiar Methods for driver upload plus a new one, cupsaddsmb: the unknown Utility, Caveats to be considered, Run "cupsaddsmb" (quiet Mode), Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, cupsaddsmb with a Samba PDC, cupsaddsmb Flowchart
    cupsomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, cupsomatic, pdqomatic, lpdomatic, directomatic
    CVS, Access Samba source code via CVS
    web, Access via CVSweb

    D

    daemon, Alternative: starting it as a daemon
    DDK, PostScript Drivers with no major problems -- even in Kernel +Mode, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    debug, Internal errors
    debug level, Debugging with Samba itself, Log level
    debuglevel, Debug levels
    default case, Miscellaneous Controls
    delete printer command, Adding new Printers with the Windows NT APW
    deleteprinter command, Parameters Recommended for Use
    DHCP, Background Information
    diff, Patches
    directory mask, File and Directory Permissions Based Controls
    directory security mask, Interaction with the standard Samba create mask + parameters
    disable spoolss, Parameters Recommended for Use
    display charset, Samba and charsets
    DNS, TCP/IP - without NetBIOS, DNS Lookup
    Active Directory, DNS and Active Directory
    Dynamic, Background Information
    dns proxy, What is Browsing?
    domain admin group, Mapping MS Windows and UNIX Groups
    domain logons, Preparing for Domain Control
    domain master, Domain Network Logon Service, Example Configuration, What is Browsing?, Making Samba the domain master
    dont descend, Miscellaneous Controls
    dos charset, Samba and charsets, Japanese charsets, CP850.so can't be found
    dos filemode, File and Directory Permissions Based Controls
    dos filetime resolution, Miscellaneous Controls
    dos filetimes, Miscellaneous Controls

    E

    EMF, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    encrypt passwords, Joining an NT4 type Domain with Samba-3, smbpasswd - Encrypted Password Database, smb.conf PAM Configuration, The tests
    enhanced browsing, What is Browsing?
    enumports command, Parameters Recommended for Use, Samba and Printer Ports
    EPM (see ESP meta packager)
    ESC/P, Driver Execution on the Server
    ESP
    Ghostscript, The CUPS Filtering Architecture, Difference between cupsomatic/foomatic-rip and +native CUPS printing
    meta packager, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Print Pro, Sources of CUPS drivers / PPDs, ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Extended Attributes, File, Directory and Share Access Controls

    F

    fake oplocks, Miscellaneous Controls
    File System, File System Access Controls
    foomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, foomatic-rip and Foomatic explained, Foomatic's strange Name
    foomatic-rip, Difference between cupsomatic/foomatic-rip and +native CUPS printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic explained, The Grand Unification +achieved...
    force create mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force group, User and Group Based Controls
    force security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force user, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!, Beware of Force User
    ftp, Accessing the samba sources via rsync and ftp

    G

    gdb, Internal errors
    GDI, GDI on Windows -- PostScript on UNIX, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    GhostScript, PostScript and Ghostscript, Ghostscript -- the Software RIP for non-PostScript Printers
    (see also PostScript)
    Ghostscript
    ESP (see ESP GhostScript)
    GID, Features and Benefits
    GPG, Verifying Samba's PGP signature
    groupadd, Features and Benefits
    groupdel, Features and Benefits
    groups
    domain, Discussion
    mapping, Mapping MS Windows and UNIX Groups
    nested, Adding MS Windows Groups to MS Windows Groups Fails
    guest account, Problem resolution, My client reports "This server is not configured to list shared resources", The [printers] Section
    guest ok, User and Group Based Controls, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    H

    hide dot files, Miscellaneous Controls
    hide files, Miscellaneous Controls
    hide unreadable, File and Directory Permissions Based Controls
    hide unwriteable files, File and Directory Permissions Based Controls
    host msdfs, Features and Benefits
    hosts allow, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section
    hosts deny, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section

    I

    idmap gid, Features and Benefits, Winbind is not resolving users and groups
    idmap uid, Features and Benefits, Winbind is not resolving users and groups
    ifconfig, Starting from inetd.conf
    imprints, Three familiar Methods for driver upload plus a new one
    inetd, The tests, Starting the smbd and nmbd, Starting from inetd.conf
    Interdomain Trusts, Interdomain Trust Relationships
    completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Inter-Domain Trust Facilities
    interfaces, Multiple interfaces, The tests, Starting from inetd.conf
    invalid users, User and Group Based Controls
    IPP, Understanding cupsaddsmb

    K

    KDC, Samba ADS Domain Membership
    Kerberos, Samba ADS Domain Membership
    kinit, Setup your /etc/krb5.conf

    L

    ldap admin dn, Configuring Samba
    ldap delete dn, Configuring Samba
    ldap filter, Configuring Samba
    ldap machine suffix, Configuring Samba
    ldap passwd sync, Configuring Samba, Password synchronisation
    ldap ssl, Configuring Samba, Security and sambaSamAccount
    ldap suffix, Configuring Samba
    ldap trust ids, Configuring Samba
    ldap user suffix, Configuring Samba
    libnss_wins.so, /etc/nsswitch.conf
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linuxprinting.org, CUPS Print Drivers from Linuxprinting.org
    lm announce, What is Browsing?
    lm interval, What is Browsing?
    LMB (see Local Master Browser)
    LMHOSTS, The LMHOSTS file
    load printers, Parameters Recommended for Use, A little Experiment to warn you, The [global] Section
    local master, What is Browsing?, Setting up WORKGROUP Browsing
    Local Master Browser, Use of the Remote Announce parameter
    locking, Discussion
    locking.tdb, The printing *.tdb Files
    (see also TDB)
    log files
    monitoring, Assumptions
    log level, Adding Machine to Domain Fails, extd_audit, Debug levels
    logon drive, Windows NT4 Workstation
    logon home, LDAP special attributes for sambaSamAccounts, Windows 9x / Me User Profiles, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon path, LDAP special attributes for sambaSamAccounts, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows 9x / Me Profile Setup, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon script, LDAP special attributes for sambaSamAccounts
    lpadmin, CUPS Print Drivers from Linuxprinting.org, Setting up Quotas
    lppause command, Parameters Recommended for Use, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    lpq cache time, Parameters Recommended for Use, The [global] Section
    lpq command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpresume command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lprm command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpstat, Troubleshooting revisited

    M

    MAC Addresses, /etc/hosts
    machine trust accounts, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    make, Building the Binaries
    mangling method, Japanese charsets
    map to guest, Parameters in the [print$] Section, Adding new Printers with the Windows NT APW, Can't reconnect to Samba under new account + from Win2K/XP, Avoid being connected to the Samba server as the + "wrong" user
    max print jobs, Parameters Recommended for Use
    max xmit, Max xmit
    messages.tdb, The printing *.tdb Files
    (see also TDB)
    MIME, MIME types and CUPS Filters, MIME type Conversion Rules, Filter Requirements, "application/octet-stream" printing
    min print space, Parameters Recommended for Use
    msdfs root, Features and Benefits

    N

    name resolve order, What is Browsing?
    nbtstat, The NetBIOS Name Cache
    NetBIOS, Features and Benefits, TCP/IP - without NetBIOS, Integrating MS Windows networks with Samba, Name resolution as used within MS Windows networking
    NetBIOS-less, TCP/IP - without NetBIOS
    nmblookup, The NetBIOS Name Cache
    nt acl support, File and Directory Permissions Based Controls, Viewing file ownership, Viewing File or Directory Permissions, Modifying file or directory permissions, Windows 2000 Service Pack 2
    ntdrivers.tdb, The printing *.tdb Files
    (see also TDB)
    ntforms.tdb, The printing *.tdb Files
    (see also TDB)
    NTFS, File System Access Controls
    ntprinters.tdb, The printing *.tdb Files
    (see also TDB)

    O

    obey pam restrictions, smb.conf PAM Configuration
    only user, User and Group Based Controls, Why can users access home directories of other users?
    oplock break wait time, Advanced Samba Opportunistic Locking Parameters, Disabling Kernel OpLocks
    oplock contention limit, Advanced Samba Opportunistic Locking Parameters
    os level, What is Browsing?, Setting up WORKGROUP Browsing, Setting up DOMAIN Browsing, Forcing Samba to be the master, Making Samba the domain master
    os2 driver map, Parameters Recommended for Use, Printer driver download for for OS/2 clients?

    P

    page_log, The page_log File Syntax
    passdb backend, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, Technical Information, The pdbedit Command, Configuring Samba, Configuring, Users can not logon, auth methods does not work, Passdb Backends and Authentication
    password level, Password checking, The tests, Case handling of passwords, Slow Logins
    password server, Server Security (User Level Security), Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, The tests
    patch, Patches
    path, "The network name cannot be found", The [printers] Section, Any [my_printer_name] Section, Print Commands, Creating the [print$] Share, Parameters in the [print$] Section, Subdirectory Structure in [print$], Samba receiving Jobfiles and passing them to CUPS, Auto-Deletion or Preservation of CUPS Spool Files, Permissions on /var/spool/samba/ get reset after each -reboot, The tests
    PCL, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    PDF, Windows Drivers, GDI and EMF, PostScript Printer Description (PPD) Specification
    pdf, MIME type Conversion Rules
    PDL, GDI on Windows -- PostScript on UNIX, PostScript and Ghostscript
    PJL, Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs, Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    point and print, Driver Installation Methods on Windows Clients, Three familiar Methods for driver upload plus a new one, cupsomatic/Foomatic -- how do they fit into the Picture?, Run "cupsaddsmb" (quiet Mode), Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    PostScript, Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, Prefilters, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs, CUPS: a "Magical Stone"?, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PPD, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, PostScript Printer Descriptions (PPDs) for non-PS Printers, PPDs for non-PS Printers on UNIX, PPDs for non-PS Printers on Windows, CUPS: a "Magical Stone"?, Installing the PostScript Driver on a Client
    CUPS (see CUPS-PPD)
    preferred master, What is Browsing?, Setting up WORKGROUP Browsing, Forcing Samba to be the master, Making Samba the domain master, The tests
    preserve case, Windows 9x / Me Profile Setup
    print command, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    print ok , Parameters Recommended for Use
    printable, Parameters Recommended for Use, The [printers] Section, Any [my_printer_name] Section
    printcap, Parameters Recommended for Use, Default Print Commands for various UNIX Print Subsystems, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for -CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    printcap name, Parameters Recommended for Use, The [global] Section
    printer, Parameters Recommended for Use
    printer admin, Parameters Recommended for Use, The [global] Section, Any [my_printer_name] Section, Parameters in the [print$] Section, Setting Drivers for existing Printers with a Client GUI, IMPORTANT! Setting Device Modes on new Printers, Always make first Client Connection as root or "printer admin", Setting Default Print Options for the Client Drivers, Adding new Printers with the Windows NT APW, More complex smb.conf Settings for -CUPS, What is required for adddriver and setdriver to succeed, Print options for all users can't be set on Win2K/XP
    printer name, Parameters Recommended for Use
    printing, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for -CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    printing.tdb, The printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    public, The [printers] Section

    Q

    queue resume command, Linking of smbd with libcups.so
    queuepause command, Parameters Recommended for Use, Linking of smbd with libcups.so
    queueresume command, Parameters Recommended for Use

    R

    read list, User and Group Based Controls
    read only, Miscellaneous Controls, The [printers] Section, Parameters in the [print$] Section
    read raw, Read raw
    read size, Read size
    remote announce, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Announce parameter, Browsing support in Samba
    remote browse sync, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Browse Sync parameter
    root preexec, Logon Scripts
    rpcclient
    adddriver, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using -rpcclient), Understanding the rpcclient man page, What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    enumdrivers, Installing PostScript Driver Files manually (using -rpcclient), Manual Driver Installation in 15 Steps
    enumports, Installing PostScript Driver Files manually (using -rpcclient)
    enumprinters, Installing PostScript Driver Files manually (using -rpcclient), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps, Troubleshooting revisited
    getdriver, Producing an Example by querying a Windows Box, Manual Driver Installation in 15 Steps
    getprinter, Producing an Example by querying a Windows Box, Manual Driver Installation in 15 Steps, Troubleshooting revisited
    setdriver, Caveats to be considered, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using -rpcclient), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    rsync, Accessing the samba sources via rsync and ftp

    S

    secrets.tdb, The printing *.tdb Files
    (see also TDB)
    security, Samba Security Modes, Domain Security Mode (User Level Security), Server Security (User Level Security), What makes Samba a SERVER?, What makes Samba a Domain Controller?, What makes Samba a Domain Member?, Constantly Losing Connections to Password Server, Preparing for Domain Control, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Why is this better than security = server?, Setup your smb.conf, Run "cupsaddsmb" (quiet Mode), "cupsaddsmb" keeps asking for root password in - neverending loop, Passdb Backends and Authentication, The tests, Configuring WfW password handling
    security mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask - parameters
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts
    sessionid.tdb, The printing *.tdb Files
    (see also TDB)
    share_info.tdb, The printing *.tdb Files
    (see also TDB)
    short preserve case, Miscellaneous Controls, Windows 9x / Me Profile Setup
    Short-Cuts, MS Windows NTFS Comparison with UNIX File Systems
    show add printer wizard, Parameters Recommended for Use, The [global] Section, Adding new Printers with the Windows NT APW
    SID, Features and Benefits
    Single Sign On, Caveats to be considered
    smbclient, Testing with smbclient, The tests
    socket options, Socket options
    spooling
    central, Central spooling vs. "Peer-to-Peer" printing
    peer-to-peer, Central spooling vs. "Peer-to-Peer" printing
    spooling-only, CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    strict locking, Discussion

    T

    TDB, The printing *.tdb Files, Trivial DataBase Files
    backing up (see tdbbackup)
    tdbbackup, Using tdbbackup
    template homedir, Linux/FreeBSD-specific PAM configuration
    testparm, The tests
    text/plain, MIME type Conversion Rules
    total print jobs, Parameters Recommended for Use, The [global] Section

    U

    UDP, NetBIOS over TCP/IP
    UID, Features and Benefits
    unexpected.tdb, The printing *.tdb Files
    (see also TDB)
    unix charset, Samba and charsets, Japanese charsets
    use client driver, Parameters Recommended for Use, The [global] Section
    user, Share Level Security, The tests
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain
    useradd, Manual Creation of Machine Trust Accounts
    username, User and Group Based Controls
    username level, Password checking
    username map, Windows 200x XP Professional

    V

    valid users, User and Group Based Controls, The tests
    veto files, Miscellaneous Controls
    vfs objects, Discussion
    vipw, Manual Creation of Machine Trust Accounts

    W

    winbind separator, Start up the winbindd daemon and test it!
    WINS, What is Browsing?, NetBIOS over TCP/IP, WINS Lookup
    wins hook, What is Browsing?
    wins proxy, What is Browsing?
    wins server, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    wins support, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    workgroup, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Browsing support in Samba
    write list, User and Group Based Controls, Parameters in the [print$] Section
    write raw, Write raw
    writeable, The [printers] Section, Any [my_printer_name] Section
    WYSIWYG, Windows Drivers, GDI and EMF

    X

    X Window System, UNIX Printfile Conversion and GUI Basics
    xinetd, Starting from inetd.conf (see inetd)
    Xprint, UNIX Printfile Conversion and GUI Basics
    +reboot, The tests
    PCL, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    PDF, Windows Drivers, GDI and EMF, PostScript Printer Description (PPD) Specification
    pdf, MIME type Conversion Rules
    PDL, GDI on Windows -- PostScript on UNIX, PostScript and Ghostscript
    PJL, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    point and print, Driver Installation Methods on Windows Clients, Three familiar Methods for driver upload plus a new one, cupsomatic/Foomatic -- how do they fit into the Picture?, Run "cupsaddsmb" (quiet Mode), Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    PostScript, Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, Prefilters, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, CUPS: a "Magical Stone"?, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PPD, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, PostScript Printer Descriptions (PPDs) for non-PS Printers, PPDs for non-PS Printers on UNIX, PPDs for non-PS Printers on Windows, CUPS: a "Magical Stone"?, Installing the PostScript Driver on a Client
    CUPS (see CUPS-PPD)
    preferred master, What is Browsing?, Setting up WORKGROUP Browsing, Forcing Samba to be the master, Making Samba the domain master, The tests
    preserve case, Windows 9x / Me Profile Setup
    print command, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    print ok , Parameters Recommended for Use
    printable, Parameters Recommended for Use, The [printers] Section, Any [my_printer_name] Section
    printcap, Parameters Recommended for Use, Default Print Commands for various UNIX Print Subsystems, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    printcap name, Parameters Recommended for Use, The [global] Section
    printer, Parameters Recommended for Use
    printer admin, Parameters Recommended for Use, The [global] Section, Any [my_printer_name] Section, Parameters in the [print$] Section, Setting Drivers for existing Printers with a Client GUI, IMPORTANT! Setting Device Modes on new Printers, Always make first Client Connection as root or "printer admin", Setting Default Print Options for the Client Drivers, Adding new Printers with the Windows NT APW, More complex smb.conf Settings for +CUPS, What is required for adddriver and setdriver to succeed, Print options for all users can't be set on Win2K/XP
    printer name, Parameters Recommended for Use
    printing, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    printing.tdb, The printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    public, The [printers] Section

    Q

    queue resume command, Linking of smbd with libcups.so
    queuepause command, Parameters Recommended for Use, Linking of smbd with libcups.so
    queueresume command, Parameters Recommended for Use

    R

    read list, User and Group Based Controls
    read only, Miscellaneous Controls, The [printers] Section, Parameters in the [print$] Section
    read raw, Read raw
    read size, Read size
    remote announce, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Announce parameter, Browsing support in Samba
    remote browse sync, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Browse Sync parameter
    root preexec, Logon Scripts
    rpcclient
    adddriver, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using +rpcclient), Understanding the rpcclient man page, What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    enumdrivers, Installing PostScript Driver Files manually (using +rpcclient), Manual Driver Installation in 15 Steps
    enumports, Installing PostScript Driver Files manually (using +rpcclient)
    enumprinters, Installing PostScript Driver Files manually (using +rpcclient), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps, Troubleshooting revisited
    getdriver, Producing an Example by querying a Windows Box, Manual Driver Installation in 15 Steps
    getprinter, Producing an Example by querying a Windows Box, Manual Driver Installation in 15 Steps, Troubleshooting revisited
    setdriver, Caveats to be considered, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using +rpcclient), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    rsync, Accessing the samba sources via rsync and ftp

    S

    secrets.tdb, The printing *.tdb Files
    (see also TDB)
    security, Samba Security Modes, Domain Security Mode (User Level Security), Server Security (User Level Security), What makes Samba a SERVER?, What makes Samba a Domain Controller?, What makes Samba a Domain Member?, Constantly Losing Connections to Password Server, Preparing for Domain Control, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Why is this better than security = server?, Setup your smb.conf, Run "cupsaddsmb" (quiet Mode), "cupsaddsmb" keeps asking for root password in + neverending loop, Passdb Backends and Authentication, The tests, Configuring WfW password handling
    security mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts
    sessionid.tdb, The printing *.tdb Files
    (see also TDB)
    share_info.tdb, The printing *.tdb Files
    (see also TDB)
    short preserve case, Miscellaneous Controls, Windows 9x / Me Profile Setup
    Short-Cuts, MS Windows NTFS Comparison with UNIX File Systems
    show add printer wizard, Parameters Recommended for Use, The [global] Section, Adding new Printers with the Windows NT APW
    SID, Features and Benefits
    Single Sign On, Caveats to be considered
    smbclient, Testing with smbclient, The tests
    socket options, Socket options
    spooling
    central, Central spooling vs. "Peer-to-Peer" printing
    peer-to-peer, Central spooling vs. "Peer-to-Peer" printing
    spooling-only, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    strict locking, Discussion

    T

    TDB, The printing *.tdb Files, Trivial DataBase Files
    backing up (see tdbbackup)
    tdbbackup, Using tdbbackup
    template homedir, Linux/FreeBSD-specific PAM configuration
    testparm, The tests
    text/plain, MIME type Conversion Rules
    total print jobs, Parameters Recommended for Use, The [global] Section

    U

    UDP, NetBIOS over TCP/IP
    UID, Features and Benefits
    unexpected.tdb, The printing *.tdb Files
    (see also TDB)
    unix charset, Samba and charsets, Japanese charsets
    use client driver, Parameters Recommended for Use, The [global] Section
    user, Share Level Security, The tests
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain
    useradd, Manual Creation of Machine Trust Accounts
    username, User and Group Based Controls
    username level, Password checking
    username map, Windows 200x XP Professional

    V

    valid users, User and Group Based Controls, The tests
    veto files, Miscellaneous Controls
    vfs objects, Discussion
    vipw, Manual Creation of Machine Trust Accounts

    W

    winbind separator, Start up the winbindd daemon and test it!
    WINS, What is Browsing?, NetBIOS over TCP/IP, WINS Lookup
    wins hook, What is Browsing?
    wins proxy, What is Browsing?
    wins server, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    wins support, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    workgroup, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Browsing support in Samba
    write list, User and Group Based Controls, Parameters in the [print$] Section
    write raw, Write raw
    writeable, The [printers] Section, Any [my_printer_name] Section
    WYSIWYG, Windows Drivers, GDI and EMF

    X

    X Window System, UNIX Printfile Conversion and GUI Basics
    xinetd, Starting from inetd.conf (see inetd)
    Xprint, UNIX Printfile Conversion and GUI Basics
    -- cgit