From b222defc2743d7003f3eaa95864e93cbe5bbea66 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij Table of Contents
-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
-provide users with the access they need while protecting resources from unauthorised access.
-
-Many UNIX administrators are unfamiliar with the MS Windows environment and in particular
-have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file
-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
-administrators are astounded at this given that ACLs were a foundational capability of the now
-decade old MS Windows NT operating system.
-
-The purpose of this chapter is to present each of the points of control that are possible with
-Samba-3 in the hope that this will help the network administrator to find the optimum method
-for delivering the best environment for MS Windows desktop users.
-
-This is an opportune point to mention that Samba was created to provide a means of interoperability
-and interchange of data between differing operating environments. Samba has no intent change
-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.
-
- 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
- UNIX File and Directory Permissions
-
- Samba honours and implements UNIX file system access controls. Users
- who access a Samba server will do so as a particular MS Windows user.
- This information is passed to the Samba server as part of the logon or
- connection setup process. Samba uses this user identity to validate
- whether or not the user should be given access to file system resources
- (files and directories). This chapter provides an overview for those
- to whom the UNIX permissions and controls are a little strange or unknown.
-
- Samba Share Definitions
-
- In configuring share settings and controls in the smb.conf file
- the network administrator can exercise over-rides to native file
- system permissions and behaviours. This can be handy and convenient
- to affect behaviour that is more like what MS Windows NT users expect
- but it is seldom the best way to achieve this.
- The basic options and techniques are described herein.
-
- Samba Share ACLs
-
- Just like it is possible in MS Windows NT to set ACLs on shares
- themselves, so it is possible to do this in Samba.
- Very few people make use of this facility, yet it remains on of the
- easiest ways to affect access controls (restrictions) and can often
- do so with minimum invasiveness compared with other methods.
-
- MS Windows ACLs through UNIX POSIX ACLs
-
- The use of POSIX ACLs on UNIX/Linux is possible ONLY if the underlying
- operating system supports them. If not, then this option will not be
- available to you. Current UNIX technology platforms have native support
- for POSIX ACLs. There are patches for the Linux kernel that provide
- 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.
-
-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.
-
- 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
- that in a transparent and consistent manner.
-
- It is good news that Samba does this to a very large extent and on top of that provides a high degree
- of optional configuration to over-ride the default behaviour. We will look at some of these over-rides,
- but for the greater part we will stay within the bounds of default behaviour. Those wishing to explore
- to depths of control ability should review the smb.conf man page.
- File System Feature Comparison
- MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, UNIX file names
- may be 1023 characters long. In MS Windows file extensions indicate particular file types,
- in UNIX this is not so rigorously observed as all names are considered arbitrary.
-
- What MS Windows calls a Folder, UNIX calls a directory.
-
-
- 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.
-
- UNIX file and directory names are case sensitive and case preserving. Samba implements the
- MS Windows file name behaviour, but it does so as a user application. The UNIX file system
- provides no mechanism to perform case insensitive file name lookups. MS Windows does this
- by default. This means that Samba has to carry the processing overhead to provide features
- that are NOT native to the UNIX operating system environment.
-
- Consider the following, all are unique UNIX names but one single MS Windows file name:
-
- MYFILE.TXT
- MyFile.txt
- myfile.txt
-
- So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in UNIX
- they can. So what should Samba do if all three are present? Answer, the one that is lexically
- first will be accessible to MS Windows users, the others are invisible and unaccessible - any
- other solution would be suicidal.
-
- MS Windows and DOS uses the back-slash '\' as a directory delimiter, UNIX uses the forward-slash '/'
- as it's directory delimiter. This is transparently handled by Samba.
-
- MS Windows products support a notion of drive letters, like C: to represent
- disk partitions. UNIX has NO concept if separate identifiers for file partitions since each
- such file system is mounted to become part of the over-all directory tree.
- The UNIX directory tree begins at '/', just like the root of a DOS drive is specified like
- C:\.
-
- MS Windows generally never experiences file names that begin with a '.', while in UNIX these
- are commonly found in a user's home directory. Files that begin with a '.' are typically
- either start up files for various UNIX applications, or they may be files that contain
- start-up configuration data.
-
-
-
-
-
- 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.
-
- Symbolic links are files in UNIX that contain the actual location of the data (file OR directory). An
- operation (like read or write) will operate directly on the file referenced. Symbolic links are also
- referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows
- one physical file to be known simultaneously by more than one file name.
-
- 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.
-
- There are three basic operations for managing directories, create, delete, rename.
- Table 13.1. Managing directories with unix and windows
-
- 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
- Attributes (EAs).
-
- UNIX/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set.
- A UNIX file listing looks as follows:-
-
-
-
- The columns above represent (from left to right): permissions, number of hard links to file, owner, group, size (bytes), access date, access time, file name.
-
- An overview of the permissions field can be found in the image below.
-
- 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
-
-
- Additional possibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = UNIX Domain Socket.
-
- The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),
- execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s),
- sticky (t).
-
- When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner.
- Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on
- directories, such as /tmp, that are world-writable.
-
- When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or
- group whose 'set user or group' bit is set. This can be very helpful in setting up directories that for which it is desired that
- all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file
- to be exclusively owned by a user who's primary group is not the group that all such users belong to.
-
- When a directory is set drw-r----- this means that the owner can read and create (write) files in it, but because
- 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.
-
-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 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
- 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
- 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
- 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
- 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
- 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
- connect to a share. In the absence of specific restrictions the default setting is to allow
- the global user Everyone Full Control (ie: Full control, Change and Read).
-
- At this time Samba does NOT provide a tool for configuring access control setting on the Share
- itself. Samba does have the capacity to store and act on access control settings, but the only
- way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
- Computer Management.
-
- Samba stores the per share access control settings in a file called share_info.tdb.
- The location of this file on your system will depend on how samba was compiled. The default location
- for Samba's tdb files is under /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.
-
- The best tool for the task is platform dependant. Choose the best tool for your environment.
-
- 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.
- Procedure 13.1. Instructions
- Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
- select , then click on the entry.
-
- 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.
-
- 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 , then click on Permissions. The default
- Windows NT4/200x permission allows Everyone Full Control on the Share.
-
- MS Windows 200x and later all comes with a tool called the Computer Management snap-in for the
- Microsoft Management Console (MMC). This tool is located by clicking on Control Panel ->
- Administrative Tools -> Computer Management.
- Procedure 13.2. Instructions
- After launching the MMC with the Computer Management snap-in, click on the menu item Connect to another computer. If you are not logged onto a domain you will be prompted
- to enter a domain login user identifier and a password. This will authenticate you to the domain.
- If you where already logged in with administrative privilege this step is not offered.
-
- If the Samba server is not shown in the Select Computer box, then type in the name of the target
- Samba server in the field Name:. Now click on the next to
- System Tools, then on the next to Shared Folders in the
- left panel.
-
- Now in the right panel, double-click on the share you wish to set access control permissions on.
- Then click on the tab Share Permissions. It is now possible to add access control entities
- to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
- wish to assign for each entry.
-
- Be careful. If you take away all permissions from the Everyone user without removing this user
- then effectively no user will be able to access the share. This is a result of what is known as
- ACL precedence. ie: Everyone with 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.
-
- Windows NT clients can use their native security settings dialog box to view and modify the
- underlying UNIX permissions.
-
- Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and
- still obeys all the file permission rules that a Samba administrator can set.
-
- Samba does not attempt to go beyond POSIX ACLs, so that the various finer-grained access control
- options provided in Windows are actually ignore.
-
- All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls.
- When trying to figure out file access problems it is vitally important to find the identity of the Windows
- user as it is presented by Samba at the point of file access. This can best be determined from the
- Samba log files.
-
- 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
- Security and you will see three buttons, ,
- , and . The
- button will cause either an error message A requested privilege is not held by the client
- to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator
- to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is
- non-functional with a Samba share at this time, as the only useful button, the
- button will not currently allow a list of users to be seen.
-
- Clicking on the
- "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
- If the parameter nt acl support is set to false
- then the file owner will be shown as the NT user "Everyone".
-
- The root user. As clicking on this button causes
- NT to attempt to change the ownership of a file to the current user logged into the NT client this will
- not work with Samba at this time.
- There is an NT chown command that will work with Samba and allow a user with Administrator privilege connected
- to a Samba server as root to change the ownership of files on both a local NTFS filesystem or remote mounted NTFS
- or Samba drive. This is available as part of the Seclib NT security library written
- by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.
- The third button is the "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).
- 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.
- 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
- the global NT group Everyone, followed
- by the list of permissions allowed for UNIX world. The UNIX
- owner and group permissions are displayed as an NT
- user icon and an NT local
- group 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
- 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
- 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
- (which has no meaning in UNIX) and reports a component with
- 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. 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"
- 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
- in the UNIX permissions world and represents the
- inherited 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 and directory permissions is as simple
- as changing the displayed permissions in the dialog box, and
- clicking the 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 The remote procedure call failed
- and did not execute). This means that you can only
- manipulate the current user/group/world permissions listed in
- the dialog box. This actually works quite well as these are the
- only permissions that UNIX actually has. If a permission triplet (either user, group, or world)
- is removed from the list of permissions in the NT dialog box,
- then when the 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
- is not what you want you must uncheck the Replace
- permissions on existing files checkbox in the NT
- dialog before clicking . If you wish to remove all permissions from a
- user/group/world component then you may either highlight the
- component and click the There are four parameters
- to control interaction with the standard Samba create mask parameters.
- These are :
-
-
-
- Once a user clicks 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
- 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
- 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
- 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.
- 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
- 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
- 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
- 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 :
- 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
- 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
-
-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.
-
- “
- 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
- root can change the file, no one else can. We need to constantly go to server to
- chgrp -R users * and chown -R nobody * to allow others users to change the file.
- ”
-
- There are many ways to solve this problem, here are a few hints:
-
- Go to the top of the directory that is shared
-
- Set the ownership to what ever public owner and group you want
-
-
- The above will set the 'sticky bit' on all directories. Read your
- UNIX/Linux man page on what that does. It causes the OS to assign
- to all files created in the directories the ownership of the
- directory.
-
-
- Directory is: /foodbar
-
- This is the same as doing: Now do:
-
-
-
- You should see:
-
- Now do:
-
-
- You should see that the file Afile created by Jill will have ownership
- and permissions of Jack, as follows:
-
-
- Now in your smb.conf for the share add:
-
-
- The above are only needed if your users are not members of the group
- you have used. ie: Within the OS do not have write permission on the directory.
-
- An alternative is to set in the smb.conf entry for the share:
-
-
- 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.
-
- 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?”
-
- Answer: Word does the following when you modify/change a Word document: Word Creates a NEW document with
- a temporary name, Word then closes the old document and deletes it, Word then renames the new document to the original document name.
- There is NO mechanism by which Samba CAN IN ANY WAY know that the new document really should be owned by the owners
- of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able
- to tell, the file that gets created is a NEW file, not one that the application (Word) is updating.
-
- There is a work-around to solve the permissions problem. That work-around involves understanding how you can manage file
- system behaviour from within the smb.conf file, as well as understanding how Unix file systems work. Set on the directory
- in which you are changing word documents: chmod g+s 'directory_name' This ensures that all files will
- be created with the group that owns the directory. In smb.conf share declaration section set:
-
-
-
- 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.
- Table of Contents
-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.
-
-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
-manage MS Windows workstations, to remotely access the Samba server, to provide customised
-logon scripts, as well as other house keeping activities that help to sustain more reliable
-network operations.
-
-This chapter presents information on each of these area. They are placed here, and not in
-other chapters, for ease of reference.
-
-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',
-the 'Server Manager'?
-
-Microsoft distributes a version of these tools called nexus for installation
-on Windows 9x / Me systems. The tools set includes:
-
-Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE
-
-The 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
-
-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.
-
- 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.
-
-
-
- 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
- well as incorporating VNC/RFB and rdesktop/RDP into it, but at a speed
- performance much better than anything you may have ever seen...
-
- Remote X is not new at all -- but what they did achieve successfully is
- a new way of compression and caching technologies which makes the thing
- fast enough to run even over slow modem/ISDN connections.
-
- 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)
- 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"
- 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
- in Italy) to my Mozilla mailing agent... These guys are certainly doing
- something right!
-
- I recommend to test drive NX to anybody with a only a remote interest
- in remote computing
- http://www.nomachine.com/testdrive.php.
-
- Just download the free of charge client software (available for RedHat,
- SuSE, Debian and Windows) and be up and running within 5 minutes (they
- need to send you your account data, though, because you are assigned
- a real Unix account on their testdrive.nomachine.com box...
-
- They plan to get to the point were you can have NX application servers
- running as a cluster of nodes, and users simply start an NX session locally,
- and can select applications to run transparently (apps may even run on
- another NX node, but pretend to be on the same as used for initial login,
- because it displays in the same window.... well, you also can run it
- fullscreen, and after a short time you forget that it is a remote session
- at all).
-
- Now the best thing at the end: all the core compression and caching
- technologies are released under the GPL and available as source code
- to anybody who wants to build on it! These technologies are working,
- albeit started from the command line only (and very inconvenient to
- use in order to get a fully running remote X session up and running....)
-
- To answer your questions:
-
- You don't need to install a terminal server; XP has RDP support built in.
-
- NX is much cheaper than Citrix -- and comparable in performance, probably faster
-
- You don't need to hack XP -- it just works
-
- You log into the XP box from remote transparently (and I think there is no
- need to change anything to get a connection, even if authentication is against a domain)
-
- The NX core technologies are all Open Source and released under the GPL --
- you can today use a (very inconvenient) commandline to use it at no cost,
- but you can buy a comfortable (proprietary) NX GUI frontend for money
-
- 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)
-
-This section needs work. Volunteer contributions most welcome. Please send your patches or updates
-to John Terpstra.
-
-There are several opportunities for creating a custom network startup configuration environment.
-
-The Samba source code tree includes two logon script generation/execution tools.
-See examples directory genlogon and
-ntlogon subdirectories.
-
-The following listings are from the genlogon directory.
-
-This is the genlogon.pl file:
-
-
-
-Those wishing to use more elaborate or capable logon processing system should check out the following sites:
-
-Printers may be added automatically during logon script processing through the use of:
-
-
-
-See the documentation in the Microsoft knowledgebase article no: 189105.
-
-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.
- Table of Contents
-This chapter did not make it into this release.
-It is planned for the published release of this document.
-
-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.
- Table of Contents
- 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"
- 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
- contains a lot of information that is relevant for CUPS.
-
- CUPS sports quite a few unique and powerful features. While their
- basic functions may be grasped quite easily, they are also
- new. Because they are different from other, more traditional printing
- systems, it is best to try and not apply any prior knowledge about
- printing upon this new system. Rather, try to understand CUPS
- from the beginning. This documentation will lead you to a
- complete understanding of CUPS. Let's start with the most basic
- things first.
-
- 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
- and IETF (Internet Engineering Task Force)
- standard for network printing. Many of its functions can be managed
- remotely (or locally) via a web browser (giving you a
- platform-independent access to the CUPS print server). Additionally, it
- has the traditional command line and several more modern GUI interfaces
- (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
- 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.
-
- 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.
- 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).
- Legacy programs often require the existence of a printcap file containing printer names or they will refuse to
- 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.
-
- 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
- if Samba is not linked against libcups.so -- but
- there are some differences in required or supported configuration
- then.
-
- 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
- other OS platforms, or its function may be embodied by a different command):
-
- The line libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) shows
- there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups
- is set, then any otherwise manually set print command in smb.conf is ignored.
- This is an important point to remember!
- 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
- 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).
- 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
- 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
- send these kind of files to print without opening a GUI
- application. Windows clients tend to have local printer drivers
- installed. And the GUI application's print buttons start a printer
- 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
- applications native format and the print data stream. If the backend
- 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.
-
-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
-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);
-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.
-
-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.
-
-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
-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
-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.
-
-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
-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
-driver for the target device needed to be installed on each and every
-client.
-
-It is possible to configure CUPS, Samba and your Windows clients in the
-same, traditional and simple way. When CUPS printers are configured
-for RAW print-through mode operation it is the responsibility of the
-Samba client to fully render the print job (file). The file must be
-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.
-
-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
-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.
-
-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
-formats. The CUPS files that need to be correctly set for RAW mode
-printers to work are:
- /etc/cups/mime.types
- /etc/cups/mime.convs
-Both contain entries (at the end of the respective files) which must
-be uncommented to allow RAW mode operation.
-In/etc/cups/mime.types make sure this line is
-present:
-
-In /etc/cups/mime.convs,
-have this line:
-
-If these two files are not set up correctly for raw Windows client
-printing, you may encounter the dreaded Unable to
-convert file 0 in your CUPS error_log file.
- editing the mime.convs and the
-mime.types file does not
-enforce "raw" printing, it only
-allows it.
- 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
-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
-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
-locally installed. If you are not interested in background information about
-more advanced CUPS/Samba printing, simply skip the remaining sections
-of this chapter.
-
-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
-HOWTO Collection. There you will find a description or reference to
-three methods of preparing the client drivers on the Samba server:
-
-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
-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.
-
-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.
-
-Possibly you need to setup CUPS in a more smart way. The reasons could
-be manifold:
- Maybe your boss wants to get monthly statistics: Which
-printer did how many pages? What was the average data size of a job?
-What was the average print run per day? What are the typical hourly
-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"?
-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.
-
-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.
-
-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
-(Page Description Languages), there are still
-many manufacturers who "roll their own" (their reasons may be
-unacceptable license fees for using printer-embedded PostScript
-interpreters, etc.).
-
-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
-Interface), as part and parcel of the OS itself, to base
-themselves on. This GDI core is used as one common unified ground, for
-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
-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.
-
-
-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
-Systems. Their Core Graphic Engine uses a
-PDF derivative for all display work.
-
-
-
-
-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
-use PostScript. That gives at least some common ground. Unfortunately,
-there are many different levels of quality for this PostScript. And
-worse: there is a huge difference (and no common root) in the way how
-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"
-also, as some had demanded at the time, and restricted itself to
-"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
-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.,
-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,
-linewidth...) and the way to manipulate (scale, distort, rotate,
-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
-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.
-
-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
-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
-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.
-
-
-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
-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....
-
-
-
-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
-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.
-
-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
-lot of file format conversions, for a very broad
-spectrum of hardware devices as well as software file formats.
-Ghostscript technology and drivers is what enables PostScript printing
-to non-PostScript hardware.
-
-
-
-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
-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 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
-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).
-
-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
-always ending up to be output on a hardware with device-specific
-features. To take care of all the differences in hardware, and to
-allow for innovations, Adobe has specified a syntax and file format
-for PostScript Printer Description (PPD)
-files. Every PostScript printer ships with one of these files.
-
-PPDs contain all information about general and special features of the
-given printer model: Which different resolutions can it handle? Does
-it have a Duplexing Unit? How many paper trays are there? What media
-types and sizes does it take? For each item it also names the special
-command string to be sent to the printer (mostly inside the PostScript
-file) in order to enable it.
-
-Information from these PPDs is meant to be taken into account by the
-printer drivers. Therefore, installed as part of the Windows
-PostScript driver for a given printer is the printer's PPD. Where it
-makes sense, the PPD features are presented in the drivers' UI dialogs
-to display to the user as choice of print options. In the end, the
-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.
-
-
-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 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
-OS in his manuals and brochures -- you can safely trust this:
-if you get hold of the Windows NT version of the PPD, you
-can use it unchanged in CUPS and thus access the full
-power of your printer just like a Windows NT user could!
-
-To check the spec compliance of any PPD online, go to http://www.cups.org/testppd.php
-and upload your PPD. You will see the results displayed
-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.
-
-
-
-For real PostScript printers don't use the
-Foomatic or cupsomatic
-PPDs from Linuxprinting.org. With these devices the original
-vendor-provided PPDs are always the first choice!
-
-If you are looking for an original vendor-provided PPD of a specific
-device, and you know that an NT4 box (or any other Windows box) on
-your LAN has the PostScript driver installed, just use
-smbclient //NT4-box/print\$ -U username to
-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 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
-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 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
-plugged in even more filters. CUPS handles all data file formats under
-the label of various MIME types. Every incoming
-printfile is subjected to an initial
-auto-typing. The auto-typing determines its given
-MIME type. A given MIME type implies zero or more possible filtering
-chains relevant to the selected target printer. This section discusses
-how MIME types recognition and conversion rules interact. They are
-used by CUPS to automatically setup a working filtering chain for any
-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"
-(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
-the generic CUPS raster to a device specific raster.
-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
-device in your Ghostscript, you either need to patch GNU
-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
-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).
-
-
-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
-type recognition rules which are applied when CUPS runs its
-auto-typing routines. The rule syntax is explained in the man page
-for mime.types and in the comments section of the
-mime.types file itself. A simple rule reads
-like this:
-
-This means: if a filename has either a
-.pdf suffix, or if the magic
-string %PDF is right at the
-beginning of the file itself (offset 0 from the start), then it is
-a PDF file (application/pdf).
-Another rule is this:
-
-Its meaning: if the filename has one of the suffixes
-.ai, .eps,
-.ps or if the file itself starts with one of the
-strings %! or <04>%!, it
-is a generic PostScript file
-(application/postscript).
-
-There is a very important difference between two similar MIME type in
-CUPS: one is application/postscript, the other is
-application/vnd.cups-postscript. While
-application/postscript is meant to be device
-independent (job options for the file are still outside the PS file
-content, embedded in commandline or environment variables by CUPS),
-application/vnd.cups-postscript may have the job
-options inserted into the PostScript data itself (were
-applicable). The transformation of the generic PostScript
-(application/postscript) to the device-specific version
-(application/vnd.cups-postscript) is the responsibility of the
-CUPS pstops filter. pstops uses information
-contained in the PPD to do the transformation.
-
-Don't confuse the other mime.types file your system might be using
-with the one in the /etc/cups/ directory.
-
-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.
-
-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
-lines naming an input MIME type, an output MIME type, a format
-conversion filter which can produce the output from the input type
-and virtual costs associated with this conversion. One example line
-reads like this:
-
-This means that the pdftops filter will take
-application/pdf as input and produce
-application/postscript as output, the virtual
-cost of this operation is 33 CUPS-$. The next filter is more
-expensive, costing 66 CUPS-$:
-
-This is the hpgltops, which processes HP-GL
-plotter files to PostScript.
-
-Here are two more examples:
-
-The last two examples name the texttops filter
-to work on "text/plain" as well as on "application/x-shell". (Hint:
-this differentiation is needed for the syntax highlighting feature of
-"texttops").
-
-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
-to meet some minimal requirements. If you find (or write) a cool
-conversion filter of some kind, make sure it complies to what CUPS
-needs, and put in the right lines in mime.types
-and mime.convs, then it will work seamlessly
-inside CUPS!
-
-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]
- The name of the printer queue (normally this is the
-name of the filter being run) The numeric job ID for the job being
-printed The string from the originating-user-name
-attribute The string from the job-name attribute The numeric value from the number-copies
-attribute The job options (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.
-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
-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
-any device-specific print options are not yet embedded into the
-PostScript by CUPS, and that the next filter to be called is
-pstops). Another pre-filter is running on all supported image formats,
-the imagetops filter. Its outcome is always of
-MIME type application/vnd.cups-postscript
-(not application/postscript), meaning it has the
-print options already embedded into the file.
-
-
-
-pstopsis the filter to convert
-application/postscript to
-application/vnd.cups-postscript. It was said
-above that this filter inserts all device-specific print options
-(commands to the printer to ask for the duplexing of output, or
-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
-ones)
-
-putting 2 or more logical pages on one sheet of paper (the
-so-called "number-up" function)
- counting the pages of the job to insert the accounting
-information into the /var/log/cups/page_log
-
-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;
-its output is application/vnd.cups-raster. This output format is not
-yet meant to be printable. Its aim is to serve as a general purpose
-input format for more specialized raster drivers,
-that are able to generate device-specific printer data.
-
-
-
-CUPS raster is a generic raster format with powerful features. It is
-able to include per-page information, color profiles and more to be
-used by the following downstream raster drivers. Its MIME type is
-registered with IANA and its specification is of course completely
-open. It is designed to make it very easy and inexpensive for
-manufacturers to develop Linux and UNIX raster drivers for their
-printer models, should they choose to do so. CUPS always takes care
-for the first stage of rasterization so these vendors don't need to care
-about Ghostscript complications (in fact, there is currently more
-than one vendor financing the development of CUPS raster drivers).
-
-
-
-CUPS versions before version 1.1.15 were shipping a binary (or source
-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
-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!
-
-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
-intermediate PostScript stage. It is used more often than the above
-mentioned prefilters. Here is a summarizing flowchart of image file
-filtering:
-
-
-
-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,
-rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo,
-rastertoescp, rastertohp and
-rastertoprinter. Don't worry if you have less
-than this; some of these are installed by commercial add-ons to CUPS
-(like rastertoturboprint), others (like
-rastertoprinter) by 3rd party driver
-development projects (such as Gimp-Print) wanting to cooperate as
-closely as possible with CUPS.
-
-
-
-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"
-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
-see from the following list. Keep in mind that local interface names
-may vary much from my examples, if your OS is not Linux:
-
-This backend sends printfiles to USB-connected printers. An
-example for the CUPS device-URI to use is:
-usb:/dev/usb/lp0
-
-This backend sends printfiles to serially connected printers.
-An example for the CUPS device-URI to use is:
-serial:/dev/ttyS0?baud=11500
-
-This backend sends printfiles to printers connected to the
-parallel port. An example for the CUPS device-URI to use is:
-parallel:/dev/lp0
-
-This backend sends printfiles to printers attached to the
-SCSI interface. An example for the CUPS device-URI to use is:
-scsi:/dev/sr1
-
-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
-
-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
-
-This backend sends printfiles to IPP connected network
-printers (or to other CUPS servers). Examples for CUPS device-URIs
-to use are:
-ipp:://192.193.194.195/ipp
-(for many HP printers) or
-ipp://remote_cups_server/printers/remote_printer_name
-
-This backend sends printfiles to HTTP connected printers.
-(The http:// CUPS backend is only a symlink to the ipp:// backend.)
-Examples for the CUPS device-URIs to use are:
-http:://192.193.194.195:631/ipp
-(for many HP printers) or
-http://remote_cups_server:631/printers/remote_printer_name
-
-This backend sends printfiles to printers shared by a Windows
-host. An example for CUPS device-URIs to use are:
-smb://workgroup/server/printersharename
-Or
-smb://server/printersharename
-or
-smb://username:password@workgroup/server/printersharename
-or
-smb://username:password@server/printersharename.
-The smb:// backend is a symlink to the Samba utility
-smbspool (doesn't ship with CUPS). If the
-symlink is not present in your CUPS backend directory, have your
-root user create it: ln -s `which smbspool`
-/usr/lib/cups/backend/smb.
-
-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
-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
-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
-printername).
-
-Not all of the mentioned backends may be present on your system or
-usable (depending on your hardware configuration). One test for all
-available CUPS backends is provided by the lpinfo
-utility. Used with the -v parameter, it lists
-all available backends:
-
-"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
-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"
-Printer & Driver Database at Linuxprinting.org.
-
-You can recognize these PPDs from the line calling the
-cupsomatic filter:
-
-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
-CUPS web interface with a foomatic namepart for
-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,
-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:
-
-The PPD generating engine at Linuxprinting.org has been revamped.
-The new PPDs comply to the Adobe spec. On top, they also provide a
-new way to specify different quality levels (hi-res photo, normal
-color, grayscale, draft...) with a single click (whereas before you
-could have required 5 or more different selections (media type,
-resolution, inktype, dithering algorithm...). There is support for
-custom-size media built in. There is support to switch
-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!
-
-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.
-
-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,
-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.
-
-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
-200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows
-approximately 5 jobs maximum at a time.
-
-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
-on the command line. You can also set up raw-only queues by simply not
-associating any PPD with it. This command:
-
-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.
-
-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.
-
-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
-sent. Because CUPS refuses to print unknown MIME types per default,
-you will probably have experienced the fact that printjobs originating
-from Windows clients were not printed. You may have found an error
-message in your CUPS logs like:
-
-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:
-
-This line (with no specific auto-typing rule set) makes all files
-not otherwise auto-typed a member of application/octet-stream. In
-/etc/cups/mime.convs, have this
-line:
-
-This line tells CUPS to use the Null Filter
-(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.
- Editing the mime.convs and the
-mime.types file does not
-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
-as MIME type
-application/octet-stream. While you
-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
-recognizes MIME types. The file
-/etc/cups/mime.convs decides which file
-conversion filter(s) may be applied to which MIME types.
-
-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
-scope for PPDs to cover non-PostScript printers too. This was not
-very difficult, because it is a standardized file format. In a way
-it was logical too: CUPS handles PostScript and uses a PostScript
-RIP (=Ghostscript) to process the jobfiles. The only difference is:
-a PostScript printer has the RIP built-in, for other types of
-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:
-
-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
-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
-filter), the file should go to the backend, which sends it to the
-output device.
-
-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
-Native CUPS rasterization works in two steps.
-
-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
-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.
-Often this produces better quality (and has several more
-advantages) than other methods.
-
-
-
-One other method is the cupsomatic/foomatic-rip
-way. Note that cupsomatic is not made by the CUPS
-developers. It is an independent contribution to printing development,
-made by people from Linuxprinting.org (see also http://www.cups.org/cups-help.html).
-cupsomatic is no longer developed and maintained and is no longer
-supported. It has now been replaced by
-foomatic-rip. foomatic-rip is a complete re-write
-of the old cupsomatic idea, but very much improved and generalized to
-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
-all the other devices built-in into Ghostscript. The quality is as
-good (or bad) as Ghostscript rendering is in other spoolers. The
-advantage is that this method supports many printer models not
-supported (yet) by the more modern CUPS method.
-
-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
-application/vnd.cups-postscript stage and
-deviates it through the CUPS-external, system wide Ghostscript
-installation: Therefore the printfile bypasses the "pstoraster" filter
-(and thus also bypasses the CUPS-raster-drivers
-"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.
-
-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":
- 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
-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 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
-PPD) into the new PostScript file; the file now is of PostScript MIME
-type
-application/vnd.cups-postscript; the file goes to the socket
-backend, which transfers the job to the printers.
- The resulting filter chain therefore is as drawn in the image below.
-
-Assume your want to print the same filter to an USB-connected
-Epson Stylus Photo printer, installed with the CUPS
-stphoto2.ppd. The first few filtering stages
-are nearly the same:
- 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
-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
-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
-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
-application/vnd.cups-postscript; the file then passes the
-pstoraster stage and becomes MIME type
-application/cups-raster; finally, the rastertoepson filter
-does its work (as is indicated in the printer's PPD), creating the
-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.
-
-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
-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,
-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
-CUPS, as they feed their creators). the Gimp-Print-Project
- (GPL, Free Software)
-provides around 140 PPDs (supporting nearly 400 printers, many driven
-to photo quality output), to be used alongside the Gimp-Print CUPS
-filters; TurboPrint
- (Shareware, non-Free) supports
-roughly the same amount of printers in excellent
-quality; OMNI
-
-(LPGL, Free) is a package made by IBM, now containing support for more
-than 400 printers, stemming from the inheritance of IBM OS/2 Know-How
-ported over to Linux (CUPS support is in a Beta-stage at
-present); HPIJS
- (BSD-style licenses, Free)
-supports around 150 of HP's own printers and is also providing
-excellent print quality now (currently available only via the Foomatic
-path); Foomatic/cupsomatic
- (LPGL, Free) from
-Linuxprinting.org are providing PPDs for practically every Ghostscript
-filter known to the world (including Omni, Gimp-Print and
-HPIJS).
-The cupsomatic/Foomatic trick from Linuxprinting.org works
-differently from the other drivers. This is explained elsewhere in this
-document.
-
-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
-PPDs for PostScript printers. Interface scripts may inject the Escape
-sequences as required into the print data stream, if the user has
-chosen to select a certain paper tray, or print landscape, or use A3
-paper, etc. Interfaces scripts are practically unknown in the Linux
-realm. On HP-UX platforms they are more often used. You can use any
-working interface script on CUPS too. Just install the printer with
-the -i option:
-
-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 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
-with a Windows 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
-(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.
-
-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
-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.
-
-
-
-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
-the printer-specific language. It is not possible for UNIX to do the
-same. Currently there is no program or method to convert a Windows
-client's GDI output on a UNIX server into something a printer could
-understand.
-
-
-
-However, there is something similar possible with CUPS. Read on...
-
-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.
-
-Here is a simple recipe showing how you can take advantage of CUPS
-powerful features for the benefit of your Windows network printing
-clients:
- Let the Windows clients send PostScript to the CUPS
-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.
-
-Firstly, to enable CUPS based printing through Samba the
-following options should be set in your smb.conf file [global]
-section:
-
-When these parameters are specified, all manually set print directives
-(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)
-support. If Samba has NOT been compiled with CUPS support, and if no
-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).
-
-
-
-Samba must use its own spool directory (it is set
-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
-spool space and passes it into the spool directory of CUPS (the CUPS
-spooling directory is set by the RequestRoot
-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".
-
-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
-need to make sure the Samba host gets access to printing on CUPS.
-
-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
-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.
-
-CUPS can load, without any conversions, the PPD file from any Windows
-(NT is recommended) PostScript driver and handle the options. There is
-a web browser interface to the print options (select http://localhost:631/printers/
-and click on one Configure Printer button to see
-it), or a commandline interface (see man lpoptions
-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.
-
-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.
-
-This is logical, as CUPS includes a fully featured PostScript
-interpreter (RIP). This RIP is based on Ghostscript. It can process
-all received PostScript (and additionally many other file formats)
-from clients. All CUPS-PPDs geared to non-PostScript printers contain
-an additional line, starting with the keyword
-*cupsFilter . This line tells the CUPS print
-system which printer-specific filter to use for the interpretation of
-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.
-
-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
-limitations). This feature enables CUPS to do a few tricks no other
-spooler can do:
- act as a networked PostScript RIP (Raster Image
-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,
-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.
-
-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.
-
-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?
-
-PostScript drivers generally are very well tested. They are not known
-to cause any problems, even though they run in Kernel Mode too. This
-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.
-
-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
-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! )
-
-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
-drivers available: Adobe, Microsoft and CUPS PostScript drivers. None
-of them is known to cause major stability problems on WTS (even if
-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,
-although the first feedbacks look very promising.
-
-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"
-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
-reason for this: The MS DDK (Device Development Kit) for Win NT (which
-used to be available at no cost to licensees of Visual Studio)
-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.
-
-As we have said before: all previously known methods to prepare client
-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.
-
-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
-clients expect drivers deposited and setup for download and
-installation. It makes the sharing of any (or all) installed CUPS
-printers very easy. cupsaddsmb can use the Adobe PostScript driver as
-well as the newly developed CUPS PostScript Driver for
-WinNT/2K/XP. Note, that cupsaddsmb does
-not work with arbitrary vendor printer drivers,
-but only with the exact driver files that are
-named in its man page.
-
-The CUPS printer driver is available from the CUPS download site. Its
-package name is cups-samba-[version].tar.gz . It
-is preferred over the Adobe drivers since it has a number of
-advantages:
- it supports a much more accurate page
-accounting; it supports banner pages, and page labels on all
-printers; it supports the setting of a number of job IPP
-attributes (such as job-priority, page-label and
-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.
-
-Prior to running cupsaddsmb, you need the following settings in
-smb.conf:
- Example 19.3. smb.conf for cupsaddsmb usage
-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
-(tar.gz, 192k). The filename to download is
-cups-samba-1.1.x.tar.gz. Upon untar-/unzip-ing,
-it will reveal these files:
-
-
-
-These have been packaged with the ESP meta packager software
-"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"
-too). Then it puts the content into
-/usr/share/cups/drivers/. This content includes 3
-files:
-
-The cups-samba.install shell scripts is easy to
-handle:
-
-The script should automatically put the driver files into the
-/usr/share/cups/drivers/ directory.
-
-Due to a bug, one recent CUPS release puts the
-cups.hlp driver file
-into/usr/share/drivers/ instead of
-/usr/share/cups/drivers/. To work around this,
-copy/move the file (after running the
-./cups-samba.install script) manually to the
-right place.
-
-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
-Visual Studio and a DDK will be able to compile for him/herself.
-
-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
-
-Adobe drivers are available for the older Windows 95/98/ME as well as
-the Windows NT/2000/XP clients. The set of files is different for the
-different platforms.
- Windows 95, 98, and Me are supported by:
- ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP DEFPRTR2.PPD ICONLIB.DLL PSMON.DLL
- Windows NT, 2000, and XP are supported by:
- ADOBEPS5.DLL ADOBEPSU.DLL ADOBEPSU.HLP
-
-
-If both, the Adobe driver files and the CUPS driver files for the
-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 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
-not easy to locate either. Probably you need to use the included
-native installer and run the installation process on one client
-once. This will install the drivers (and one Generic PostScript
-printer) locally on the client. When they are installed, share the
-Generic PostScript printer. After this, the client's
-[print$] share holds the Adobe files, from
-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.
-
-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
-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
-and select Export Driver... from the menu. Of
-course you need to have prepared Samba beforehand too to handle the
-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.
-
-Once you have run the install script (and possibly manually
-moved the cups.hlp file to
-/usr/share/cups/drivers/), the driver is
-ready to be put into Samba's [print$] share (which often maps to
-/etc/samba/drivers/ and contains a subdir
-tree with WIN40 and
-W32X86 branches): You do this by running
-"cupsaddsmb" (see also man cupsaddsmb for
-CUPS since release 1.1.16).
-
-
-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
-working in an environment where everything is configured for
-Single Sign On to a Windows Domain Controller.
-
-Once the driver files are in the [print$] share
-and are initialized, they are ready to be downloaded and installed by
-the Win NT/2k/XP clients.
-
-
-Win 9x/ME clients won't work with the CUPS PostScript driver. For
-these you'd still need to use the ADOBE*.*
-drivers as previously.
-
-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.
-
-
-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
-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),
-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
-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"
-dialog, or use rpcclient with the
-setdriver sub-command.
-
-
-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
-<1B >%-12345X or
-<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
-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
-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
-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
-additional print options are: naming the CUPS standard
-banner pages (or the custom ones, should they be
-installed at the time of driver download), using the CUPS
-page-label option, setting a
-job-priority and setting the scheduled
-time of printing (with the option to support additional
-useful IPP job attributes in the future). the CUPS PostScript driver supports the inclusion of
-the new *cupsJobTicket comments at the
-beginning of the PostScript file (which could be used in the future
-for all sort of beneficial extensions on the CUPS side, but which will
-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).
-The cupsaddsmb command copies the needed files into your
-[print$] share. Additionally, the PPD
-associated with this printer is copied from
-/etc/cups/ppd/ to
-[print$]. There the files wait for convenient
-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).
-
-Here is an example of a successfully run cupsaddsmb command.
-
-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
-obvious that it only works for queues with a CUPS driver associated.
-
-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
-a line indicate that I inserted an artificial line break plus some
-indentation here:
-
-You will see the root password for the Samba account printed on
-screen.
-
-If you look closely, you'll discover your root password was transferred
-unencrypted over the wire, so beware! Also, if you look further her,
-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.
-
-What has happened? What did cupsaddsmb do? There are five stages of
-the procedure
-
-
- call the CUPS server via IPP and request the
-driver files and the PPD file for the named printer; store the files temporarily in the local
-TEMPDIR (as defined in
-cupsd.conf); connect via smbclient to the Samba server's
- [print$] share and put the files into the
- share's WIN40 (for Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub
- directories;
-
- connect via rpcclient to the Samba server and
-execute the "adddriver" command with the correct
-parameters;
-
- connect via rpcclient to the Samba server a second
-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
-good idea try it and see more clearly what is going on (though in real
-life most people will have their CUPS and Samba servers run on the
-same host):
-
-You must always check if the utility completed
-successfully in all fields. You need as a minimum these 3 messages
-amongst the output:
- Printer Driver infotec_2105 successfully
-installed. # (for the W32X86 == WinNT/2K/XP
-architecture...) Printer Driver infotec_2105 successfully
-installed. # (for the WIN40 == Win9x/ME
-architecture...) Successfully set [printerXPZ] to driver
-[printerXYZ].
-These messages probably not easily recognized in the general
-output. If you run cupsaddsmb with the -a
-parameter (which tries to prepare all active CUPS
-printer drivers for download), you might miss if individual printers
-drivers had problems to install properly. Here a redirection of the
-output will help you analyze the results in retrospective.
-
-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.
-
-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
-variations:
-
-(Note the two backslashes: the first one is required to
-"escape" the second one).
-
-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!
-
-
-
-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
-server;
- 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
-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
-an application like Winword, the new printer will appears in a
-\\SambaServer\PrinterName entry in the
-dropdown list of available printers.
-
-
-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
-install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients. Then point the client's printer queue to the Samba printer
-share for a UNC type of connection:
-
-should you desire to use the CUPS networked PostScript RIP
-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).
-
-Soooo: 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 very good. Some jobs print fast, and some are
-dead-slow. Many of these problems can be greatly reduced or even
-completely eliminated if you follow a few guidelines. Remember, if
-your print device is not PostScript-enabled, you are treating your
-Ghostscript installation on your CUPS host with the output your client
-driver settings produce. Treat it well:
- Avoid the PostScript Output Option: Optimize
-for Speed setting. Rather use the Optimize for
-Portability instead (Adobe PostScript
-driver). Don't use the Page Independence:
-NO setting. Instead use Page Independence
-YES (CUPS PostScript Driver) Recommended is the True Type Font
-Downloading Option: Native True Type over
-Automatic and Outline; you
-should by all means avoid Bitmap (Adobe
-PostScript Driver) Choose True Type Font: Download as Softfont
-into Printer over the default Replace by Device
-Font (for exotic fonts you may need to change it back to
-get a printout at all) (Adobe) Sometimes you can choose PostScript Language
-Level: 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)
-Of course you can run all the commands which are embedded into the
-cupsaddsmb convenience utility yourself, one by one, and hereby upload
-and prepare the driver files for future client downloads.
-
-
-
-
-
-
-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,
-adddriver, setdriver are amongst
-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
-mimic this too.
-
-First let's have a little check of the rpcclient man page. Here are
-two relevant passages:
-
-adddriver <arch> <config> Execute an
-AddPrinterDriver() RPC to install the printer driver information on
-the server. Note that the driver files should already exist in the
-directory returned by getdriverdir. Possible
-values for arch are the same as those for the
-getdriverdir command. The
-config parameter is defined as follows:
- 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".
-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
-
-setdriver <printername> <drivername>
-Execute a SetPrinter() command to update the
-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.
-
-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 in one line without the linebreaks:
-
-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
-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
-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
-by Windows computers on the wire. We may as well turn to a Windows
-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.
-
-
-
-We could run rpcclient with a
-getdriver or a getprinter
-subcommand (in level 3 verbosity) against it. Just sit down at UNIX or
-Linux workstation with the Samba utilities installed. Then type the
-following command:
-
-From the result it should become clear which is which. Here is an
-example from my installation:
-
-Some printer drivers list additional files under the label
-"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.
-
-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
-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
-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
-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
-Samba you may use the enumprinters subcommand to
-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.
-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
-single action item as it comes up.
- Procedure 19.1. Manual Driver Installation installation Install the Printer on CUPS
-This installs printer with the name mysmbtstprn
-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
-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
-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
-[print$].
- (optional) Check if Samba knows a Driver for the
-Printer
-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".
- Put all required Driver Files into Samba's
-[print$]
-(Note that this command should be entered in one long single
-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.
- Verify where the Driver Files are now
-The driver files now are in the W32X86 architecture "root" of
-[print$].
- Tell Samba that these are
-Driver Files
-(adddriver)
-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
-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
-the printername; however, in big installations you may use this driver
-for a number of printers which have obviously different names. So the
-name of the driver is not fixed.
- Verify where the Driver Files are now
-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
-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)
-Since you can bind any printername (=printqueue) to any driver, this
-is a very convenient way to setup many queues which use the same
-driver. You don't need to repeat all the previous steps for the
-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
-
-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.
- (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".
-
-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):
-
-Change any printer setting once (like changing "portrait" to
- "landscape"), click ; change the setting
-back.
- Install the Printer on a Client
-("Point'n'Print")
-If it doesn't work it could be a permission problem with the
-[print$] share.
- Thirteenth Step (optional): Print a Test Page
-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!
- Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
-Success
-The setdriver command will fail, if in Samba's mind the queue is not
-already there. You had promising messages about the:
-
-after the "adddriver" parts of the procedure? But you are also seeing
-a disappointing message like this one beneath?
-
-
-It is not good enough that you
-can see the queue in CUPS, using
-the lpstat -p ir85wm command. A
-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"
-the printer:
-
-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!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Some mystery is associated with the series of files with a
-tdb-suffix appearing in every Samba installation. They are
-connections.tdb,
-printing.tdb,
-share_info.tdb ,
-ntdrivers.tdb,
-unexpected.tdb,
-brlock.tdb ,
-locking.tdb,
-ntforms.tdb,
-messages.tdb ,
-ntprinters.tdb,
-sessionid.tdb and
-secrets.tdb. What is their purpose?
-
-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,
-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
-series of *.tdb files. (TDB = Trivial Data
-Base). These are often located in /var/lib/samba/
-or /var/lock/samba/ . The printing related files
-are ntprinters.tdb,
-printing.tdb,ntforms.tdb and
-ntdrivers.tdb.
-
-*.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."
--- 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
-environments many thousand of them. Some of these smbds might need to
-write-access the same *.tdb file at the
-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.
-
-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
-kill -9 `pidof smbd` while a write access is in
-progress could do the damage as well as a power interruption,
-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.
-
-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:
-
-Here is how I backed up my printing.tdb file:
-
-CUPS ships with good support for HP LaserJet type printers. You can
-install the generic driver as follows:
-
-The -m switch will retrieve the
-laserjet.ppd from the standard repository for
-not-yet-installed-PPDs, which CUPS typically stores in
-/usr/share/cups/model. Alternatively, you may use
--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
-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
-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.
-
-
-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
-new-style PPDs for your foomatic-driven printers. foomatic-rip will
-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!
-
-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
-should be, that it also has a very end-user friendly interface which
-allows for an easy update of drivers and PPDs, for all supported
-models, all spoolers, all operating systems and all package formats
-(because there is none). Its history goes back a few years.
-
-Recently Foomatic has achieved the astonishing milestone of 1000
-listed printer models. Linuxprinting.org keeps all the
-important facts about printer drivers, supported models and which
-options are available for the various driver/printer combinations in
-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!
-
-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
-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
-anywhere near the quality it is today!
-
-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
-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.
-
-"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"
-(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
-Ghostscript). On the other hand, CUPS provided brilliant support for
-controlling all printer options through
-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"
-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":
- 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
-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.
-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
-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
-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
-(for PDQ) and LPD-O-Matic
-(for - you guessed it - LPD); the configuration here didn't use PPDs
-but other spooler-specific files.
-
-From late summer of that year, Till Kamppeter
-started to put work into the database. Till had been newly employed by
-MandrakeSoft to
-convert their printing system over to CUPS, after they had seen his
-FLTK-based XPP (a GUI frontend to
-the CUPS lp-command). He added a huge amount of new information and new
-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)....
-
-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
-configuration files..
-
-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
-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
-their system.... For users there is improved media type and source
-support; paper sizes and trays are easier to configure.
-
-Also, the New Generation of Linuxprinting.org PPDs doesn't contain
-Perl data structures any more. If you are a distro maintainer and have
-used the previous version of Foomatic, you may want to give the new
-one a spin: but don't forget to generate a new-version set of PPDs,
-via the new foomatic-db-engine!
-Individual users just need to generate a single new PPD specific to
-their model by following
-the steps outlined in the Foomatic tutorial or further
-below. This new development is truly amazing.
-
-foomatic-rip is a very clever wrapper around the need to run
-Ghostscript with a different syntax, different options, different
-device selections and/or different filters for each different printer
-or different spooler. At the same time it can read the PPD associated
-with a print queue and modify the print job according to the user
-selections. Together with this comes the 100% compliance of the new
-Foomatic PPDs with the Adobe spec. Some really innovative features of
-the Foomatic concept will surprise users: it will support custom paper
-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).
-
-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
-database. In addition, it also provides the Foomatic glue to integrate
-the many drivers into any modern (or legacy) printing system known to
-the world.
-
-Speaking of the different driver development groups: most of
-the work is currently done in three projects. These are:
- Omni
--- a Free Software project by IBM which tries to convert their printer
-driver knowledge from good-ol' OS/2 times into a modern, modular,
-universal driver architecture for Linux/UNIX (still Beta). This
-currently supports 437 models. HPIJS --
-a Free Software project by HP to provide the support for their own
-range of models (very mature, printing in most cases is perfect and
-provides true photo quality). This currently supports 369
-models. Gimp-Print -- a Free software
-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.
-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
-systems are also going there, and the relatively new Mac
-OS X forum has turned out to be one of the most frequented
-fora after only a few weeks.
-
-Linuxprinting.org and the Foomatic driver wrappers around Ghostscript
-are now a standard toolchain for printing on all the important
-distros. Most of them also have CUPS underneath. While in recent years
-most printer data had been added by Till (who works at Mandrake), many
-additional contributions came from engineers with SuSE, RedHat,
-Connectiva, Debian and others. Vendor-neutrality is an important goal
-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.
-
-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
-its internal XML-based datasets. While these PPDs are modelled to 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"
-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
-PPDs now call foomatic-rip). This filter
-script calls Ghostscript on the host system (the recommended variant
-is ESP Ghostscript) to do the rendering work. foomatic-rip knows which
-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
-web interface) read the PPD too and use this information to present
-the available settings to the user as an intuitive menu selection.
-
-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
-Linuxprinting.org ensures you to get the latest driver/PPD files):
- Check the complete list of printers in the database:
-http://www.linuxprinting.org/printer_list.cgi?make=Anyone
- There select your model and click on the
-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:
- 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
-visit them all, if you are not familiar with the Linuxprinting.org
-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
-spoolers. Another link may lead you to the homepage of the
-driver author or the driver. Important links are the ones which provide hints with
-setup instructions for CUPS (http://www.linuxprinting.org/cups-doc.html),
-PDQ (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
-). 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)
-generate and download the PPD: http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=0
- The PPD contains all the information needed to use our
-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
-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"
-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
-the PPD to a suitable place on your harddisk, say
-/path/to/my-printer.ppd (if you prefer to install
-your printers with the help of the CUPS web interface, save the PPD to
-the /usr/share/cups/model/ path and re-start
-cupsd). Then install the printer with a suitable commandline,
-e.g.:
- 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
-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:
-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
-cupsd.
-Once you print to a printqueue set up with the Foomatic-PPD, CUPS will
-insert the appropriate commands and comments into the resulting
-PostScript jobfile. foomatic-rip is able to read and act upon
-these. foomatic-rip uses some specially encoded Foomatic comments,
-embedded in the jobfile. These in turn are used to construct
-(transparently for you, the user) the complicated ghostscript command
-line telling for the printer driver how exactly the resulting raster
-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
-to print with CUPS (it is only one important
-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
-produced for cupsomatic don't work with
-foomatic-rip).
-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.
-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
-jobs or on the number of pages or both, and are spanning any time
-period you want.
-
-This is an example command how root would set a print quota in CUPS,
-assuming an existing printer named "quotaprinter":
-
-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).
-
-For CUPS to count correctly, the printfile needs to pass the CUPS
-"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!
-
-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
-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/.
-
-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
-therefore was not counted correctly (the reason is that it often,
-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).
-
-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
-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
-current from CUPS 1.1.16).
-
-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
-1.1.19)
-Here is an extract of my CUPS server's page_log file to illustrate the
-format and included items:
-
-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".
-
-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
-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
-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
-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".
-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
-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
-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
-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://,
-smb://, ipp://, http://, parallel:/, serial:/, usb:/ etc.)
-
-"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
-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
-away and re-directs it to go through Ghostscript. CUPS accepts this,
-because the associated CUPS-O-Matic-/Foomatic-PPD specifies:
-
-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
-Jobs arriving from Windows which are auto-typed
-"application/octet-stream", with the according changes in
-/etc/cups/mime.types in place.
-
-CUPS is widely configurable and flexible, even regarding its filtering
-mechanism. Another workaround in some situations would be to have in
-/etc/cups/mime.types entries as follows:
-
-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
-want to print PS code on non-PS printers (provided they support ASCII
-text printing) an entry as follows could be useful:
-
-and would effectively send all files to the
-backend without further processing.
-
-Lastly, you could have the following entry:
-
-You will need to write a my_PJL_stripping_filter
-(could be a shellscript) that parses the PostScript and removes the
-unwanted PJL. This would need to conform to CUPS filter design
-(mainly, receive and pass the parameters printername, job-id,
-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".
-
-CUPS can handle -o job-hold-until=indefinite.
-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
-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.).
-
-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.
-
-Some important parameter settings in the CUPS configuration file
-cupsd.conf are:
-
-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
-similar job as the old-fashioned BSD-LPD control files). This is set
-to "Yes" as a default.
-
-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
-default.
-
-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
-make room for the new one. If all of the known jobs are still
-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"...)
-
-For everything to work as announced, you need to have three
-things:
-
-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):
-
-(adapt paths as needed). These commands leave out the empty
-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?
-;-)
-
-From time to time the question arises, how you can print
-to a Windows attached printer
-from Samba. Normally the local connection
-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
-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"
-file there. It should be a symlink to smbspool
-which file must exist and be executable:
-
-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
-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
-be able to print to the printer if it were hooked directly at your
-Samba/CUPS host. For troubleshooting purposes, this is what you
-should do, to determine if that part of the process chain is in
-order. Then proceed to fix the network connection/authentication to
-the Windows host, etc.
-
-To install a printer with the smb backend on CUPS, use this command:
-
-The PPD must be able to direct CUPS to generate
-the print data for the target model. For PostScript printers just use
-the PPD that would be used with the Windows NT PostScript driver. But
-what can you do if the printer is only accessible with a password? Or
-if the printer's host is part of another workgroup? This is provided
-for: you can include the required parameters as part of the
-smb:// device-URI. Like this:
- smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename smb://username:password@WINDOWSNETBIOSNAME/printersharename
-Note that the device-URI will be visible in the process list of the
-Samba server (e.g. when someone uses the ps -aux
-command on Linux), even if the username and passwords are sanitized
-before they get written into the log files. So this is an inherently
-insecure option. However it is the only one. Don't use it if you want
-to protect your passwords. Better share the printer in a way that
-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? :-).
-
-The following diagrams reveal how CUPS handles print jobs.
-
-Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-CUPS and ESP PrintPro plug-in where rastertosomething is noted.
- 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. 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). 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
-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
-cupsd.conf
-set to a valid value and is it writeable?
- 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? 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
-smbstatus to check for active connections. Kill the
-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")
-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
-in the Network Neighbourhood), right-click the
-printer in question and select
-Connect... 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. 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). 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). 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
-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. Local Security Policies may not
-allow the installation of unsigned drivers. "Local Security Policies"
-may not allow the installation of printer drivers at
-all. 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
-automatically install printers for all
-users. 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 introduced a Point and Print
-Restriction Policy (this restriction doesn't apply to
-"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
-Enabled and the Users can only Point
-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. 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:
- The first "wrong" way:
-
- Open the Printers
-folder. Right-click on the printer
-(remoteprinter on cupshost) and
-select in context menu Printing
-Preferences... Look at this dialog closely and remember what it looks
-like.
- The second "wrong" way:
-
- Open the Printers
-folder. Right-click on the printer (remoteprinter on
-cupshost) and select in the context menu
-Properties Click on the General
-tab Click on the button Printing
-Preferences... A new dialog opens. Keep this dialog open and go back
-to the parent dialog.
- The third, the "correct" way: (should you do
-this from the beginning, just carry out steps 1. and 2. from second
-"way" above)
-
- Click on the Advanced
-tab. (Hmmm... if everything is "Grayed Out", then you are not logged
-in as a user with enough privileges). Click on the Printing
-Defaults... button. On any of the two new tabs, click on the
-Advanced...
-button. A new dialog opens. Compare this one to the other,
-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
-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
-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). Don't use Optimize for
-Speed: use Optimize for
-Portability instead (Adobe PS Driver) Don't use
-Page Independence: No: always
-settle with Page Independence:
-Yes (Microsoft PS Driver and CUPS PS Driver for
-WinNT/2K/XP) If there are problems with fonts: use
-Download as Softfont into
-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. 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
-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. 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]
-section). These must be different. Set
-RequestRoot /var/spool/cups/ in
-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. 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
-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
-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"
-then, giving you a better control over what may happen in a large
-networked environment. 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. Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents
-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.
-
-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.
-
-Given that Samba-3 has the capability to function with a scalable backend authentication
-database such as LDAP, and given it's ability to run in Primary as well as Backup Domain control
-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.
-
-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
-this design significantly impacts the delegation of administrative responsibilities in
-large and diverse organisations.
-
-Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
-of circumventing the limitations of the older technologies. Not every organisation is ready
-or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
-is quite adequate, there thus remains an entrenched user base for whom there is no direct
-desire to go through a disruptive change to adopt ADS.
-
-Microsoft introduced with MS Windows NT the ability to allow differing security domains
-to affect a mechanism so that users from one domain may be given access rights and privileges
-in another domain. The language that describes this capability is couched in terms of
-Trusts. Specifically, one domain will trust the users
-from another domain. The domain from which users are available to another security domain is
-said to be a trusted domain. The domain in which those users have assigned rights and privileges
-is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
-thus if users in both domains are to have privileges and rights in each others' domain, then it is
-necessary to establish two (2) relationships, one in each direction.
-
-In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
-are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
-relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
-implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
-transitive.
-
-
-New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
-by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
-domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
-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.
-
-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.
-
-
-
-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 menu, select
- . Next to the lower box labelled
-Permitted to Trust this Domain are two buttons,
-and . The button will open a panel in which
-to enter the name of the remote domain that will be able to assign access rights to users in
-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).
-
-
-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
- 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.
-
-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:
-
- DomA (completes the trust connection) Trusts DomB
-
- DomA is the Trusting domain
-
- DomB is the Trusted domain (originates the trust account)
-
- Users in DomB can access resources in DomA
-
- Users in DomA can NOT access resources in DomB
-
- Global groups from DomB CAN be used in DomA
-
- Global groups from DomA can NOT be used in DomB
-
- DomB DOES appear in the logon dialog box on client workstations in DomA
-
- DomA does NOT appear in the logon dialog box on client workstations in DomB
-
- Users / Groups in a trusting domain can NOT be granted rights, permissions or access
- to a trusted domain.
-
- The trusting domain CAN access and use accounts (Users / Global Groups) in the
- trusted domain.
-
- Administrators of the trusted domain CAN be granted admininstrative rights in the
- trusting domain.
-
- Users in a trusted domain CAN be given rights and privileges in the trusting
- domain.
-
- Trusted domain Global Groups CAN be given rights and permissions in the trusting
- domain.
-
- Global Groups from the trusted domain CAN be made members in Local Groups on
- MS Windows domain member machines.
-
-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.
-
-Each of the procedures described below assumes the peer domain in the trust relationship is
-controlled by a Windows NT4 server. However, the remote end could just as well be another
-Samba-3 domain. It can be clearly seen, after reading this document, that combining
-Samba-specific parts of what's written below leads to trust between domains in a purely Samba
-environment.
-
-In order to set the Samba PDC to be the trusted party of the relationship you first need
-to create a special account for the domain that will be the trusting party. To do that,
-you can use the 'smbpasswd' utility. Creating the trusted domain account is very
-similar to creating a trusted machine account. Suppose, your domain is
-called SAMBA, and the remote domain is called RUMBA. The first step
-will be to issue this command from your favourite shell:
-
-
-
-where -a means to add a new account into the
-passdb database and -i means: ''create this
-account with the InterDomain trust flag''
-
-The account name will be 'rumba$' (the name of the remote domain)
-
-After issuing this command you'll be asked to enter the password for
-the account. You can use any password you want, but be aware that Windows NT will
-not change this password until 7 days following account creation.
-After the command returns successfully, you can look at the entry for the new account
-(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
- menu, select .
-Right beside the Trusted domains list box press the
- button. You will be prompted for
-the trusted domain name and the relationship password. Type in SAMBA, as this is
-the name of the remote domain, and the password used at the time of account creation.
-Press OK and, if everything went without incident, you will see
-Trusted domain relationship successfully
-established message.
-
-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
- , .
-Now, next to the Trusted Domains box press the
-button, and type in the name of the trusted domain (SAMBA) and the password to use in securing
-the relationship.
-
-The password can be arbitrarily chosen. It is easy to change the password
-from the Samba server whenever you want. After confirming the password your account is
-ready for use. Now it's Samba's turn.
-
-Using your favourite shell while being logged in as root, issue this command:
-
-root# net rpc trustdom establish rumba
-
-You will be prompted for the password you just typed on your Windows NT4 Server box.
-Do not worry if you see an error message that mentions a return code of
-NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the
-password you gave is correct and the NT4 Server says the account is
-ready for interdomain connection and not for ordinary
-connection. After that, be patient; it can take a while (especially
-in large networks), but eventually you should see the Success message.
-Congratulations! Your trust relationship has just been established.
-
-Note that you have to run this command as root because you must have write access to
-the secrets.tdb file.
-
-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
-Samba to trust a Windows 2000 server, however, more testing is still needed in this area.
-
-After creating the interdomain trust account on the
-Samba server as described above, open Active Directory Domains and
-Trusts on the AD controller of the domain whose resources you wish Samba users
-to have access to. Remember that since NT4-style trusts are not transitive, if you want
-your users to have access to multiple mixed-mode domains in your AD forest, you will need to
-repeat this process for each of those domains. With Active Directory Domains
-and Trusts open, right-click on the name of the Active Directory domain that
-will trust our Samba domain and choose , then click on
-the Trusts tab. In the upper part of the panel, you will see a list box
-labelled Domains trusted by this domain:, and an
-Add... button next to it. Press this button, and just as with NT4, you
-will be prompted for the trusted domain name and the relationship password. Press OK, and
-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.
- “
-"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
-transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
-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.
-
-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
-ran over UDP. When there was a need to run it over TCP so that it would be compatible
-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
-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
-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.
-
-Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
-Common Insecurities Fail Scrutiny:
-
-Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
-stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
-been dutifully waded through during the information-gathering stages of this project, and there
-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?
-
- 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.
-
- 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
- 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;
- 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
- essential functions of your input/output hardware -- whereas NetBIOS controls the
- essential functions of your input/output traffic via the network. Again, this is a bit
- of an exaggeration but it should help that paradigm shift. What is important to realize
- is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
- 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
- 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".
- It is not often heard from these days.
-
- 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
- traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137,
- NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service
- (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts,
- and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002
- (Detailed specifications).
-
- W2K: Acronym for Windows 2000 Professional or Server
-
- 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).
-
-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.
-
- SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
- that Microsoft Windows and OS/2 Lan Manager use to share files and printers
- over local networks) and access them just like any other Unix directory. This is useful
- if you just want to mount such filesystems without being a SMBFS server.
-
- CIFS VFS (Common Internet File System Virtual File System) is the successor to SMBFS, and
- is being actively developed for the upcoming version of the Linux kernel. The intent of this module
- is to provide advanced network file system functionality including support for dfs (hierarchical
- name space), secure per-user session establishment, safe distributed caching (oplock),
- optional packet signing, Unicode and other internationalization improvements, and optional
- Winbind (nsswitch) integration.
-
-Again, it's important to note that these are implementations for client filesystems, and have
-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.
-
-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
- or 445/tcp.
-
- "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
- 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
- Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
- Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
- Authentication
-
- SMB Session Startup. Passwords are encrypted (or not) according to one of
- the following methods: Null (no encryption); Cleartext (no encryption); LM
- and NTLM; NTLM; NTLMv2
-
- SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
- to a service type (e.g., IPC$ named pipe)
-
-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.
- “
-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
-and who have had years of experience, just don't know how it works internally.
-Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
-mess that fixing one bug might just break a hundred programs that depend on
-that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
-in making money. They don't have anybody who takes pride in Windows 95 as an
-operating system.
-” “
-People inside Microsoft know it's a bad operating system and they still
-continue obviously working on it because they want to get the next version out
-because they want to have all these new features to sell more copies of the
-system.
-” “
-The problem with that is that over time, when you have this kind of approach,
-and because nobody understands it, because nobody REALLY fixes bugs (other than
-when they're really obvious), the end result is really messy. You can't trust
-it because under certain circumstances it just spontaneously reboots or just
-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.
-” “
-That's what's really irritating to me."
-” --
-Linus Torvalds, from an interview with BOOT Magazine, Sept 1998
-
-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.
- Table of Contents
-This is a rough guide to assist those wishing to migrate from NT4 domain control to
-Samba-3 based domain control.
-
-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.
-
-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.
-
-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
-should remain in place. Many who have introduced open source technologies have experienced
-pressure to return to a Microsoft based platform solution at the first sign of trouble.
-
-Before attempting a migration to a Samba-3 controlled network make every possible effort to
-gain all-round commitment to the change. Know precisely why the change
-is important for the organisation. Possible motivations to make a change include:
- Improve network manageability Obtain better user level functionality Reduce network operating costs Reduce exposure caused by Microsoft withdrawal of NT4 support Avoid MS License 6 implications Reduce organisation's dependency on Microsoft
-Make sure that everyone knows that Samba-3 is NOT MS Windows NT4. Samba-3 offers
-an alternative solution that is both different from MS Windows NT4 and that offers
-advantages compared with it. Gain recognition that Samba-3 lacks many of the
-features that Microsoft has promoted as core values in migration from MS Windows NT4 to
-MS Windows 2000 and beyond (with or without Active Directory services).
-
-What are the features that Samba-3 can NOT provide?
- Active Directory Server Group Policy Objects (in Active Directory) Machine Policy objects Logon Scripts in Active Directory Software Application and Access Controls in Active Directory
-The features that Samba-3 DOES provide and that may be of compelling interest to your site
-includes:
- Lower Cost of Ownership Global availability of support with no strings attached Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system) Creation of on-the-fly logon scripts Creation of on-the-fly Policy Files Greater Stability, Reliability, Performance and Availability Manageability via an ssh connection Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam) Ability to implement a full single-sign-on architecture Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand
-Before migrating a network from MS Windows NT4 to Samba-3 consider all necessary factors. Users
-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:
-
-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
-paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs).
-One way in which Samba-3 differs from Microsoft technology is that if one chooses to use an LDAP
-authentication backend then the same database can be used by several different domains. In a
-complex organisation there can be a single LDAP database, which itself can be distributed (ie: Have
-a master server and multiple slave servers) that can simultaneously serve multiple domains.
-
-From a design perspective, the number of users per server, as well as the number of servers, per
-domain should be scaled taking into consideration server capacity and network bandwidth.
-
-A physical network segment may house several domains. Each may span multiple network segments.
-Where domains span routed network segments, consider and test the performance implications of
-the design and layout of a network. A Centrally located domain controller that is designed to
-serve multiple routed network segments may result in severe performance problems. Check the
-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.
-
-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
-of keeping systems secure and functional.
-
-Keep in mind the nature of how data must be share. Physical disk space layout should be considered
-carefully. Some data must be backed up. The simpler the disk layout the easier it will be to
-keep track of backed needs. Identify what back media will be meet needs, consider backup to tape
-, CD-ROM or (DVD-ROM), or other off-line storage medium. Plan and implement for minimum
-maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance:
-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
-directories may substantially avoid file access complaints from samba share users.
-
-Inexperienced network administrators often attempt elaborate techniques to set access
-controls on files, directories, shares, as well as in share definitions.
-Keep your design and implementation simple and document your design extensively. Have others
-audit your documentation. Do not create a complex mess that your successor will not understand.
-Remember, job security through complex design and implementation may cause loss of operations
-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 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.
-
-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.
-
-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.
-
-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.
-
-The approximate migration process is described below.
-
-You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
-
-Samba-3 set up as a DC with netlogon share, profile share, etc. Configure the smb.conf file
-to fucntion as a BDC. ie: domain master = No.
- Procedure 31.1. The Account Migration Process Create a BDC account for the samba server using NT Server Manager Samba must NOT be running net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd net rpc vampire -S NT4PDC -U administrator%passwd pdbedit -L Note - did the users migrate?
- Now assign each of the UNIX groups to NT groups:
- (Note: It may be useful to copy this text to a script called
- initGroups.sh)
-
- net groupmap list Now check that all groups are recognised
-Now migrate all the profiles, then migrate all policy files.
-
-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 Want simple conversion with NO pain Want new features, can manage some in-house complexity Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas
-There are three basic choices for sites that intend to migrate from MS Windows NT4
-to Samba-3.
-
- Simple Conversion (total replacement)
-
- Upgraded Conversion (could be one of integration)
-
- Complete Redesign (completely new solution)
-
-Minimise down-stream problems by:
-
- Take sufficient time
-
- Avoid Panic
-
- Test ALL assumptions
-
- Test full roll-out program, including workstation deployment
- Table 31.2. Nature of the Conversion Choices 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 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
-
- Samba-3 can use a local authentication backend:
- smbpasswd, tdbsam, ldapsam, mysqlsam
- On the Share itself - using Share ACLs On the file system - using UNIX permissions on files and directories Note: Can Enable Posix ACLs in file system also Through Samba share parameters - Not recommended - except as last resort Using Group Policy Editor (NT4) - Watch out for Tattoo effect
- Platform specific so use platform tool to change from a Local to a Roaming profile
- Can use new profiles tool to change SIDs (NTUser.DAT)
-
- Know how they work
- username map facility may be needed Use 'net groupmap' to connect NT4 groups to Unix groups Use pdbedit to set/change user configuration
- NOTE: When migrating to LDAP back, end it may be easier to dump initial
- LDAP database to LDIF, then edit, then reload into LDAP
- Add/Delete Users: Note OS limits on size of name
- (Linux 8 chars) NT4 up to 254 chars Add/Delete Machines: Applied only to domain members
- (Note: Machine names may be limited to 16 characters) Use 'net groupmap' to connect NT4 groups to Unix groups Add/Delete Groups: Note OS limits on size and nature.
- Linux limit is 16 char, no spaces and no upper case chars (groupadd)
- Domain Control (NT4 Style) Profiles, Policies, Access Controls, Security
- Samba: net, rpcclient, smbpasswd, pdbedit, profiles Windows: NT4 Domain User Manager, Server Manager (NEXUS)
- Table of Contents
-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
-NOT involved in browse list handling except by way of name to address resolution.
-
-MS Windows 2000 and later can be configured to operate with NO NetBIOS
-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.
-
-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
-lusty features, NetBIOS is like Paterson's Curse.
-
-For those not familiar with botanical problems in Australia: Paterson's curse,
-Echium plantagineum, was introduced to Australia from Europe during the mid-nineteenth
-century. Since then it has spread rapidly. The high seed production, with densities of
-thousands of seeds per square metre, a seed longevity of more than seven years, and an
-ability to germinate at any time of year, given the right conditions, are some of the
-features which make it such a persistent weed.
-
-In this chapter we explore vital aspects of SMB (Server Message Block) networking with
-a particular focus on SMB as implemented through running NetBIOS (Network Basic
-Input / Output System) over TCP/IP. Since Samba does NOT implement SMB or NetBIOS over
-any other protocols we need to know how to configure our network environment and simply
-remember to use nothing but TCP/IP on all our MS Windows network clients.
-
-Samba provides the ability to implement a WINS (Windows Internetworking Name Server)
-and implements extensions to Microsoft's implementation of WINS. These extensions
-help Samba to affect stable WINS operations beyond the normal scope of MS WINS.
-
-Please note that WINS is exclusively a service that applies only to those systems
-that run NetBIOS over TCP/IP. MS Windows 200x / XP have the capacity to turn off
-support for NetBIOS, in which case WINS is of no relevance. Samba supports this also.
-
-For those networks on which NetBIOS has been disabled (ie: WINS is NOT required)
-the use of DNS is necessary for host name resolution.
-
-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.
-
-What seems so simple is in fact a very complex interaction of different technologies.
-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.
- Name Resolution Method:
- name resolve order(*).
- WINS options:
- 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.
-
-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.
-
-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
-to remote network segments via unicast UDP. Similarly, the
-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,
-wherever possible nmbd should be configured on one (1) machine as the WINS
-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
-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.
-
-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
-of the Samba-3.0.0 release. Hopefully, this will become a supported feature
-of one of the Samba-3 release series.
-
-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
-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
-on other subnets. This setup is not recommended, but is mentioned as a practical
-consideration (ie: an 'if all else fails' scenario).
-
-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.
-
-
-
-
-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
-the Internet usable. DNS based host name resolution is supported by nearly all TCP/IP
-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
-
-When an MS Windows 200x / XP system attempts to resolve a host name to an IP address
-it follows a defined path:
-
- Checks the hosts file. It is located in
- C:\WinNT\System32\Drivers\etc.
-
- Does a DNS lookup
-
- Checks the NetBIOS name cache
-
- Queries the WINS server
-
- Does a broadcast name lookup over UDP
-
- 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
-
-With Active Directory (ADS), a correctly functioning DNS server is absolutely
-essential. In the absence of a working DNS server that has been correctly configured,
-MS Windows clients and servers will be totally unable to locate each other,
-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.
-
-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
-to use BIND version 8 or 9, but it will almost certainly be necessary to create service records
-so that MS Active Directory clients can resolve host names to locate essential network services.
-The following are some of the default service records that Active Directory requires:
- _ldap._tcp.pdc.ms-dcs.Domain
- This provides the address of the Windows NT PDC for the Domain.
- _ldap._tcp.pdc.ms-dcs.DomainTree
- Resolves the addresses of Global Catalog servers in the domain.
- _ldap._tcp.site.sites.writable.ms-dcs.Domain
- Provides list of domain controllers based on sites.
- _ldap._tcp.writable.ms-dcs.Domain
- Enumerates list of domain controllers that have the writable
- copies of the Active Directory data store.
- _ldap._tcp.GUID.domains.ms-dcs.DomainTree
- Entry used by MS Windows clients to locate machines using the
- Global Unique Identifier.
- _ldap._tcp.Site.gc.ms-dcs.DomainTree
- Used by MS Windows clients to locate site configuration dependent
- Global Catalog server.
-
-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
-takes place is determined by whether or not the MS Windows client/server
-has been given a WINS server address, whether or not LMHOSTS lookup
-is enabled, or if DNS for NetBIOS name resolution is enabled, etc.
-
-In the case where there is no WINS server, all name registrations as
-well as name lookups are done by UDP broadcast. This isolates name
-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).
-
-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
-and thus WINS allows name resolution to function across routed networks.
-
-During the startup process an election will take place to create a
-local master browser if one does not already exist. On each NetBIOS network
-one machine will be elected to function as the domain master browser. This
-domain browsing has nothing to do with MS security domain control.
-Instead, the domain master browser serves the role of contacting each local
-master browser (found by asking WINS or from LMHOSTS) and exchanging browse
-list contents. This way every master browser will eventually obtain a complete
-list of all machines that are on the network. Every 11-15 minutes an election
-is held to determine which machine will be the master browser. By the nature of
-the election criteria used, the machine with the highest uptime, or the
-most senior protocol version, or other criteria, will win the election
-as domain master browser.
-
-Clients wishing to browse the network make use of this list, but also depend
-on the availability of correct name resolution to the respective IP
-address/addresses.
-
-Any configuration that breaks name resolution and/or browsing intrinsics
-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.
-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
-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.
-This mechanism could be via DNS, /etc/hosts,
-and so on.
-
-To set up cross subnet browsing on a network containing machines
-in up to be in a WORKGROUP, not an NT Domain you need to set up one
-Samba server to be the Domain Master Browser (note that this is *NOT*
-the same as a Primary Domain Controller, although in an NT Domain the
-same machine plays both roles). The role of a Domain master browser is
-to collate the browse lists from local master browsers on all the
-subnets that have a machine participating in the workgroup. Without
-one machine configured as a domain master browser each subnet would
-be an isolated workgroup, unable to see any machines on any other
-subnet. It is the presence of a domain master browser that makes
-cross subnet browsing possible for a workgroup.
-
-In an WORKGROUP environment the domain master browser must be a
-Samba server, and there must only be one domain master browser per
-workgroup name. To set up a Samba server as a domain master browser,
-set the following option in the [global] section
-of the smb.conf file :
-
-
-
-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
-
-The domain master browser may be the same machine as the WINS
-server, if you require.
-
-Next, you should ensure that each of the subnets contains a
-machine that can act as a local master browser for the
-workgroup. Any MS Windows NT/2K/XP/2003 machine should be
-able to do this, as will Windows 9x machines (although these
-tend to get rebooted more often, so it's not such a good idea
-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
-
-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
-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
-be the local master browser then you can disable Samba from
-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
-
-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
-is also the Domain master browser for that domain, and many
-things will break if a Samba server registers the Domain master
-browser NetBIOS name (DOMAIN<1B>)
-with WINS instead of the PDC.
-
-For subnets other than the one containing the Windows NT PDC
-you may set up Samba servers as local master browsers as
-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
-
-If you wish to have a Samba server fight the election with machines
-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
-Forcing Samba to be the master browser
-below.
-
-If you have Windows NT machines that are members of the domain
-on all subnets, and you are sure they will always be running then
-you can disable Samba from taking part in browser elections and
-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
-
-Who becomes the master browser is determined by an election
-process using broadcasts. Each election packet contains a number of parameters
-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
-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
-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
-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
-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
-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.
-
-It is possible to configure two Samba servers to attempt to become
-the domain master browser for a domain. The first server that comes
-up will be the domain master browser. All other Samba servers will
-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.
-
-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
-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
-workgroup that has the same name as an NT Domain.
-
-When Samba is the domain master and the master browser, it will listen
-for master announcements (made roughly every twelve minutes) from local
-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
-startup.
-
-Note that all your servers (including Samba) and clients should be
-using a WINS server to resolve NetBIOS names. If your clients are only
-using broadcasting to resolve NetBIOS names, then two things will occur:
-
- your local master browsers will be unable to find a domain master
- browser, as it will only be looking on the local subnet.
-
- if a client happens to get hold of a domain-wide browse list, and
- a user attempts to access a host in that list, it will be unable to
- resolve the NetBIOS name of that host.
-
-If, however, both Samba and your clients are using a WINS server, then:
-
- your local master browsers will contact the WINS server and, as long as
- Samba has registered that it is a domain master browser with the WINS
- server, your local master browser will receive Samba's IP address
- as its domain master browser.
-
- when a client receives a domain-wide browse list, and a user attempts
- to access a host in that list, it will contact the WINS server to
- 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.
-
-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.
-
-Samba now supports machines with multiple network interfaces. If you
-have multiple interfaces then you will need to use the interfaces
-option in smb.conf to configure them.
-
-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:
-
-or
-
-
-where:
-
-
-
-
- is either the LMB (Local Master Browser) IP address
-or the broadcast address of the remote network.
-ie: the LMB is at 192.168.1.10, or the address
-could be given as 192.168.1.255 where the netmask
-is assumed to be 24 bits (255.255.255.0).
-When the remote announcement is made to the broadcast
-address of the remote network, every host will receive
-our announcements. This is noisy and therefore
-undesirable but may be necessary if we do NOT know
-the IP address of the remote LMB. is optional and can be either our own workgroup
-or that of the remote network. If you use the
-workgroup name of the remote network then our
-NetBIOS machine names will end up looking like
-they belong to that workgroup, this may cause
-name resolution problems and should be avoided.
-
-
-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:
-
-
-
-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.
-
-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.
-eg: It registers its name directly as a unique (the type 0x03) name.
-It also registers its name if it is running the LanManager compatible
-server service (used to make shares and printers available to other users)
-by registering the server (the type 0x20) name.
-
-All NetBIOS names are up to 15 characters in length. The name_type variable
-is added to the end of the name - thus creating a 16 character name. Any
-name that is shorter than 15 characters is padded with spaces to the 15th
-character. ie: All NetBIOS names are 16 characters long (including the
-name_type information).
-
-WINS can store these 16 character names as they get registered. A client
-that wants to log onto the network can ask the WINS server for a list
-of all names that have registered the NetLogon service name_type. This saves
-broadcast traffic and greatly expedites logon processing. Since broadcast
-name resolution can not be used across network segments this type of
-information can only be provided via WINS or via statically configured
-lmhosts files that must reside on all clients in the
-absence of WINS.
-
-WINS also serves the purpose of forcing browse list synchronisation by all
-LMB's. LMB's must synchronise their browse list with the DMB (domain master
-browser) and WINS helps the LMB to identify it's DMB. By definition this
-will work only within a single workgroup. Note that the domain master browser
-has NOTHING to do with what is referred to as an MS Windows NT Domain. The
-later is a reference to a security environment while the DMB refers to the
-master controller for browse list information only.
-
-Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
-has been configured to use the WINS server/s. Any client that has not been
-configured to use the WINS server will continue to use only broadcast based
-name registration so that WINS may NEVER get to know about it. In any case,
-machines that have not registered with a WINS server will fail name to address
-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
-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.
-
-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!
-
-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 :
-in the [global] section add the line
-
-
-
-Versions of Samba prior to 1.9.17 had this parameter default to
-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
-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
-server.
-
-To set up a Windows NT Server as a WINS server you need to set up
-the WINS service - see your NT documentation for details. Note that
-Windows NT WINS Servers can replicate to each other, allowing more
-than one to be set up in a complex subnet environment. As Microsoft
-refuses to document these replication protocols, Samba cannot currently
-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.
-
-After the WINS server has been configured you must ensure that all
-machines participating on the network are configured with the address
-of this WINS server. If your WINS server is a Samba machine, fill in
-the Samba machine IP address in the Primary WINS Server field of
-the Control Panel->Network->Protocols->TCP->WINS Server dialogs
-in Windows 95 or Windows NT. To tell a Samba server the IP address
-of the WINS server add the following line to the [global] section of
-all smb.conf files :
-
-
-
-where <name or IP address> is either the DNS name of the WINS server
-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
-nmbd will fail to start.
-
-There are two possible scenarios for setting up cross subnet browsing.
-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.
-
-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.
-
-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.
-
-Entries in wins.dat take the form of
-
-
-
-where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the
-time-to-live as an absolute time in seconds, ADDRESS+ is one or more
-addresses corresponding to the registration and FLAGS are the NetBIOS
-flags for the registration.
-
-A typical dynamic entry looks like:
-
-
-To make it static, all that has to be done is set the TTL to 0:
-
-
-
-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.
-
-The following hints should be carefully considered as they are stumbling points
-for many new network administrators.
-
-Do NOT use more than one (1) protocol on MS Windows machines
-
-A very common cause of browsing problems results from installing more than
-one protocol on an MS Windows machine.
-
-Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
-every 15 minutes. A set of election criteria is used to determine the order
-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
-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
-the only one with both protocols then the LMB may be won on the NetBIOS
-interface over the IPX protocol. Samba will then lose the LMB role as Windows
-9x will insist it knows who the LMB is. Samba will then cease to function
-as an LMB and thus browse list operation on all TCP/IP only machines will
-fail.
-
-Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
-The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
-referred to as the WinNT family, but it should be recognised that 2000 and
-XP/2003 introduce new protocol extensions that cause them to behave
-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!
-
-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:
- WINS: the best tool! LMHOSTS: is static and hard to maintain. Broadcast: uses UDP and can not resolve names across remote segments.
-Alternative means of name resolution includes:
- /etc/hosts: is static, hard to maintain, and lacks name_type info DNS: is a good choice but lacks essential name_type info.
-Many sites want to restrict DNS lookups and want to avoid broadcast name
-resolution traffic. The name resolve order parameter is of great help here.
-The syntax of the name resolve order parameter is:
-
-or
-
-The default is:
-
-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.
-
-SMB networking provides a mechanism by which clients can access a 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
-list is heavily used by all SMB clients. Configuration of SMB
-browsing has been problematic for some Samba users, hence this
-document.
-
-MS Windows 2000 and later, as with Samba 3 and later, can be
-configured to not use NetBIOS over TCP/IP. When configured this way,
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will NOT work if name resolution
-from SMB machine names to IP addresses does not function correctly.
-
-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.
-
-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
-to support domain logons and scripts is now available.
-
-Samba can also act as a domain master browser for a workgroup. This
-means that it will collate lists from local browse masters into a
-wide area network server list. In order for browse clients to
-resolve the names they may find in this list, it is recommended that
-both Samba and your clients use a WINS server.
-
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain: on each wide area
-network, you must only ever have one domain master browser per workgroup,
-regardless of whether it is NT, Samba or any other type of domain master
-that is providing this service.
-
-Nmbd can be configured as a WINS server, but it is not
-necessary to specifically use Samba as your WINS server. MS Windows
-NT4, Server or Advanced Server 2000 or 2003 can be configured as
-your WINS server. In a mixed NT/2000/2003 server and Samba environment on
-a Wide Area Network, it is recommended that you use the Microsoft
-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 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
-smb.conf man page.
-
-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
-in text form in a file called browse.dat.
-
-Note that if it doesn't work for you, then you should still be able to
-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
-IPC$ connection that lists the shares is done as guest, and thus you must
-have a valid guest account.
-
-MS Windows 2000 and upwards (as with Samba) can be configured to disallow
-anonymous (ie: Guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged in user to query the IPC$ share. MS Windows
-9X clients are not able to do this and thus will NOT be able to browse
-server resources.
-
-The other big problem people have is that their broadcast address,
-netmask or IP address is wrong (specified with the "interfaces" option
-in smb.conf)
-
-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.
-
-To see browse lists that span TCP/IP subnets (ie. networks separated
-by routers that don't pass broadcast traffic), you must set up at least
-one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing
-NetBIOS name to IP address translation to be done by doing a direct
-query of the WINS server. This is done via a directed UDP packet on
-port 137 to the WINS server machine. The reason for a WINS server is
-that by default, all NetBIOS name to IP address translation is done
-by broadcasts from the querying machine. This means that machines
-on one subnet will not be able to resolve the names of machines on
-another subnet without using a WINS server.
-
-Remember, for browsing across subnets to work correctly, all machines,
-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.
-
-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.
-Samba is capable of cross subnet browsing when configured correctly.
-
- Consider a network set up as in the diagram below.
-
-Consisting of 3 subnets (1, 2, 3) connected by two routers
-(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines
-on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume
-for the moment that all these machines are configured to be in the
-same workgroup (for simplicity's sake). Machine N1_C on subnet 1
-is configured as Domain Master Browser (ie. it will collate the
-browse lists for the workgroup). Machine N2_D is configured as
-WINS server and all the other machines are configured to register
-their NetBIOS names with it.
-
-As all these machines are booted up, elections for master browsers
-will take place on each of the three subnets. Assume that machine
-N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
-subnet 3 - these machines are known as local master browsers for
-their particular subnet. N1_C has an advantage in winning as the
-local master browser on subnet 1 as it is set up as Domain Master
-Browser.
-
-On each of the three networks, machines that are configured to
-offer sharing services will broadcast that they are offering
-these services. The local master browser on each subnet will
-receive these broadcasts and keep a record of the fact that
-the machine is offering a service. This list of records is
-the basis of the browse list. For this case, assume that
-all the machines are configured to offer services so all machines
-will be on the browse list.
-
-For each network, the local master browser on that network is
-considered 'authoritative' for all the names it receives via
-local broadcast. This is because a machine seen by the local
-master browser via a local broadcast must be on the same
-network as the local master browser and thus is a 'trusted'
-and 'verifiable' resource. Machines on other networks that
-the local master browsers learn about when collating their
-browse lists have not been directly seen - these records are
-called 'non-authoritative'.
-
-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
-
-Note that at this point all the subnets are separate, no
-machine is seen across any of the subnets.
-
-Now examine subnet 2. As soon as N2_B has become the local
-master browser it looks for a Domain master browser to synchronize
-its browse list with. It does this by querying the WINS server
-(N2_D) for the IP address associated with the NetBIOS name
-WORKGROUP<1B>. This name was registered by the Domain master
-browser (N1_C) with the WINS server as soon as it was booted.
-
-Once N2_B knows the address of the Domain master browser it
-tells it that is the local master browser for subnet 2 by
-sending a MasterAnnouncement packet as a UDP port 138 packet.
-It then synchronizes with it by doing a NetServerEnum2 call. This
-tells the Domain Master Browser to send it all the server
-names it knows about. Once the domain master browser receives
-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
-
-Servers with a (*) after them are non-authoritative names.
-
-At this point users looking in their network neighborhood on
-subnets 1 or 2 will see all the servers on both, users on
-subnet 3 will still only see the servers on their own subnet.
-
-The same sequence of events that occurred for N2_B now occurs
-for the local master browser on subnet 3 (N3_D). When it
-synchronizes browse lists with the domain master browser (N1_A)
-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
-
-Servers with a (*) after them are non-authoritative names.
-
-At this point users looking in their network neighborhood on
-subnets 1 or 3 will see all the servers on all subnets, users on
-subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
-
-Finally, the local master browser for subnet 2 (N2_B) will sync again
-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
-
-Servers with a (*) after them are non-authoritative names.
-
-Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.
-
-If either router R1 or R2 fails the following will occur:
-
- Names of computers on each side of the inaccessible network fragments
- will be maintained for as long as 36 minutes, in the network neighbourhood
- lists.
-
- Attempts to connect to these inaccessible computers will fail, but the
- names will not be removed from the network neighbourhood lists.
-
- If one of the fragments is cut off from the WINS server, it will only
- 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.
-
-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.
-
-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
-in the browse list. When nmbd is taken out of service another machine on the network will
-become the browse master. This new list may still have the rogue entry in it. If you really
-want to clear a rogue machine from the list then every machine on the network will need to be
-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).
-
-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.
- 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? Table of Contents This chapter contains client-specific information.
- Yes. Thursby now has a CIFS Client / Server called DAVE
-
-They test it against Windows 95, Windows NT and samba for
-compatibility issues. At the time of writing, DAVE was at version
-1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
-the Thursby web site (the speed of finder copies has been greatly
-enhanced, and there are bug-fixes included).
-
-Alternatives - There are two free implementations of AppleTalk for
-several kinds of UNIX machines, and several more commercial ones.
-These products allow you to run file services and print services
-natively to Macintosh users, with no additional support required on
-the Macintosh. The two free implementations are
-Netatalk, and
-CAP.
-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. 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
- 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
- is then moved to 'Current Configuration'. Select that line,
- 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
- 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. You can use the free Microsoft LAN Manager 2.2c Client
- for OS/2 from
-
- ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/.
- In
- a nutshell, edit the file \OS2VER in the root directory of
- the OS/2 boot partition and add the lines: before you install the client. Also, don't use the
- included NE2000 driver because it is buggy. Try the NE2000
- or NS2000 driver from
-
- ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead.
- 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
- 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.:
- HP LaserJet 5L = LASERJET.HP LaserJet 5L You can have multiple drivers mapped in this file. If you only specify the OS/2 driver name, and not the
- device name, the first attempt to download the driver will
- actually download the files, but the OS/2 client will tell
- 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.
- 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
-VxD drivers. The latest release can be found on their ftp site at
-ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
-There is an update.txt file there that describes the problems that were
-fixed. New files include WINSOCK.DLL,
-TELNET.EXE,
-WSOCK.386,
-VNBT.386,
-WSTCP.386,
-TRACERT.EXE,
-NETSTAT.EXE, and
-NBTSTAT.EXE.
-
-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.
-
-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.
-
-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 Menu.
-This program allows you to control how WFW handles passwords. ie disable Password Caching etc
-for use with security = user
- 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. 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.
- Note that some people have found that setting DefaultRcvWindow in
-the [MSTCP] section of the
-SYSTEM.INI file under WfWg to 3072 gives a
-big improvement. I don't know why.
-
-My own experience with DefaultRcvWindow is that I get much better
-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.
-
-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.
-
-There are more updates than the ones mentioned here. You are referred to the
-Microsoft Web site for all currently available updates to your specific version
-of Windows 95.
-
-Also, if using MS Outlook it is desirable to
-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.
-
-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
-that Samba is a member of the domain, but the problem will
-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
-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
-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
-releases prior to Samba 2.2.2.
-
-The following is a minimal profile share:
- Example 38.1. Minimal profile share
-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
-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
-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"> This bug does not occur when using winbind to
-create accounts on the Samba host for Domain users. If you have problems communicating across routers with Windows
-NT 3.1 workstations, read this Microsoft Knowledge Base article.
-
- Table of Contents
-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.
-
-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"
-(or mistakes) administrators made and then requested help to resolve.
-
-By the time that MS Windows 2000 and Active Directory was released, administrators
-got the message: Group Policies are a good thing! They can help reduce administrative
-costs and actually can help to create happier users. But adoption of the true
-potential of MS Windows 200x Active Directory and Group Policy Objects (GPOs) for users
-and machines were picked up on rather slowly. This was very obvious from the samba
-mailing list as in 2000 and 2001 there were very few postings regarding GPOs and
-how to replicate them in a Samba environment.
-
-Judging by the traffic volume since mid 2002, GPOs have become a standard part of
-the deployment in many sites. This chapter reviews techniques and methods that can
-be used to exploit opportunities for automation of control over user desktops and
-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.
-
-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
-this file is read and the contents initiate changes to the registry of the client
-machine. This file allows changes to be made to those parts of the registry that
-affect users, groups of users, or machines.
-
-For MS Windows 9x/Me this file must be called Config.POL and may
-be generated using a tool called poledit.exe, better known as the
-Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
-disappeared again with the introduction of MS Windows Me (Millennium Edition). From
-comments from MS Windows network administrators it would appear that this tool became
-a part of the MS Windows Me Resource Kit.
-
-MS Windows NT4 Server products include the System Policy Editor
-under the Start -> Programs -> Administrative Tools menu item.
-For MS Windows NT4 and later clients this file must be called NTConfig.POL.
-
-New with the introduction of MS Windows 2000 was the Microsoft Management Console
-or MMC. This tool is the new wave in the ever changing landscape of Microsoft
-methods for management of network access and security. Every new Microsoft product
-or technology seems to obsolete the old rules and to introduce newer and more
-complex tools and methods. To Microsoft's credit though, the MMC does appear to
-be a step forward, but improved functionality comes at a great price.
-
-Before embarking on the configuration of network and system policies it is highly
-advisable to read the documentation available from Microsoft's web site regarding
-
-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".
-
-What follows is a very brief discussion with some helpful notes. The information provided
-here is incomplete - you are warned.
-
- 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
- Add/Remove Programs facility and then click on the 'Have Disk' tab.
-
- Use the Group Policy Editor to create a policy file that specifies the location of
- user profiles and/or the My Documents etc. Then save these
- settings in a file called Config.POL that needs to be placed in the
- root of the [NETLOGON] share. If Win98 is configured to log onto
- the Samba Domain, it will automatically read this file and update the Win9x/Me registry
- of the machine as it logs on.
-
- Further details are covered in the Win98 Resource Kit documentation.
-
- If you do not take the right steps, then every so often Win9x/Me will check the
- integrity of the registry and will restore it's settings from the back-up
- copy of the registry it stores on each Win9x/Me machine. Hence, you will
- occasionally notice things changing back to the original settings.
-
- Install the group policy handler for Win9x to pick up group policies. Look on the
- Win98 CD in \tools\reskit\netadmin\poledit.
- Install group policies on a Win9x client by double-clicking
- 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.
-
- 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
- Workstation but it is not suitable for creating Domain Policies.
- Further, although the Windows 95 Policy Editor can be installed on an NT4
- Workstation/Server, it will not work with NT clients. However, the files from
- the NT Server will run happily enough on an NT4 Workstation.
-
- You need poledit.exe, common.adm and winnt.adm.
- It is convenient to put the two *.adm files in the c:\winnt\inf
- directory which is where the binary will look for them unless told otherwise. Note also that that
- directory is normally 'hidden'.
-
- The Windows NT policy editor is also included with the Service Pack 3 (and
- later) for Windows NT 4.0. Extract the files using servicepackname /x,
- i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor,
- poledit.exe and the associated template files (*.adm) should
- 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.
-
- 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.
-
- 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.
-
- New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
- a superset of capabilities compared with NT4 style policies. Obviously, the tool used
- to create them is different, and the mechanism for implementing them is much changed.
-
- The older NT4 style registry based policies are known as Administrative Templates
- in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
- configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
- users' desktop (including: the location of My Documents files (directory), as
- well as intrinsics of where menu items will appear in the Start menu). An additional new
- feature is the ability to make available particular software Windows applications to particular
- users and/or groups.
-
- Remember: NT4 policy files are named NTConfig.POL and are stored in the root
- of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
- and selects the domain name to which the logon will attempt to take place. During the logon
- process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
- server, modifies the local registry values according to the settings in this file.
-
- Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
- a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
- in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
- Directory domain controllers. The part that is stored in the Active Directory itself is called the
- group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
- known as the group policy template (GPT).
-
- With NT4 clients the policy file is read and executed upon only as each user logs onto the network.
- MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
- startup (machine specific part) and when the user logs onto the network the user specific part
- is applied. In MS Windows 200x style policy management each machine and/or user may be subject
- 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.
-
- 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:
- Go to the Windows 200x / XP menu
- Select the domain or organizational unit (OU) that you wish to manage, then right click
- to open the context menu for that object, select the properties item.
-
- Now left click on the Group Policy tab, then left click on the New tab. Type a name
- for the new policy you will create.
-
- Now left click on the Edit tab to commence the steps needed to create the GPO.
-
- All policy configuration options are controlled through the use of policy administrative
- templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
- Beware however, since the .adm files are NOT interchangeable across NT4 and Windows 200x.
- The later introduces many new features as well as extended definition capabilities. It is
- well beyond the scope of this documentation to explain how to program .adm files, for that
- the administrator is referred to the Microsoft Windows Resource Kit for your particular
- version of MS Windows.
-
- 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.
-
-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.
-
-If you create a policy that will be automatically downloaded from validating domain controllers,
-you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
-policy file and, by modifying the Windows NT-based workstation, directing the computer to update
-the policy from a manual path. You can do this by either manually changing the registry or by using
-the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
-but if a change is necessary to all machines, this change must be made individually to each workstation.
-
-When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain
-controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
-applied to the user's part of the registry.
-
-MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
-acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
-itself. The key benefit of using AS GPOs is that they impose no registry spoiling effect.
-This has considerable advantage compared with the use of NTConfig.POL (NT4) style policy updates.
-
-In addition to user access controls that may be imposed or applied via system and/or group policies
-in a manner that works in conjunction with user profiles, the user management environment under
-MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
-Common restrictions that are frequently used includes:
-
- Logon Hours Password Aging Permitted Logon from certain machines only Account type (Local or Global) User Rights
-
- 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
- this tool. editreg is being built with the intent to enable NTConfig.POL
- files to be saved in text format and to permit the building of new NTConfig.POL files with
- 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.
-
- 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.
-
-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:
-
- Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
- Convention Provider (MUP) start
-
- Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
- and applied. The list may include GPOs that:
- Apply to the location of machines in a Directory Apply only when settings have changed Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.
- No desktop user interface is presented until the above have been processed.
-
- Execution of start-up scripts (hidden and synchronous by default).
-
- A keyboard action to affect start of logon (Ctrl-Alt-Del).
-
- User credentials are validated, User profile is loaded (depends on policy settings).
-
- An ordered list of User GPOs is obtained. The list contents depends on what is configured in respect of:
-
- Is user a domain member, thus subject to particular policies Loopback enablement, and the state of the loopback policy (Merge or Replace) Location of the Active Directory itself Has the list of GPOs changed. No processing is needed if not changed.
-
- User Policies are applied from Active Directory. Note: There are several types.
-
- Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
- Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
- window.
-
- 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.
-
-Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following
-collection demonstrates only basic issues.
-
- “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?”
-
-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.
- Table of Contents 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.
-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
-initgroups() reads the latter. Most system admins who know the ropes
-symlink /etc/group to /etc/logingroup
-(hard link doesn't work for reasons too stupid to go into here). initgroups() will complain if one of the
-groups you're in in /etc/logingroup has what it considers to be an invalid
-ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think)
-60000 currently on HP-UX. This precludes -2 and 65534, the usual nobody
-GIDs.
-
-If you encounter this problem, make sure that the programs that are failing
-to initgroups() be run as users not in any groups with GIDs outside the
-allowed range.
- This is documented in the HP manual pages under setgroups(2) and passwd(4).
-
-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.
-
-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.
-
-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 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.
-
-For this reason Samba by default defines the macro NO_EID in the DNIX
-section of includes.h. This works around the problem in a limited way,
-but it is far from ideal, some things still won't work right.
-
-To fix the problem properly you need to assemble the following two
-functions and then either add them to your C library or link them into
-Samba.
-
-put this in the file setegid.s:
-
-put this in the file seteuid.s:
-
-after creating the above files you then assemble them using
-
-that should produce the files seteuid.o and
-setegid.o
-
-then you need to add these to the LIBSM line in the DNIX section of
-the Samba Makefile. Your LIBSM line will then look something like this:
-
-You should then remove the line:
- from the DNIX section of includes.h
-By default RedHat Rembrandt-II during installation adds an
-entry to /etc/hosts as follows:
-
-
-This causes Samba to loop back onto the loopback interface.
-The result is that Samba fails to communicate correctly with
-the world and therefor may fail to correctly negotiate who
-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
- 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,
-then try again. The lock attempt was failing before the grant was
-occurring. So the visible manifestation of this would be a handful of
-processes stealing all of the CPU, and when they were trussed they would
-be stuck if F_SETLKW64 loops.
-
-Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
-has not been released yet.
-
-The patch revision for 2.6 is 105181-34
-for 8 is 108528-19 and for 9 is 112233-04
-
-After the install of these patches it is recommended to reconfigure
-and rebuild samba.
- Thanks to Joe Meslovich for reporting Table of Contents
-Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for
-some administrators.
-
-Roaming Profiles allow an administrator to make available a consistent user desktop
-as the user moves from one machine to another. This chapter provides much information
-regarding how to configure and manage Roaming Profiles.
-
-While Roaming Profiles might sound like nirvana to some, they are a real and tangible
-problem to others. In particular, users of mobile computing tools, where often there may not
-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 support is different for Win9x / Me and Windows NT4/200x.
-
-Before discussing how to configure roaming profiles, it is useful to see how
-Windows 9x / Me and Windows NT4/200x clients implement these features.
-
-Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
-profiles location. However, the response does not have room for a separate
-profiles location field, only the user's home share. This means that Win9X/Me
-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.
-
-This section documents how to configure Samba for MS Windows client profile support.
-
-To support Windows NT4/200x clients, in the [global] section of smb.conf set the
-following (for example):
-
-
-
- This is typically implemented like:
-
-
-where %L translates to the name of the Samba server and %u translates to the user name
-
-The default for this option is \\%N\%U\profile,
-namely \\sambaserver\username\profile.
-The \\N%\%U service is created automatically by the [homes] service. If you are using
-a samba server for the profiles, you _must_ make the share specified in the logon path
-browseable. Please refer to the man page for smb.conf in respect of the different
-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.
-
- 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.
-
-By using the logon home parameter, you are restricted to putting Win9x / Me
-profiles in the user's home directory. But wait! There is a trick you
-can use. If you set the following in the [global] section of your smb.conf file:
-
-then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
-of your home directory called .profiles (thus making them hidden).
-
-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.
-
-You can support profiles for both Win9X and WinNT clients by setting both the
-logon home and logon path parameters. For example:
-
- A question often asked is “How may I enforce use of local profiles?” or
- “How do I disable Roaming Profiles?”
-
-There are three ways of doing this:
-
- Affect the following settings and ALL clients
- will be forced to use a local profile:
-
-
- By using the Microsoft Management Console gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This of course modifies registry settings. The full path to the option is:
-
-
-
-
- From the start menu right click on the
- My Computer icon, select User Profiles
- tab, select the profile you wish to change from Roaming type to Local, click .
-
-Consult the MS Windows registry guide for your particular MS Windows version for more
-information about which registry keys to change to enforce use of only local user
-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.
-
-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
-in any of the profile folders.
-
-The user.DAT file contains all the user's preferences. If you wish to
-enforce a set of preferences, rename their user.DAT file to user.MAN,
-and deny them write access to this file.
-
- On the Windows 9x / Me machine, go to User Profiles tab. Select the required level of
- roaming preferences. Press , but do _not_ allow the computer
- to reboot.
-
- On the Windows 9x / Me machine, go to Preferences. Select Log on to
- NT Domain. Then, ensure that the Primary Logon is Client for
- Microsoft Networks. Press , and this time allow the computer
- to reboot.
-
-Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
-If you have the Primary Logon as 'Client for Novell Networks', then
-the profiles and logon script will be downloaded from your Novell
-Server. If you have the Primary Logon as 'Windows Logon', then the
-profiles will be loaded from the local machine - a bit against the
-concept of roaming profiles, it would seem!
-
-You will now find that the Microsoft Networks Login box contains
-[user, password, domain] instead of just [user, password]. Type in
-the samba server's domain name (or any other domain known to exist,
-but bear in mind that the user will be authenticated against this
-domain and profiles downloaded from it, if that domain logon server
-supports it), user name and user's password.
-
-Once the user has been successfully validated, the Windows 9x / Me machine
-will inform you that The user has not logged on before and asks you
-Do you wish to save the user's preferences?. Select
-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
-on the samba server and verify that the Desktop, Start Menu,
-Programs and Nethood folders have been created.
-
-These folders will be cached locally on the client, and updated when
-the user logs off (if you haven't made them read-only by then).
-You will find that if the user creates further folders or short-cuts,
-that the client will merge the profile contents downloaded with the
-contents of the profile directory already on the local client, taking
-the newest folders and short-cuts from each set.
-
-If you have made the folders / files read-only on the samba server,
-then you will get errors from the Windows 9x / Me machine on logon and logout, as
-it attempts to merge the local and the remote profile. Basically, if
-you have any errors reported by the Windows 9x / Me machine, check the UNIX file
-permissions and ownership rights on the profile directory contents,
-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".
-
- Before deleting the contents of the
- directory listed in the ProfilePath (this is likely to be
- c:\windows\profiles\username), ask them if they
- have any important files stored on their desktop or in their start menu.
- Delete the contents of the directory ProfilePath (making a backup if any
- of the files are needed).
-
- 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.
-
- instead of logging in under the [user, password, domain] dialog,
- press
- run the regedit.exe program, and look in:
-
- HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
-
- you will find an entry, for each user, of ProfilePath. Note the
- contents of this key (likely to be c:\windows\profiles\username),
- then delete the key ProfilePath for the required user.
- [Exit the registry editor].
- search for the user's .PWL password-caching file in the c:\windows
- directory, and delete it.
-
- log off the windows 9x / Me client.
-
- 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.
-
-If all else fails, increase samba's debug log levels to between 3 and 10,
-and / or run a packet trace program such as ethereal or netmon.exe, and
-look for error messages.
-
-If you have access to an Windows NT4/200x server, then first set up roaming profiles
-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.
-
-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.
-
-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.
-
-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
-extension. The user, while logging in, must have write permission to
-create the full profile path (and the folder with the .PDS extension
-for those situations where it might be created.)
-
-In the profile directory, Windows NT4 creates more folders than Windows 9x / Me.
-It creates Application Data and others, as well as Desktop, Nethood,
-Start Menu and Programs. The profile itself is stored in a file
-NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
-its purpose is currently unknown.
-
-You can use the System Control Panel to copy a local profile onto
-a samba server (see NT Help on profiles: it is also capable of firing
-up the correct location in the System Control Panel for you). The
-NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
-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.
-
-You must first convert the profile from a local profile to a domain
-profile on the MS Windows workstation as follows:
-
- Log on as the LOCAL workstation administrator.
-
- Right click on the My Computer Icon, select
-
- Click on the User Profiles tab
-
- Select the profile you wish to convert (click on it once)
-
- Click on the button
- In the Permitted to use box, click on the button.
-
- 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.
- You will need to log on if a logon box opens up. Eg: In the connect as: DOMAIN\root, password: mypassword.
- To make the profile capable of being used by anyone select 'Everyone'
-
- Click
- Now click on the
-Done. You now have a profile that can be edited using the samba
-profiles tool.
-
-Under NT/2K the use of mandatory profiles forces the use of MS Exchange
-storage of mail data. That keeps desktop profiles usable.
- Procedure 24.2. Windows XP Service Pack 1
-This is a security check new to Windows XP (or maybe only
-Windows XP service pack 1). It can be disabled via a group policy in
-Active Directory. The policy is: Computer Configuration\Administrative Templates\System\User
-Profiles\Do not check for user ownership of Roaming Profile Folders ...and it should be set to Enabled.
-Does the new version of samba have an Active Directory analogue? If so,
-then you may be able to set the policy through this.
-
-If you cannot set group policies in samba, then you may be able to set
-the policy locally on each machine. If you want to try this, then do
-the following (N.B. I don't know for sure that this will work in the
-same way as a domain group policy):
-
-On the XP workstation log in with an Administrator account.
- Click: Type: mmc Click: A Microsoft Management Console should appear. Click: Double-Click: Group Policy Click: Click: In the "Console Root" window: Expand: Local Computer Policy, Computer Configuration,
- Administrative Templates, System, User Profiles Double-Click: Do not check for user ownership of Roaming Profile Folders Select: Enabled Click: 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). Reboot
-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
-of MS Windows clients. Probably the more salient reason to NOT mix profiles
-is that when logging off an earlier version of MS Windows the older format
-of profile contents may overwrite information that belongs to the newer
-version resulting in loss of profile information content when that user logs
-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.
-
-If you have this set up correctly, you will find separate user.DAT and
-NTuser.DAT files in the same profile directory.
-
-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.
-
-Unfortunately, the Resource Kit information is specific to the version of MS Windows
-NT4/200x. The correct resource kit is required for each platform.
-
-Here is a quick guide:
-
-On your NT4 Domain Controller, right click on My Computer, then
-select the tab labelled User Profiles.
-
-Select a user profile you want to migrate and click on it.
- 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 In the box labelled Copy Profile to add your new path, eg:
- c:\temp\foobar Click on the button Permitted to use box. Click on the group 'Everyone' and then click Now click
-Follow the above for every profile you need to migrate.
-
-You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.
-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.
-
-You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
-Resource Kit.
-
-Windows NT 4.0 stores the local profile information in the registry under
-the following key:
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
-
-Under the ProfileList key, there will be subkeys named with the SIDs of the
-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.
-
-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
-user any ability to change the desktop environment then this must be done through
-policy settings. See previous chapter.
-
-Under NO circumstances should the profile directory (or it's contents) be made read-only
-as this may render the profile un-usable.
-
-For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
-also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
-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.
-
-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
-use of Group Profiles. A Group Profile is a profile that is created firstly using
-a template (example) user. Then using the profile migration tool (see above) the
-profile is assigned access rights for the user group that needs to be given access
-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
-the now modified profile.
-
- 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.
-
-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.
-
-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.
-
-To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
-select -> , then click on the
-Local Computer icon, click on Windows 98 System,
-select User Profiles, click on the enable box. Do not forget to save the registry changes.
-
-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.
-
-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:
-
-If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
-version of the user profile. Windows 9x / Me also checks the user's home directory (or other
-specified directory if the location has been modified) on the server for the User Profile.
-If a profile exists in both locations, the newer of the two is used. If the User Profile exists
-on the server, but does not exist on the local machine, the profile on the server is downloaded
-and used. If the User Profile only exists on the local machine, that copy is used.
-
-If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
-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.
-
-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
-three (3) directories: Administrator, All Users, Default User.
-
-The All Users directory contains menu settings that are common across all
-system users. The Default User directory contains menu entries that are
-customisable per user depending on the profile settings chosen/created.
-
-When a new user first logs onto an MS Windows NT4 machine a new profile is created from:
- All Users settings Default User settings (contains the default NTUser.DAT file)
-When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
-the following steps are followed in respect of profile handling:
-
- The users' account information which is obtained during the logon process contains
- the location of the users' desktop profile. The profile path may be local to the
- machine or it may be located on a network share. If there exists a profile at the location
- of the path from the user account, then this profile is copied to the location
- %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the
- settings in the All Users profile in the %SystemRoot%\Profiles
- location.
-
- If the user account has a profile path, but at it's location a profile does not exist,
- then a new profile is created in the %SystemRoot%\Profiles\%USERNAME%
- directory from reading the Default User profile.
-
- If the NETLOGON share on the authenticating server (logon server) contains a policy file
- (NTConfig.POL) then it's contents are applied to the NTUser.DAT
- which is applied to the HKEY_CURRENT_USER part of the registry.
-
- When the user logs out, if the profile is set to be a roaming profile it will be written
- out to the location of the profile. The NTuser.DAT file is then
- re-created from the contents of the HKEY_CURRENT_USER contents.
- Thus, should there not exist in the NETLOGON share an NTConfig.POL at the
- next logon, the effect of the previous NTConfig.POL will still be held
- in the profile. The effect of this is known as tatooing.
-
-MS Windows NT4 profiles may be Local or Roaming. A Local profile
-will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will
-also remain stored in the same way, unless the following registry key is created:
-
-
-
-In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be
-deleted on logout.
-
-Under MS Windows NT4 default locations for common resources (like My Documents
-may be redirected to a network share by modifying the following registry keys. These changes may be affected
-via use of the System Policy Editor (to do so may require that you create your owns template extension
-for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
-creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.
-
-The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows NT4 is:
-
-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
-
-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
-
-The registry key that contains the location of the default profile settings is:
-
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
-
-The default entries are:
-
- Table 24.2. Defaults of profile settings registry keys
-
- 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
- clients that CAN participate in domain logon processes allows the administrator to create
- a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
-
-When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
-C:\Documents and Settings\Default User. The administrator can modify (or change
-the contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum
-arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
-workstation.
-
-When MS Windows 200x/XP participate in a domain security context, and if the default user
-profile is not found, then the client will search for a default profile in the NETLOGON share
-of the authenticating server. ie: In MS Windows parlance:
-%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this
-to the workstation to the C:\Documents and Settings\ under the Windows
-login name of the user.
-
- This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
- should be created at the root of this share and must be called Default Profile.
-
-If a default profile does not exist in this location then MS Windows 200x/XP will use the local
-default profile.
-
-On logging out, the users' desktop profile will be stored to the location specified in the registry
-settings that pertain to the user. If no specific policies have been created, or passed to the client
-during the login process (as Samba does automatically), then the user's profile will be written to
-the local machine only under the path C:\Documents and Settings\%USERNAME%.
-
-Those wishing to modify the default behaviour can do so through three methods:
-
- Modify the registry keys on the local machine manually and place the new default profile in the
- NETLOGON share root - NOT recommended as it is maintenance intensive.
-
- Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
- in the root of the NETLOGON share along with the new default profile.
-
- Create a GPO that enforces this through Active Directory, and place the new default profile
- in the NETLOGON share.
-
-The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows 200x/XP is:
-
-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
-
-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
-
-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
-stored on a dedicated location on a network server. This means that it will NOT be necessary to
-write the Outlook PST file over the network for every login and logout.
-
-To set this to a network location you could use the following examples:
- %LOGONSERVER%\%USERNAME%\Default Folders
-This would store the folders in the user's home directory under a directory called Default Folders
-You could also use:
- \\SambaServer\FolderShare\%USERNAME%
- in which case the default folders will be stored in the server named SambaServer
-in the share called FolderShare under a directory that has the name of the MS Windows
-user as seen by the Linux/UNIX file system.
-
-Please note that once you have created a default profile share, you MUST migrate a user's profile
-(default or custom) to it.
-
-MS Windows 200x/XP profiles may be Local or Roaming.
-A roaming profile will be cached locally unless the following registry key is created:
-
-
-In which case, the local cache copy will be deleted on logout.
-
-The following are some typical errors/problems/questions that have been asked.
-
-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
-directory.
-
-If disabled globally then no-one will have roaming profile ability.
-If enabled and you want it to apply only to certain machines, then on
-those machines on which roaming profile support is NOT wanted it is then
-necessary to disable roaming profile handling in the registry of each such
-machine.
-
-With samba-3 you can have a global profile
-setting in smb.conf _AND_ you can over-ride this by per-user settings
-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)
-A user requested the following:
-“
-I do not want Roaming profiles to be implemented. I want to give users a local profile alone. ...
-Please help me I am totally lost with this error. For the past two days I tried everything, I googled
-around but found no useful pointers. Please help me.
-”
-The choices are:
-
- I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out
-
- As a user logs onto the network a centrally stored profile is copied to the workstation
- to form a local profile. This local profile will persist (remain on the workstation disk)
- unless a registry key is changed that will cause this profile to be automatically deleted
- on logout.
-
-The Roaming Profile choices are:
-
- These are typically stored in a profile share on a central (or conveniently located
- local) server.
-
- Workstations 'cache' (store) a local copy of the profile. This cached copy is used when
- the profile can not be downloaded at next logon.
- These are loaded from a central profile server
- Mandatory profiles can be created for a user as well as for any group that a user
- is a member of. Mandatory profiles can NOT be changed by ordinary users. Only the administrator
- can change or reconfigure a mandatory profile.
-
-A WinNT4/2K/XP profile can vary in size from 130KB to off the scale.
-Outlook PST files are most often part of the profile and can be many GB in
-size. On average (in a well controlled environment) roaming profile size of
-2MB is a good rule of thumb to use for planning purposes. In an
-undisciplined environment I have seen up to 2GB profiles. Users tend to
-complain when it take an hour to log onto a workstation but they harvest
-the fruits of folly (and ignorance).
-
-The point of all the above is to show that roaming profiles and good
-controls of how they can be changed as well as good discipline make up for
-a problem free site.
-
-Microsoft's answer to the PST problem is to store all email in an MS
-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.
-Question:
-“
-When the client logs onto the domain controller it searches for a profile to download,
-where do I put this default profile?
-”
-Firstly, the samba server needs to be configured as a domain controller.
-This can be done by setting in smb.conf:
-
-There must be an [netlogon] share that is world readable.
-It is a good idea to add a logon script to pre-set printer and
-drive connections. There is also a facility for automatically
-synchronizing the workstation time clock with that of the logon
-server (another good thing to do).
-
-To invoke auto-deletion of roaming profile from the local
-workstation cache (disk storage) use the Group Policy Editor
-to create a file called NTConfig.POL with the appropriate entries. This
-file needs to be located in the netlogon share root directory.
-Windows clients need to be members of the domain. Workgroup machines do NOT use network logons so
-they do not interoperate with domain profiles.
-
-For roaming profiles add to smb.conf:
-
-
- Table of Contents
-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
-of samba. It has a wizard that may help to get samba configured quickly, it has context
-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.
-
-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
-parameter settings, so when SWAT writes the smb.conf file to disk it will write only
-those parameters that are at other than the default settings. The result is that all comments
-will be lost from the smb.conf file. Additionally, the parameters will be written back in
-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.
-
-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.
-
-The nature and location of the network super-daemon varies with the operating system
-implementation. The control file (or files) can be located in the file
-/etc/inetd.conf or in the directory /etc/[x]inet.d
-or similar.
-
-The control entry for the older style file might be:
-
-A control file for the newer style xinetd could be:
-
-
-
-
-Both the above examples assume that the swat binary has been
-located in the /usr/sbin directory. In addition to the above
-SWAT will use a directory access point from which it will load it's help files
-as well as other control information. The default location for this on most Linux
-systems is in the directory /usr/share/samba/swat. The default
-location using samba defaults will be /usr/local/samba/swat.
-
-Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user
-the only permission allowed is to view certain aspects of configuration as well as
-access to the password change facility. The buttons that will be exposed to the non-root
-user are:
-So long as you log onto SWAT as the user root you should obtain
-full change and commit ability. The buttons that will be exposed includes:
- , , , ,
- , , , .
-
-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
-
-Modifications to the swat setup are as following:
-
- install OpenSSL
-
- generate certificate and private key
-
-
- remove swat-entry from [x]inetd
-
- start stunnel
-
-
-afterwords simply contact to swat by using the URL https://myhost:901, accept the certificate
-and the SSL connection is up.
-
-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".
-
-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
-also. One diagnostic tool that is NOT mentioned on this page, but that is particularly
-useful is ethereal.
-
-SWAT can be configured to run in demo mode. This is NOT recommended
-as it runs SWAT without authentication and with full administrative ability. ie: Allows
-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.
-
-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:
-
- Basic - exposes common configuration options.
-
- Advanced - exposes configuration options needed in more
- complex environments.
-
- Developer - exposes configuration options that only the brave
- will want to tamper with.
-
-To switch to other than Basic editing ability click on either the
-Advanced or the Developer button. You may also
-do this by clicking on the radio button, then click the button.
-
-After making any changes to configuration parameters make sure that you click on the
-
-SWAT has context sensitive help. To find out what each parameter is for simply click the
-
-To affect a currently configured share, simply click on the pull down button between the
-
-To create a new share, next to the button labelled
-To affect a currently configured printer, simply click on the pull down button between the
-
-To create a new printer, next to the button labelled
-The purpose if the SWAT Wizard is to help the Microsoft knowledgeable network administrator
-to configure Samba with a minimum of effort.
-
-The Wizard page provides a tool for rewriting the smb.conf file in fully optimised format.
-This will also happen if you press the commit button. The two differ in the the rewrite button
-ignores any changes that may have been made, while the Commit button causes all changes to be
-affected.
-
-The
-Finally, there are a limited set of options that will determine what type of server Samba
-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 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.
-
-The daemons may be controlled individually or as a total group. Additionally, you may set
-an automatic screen refresh timing. As MS Windows clients interact with Samba new smbd processes
-will be continually spawned. The auto-refresh facility will allow you to track the changing
-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.
-
-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 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.
-
-When logged in as a non-root account the user will have to provide the old password as well as
-the new password (twice). When logged in as root only the new password is
-required.
-
-One popular use for this tool is to change user passwords across a range of remote MS Windows
-servers.
-Action MS Windows Command UNIX Command create md folder mkdir folder delete rd folder rmdir folder rename rename oldname newname mv oldname newname
-$ ls -la
-total 632
-drwxr-xr-x 13 maryo gnomes 816 2003-05-12 22:56 .
-drwxrwxr-x 37 maryo gnomes 3800 2003-05-12 22:29 ..
-dr-xr-xr-x 2 maryo gnomes 48 2003-05-12 22:29 muchado02
-drwxrwxrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado03
-drw-rw-rw- 2 maryo gnomes 48 2003-05-12 22:29 muchado04
-d-w--w--w- 2 maryo gnomes 48 2003-05-12 22:29 muchado05
-dr--r--r-- 2 maryo gnomes 48 2003-05-12 22:29 muchado06
-drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08
----------- 1 maryo gnomes 1242 2003-05-12 22:31 mydata00.lst
---w--w--w- 1 maryo gnomes 7754 2003-05-12 22:33 mydata02.lst
--r--r--r-- 1 maryo gnomes 21017 2003-05-12 22:32 mydata04.lst
--rw-rw-rw- 1 maryo gnomes 41105 2003-05-12 22:32 mydata06.lst
-$
-
- -rwxr-x--- Means: The owner (user) can read, write, execute
- the group can read and execute
- everyone else can NOT do anything with it
-
Warning
Note
security mask = 0777 force security mode = 0 directory security mask = 0777 force directory security mode = 0 Note
-$ find 'directory_name' -type d -exec chown user.group {}\;
-$ find 'directory_name' -type d -exec chmod 6775 'directory_name'
-$ find 'directory_name' -type f -exec chmod 0775 {} \;
-$ find 'directory_name' -type f -exec chown user.group {}\;
-
Note
-$ chown jack.engr /foodbar
-
Note
-$ chown jack /foodbar
-$ chgrp engr /foodbar
-
-$ chmod 6775 /foodbar
-$ ls -al /foodbar/..
-
-drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar
-
-$ su - jill
-$ cd /foodbar
-$ touch Afile
-$ ls -al
-
--rw-r--r-- 1 jack engr 0 2003-02-04 09:57 Afile
-
force create mode = 0775 force direcrtory mode = 6775 Note
force user = jack force group = engr force create mode = 0660 force directory mode = 0770 Server Manager User Manager for Domains Event Viewer
-> I have a wonderful linux/samba server running as PDC for a network.
-> Now I would like to add remote desktop capabilities so that
-> users outside could login to the system and get their desktop up from
-> home or another country..
->
-> Is there a way to accomplish this? Do I need a windows terminal server?
-> Do I need to configure it so that it is a member of the domain or a
-> BDC,PDC? Are there any hacks for MS Windows XP to enable remote login
-> even if the computer is in a domain?
->
-> Any ideas/experience would be appreciated :)
-
No Logon Script Simple universal Logon Script that applies to all users Use of a conditional Logon Script that applies per user or per group attributes Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
- a custom Logon Script and then execute it. User of a tool such as KixStart
- #!/usr/bin/perl
- #
- # genlogon.pl
- #
- # Perl script to generate user logon scripts on the fly, when users
- # connect from a Windows client. This script should be called from smb.conf
- # with the %U, %G and %L parameters. I.e:
- #
- # root preexec = genlogon.pl %U %G %L
- #
- # The script generated will perform
- # the following:
- #
- # 1. Log the user connection to /var/log/samba/netlogon.log
- # 2. Set the PC's time to the Linux server time (which is maintained
- # daily to the National Institute of Standard's Atomic clock on the
- # internet.
- # 3. Connect the user's home drive to H: (H for Home).
- # 4. Connect common drives that everyone uses.
- # 5. Connect group-specific drives for certain user groups.
- # 6. Connect user-specific drives for certain users.
- # 7. Connect network printers.
-
- # 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";
- close LOG;
-
- # Start generating logon script
- 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")
- {
- 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")
- {
- 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")
- {
- 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
- # differently, because they are the exceptions that have desktop
- # printers on LPT1: - all other user's go to the LaserJet on the
- # server.
- 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";
- }
- else
- {
- 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.
- close LOGON;
-
http://www.craigelachie.org/rhacer/ntlogon http://www.kixtart.org http://support.microsoft.com/default.asp?scid=kb;en-us;189105
- rundll32 printui.dll,PrintUIEntry /?
-
-root# ldd `which smbd`
-libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
-[....]
-
Tip
[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 [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
- application/octet-stream
-
- application/octet-stream application/vnd.cups-raw 0 -
-
Note
Note
Note
Tip
Warning
Tip
Warning
Tip
- application/pdf pdf string(0,%PDF)
-
- application/postscript ai eps ps string(0,%!) string(0,<04>%!)
-
Note
Warning
- application/pdf application/postscript 33 pdftops
-
- application/vnd.hp-HPGL application/postscript 66 hpgltops
-
- application/octet-stream
-
- application/x-shell application/postscript 33 texttops
- text/plain application/postscript 33 texttops
-
Tip
-$ lpinfo -v
-
- *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"
-
-
- *cupsFilter: "application/vnd.cups-postscript 0 foomatic-rip"
-
-
Tip
-$ lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E
-
- Unable to convert file 0 to printable format for job
-
- application/octet-stream
-
- application/octet-stream application/vnd.cups-raw 0 -
-
Note
- *cupsFilter: application/vnd.cups-raster 66 rastertoprinter
-
PPD file Printer type deskjet.ppd older HP inkjet printers and compatible deskjet2.ppd newer HP inkjet printers and compatible dymo.ppd label printers epson9.ppd Epson 24pin impact printers and compatible epson24.ppd Epson 24pin impact printers and compatible okidata9.ppd Okidata 9pin impact printers and compatible okidat24.ppd Okidata 24pin impact printers and compatible stcolor.ppd older Epson Stylus Color printers stcolor2.ppd newer Epson Stylus Color printers stphoto.ppd older Epson Stylus Photo printers stphoto2.ppd newer Epson Stylus Photo printers laserjet.ppd all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS. Note
-root# lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
- -i /path/to/interface-script
-
[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
-root# tar xvzf cups-samba-1.1.19.tar.gz
-cups-samba.install
-cups-samba.license
-cups-samba.readme
-cups-samba.remove
-cups-samba.ss
-
-root# tar tv cups-samba.ss
-cupsdrvr.dll
-cupsui.dll
-cups.hlp
-
-root# ./cups-samba.install
-[....]
-Installing software...
-Updating file permissions...
-Running post-install commands...
-Installation is complete.
-
Warning
-root# cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-
Note
Tip
Note
-root# cupsaddsmb -U root infotec_IS2027
-Password for root required to access localhost via Samba: ['secret']
-
Warning
-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' \
- -c 'mkdir W32X86; \
- put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
- put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
- put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
- put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
-added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
-NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
-putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
-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"
-Printer Driver infotec_2105 successfully installed.
-
-Running command: smbclient //localhost/print\$ -N -U'root%secret' \
--c 'mkdir WIN40; \
- put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
- put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM; \
- put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
- put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
- put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
- put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
- put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
- added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
- putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
- putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
- putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
- putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
- putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
- putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
- 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: \
- 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: \
- ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP, \
- PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
- Printer Driver infotec_2105 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret' \
- -c 'setdriver infotec_2105 infotec_2105'
- cmd = setdriver infotec_2105 infotec_2105
- Successfully set infotec_2105 to driver infotec_2105.
-
-
-root# cupsaddsmb -H sambaserver -h cupsserver -v printername
-
Note
-root# cupsaddsmb -U MIDEARTH\\root -v printername
-root# cupsaddsmb -H SAURON -U MIDEARTH\\root -v printername
-root# cupsaddsmb -H SAURON -U MIDEARTH\\root -h cups-server -v printername
-
Note
-C:\> net use lpt1: \\sambaserver\printershare /user:ntadmin
-
-Long Printer Name:\
-Driver File Name:\
-Data File Name:\
-Config File Name:\
-Help File Name:\
-Language Monitor Name:\
-Default Data Type:\
-Comma Separated list of Files
-
- adddriver "Architecture" \
- "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
- LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-
-root# rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
-
-root# rpcclient -U'Danka%xxxx' W2KSERVER \
- -c'getdriver "DANKA InfoStream Virtual Printer" 3'
- cmd = getdriver "DANKA InfoStream Virtual Printer" 3
-
- [Windows NT x86]
- Printer Driver Info 3:
- Version: [2]
- Driver Name: [DANKA InfoStream]
- Architecture: [Windows NT x86]
- Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.DLL]
- Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\INFOSTRM.PPD]
- Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRPTUI.DLL]
- Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.HLP]
-
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
-
- Monitorname: []
- Defaultdatatype: []
-
-
-root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P canonIR85.ppd
-
-root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
-flags:[0x800000]
-name:[\\kde-bitshop\mysmbtstprn]
-description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
-comment:[mysmbtstprn]
-
-root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep driver
-drivername:[]
-
-root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep -C4 driv
-servername:[\\kde-bitshop]
-printername:[\\kde-bitshop\mysmbtstprn]
-sharename:[mysmbtstprn]
-portname:[Samba Printer Port]
-drivername:[]
-comment:[mysmbtstprn]
-location:[]
-sepfile:[]
-printprocessor:[winprint]
-
-root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
- result was WERR_UNKNOWN_PRINTER_DRIVER
-
-
-root# smbclient //localhost/print\$ -U 'root%xxxx' \
- -c 'cd W32X86; \
- put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \
- put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
- put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
- put /usr/share/cups/drivers/cups.hlp cups.hlp'
-
-root# ls -l /etc/samba/drivers/W32X86/
-total 669
-drwxr-sr-x 2 root ntadmin 532 May 25 23:08 2
-drwxr-sr-x 2 root ntadmin 670 May 16 03:15 3
--rwxr--r-- 1 root ntadmin 14234 May 25 23:21 cups.hlp
--rwxr--r-- 1 root ntadmin 278380 May 25 23:21 cupsdrvr.dll
--rwxr--r-- 1 root ntadmin 215848 May 25 23:21 cupsui.dll
--rwxr--r-- 1 root ntadmin 169458 May 25 23:21 mysmbtstprn.PPD
-
-root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
- cupsdrvr.dll:mysmbtstprn.PPD: \
- cupsui.dll:cups.hlp:NULL:RAW:NULL" \
- localhost
-Printer Driver mydrivername successfully installed.
-
-root# ls -l /etc/samba/drivers/W32X86/
-total 1
-drwxr-sr-x 2 root ntadmin 532 May 25 23:22 2
-drwxr-sr-x 2 root ntadmin 670 May 16 03:15 3
-
-root# ls -l /etc/samba/drivers/W32X86/2
-total 5039
-[....]
--rwxr--r-- 1 root ntadmin 14234 May 25 23:21 cups.hlp
--rwxr--r-- 1 root ntadmin 278380 May 13 13:53 cupsdrvr.dll
--rwxr--r-- 1 root ntadmin 215848 May 13 13:53 cupsui.dll
--rwxr--r-- 1 root ntadmin 169458 May 25 23:21 mysmbtstprn.PPD
-
-root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
- | grep -B2 -A5 mydrivername
-Printer Driver Info 3:
-Version: [2]
-Driver Name: [mydrivername]
-Architecture: [Windows NT x86]
-Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-
-root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
-Successfully set mysmbtstprn to driver mydrivername
-
-root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep driver
-drivername:[mydrivername]
-
-root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep -C4 driv
-servername:[\\kde-bitshop]
-printername:[\\kde-bitshop\mysmbtstprn]
-sharename:[mysmbtstprn]
-portname:[Done]
-drivername:[mydrivername]
-comment:[mysmbtstprn]
-location:[]
-sepfile:[]
-printprocessor:[winprint]
-
-root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
-[Windows NT x86]
-Printer Driver Info 3:
- Version: [2]
- Driver Name: [mydrivername]
- Architecture: [Windows NT x86]
- Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
- Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
- Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
- Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
- Monitorname: []
- Defaultdatatype: [RAW]
- Monitorname: []
- Defaultdatatype: [RAW]
-
-root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
- name:[\\kde-bitshop\mysmbtstprn]
- description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
- comment:[mysmbtstprn]
-
-
-C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
- \\sambacupsserver\mysmbtstprn"
-
-C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
-
-C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
-
-root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
-
-
- Printer Driver ABC successfully installed.
-
-
-
- result was NT_STATUS_UNSUCCESSFUL
-
-
-root# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep ir85wm
- printername:[ir85wm]
-
-root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm'
- cmd = getprinter ir85wm
- flags:[0x800000]
- name:[\\transmeta\ir85wm]
- description:[\\transmeta\ir85wm,ir85wm,DPD]
- comment:[CUPS PostScript-Treiber for WinNT/2K/XP]
-
-root# tdbbackup
- Usage: tdbbackup [options] <fname...>
-
- Version:3.0a
- -h this help message
- -s suffix set the backup suffix
- -v verify mode (restore if corrupt)
-
-
-root# ls
-. browse.dat locking.tdb ntdrivers.tdb printing.tdb
-.. share_info.tdb connections.tdb messages.tdb ntforms.tdb
-printing.tdbkp unexpected.tdb brlock.tdb gmon.out namelist.debug
-ntprinters.tdb sessionid.tdb
-
-root# tdbbackup -s .bak printing.tdb
- printing.tdb : 135 records
-
-root# ls -l printing.tdb*
- -rw------- 1 root root 40960 May 2 03:44 printing.tdb
- -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak
-
-
-root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
-
Note
Note
-root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-
-root# lpadmin -p quotaprinter -o job-quota-period=604800 \
- -o job-k-limit=1024 -o job-page-limit=100
-
-infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
-infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
-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
-
- *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"
-
- application/postscript application/vnd.cups-raw 0 -
- application/vnd.cups-postscript application/vnd.cups-raw 0 -
-
- */* application/vnd.cups-raw 0 -
-
-application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
-
-$ grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
-
-root# ls -l /usr/lib/cups/backend/
-total 253
-drwxr-xr-x 3 root root 720 Apr 30 19:04 .
-drwxr-xr-x 6 root root 125 Dec 19 17:13 ..
--rwxr-xr-x 1 root root 10692 Feb 16 21:29 canon
--rwxr-xr-x 1 root root 10692 Feb 16 21:29 epson
-lrwxrwxrwx 1 root root 3 Apr 17 22:50 http -> ipp
--rwxr-xr-x 1 root root 17316 Apr 17 22:50 ipp
--rwxr-xr-x 1 root root 15420 Apr 20 17:01 lpd
--rwxr-xr-x 1 root root 8656 Apr 20 17:01 parallel
--rwxr-xr-x 1 root root 2162 Mar 31 23:15 pdfdistiller
-lrwxrwxrwx 1 root root 25 Apr 30 19:04 ptal -> /usr/sbin/ptal-cups
--rwxr-xr-x 1 root root 6284 Apr 20 17:01 scsi
-lrwxrwxrwx 1 root root 17 Apr 2 03:11 smb -> /usr/bin/smbspool
--rwxr-xr-x 1 root root 7912 Apr 20 17:01 socket
--rwxr-xr-x 1 root root 9012 Apr 20 17:01 usb
-
-root# ls -l `which smbspool`
--rwxr-xr-x 1 root root 563245 Dec 28 14:49 /usr/bin/smbspool
-
-root# ln -s `which smbspool` /usr/lib/cups/backend/smb
-
-root# lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \
- -P /path/to/PPD
-
Note
-root# smbpasswd -a -i rumba
-New SMB password: XXXXXXXX
-Retype SMB password: XXXXXXXX
-Added user rumba$
-
Note
-#!/bin/bash
-#### 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
-
-# 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
-
Number of Users Description < 50 50 - 250 > 250 Simple Upgraded Redesign Note
domain master = yes [global] domain master = yes local master = yes preferred master = yes os level = 65 [global] domain master = no local master = yes preferred master = yes os level = 65 [global] domain master = no local master = no preferred master = no os level = 0 [global] domain master = no local master = yes preferred master = yes os level = 65 [global] domain master = no local master = no preferred master = no os level = 0 remote announce = a.b.c.d [e.f.g.h] ... remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... remote browse sync = a.b.c.d Important
wins support = yes wins server = <name or IP address>
-"NAME#TYPE" TTL ADDRESS+ FLAGS
-
-"MADMAN#03" 1055298378 192.168.1.2 66R
-
-"MADMAN#03" 0 192.168.1.2 66R
-
Warning
name resolve order = wins lmhosts bcast host name resolve order = wins lmhosts (eliminates bcast and host) name resolve order = host lmhost wins bcast Note
Subnet Browse Master List Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E Subnet2 N2_B N2_A, N2_B, N2_C, N2_D Subnet3 N3_D N3_A, N3_B, N3_C, N3_D Subnet Browse Master List Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
-N2_A(*), N2_B(*), N2_C(*), N2_D(*) Subnet2 N2_B N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*) Subnet3 N3_D N3_A, N3_B, N3_C, N3_D Subnet Browse Master List Subnet1 N1_C N1_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(*) Subnet2 N2_B N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*) Subnet3 N3_D N3_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(*) Subnet Browse Master List Subnet1 N1_C N1_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(*) Subnet2 N2_B N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*),
-N3_C(*), N3_D(*) Subnet3 N3_D N3_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(*)
- 20=setup.exe
- 20=netwksta.sys
- 20=netvdd.sys
-
Kernel Update: KRNLUPD.EXE Ping Fix: PINGUPD.EXE RPC Update: RPCRTUPD.EXE TCP/IP Update: VIPUPD.EXE Redirector Update: VRDRUPD.EXE [profile] path = /export/profile create mask = 0600 directory mask = 0700 nt acl support = no read only = no Note
Note
- .globl _setegid
-_setegid:
- moveq #47,d0
- movl #100,a0
- moveq #1,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-
- .globl _seteuid
-_seteuid:
- moveq #47,d0
- movl #100,a0
- moveq #0,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-
-$ as seteuid.s
-$ as setegid.s
-
-LIBSM = setegid.o seteuid.o -ln
-
-#define NO_EID
-
- 127.0.0.1 loopback "hostname"."domainname"
-
Warning
logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath logon path = \\%L\Profiles\%u Note
logon home = \\%L\%U\.profiles logon home = \\%L\%u\.profiles logon path = \\%L\profiles\%u logon home logon path
- Local Computer Policy\
- Computer Configuration\
- Administrative Templates\
- System\
- User Profiles\
-
- Disable: Only Allow Local User Profiles
- Disable: Prevent Roaming Profile Change from Propagating to the Server
-
Note
Warning
Note
Note
Note
Note
Note
-HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
-winlogon\"DeleteRoamingCache"=dword:00000001
-
Name Default 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 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 Note
Note
Name Default 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
-HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
- winlogon\"DeleteRoamingCache"=dword:00000001
security = user os level = 32 (or more) domain logons = Yes Note
logon path = \\%N\profiles\%U # Default logon drive is Z: logon drive = H: # This requires a PROFILES share that is world writable. Note
- # swat is the Samba Web Administration Tool
- swat stream tcp nowait.400 root /usr/sbin/swat swat
-
- # default: off
- # description: SWAT is the Samba Web Admin Tool. Use swat \
- # to configure your Samba server. To use SWAT, \
- # connect to port 901 with your favorite web browser.
- service swat
- {
- port = 901
- socket_type = stream
- wait = no
- only_from = localhost
- user = root
- server = /usr/sbin/swat
- log_on_failure += USERID
- disable = yes
- }
-
-root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
- /usr/share/doc/packages/stunnel/stunnel.cnf \
- -out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
-
-root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
- -l /usr/local/samba/bin/swat swat
-
Warning
Note
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 -
Table of Contents
Table of Contents
Definition of NetBIOS Protocol and Name Resolution Modes
Luke Leighton
Dan Shearer
Chris Hertel
Steve French
Simo Sorce
Andrew Bartlett
Tim Potter
Martin Pool
David Chappell <David.Chappell@mail.trincoll.edu>
Chris Hertel
Andrew Tridgell
Andrew Tridgell
Finding useful information on windows
Jelmer R. Vernooij <jelmer@samba.org>
Andrew Tridgell <tridge@samba.org>
Luke Leighton <lkcl@switchboard.net>
Paul Ashton <paul@argo.demon.co.uk>
Duncan Stansfield <duncans@sco.com>
Gerald Carter
Gerald Carter
Andrew Bartlett
LanMan and NT Password Encryption
Jeremy Allison <samba@samba.org>
Jelmer Vernooij <jelmer@samba.org>
Anthony Liguori <aliguor@us.ibm.com>
Jelmer Vernooij <jelmer@samba.org>
Alexander Bokovoy <ab@samba.org>
Stefan Metzmacher <metze@metzemix.de>
Jelmer Vernooij
Jelmer R. Vernooij <jelmer@samba.org>
Table of Contents
+
Luke Leighton
Dan Shearer
Chris Hertel
Steve French
Simo Sorce
Andrew Bartlett
Tim Potter
Martin Pool
David Chappell <
Chris Hertel
Andrew Tridgell
Andrew Tridgell
Jelmer R. Vernooij <
Andrew Tridgell <
Luke Leighton <
Paul Ashton <
Duncan Stansfield <
Gerald Carter
Gerald Carter
Andrew Bartlett
Jeremy Allison <
Jelmer Vernooij <
Anthony Liguori <
Jelmer Vernooij <
Alexander Bokovoy <
Stefan Metzmacher <
Jelmer Vernooij
Jelmer R. Vernooij <
Table of Contents
NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX. Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS Session Service NetBIOS Datagram Service, and NetBIOS Names, see @@ -75,7 +75,7 @@ NetBIOS names are either UNIQUE or GROUP. Only one application can claim a UNIQUE NetBIOS name on a network.
There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point. -
Clients can claim names, and therefore offer services on successfully claimed names, on their broadcast-isolated subnet. One way to get NetBIOS services (such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and @@ -87,7 +87,7 @@ find that some of your hosts spend 95 percent of their time dealing with broadcast traffic. [If you have IPX/SPX on your LAN or WAN, you will find that this is already happening: a packet analyzer will show, roughly every twelve minutes, great swathes of broadcast traffic!]. -
rfc1001.txt describes, amongst other things, the implementation and use of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' which is fully rfc1001/2 compliant, but has had to take specific action @@ -128,7 +128,7 @@ WINS Clients therefore claim names from the WINS server. If the WINS server allows them to register a name, the client's NetBIOS session service can then offer services on this name. Other WINS clients will then contact the WINS server to resolve a NetBIOS name. -
This document gives a general overview of how Samba works internally. The Samba Team has tried to come up with a model which is the best possible compromise between elegance, portability, security @@ -139,7 +139,7 @@ It also tries to answer some of the frequently asked questions such as:
Is Samba secure when running on Unix? The xyz platform? What about the root priveliges issue? -
Pros and cons of multithreading in various parts of Samba
Why not have a separate process for name resolution, WINS, and browsing?
People sometimes tout threads as a uniformly good thing. They are very nice in their place but are quite inappropriate for smbd. nmbd is another matter, and multi-threading it would be very nice. @@ -156,7 +156,7 @@ smbd multi-threaded. Multi-threading would actually make Samba much slower, less scalable, less portable and much less robust. The fact that we use a separate process for each connection is one of Samba's biggest advantages. -
A few problems that would arise from a threaded smbd are:
It's not only to create threads instead of processes, but you @@ -181,7 +181,7 @@ A few problems that would arise from a threaded smbd are:
we couldn't use the system locking calls as the locking context of fcntl() is a process, not a thread. -
This would be ideal, but gets sunk by portability requirements.
Andrew tried to write a test threads library for nmbd that used only @@ -208,7 +208,7 @@ packet that arrives. Having a pool of processes is possible but is nasty to program cleanly due to the enormous amount of shared data (in complex structures) between the processes. We can't rely on each platform having a shared memory system. -
Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really confusing debugging sessions. Luke Leighton rewrote it to use a @@ -229,7 +229,7 @@ keeps the idea of a distinct packet. See "struct packet_struct" in nameserv.h. It has all the detail but none of the on-the-wire mess. This makes it ideal for using in disk or memory-based databases for browsing and WINS support. -
Table of Contents
Table of Contents
The syntax of a debugging log file is represented as:
>debugfile< :== { >debugmsg< } @@ -282,7 +282,7 @@ by a newline. Note that in the above example the function names are not listed on the header line. That's because the example above was generated on an SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro. -
Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters. The first is the message level, the second is the body of a function call to the Debug1() function. @@ -333,7 +333,7 @@ would look like this: [1998/07/30 16:00:51, 0] file.c:function(261) .
Which isn't much use. The format buffer kludge fixes this problem. -
In addition to the kludgey solution to the broken line problem described above, there is a clean solution. The DEBUGADD() macro never generates a header. It will append new text to the current debug @@ -347,7 +347,7 @@ DEBUGADD() macro is the same as that of the DEBUG() macro. This is the first line. This is the second line. This is the third line. -
One of the problems with the DEBUG() macro was that DEBUG() lines tended to get a bit long. Consider this example from nmbd_sendannounce.c: @@ -382,7 +382,7 @@ within the DEBUGLVL() block.
Processing that is only relevant to debug output can be contained within the DEBUGLVL() block. -
This function prints debug message text to the debug file (and possibly to syslog) via the format buffer. The function uses a variable argument list just like printf() or Debug1(). The @@ -391,7 +391,7 @@ and then passed to format_debug_text(). If you use DEBUGLVL() you will probably print the body of the message using dbgtext(). -
This is the function that writes a debug message header. Headers are not processed via the format buffer. Also note that if the format buffer is not empty, a call to dbghdr() will not @@ -399,7 +399,7 @@ produce any output. See the comments in dbghdr() for more info.
It is not likely that this function will be called directly. It is used by DEBUG() and DEBUGADD(). -
This is a static function in debug.c. It stores the output text for the body of the message in a buffer until it encounters a newline. When the newline character is found, the buffer is @@ -429,9 +429,9 @@ have observed that eight character tabs seem to be preferred in Samba source. If you are interested in the topic of coding style, two oft-quoted documents are:
-http://lxr.linux.no/source/Documentation/CodingStyle
+
-http://www.fsf.org/prep/standards_toc.html
+
But note that coding style in Samba varies due to the many different programmers who have contributed. @@ -550,7 +550,7 @@ The suggestions above are simply that, suggestions, but the information may help in reducing the routine rework done on new code. The preceeding list is expected to change routinely as new support routines and macros are added. -
Table of Contents
Table of Contents
This section describes character set handling in Samba, as implemented in Samba 3.0 and above
@@ -560,7 +560,7 @@ strings to/from DOS codepages. The problem is that there was no way of telling if a particular char* is in dos codepage or unix codepage. This led to a nightmare of code that tried to cope with particular cases without handlingt the general case. -
The new system works like this:
all char* strings inside Samba are "unix" strings. These are @@ -622,28 +622,28 @@ The new system works like this: parameters is gone.
all vfs functions take unix strings. Don't convert when passing to them -
This section describes the macros defined in byteorder.h. These macros are used extensively in the Samba code. -
+
returns the value of the unsigned short (16 bit) little-endian integer at offset pos within buffer buf. An integer of this type is sometimes refered to as "USHORT". -
returns the value of the unsigned 32 bit little-endian integer at offset -pos within buffer buf.
returns the value of the signed short (16 bit) little-endian integer at -offset pos within buffer buf.
returns the value of the signed 32 bit little-endian integer at offset pos -within buffer buf.
sets the unsigned short (16 bit) little-endian integer at offset pos within -buffer buf to value val.
sets the unsigned 32 bit little-endian integer at offset pos within buffer -buf to the value val.
sets the short (16 bit) signed little-endian integer at offset pos within -buffer buf to the value val.
sets the signed 32 bit little-endian integer at offset pos withing buffer -buf to the value val.
returns the value of the unsigned short (16 bit) big-endian integer at -offset pos within buffer buf.
returns the value of the unsigned 32 bit big-endian integer at offset -pos within buffer buf.
returns the value of the unsigned 32 bit little-endian integer at offset +pos within buffer buf.
returns the value of the signed short (16 bit) little-endian integer at +offset pos within buffer buf.
returns the value of the signed 32 bit little-endian integer at offset pos +within buffer buf.
sets the unsigned short (16 bit) little-endian integer at offset pos within +buffer buf to value val.
sets the unsigned 32 bit little-endian integer at offset pos within buffer +buf to the value val.
sets the short (16 bit) signed little-endian integer at offset pos within +buffer buf to the value val.
sets the signed 32 bit little-endian integer at offset pos withing buffer +buf to the value val.
returns the value of the unsigned short (16 bit) big-endian integer at +offset pos within buffer buf.
returns the value of the unsigned 32 bit big-endian integer at offset +pos within buffer buf.
sets the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf to value val. -refered to as "USHORT".
This section describes the functions need to make a LAN Manager RPC call. This information had been obtained by examining the Samba code and the LAN Manager 2.0 API documentation. It should not be considered entirely @@ -656,7 +656,7 @@ call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,
This function is defined in client.c. It uses an SMB transaction to call a remote api. -
The parameters are as follows:
+
The parameters are as follows:
prcnt: the number of bytes of parameters begin sent.
drcnt: the number of bytes of data begin sent. @@ -701,7 +701,7 @@ substructures apply, this string is of zero length.
The code in client.c always calls call_api() with no data. It is unclear when a non-zero length data buffer would be sent. -
The returned parameters (pointed to by rparam), in their order of appearance are:
An unsigned 16 bit integer which contains the API function's return code. @@ -732,7 +732,7 @@ fix_char_ptr() in client.c can be used for this purpose. The third parameter (which may be read as "SVAL(rparam,4)") has something to do with indicating the amount of data returned or possibly the amount of data which can be returned if enough buffer space is allowed. -
Table of Contents
Table of Contents
Basically, the file is processed on a line by line basis. There are four types of lines that are recognized by the lexical analyzer (params.c): @@ -782,7 +782,7 @@ ignores them. The latter two line types are scanned for These are the only tokens passed to the parameter loader (loadparm.c). Parameter names and values are divided from one another by an equal sign: '='. -
+
Whitespace is defined as all characters recognized by the isspace() function (see ctype(3C)) except for the newline character ('\n') The newline is excluded because it identifies the end of the line. @@ -797,7 +797,7 @@ the exception of carriage return characters ('\r'), all of which are removed.
Leading and trailing whitespace is removed from names and values. -
Long section header and parameter lines may be extended across multiple lines by use of the backslash character ('\\'). Line continuation is ignored for blank and comment lines. @@ -820,7 +820,7 @@ line, plus the four preceeding the word 'with' in the second line. Line continuation characters are ignored on blank lines and at the end of comments. They are *only* recognized within section and parameter lines. -
The syntax of the smb.conf file is as follows:
<file> :== { <section> } EOF <section> :== <section header> { <parameter line> } <section header> :== '[' NAME ']' @@ -863,12 +863,12 @@ terminating character, and the rest of the line is ignored. The lines A parameter line is divided into a NAME and a VALUE. The *first* equal sign on the line separates the NAME from the VALUE. The VALUE is terminated by a newline character (NL = '\n'). -
Table of Contents
Table of Contents
This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with them. They may help people who are looking at unix<->PC @@ -876,7 +876,7 @@ interoperability.
It was written to help out a person who was writing a paper on unix to PC connectivity. -
The SMB protocol has only a loose username concept. Early SMB protocols (such as CORE and COREPLUS) have no username concept at all. Even in later protocols clients often attempt operations @@ -913,7 +913,7 @@ in the vast majority of cases. The methods include username maps, the service%user syntax, the saving of session setup usernames for later validation and the derivation of the username from the service name (either directly or via the user= option). -
The commonly used SMB protocols have no way of saying "you can't do that because you don't own the file". They have, in fact, no concept of file ownership at all. @@ -931,7 +931,7 @@ file time comparisons right. There are several possible solutions to this problem, including username mapping, and forcing a specific username for particular shares. -
Many SMB clients uppercase passwords before sending them. I have no idea why they do this. Interestingly WfWg uppercases the password only if the server is running a protocol greater than COREPLUS, so @@ -953,7 +953,7 @@ This means that it is *VERY* important to ensure that the Samba smbpasswd file containing these password hashes is only readable by the root user. See the documentation ENCRYPTION.txt for more details. -
Since samba 2.2, samba supports other types of locking as well. This section is outdated.
@@ -984,7 +984,7 @@ asking the server to notify it if anyone else tries to do something on the same file, at which time the client will say if it is willing to give up its lock. Unix has no simple way of implementing opportunistic locking, and currently Samba has no support for it. -
When a SMB client opens a file it asks for a particular "deny mode" to be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE, DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be @@ -998,7 +998,7 @@ directory or a shared memory implementation. The lock file method is clumsy and consumes processing and file resources, the shared memory implementation is vastly prefered and is turned on by default for those systems that support it. -
A SMB session can run with several uids on the one socket. This happens when a user connects to two shares with different usernames. To cope with this the unix server needs to switch uids @@ -1008,7 +1008,7 @@ a single uid.
Note that you can also get the "trapdoor uid" message for other reasons. Please see the FAQ for details. -
There is a convention that clients on sockets use high "unprivilaged" port numbers (>1000) and connect to servers on low "privilaged" port numbers. This is enforced in Unix as non-root users can't open a @@ -1031,7 +1031,7 @@ to any of these OSes unless they are running as root. The answer comes back, but it goes to port 137 which the unix user can't listen on. Interestingly WinNT3.1 got this right - it sends node status responses back to the source port in the request. -
There are many "protocol levels" in the SMB protocol. It seems that each time new functionality was added to a Microsoft operating system, they added the equivalent functions in a new protocol level of the SMB @@ -1145,9 +1145,9 @@ causes printing to fail with Samba: The process is trying to first open /dev/null read-write then read-only. Both fail. This means /dev/null has incorrect permissions. -
Table of Contents
Table of Contents
Table of Contents
Table of Contents
This document contains information to provide an NT workstation with login
-services, without the need for an NT server. It is the sgml version of http://mailhost.cb1.com/~lkcl/cifsntdomain.txt, controlled by Luke.
+services, without the need for an NT server. It is the sgml version of
It should be possible to select a domain instead of a workgroup (in the NT workstation's TCP/IP settings) and after the obligatory reboot, type in a @@ -1169,10 +1169,10 @@ This document is available from comp.protocols.smb; from the ntsecurity.net digest and from the samba digest, amongst other sources.
A copy is available from: -
http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935
http://mailhost.cb1.com/~lkcl/crypt.html
-A c-code implementation, provided by Linus Nordberg +
+A c-code implementation, provided by
http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html
http://mailhost.cb1.com/~lkcl/crypt.txt
+
Also used to provide debugging information is the Check Build version of NT workstation, and enabling full debugging in NETLOGON. This is achieved by setting the following REG_SZ registry key to 0x1ffffff: @@ -1191,7 +1191,7 @@ Failure to return this error code will make the workstation report that it is already a member of the domain.
the cryptographic side of the NetrServerPasswordSet command, which would allow the workstation to change its password. This password is used to generate the long-term session key. [It is possible to reject this -command, and keep the default workstation password].
cket Traces from Netmonitor (Service Pack 1 and above) |
ul Ashton and Luke Leighton's other "NT Domain" doc. |
FS documentation - cifs6.txt |
FS documentation - cifsrap2.txt |
Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based. |
Duncan Stansfield: low-level analysis of MSRPC Pipes. |
Linus Nordberg: producing c-code from Paul's crypto spec. |
Windows Sourcer development team |
+command, and keep the default workstation password].
cket Traces from Netmonitor (Service Pack 1 and above) |
ul Ashton and Luke Leighton's other "NT Domain" doc. |
FS documentation - cifs6.txt |
FS documentation - cifsrap2.txt |
Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based. |
Duncan Stansfield: low-level analysis of MSRPC Pipes. |
Linus Nordberg: producing c-code from Paul's crypto spec. |
Windows Sourcer development team |
In the SMB Transact pipes, some "Structures", described here, appear to be 4-byte aligned with the SMB header, at their start. Exactly which "Structures" need aligning is not precisely known or documented. @@ -1219,15 +1219,15 @@ into or taken out of the SMB data stream. if the count is non-zero, then the pointer is also non-zero. immediately following the pointer is the count again, followed by an array of container sub-structures. the count appears a third time after the last sub-structure. -
command number in the msrpc packet header
0x00
0x02
0x0B
0x0C
UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).
num of sub-authorities in domain SID
SID revision number
num of sub-authorities in domain SID
6 bytes for domain SID - Identifier Authority.
domain SID sub-authorities
Note: the domain SID is documented elsewhere. -
length of unicode string
max length of unicode string
4 - undocumented.
unicode string header
undocumented buffer pointer
length of unicode string
null-terminated string of unicode characters.
padding to get unicode string 4-byte aligned with the start of the SMB header.
max length of unicode string
0 - undocumented
length of unicode string
string of uncode characters
0x18 - length (in bytes) including the length field.
0 - root directory (pointer)
0 - object name (pointer)
0 - attributes (undocumented)
0 - security descriptior (pointer)
0 - security quality of service
5 - SID type
0 - undocumented
domain SID unicode string header
domain SID unicode string
Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.
Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.
5 - well-known SID. 1 - user SID (see ShowACLs)
5 - undocumented
domain RID
0 - domain index out of above reference domains
Note: logon server name starts with two '\' characters and is upper case.
Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.
undocumented buffer pointer
logon server unicode string
account name unicode string
sec_chan - security channel type
logon client machine unicode string
Note: logon server name starts with two '\' characters and is upper case.
undocumented buffer pointer
logon server unicode string
undocumented buffer pointer
logon client machine unicode string
Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to - maintain an authenticated request/response trail.
client and server names
???? padding, for 4-byte alignment with SMB header.
pointer to client credentials.
client-calculated credentials + client time
Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.
logon account info
client-calculated credentials + client time
ptr_id_info_1
domain name unicode header
param control
logon ID
user name unicode header
workgroup name unicode header
arc4 LM OWF Password
arc4 NT OWF Password
domain name unicode string
user name unicode string
workstation name unicode string
Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.
client identification/authentication info
pointer to return credentials.
return credentials - ignored.
logon level
switch value
+
command number in the msrpc packet header
0x00
0x02
0x0B
0x0C
UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).
num of sub-authorities in domain SID
SID revision number
num of sub-authorities in domain SID
6 bytes for domain SID - Identifier Authority.
domain SID sub-authorities
Note: the domain SID is documented elsewhere. +
length of unicode string
max length of unicode string
4 - undocumented.
unicode string header
undocumented buffer pointer
length of unicode string
null-terminated string of unicode characters.
padding to get unicode string 4-byte aligned with the start of the SMB header.
max length of unicode string
0 - undocumented
length of unicode string
string of uncode characters
0x18 - length (in bytes) including the length field.
0 - root directory (pointer)
0 - object name (pointer)
0 - attributes (undocumented)
0 - security descriptior (pointer)
0 - security quality of service
5 - SID type
0 - undocumented
domain SID unicode string header
domain SID unicode string
Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.
Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.
5 - well-known SID. 1 - user SID (see ShowACLs)
5 - undocumented
domain RID
0 - domain index out of above reference domains
Note: logon server name starts with two '\' characters and is upper case.
Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.
undocumented buffer pointer
logon server unicode string
account name unicode string
sec_chan - security channel type
logon client machine unicode string
Note: logon server name starts with two '\' characters and is upper case.
undocumented buffer pointer
logon server unicode string
undocumented buffer pointer
logon client machine unicode string
Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to + maintain an authenticated request/response trail.
client and server names
???? padding, for 4-byte alignment with SMB header.
pointer to client credentials.
client-calculated credentials + client time
Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.
logon account info
client-calculated credentials + client time
ptr_id_info_1
domain name unicode header
param control
logon ID
user name unicode header
workgroup name unicode header
arc4 LM OWF Password
arc4 NT OWF Password
domain name unicode string
user name unicode string
workstation name unicode string
Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.
client identification/authentication info
pointer to return credentials.
return credentials - ignored.
logon level
switch value
switch (switch_value) case 1: { ID_INFO_1 id_info_1; } -
undocumented buffer pointer.
num referenced domains?
undocumented domain name buffer pointer.
32 - max number of entries
4 - num referenced domains?
domain name unicode string header
referenced domain unicode string headers
domain name unicode string
referenced domain SIDs
??? padding to get 4-byte alignment with start of SMB header
domain name string length * 2
domain name string length * 2
undocumented domain name string buffer pointer
undocumented domain SID string buffer pointer
domain name (unicode string)
domain SID
Note: it would be nice to know what the 16 byte user session key is for.
logon time
logoff time
kickoff time
password last set time
password can change time
password must change time
username unicode string header
user's full name unicode string header
logon script unicode string header
profile path unicode string header
home directory unicode string header
home directory drive unicode string header
logon count
bad password count
User ID
Group ID
num groups
undocumented buffer pointer to groups.
user flags
user session key
logon server unicode string header
logon domain unicode string header
undocumented logon domain id pointer
40 undocumented padding bytes. future expansion?
0 - num_other_sids?
NULL - undocumented pointer to other domain SIDs.
username unicode string
user's full name unicode string
logon script unicode string
profile path unicode string
home directory unicode string
home directory drive unicode string
num groups
group info
logon server unicode string
logon domain unicode string
domain SID
other domain SIDs?
Note: see cifsrap2.txt section5, page 10.
0 for shi1_type indicates a Disk. |
1 for shi1_type indicates a Print Queue. |
2 for shi1_type indicates a Device. |
3 for shi1_type indicates an IPC pipe. |
0x8000 0000 (top bit set in shi1_type) indicates a hidden share. |
shi1_netname - pointer to net name
shi1_type - type of share. 0 - undocumented.
shi1_remark - pointer to comment.
shi1_netname - unicode string of net name
shi1_remark - unicode string of comment.
share container with 0 entries:
0 - EntriesRead
0 - Buffer
share container with > 0 entries:
EntriesRead
non-zero - Buffer
EntriesRead
share entry pointers
share entry strings
padding to get unicode string 4-byte aligned with start of the SMB header.
EntriesRead
0 - padding
Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.
0x00000001 All workstations
0x00000002 All servers
0x00000004 Any server running with SQL server
0x00000008 Primary domain controller
0x00000010 Backup domain controller
0x00000020 Server running the timesource service
0x00000040 Apple File Protocol servers
0x00000080 Novell servers
0x00000100 Domain Member
0x00000200 Server sharing print queue
0x00000400 Server running dialin service.
0x00000800 Xenix server
0x00001000 NT server
0x00002000 Server running Windows for
0x00008000 Windows NT non DC server
0x00010000 Server that can run the browser service
0x00020000 Backup browser server
0x00040000 Master browser server
0x00080000 Domain Master Browser server
0x40000000 Enumerate only entries marked "local"
0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.
500 - platform_id
pointer to name
5 - major version
4 - minor version
type (SV_TYPE_... bit field)
pointer to comment
sv101_name - unicode string of server name
sv_101_comment - unicode string of server comment.
padding to get unicode string 4-byte aligned with start of the SMB header.
For details on the SMB Transact Named Pipe, see cifs6.txt
undocumented buffer pointer.
num referenced domains?
undocumented domain name buffer pointer.
32 - max number of entries
4 - num referenced domains?
domain name unicode string header
referenced domain unicode string headers
domain name unicode string
referenced domain SIDs
??? padding to get 4-byte alignment with start of SMB header
domain name string length * 2
domain name string length * 2
undocumented domain name string buffer pointer
undocumented domain SID string buffer pointer
domain name (unicode string)
domain SID
Note: it would be nice to know what the 16 byte user session key is for.
logon time
logoff time
kickoff time
password last set time
password can change time
password must change time
username unicode string header
user's full name unicode string header
logon script unicode string header
profile path unicode string header
home directory unicode string header
home directory drive unicode string header
logon count
bad password count
User ID
Group ID
num groups
undocumented buffer pointer to groups.
user flags
user session key
logon server unicode string header
logon domain unicode string header
undocumented logon domain id pointer
40 undocumented padding bytes. future expansion?
0 - num_other_sids?
NULL - undocumented pointer to other domain SIDs.
username unicode string
user's full name unicode string
logon script unicode string
profile path unicode string
home directory unicode string
home directory drive unicode string
num groups
group info
logon server unicode string
logon domain unicode string
domain SID
other domain SIDs?
Note: see cifsrap2.txt section5, page 10.
0 for shi1_type indicates a Disk. |
1 for shi1_type indicates a Print Queue. |
2 for shi1_type indicates a Device. |
3 for shi1_type indicates an IPC pipe. |
0x8000 0000 (top bit set in shi1_type) indicates a hidden share. |
shi1_netname - pointer to net name
shi1_type - type of share. 0 - undocumented.
shi1_remark - pointer to comment.
shi1_netname - unicode string of net name
shi1_remark - unicode string of comment.
share container with 0 entries:
0 - EntriesRead
0 - Buffer
share container with > 0 entries:
EntriesRead
non-zero - Buffer
EntriesRead
share entry pointers
share entry strings
padding to get unicode string 4-byte aligned with start of the SMB header.
EntriesRead
0 - padding
Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.
0x00000001 All workstations
0x00000002 All servers
0x00000004 Any server running with SQL server
0x00000008 Primary domain controller
0x00000010 Backup domain controller
0x00000020 Server running the timesource service
0x00000040 Apple File Protocol servers
0x00000080 Novell servers
0x00000100 Domain Member
0x00000200 Server sharing print queue
0x00000400 Server running dialin service.
0x00000800 Xenix server
0x00001000 NT server
0x00002000 Server running Windows for
0x00008000 Windows NT non DC server
0x00010000 Server that can run the browser service
0x00020000 Backup browser server
0x00040000 Master browser server
0x00080000 Domain Master Browser server
0x40000000 Enumerate only entries marked "local"
0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.
500 - platform_id
pointer to name
5 - major version
4 - minor version
type (SV_TYPE_... bit field)
pointer to comment
sv101_name - unicode string of server name
sv_101_comment - unicode string of server comment.
padding to get unicode string 4-byte aligned with start of the SMB header.
For details on the SMB Transact Named Pipe, see cifs6.txt
The MSRPC is conducted over an SMB Transact Pipe with a name of \PIPE\. You must first obtain a 16 bit file handle, by sending a SMBopenX with the pipe name \PIPE\srvsvc for @@ -1268,11 +1268,11 @@ listed below:
initial SMBopenX request: RPC API command 0x26 params: "\\PIPE\\lsarpc" 0x65 0x63; 0x72 0x70; 0x44 0x65; "\\PIPE\\srvsvc" 0x73 0x76; 0x4E 0x00; 0x5C 0x43; -
[section to be rewritten, following receipt of work by Duncan Stansfield]
Interesting note: if you set packed data representation to 0x0100 0000 -then all 4-byte and 2-byte word ordering is turned around!
The start of each of the NTLSA and NETLOGON named pipes begins with:
offset: 00
Variable type: UINT8
Variable data: 5 - RPC major version
offset: 01
Variable type: UINT8
Variable data: 0 - RPC minor version
offset: 02
Variable type: UINT8
Variable data: 2 - RPC response packet
offset: 03
Variable type: UINT8
Variable data: 3 - (FirstFrag bit-wise or with LastFrag)
offset: 04
Variable type: UINT32
Variable data: 0x1000 0000 - packed data representation
offset: 08
Variable type: UINT16
Variable data: fragment length - data size (bytes) inc header and tail.
offset: 0A
Variable type: UINT16
Variable data: 0 - authentication length
offset: 0C
Variable type: UINT32
Variable data: call identifier. matches 12th UINT32 of incoming RPC data.
offset: 10
Variable type: UINT32
Variable data: allocation hint - data size (bytes) minus header and tail.
offset: 14
Variable type: UINT16
Variable data: 0 - presentation context identifier
offset: 16
Variable type: UINT8
Variable data: 0 - cancel count
offset: 17
Variable type: UINT8
Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.
offset: 18
Variable type: ......
Variable data: start of data (goes on for allocation_hint bytes)
reply same as request (0x05)
reply same as request (0x00)
one of the MSRPC_Type enums
reply same as request (0x00 for Bind, 0x03 for Request)
reply same as request (0x00000010)
the length of the data section of the SMB trans packet
call identifier. (e.g. 0x00149594)
the remainder of the packet depending on the "type"
the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc
+
[section to be rewritten, following receipt of work by Duncan Stansfield]
Interesting note: if you set packed data representation to 0x0100 0000 +then all 4-byte and 2-byte word ordering is turned around!
The start of each of the NTLSA and NETLOGON named pipes begins with:
offset: 00
Variable type: UINT8
Variable data: 5 - RPC major version
offset: 01
Variable type: UINT8
Variable data: 0 - RPC minor version
offset: 02
Variable type: UINT8
Variable data: 2 - RPC response packet
offset: 03
Variable type: UINT8
Variable data: 3 - (FirstFrag bit-wise or with LastFrag)
offset: 04
Variable type: UINT32
Variable data: 0x1000 0000 - packed data representation
offset: 08
Variable type: UINT16
Variable data: fragment length - data size (bytes) inc header and tail.
offset: 0A
Variable type: UINT16
Variable data: 0 - authentication length
offset: 0C
Variable type: UINT32
Variable data: call identifier. matches 12th UINT32 of incoming RPC data.
offset: 10
Variable type: UINT32
Variable data: allocation hint - data size (bytes) minus header and tail.
offset: 14
Variable type: UINT16
Variable data: 0 - presentation context identifier
offset: 16
Variable type: UINT8
Variable data: 0 - cancel count
offset: 17
Variable type: UINT8
Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.
offset: 18
Variable type: ......
Variable data: start of data (goes on for allocation_hint bytes)
reply same as request (0x05)
reply same as request (0x00)
one of the MSRPC_Type enums
reply same as request (0x00 for Bind, 0x03 for Request)
reply same as request (0x00000010)
the length of the data section of the SMB trans packet
call identifier. (e.g. 0x00149594)
the remainder of the packet depending on the "type"
the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc
abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003) transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002) -
the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck
maximum transmission fragment size (0x1630)
max receive fragment size (0x1630)
associated group id (0x0)
the number of elements (0x1)
presentation context identifier (0x0)
the number of syntaxes (has always been 1?)(0x1)
4-byte alignment padding, against SMB header
num and vers. of interface client is using
num and vers. of interface to use for replies
length of the string including null terminator
the string above in single byte, null terminated form
the response to place after the header in the reply packet
same as request
same as request
zero
the address string, as described earlier
4-byte alignment padding, against SMB header
the number of results (0x01)
4-byte alignment padding, against SMB header
result (0x00 = accept)
reason (0x00 = no reason specified)
the transfer syntax from the request
the remainder of the packet after the header for every other other request
the size of the stub data in bytes
presentation context identifier (0x0)
operation number (0x15)
a packet dependent on the pipe name (probably the interface) and the op number)
The end of each of the NTLSA and NETLOGON named pipes ends with:
end of data
return code
the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck
maximum transmission fragment size (0x1630)
max receive fragment size (0x1630)
associated group id (0x0)
the number of elements (0x1)
presentation context identifier (0x0)
the number of syntaxes (has always been 1?)(0x1)
4-byte alignment padding, against SMB header
num and vers. of interface client is using
num and vers. of interface to use for replies
length of the string including null terminator
the string above in single byte, null terminated form
the response to place after the header in the reply packet
same as request
same as request
zero
the address string, as described earlier
4-byte alignment padding, against SMB header
the number of results (0x01)
4-byte alignment padding, against SMB header
result (0x00 = accept)
reason (0x00 = no reason specified)
the transfer syntax from the request
the remainder of the packet after the header for every other other request
the size of the stub data in bytes
presentation context identifier (0x0)
operation number (0x15)
a packet dependent on the pipe name (probably the interface) and the op number)
The end of each of the NTLSA and NETLOGON named pipes ends with:
end of data
return code
RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc) with a "transfer syntax" (see RPC_Iface structure). The purpose for doing this is unknown. @@ -1280,7 +1280,7 @@ this is unknown. returned by the SMBopenX Transact response.
Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The RPC_ResBind member transfersyntax is the same in the response as the
Note: The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe. The - mapping identified so far is:
RPC_ResBind response:
"\\PIPE\\ntsvcs"
"\\PIPE\\lsass"
"\\PIPE\\lsass"
"\\PIPE\\wksvcs"
"\\PIPE\\NETLOGON"
Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.
Request:
RPC_Packet |
RPC_ReqBind |
Response:
RPC_Packet |
RPC_ResBind |
The sequence of actions taken on this pipe are:
Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords. |
Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle. |
Using the file handle, send a Set Named Pipe Handle state to 0x4300. |
Send an LSA Open Policy request. Store the Policy Handle. |
Using the Policy Handle, send LSA Query Info Policy requests, etc. |
Using the Policy Handle, send an LSA Close. |
Close the IPC$ share. |
Defines for this pipe, identifying the query are:
0x2c
0x07
0x0d
0xff
0xfe
0xfd
0x00
Note: The policy handle can be anything you like.
buffer pointer
server name - unicode string starting with two '\'s
object attributes
1 - desired access
Note: The info class in response must be the same as that in the request.
undocumented buffer pointer
info class (same as info class in request).
+ mapping identified so far is:
- initial SMBopenX request:
RPC_ResBind response:
- "\\PIPE\\srvsvc"
"\\PIPE\\ntsvcs"
- "\\PIPE\\samr"
"\\PIPE\\lsass"
- "\\PIPE\\lsarpc"
"\\PIPE\\lsass"
- "\\PIPE\\wkssvc"
"\\PIPE\\wksvcs"
- "\\PIPE\\NETLOGON"
"\\PIPE\\NETLOGON"
Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.
Request:
RPC_Packet |
RPC_ReqBind |
Response:
RPC_Packet |
RPC_ResBind |
The sequence of actions taken on this pipe are:
Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords. |
Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle. |
Using the file handle, send a Set Named Pipe Handle state to 0x4300. |
Send an LSA Open Policy request. Store the Policy Handle. |
Using the Policy Handle, send LSA Query Info Policy requests, etc. |
Using the Policy Handle, send an LSA Close. |
Close the IPC$ share. |
Defines for this pipe, identifying the query are:
0x2c
0x07
0x0d
0xff
0xfe
0xfd
0x00
Note: The policy handle can be anything you like.
buffer pointer
server name - unicode string starting with two '\'s
object attributes
1 - desired access
Note: The info class in response must be the same as that in the request.
Note: num_entries in response must be same as num_entries in request.
LSA policy handle
num_entries
undocumented domain SID buffer pointer
undocumented domain name buffer pointer
DOM_SID[num_entries] domain SIDs to be looked up.
completely undocumented 16 bytes.
Note: num_entries in response must be same as num_entries in request.
LSA policy handle
num_entries
num_entries
undocumented domain SID buffer pointer
undocumented domain name buffer pointer
names to be looked up.
undocumented bytes - falsely translated SID structure?
The sequence of actions taken on this pipe are:
tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords. |
en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle. |
ing the file handle, send a Set Named Pipe Handle state to 0x4300. |
eate Client Challenge. Send LSA Request Challenge. Store Server Challenge. |
lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge. |
lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds. |
lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds. |
lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds. |
ose the IPC$ share. |
Defines for this pipe, identifying the query are
0x04
0x06
0x02
0x03
0x0f
0x0e
Note: logon server name starts with two '\' characters and is upper case.
Note: logon client is the machine, not the user.
Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).
undocumented buffer pointer
logon server unicode string
logon client unicode string
client challenge
Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).
Note: neg_flags in the response is the same as that in the request.
Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.
client identification info
client-calculated credentials
padding to 4-byte align with start of SMB header.
neg_flags - negotiated flags (usual value is 0x0000 01ff)
Note: the new password is suspected to be a DES encryption using the old password to generate the key.
Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).
Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.
Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.
Note: num_entries in response must be same as num_entries in request.
LSA policy handle
num_entries
undocumented domain SID buffer pointer
undocumented domain name buffer pointer
DOM_SID[num_entries] domain SIDs to be looked up.
completely undocumented 16 bytes.
Note: num_entries in response must be same as num_entries in request.
LSA policy handle
num_entries
num_entries
undocumented domain SID buffer pointer
undocumented domain name buffer pointer
names to be looked up.
undocumented bytes - falsely translated SID structure?
The sequence of actions taken on this pipe are:
tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords. |
en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle. |
ing the file handle, send a Set Named Pipe Handle state to 0x4300. |
eate Client Challenge. Send LSA Request Challenge. Store Server Challenge. |
lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge. |
lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds. |
lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds. |
lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds. |
ose the IPC$ share. |
Defines for this pipe, identifying the query are
0x04
0x06
0x02
0x03
0x0f
0x0e
Note: logon server name starts with two '\' characters and is upper case.
Note: logon client is the machine, not the user.
Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).
undocumented buffer pointer
logon server unicode string
logon client unicode string
client challenge
Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).
Note: neg_flags in the response is the same as that in the request.
Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.
client identification info
client-calculated credentials
padding to 4-byte align with start of SMB header.
neg_flags - negotiated flags (usual value is 0x0000 01ff)
Note: the new password is suspected to be a DES encryption using the old password to generate the key.
Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).
Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.
Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.
Note: valid_user is True iff the username and password hash are valid for the requested domain. -
undocumented buffer pointer
server credentials. server time stamp appears to be ignored.
+
Note: presumably, the SAM_INFO structure is validated, and a (currently undocumented) error code returned if the Logoff is invalid. -
Note: mailslots will contain a response mailslot, to which the response should be sent. the target NetBIOS name is REQUEST_NAME<20>, where REQUEST_NAME is the name of the machine that sent the request. -
Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.
0x0007 - Query for PDC
machine name
response mailslot
padding to 2-byte align with start of mailslot.
machine name
NTversion
LMNTtoken
LM20token
0x000A - Respose to Query for PDC
machine name (in uppercase)
padding to 2-byte align with start of mailslot.
machine name
domain name
NTversion (same as received in request)
LMNTtoken (same as received in request)
LM20token (same as received in request)
Note: machine name in response is preceded by two '\' characters.
Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.
Note: user name in the response is presumably the same as that in the request.
0x0012 - SAM Logon
request count
machine name
user name
response mailslot
alloweable account
domain SID size
domain SID, of sid_size bytes.
???? padding to 4? 2? -byte align with start of mailslot.
NTversion
LMNTtoken
LM20token
Defines for this pipe, identifying the query are:
0x0f
0x15
Note: share level and switch value in the response are presumably the same as those in the request.
Note: cifsrap2.txt (section 5) may be of limited assistance here.
pointer (to server name?)
server name
padding to get unicode string 4-byte aligned with the start of the SMB header.
share level
switch value
pointer to SHARE_INFO_1_CTR
share info with 0 entries
preferred maximum length (0xffff ffff)
Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2
DES ECB encryption of 8 byte data D using 7 byte key K
Lan man hash
NT hash
md4(machine_password) == md4(lsadump $machine.acc) == +
Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.
0x0007 - Query for PDC
machine name
response mailslot
padding to 2-byte align with start of mailslot.
machine name
NTversion
LMNTtoken
LM20token
0x000A - Respose to Query for PDC
machine name (in uppercase)
padding to 2-byte align with start of mailslot.
machine name
domain name
NTversion (same as received in request)
LMNTtoken (same as received in request)
LM20token (same as received in request)
Note: machine name in response is preceded by two '\' characters.
Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.
Note: user name in the response is presumably the same as that in the request.
0x0012 - SAM Logon
request count
machine name
user name
response mailslot
alloweable account
domain SID size
domain SID, of sid_size bytes.
???? padding to 4? 2? -byte align with start of mailslot.
NTversion
LMNTtoken
LM20token
Defines for this pipe, identifying the query are:
0x0f
0x15
Note: share level and switch value in the response are presumably the same as those in the request.
Note: cifsrap2.txt (section 5) may be of limited assistance here.
pointer (to server name?)
server name
padding to get unicode string 4-byte aligned with the start of the SMB header.
share level
switch value
pointer to SHARE_INFO_1_CTR
share info with 0 entries
preferred maximum length (0xffff ffff)
Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2
DES ECB encryption of 8 byte data D using 7 byte key K
Lan man hash
NT hash
md4(machine_password) == md4(lsadump $machine.acc) == pwdump(machine$) (initially) == md4(lmowf(unicode(machine))) -
ARC4 encryption of data D of length Ld with key K of length Lk
subset of v from bytes m to n, optionally padded with zeroes to length l
E(K[7..7,7],E(K[0..6],D)) computes a credential
4 byte current time
8 byte client and server challenges Rc,Rs: 8 byte client and server credentials
+
ARC4 encryption of data D of length Ld with key K of length Lk
subset of v from bytes m to n, optionally padded with zeroes to length l
E(K[7..7,7],E(K[0..6],D)) computes a credential
4 byte current time
8 byte client and server challenges Rc,Rs: 8 byte client and server credentials
C->S ReqChal,Cc S->C Cs
@@ -1358,7 +1358,7 @@ S: Ts = Time() S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc) C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1)) C: Rc = Cred(Ks,Rc+Tc+1) -
On first joining the domain the session key could be computed by anyone listening in on the network as the machine password has a well known value. Until the machine is rebooted it will use this session @@ -1379,30 +1379,30 @@ returned by the server. The password OWFs should NOT be sent over the network reversibly encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server computing the same function using the owf values in the SAM. -
SIDs and RIDs are well documented elsewhere.
A SID is an NT Security ID (see DOM_SID structure). They are of the form:
revision-NN-SubAuth1-SubAuth2-SubAuth3... |
revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3... |
currently, the SID revision is 1. The Sub-Authorities are known as Relative IDs (RIDs). -
S-1-0-0
S-1-1-0
S-1-2-0
S-1-3-0
S-1-3-1
S-1-3-2
S-1-3-3
S-1-4
+
S-1-0-0
S-1-1-0
S-1-2-0
S-1-3-0
S-1-3-1
S-1-3-2
S-1-3-3
S-1-4
A RID is a sub-authority value, as part of either a SID, or in the case of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1 structure, in the LSA SAM Logon response. -
Groupname: DOMAIN_USER_RID_ADMIN
????: 0x0000
RID: 01F4
Groupname: DOMAIN_USER_RID_GUEST
????: 0x0000
RID: 01F5
Groupname: DOMAIN_GROUP_RID_ADMINS
????: 0x0000
RID: 0200
Groupname: DOMAIN_GROUP_RID_USERS
????: 0x0000
RID: 0201
Groupname: DOMAIN_GROUP_RID_GUESTS
????: 0x0000
RID: 0202
Groupname: DOMAIN_ALIAS_RID_ADMINS
????: 0x0000
RID: 0220
Groupname: DOMAIN_ALIAS_RID_USERS
????: 0x0000
RID: 0221
Groupname: DOMAIN_ALIAS_RID_GUESTS
????: 0x0000
RID: 0222
Groupname: DOMAIN_ALIAS_RID_POWER_USERS
????: 0x0000
RID: 0223
Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS
????: 0x0000
RID: 0224
Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS
????: 0x0000
RID: 0225
Groupname: DOMAIN_ALIAS_RID_PRINT_OPS
????: 0x0000
RID: 0226
Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS
????: 0x0000
RID: 0227
Groupname: DOMAIN_ALIAS_RID_REPLICATOR
????: 0x0000
RID: 0228
Table of Contents
Groupname: DOMAIN_USER_RID_ADMIN
????: 0x0000
RID: 01F4
Groupname: DOMAIN_USER_RID_GUEST
????: 0x0000
RID: 01F5
Groupname: DOMAIN_GROUP_RID_ADMINS
????: 0x0000
RID: 0200
Groupname: DOMAIN_GROUP_RID_USERS
????: 0x0000
RID: 0201
Groupname: DOMAIN_GROUP_RID_GUESTS
????: 0x0000
RID: 0202
Groupname: DOMAIN_ALIAS_RID_ADMINS
????: 0x0000
RID: 0220
Groupname: DOMAIN_ALIAS_RID_USERS
????: 0x0000
RID: 0221
Groupname: DOMAIN_ALIAS_RID_GUESTS
????: 0x0000
RID: 0222
Groupname: DOMAIN_ALIAS_RID_POWER_USERS
????: 0x0000
RID: 0223
Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS
????: 0x0000
RID: 0224
Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS
????: 0x0000
RID: 0225
Groupname: DOMAIN_ALIAS_RID_PRINT_OPS
????: 0x0000
RID: 0226
Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS
????: 0x0000
RID: 0227
Groupname: DOMAIN_ALIAS_RID_REPLICATOR
????: 0x0000
RID: 0228
Table of Contents
The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics of certain features of Windows client printing. -
Samba uses a table of function pointers to seven functions. The @@ -1413,7 +1413,7 @@ Currently there are only two printing back end implementations defined.
a generic set of functions for working with standard UNIX printing subsystems
a set of CUPS specific functions (this is only enabled if - the CUPS libraries were located at compile time).
Samba provides periodic caching of the output from the "lpq command" @@ -1502,11 +1502,11 @@ and the job has the printer's device mode associated with it by default. Only non-default Device Mode are stored with print jobs in the print queue TDB. Otherwise, the Device Mode is obtained from the printer object when the client issues a GetJob(level == 2) request. -
When working with Windows NT+ clients, it is possible for a @@ -1604,7 +1604,7 @@ handle for notification. Samba currently uses the snum of the printer for this which can break if the list of services has been modified since the notification handle was registered.
The size is either (a) the string length in UNICODE for strings, (b) the size in bytes of the security descriptor, or (c) 0 for -data values.
Table of Contents
Table of Contents
The current Samba codebase possesses the capability to use groups of WINS servers that share a common namespace for NetBIOS name registration and resolution. The formal parameter syntax is @@ -1646,7 +1646,7 @@ If a timeout occurs when querying a specific WINS server, that server is marked prevent further timeouts and the next server in the WINS group is contacted. Once marked as dead, Samba will not attempt to contact that server for name registration/resolution queries for a period of 10 minutes. -
Table of Contents
Table of Contents
One of the biggest problems with passdb is it's implementation of 'security'. Access control is on a 'are you root at the moment' basis, and it has no concept of NT ACLs. Things like ldapsam had to add 'magic' 'are you root' checks.
We took this very seriously when we started work, and the new structure @@ -1706,7 +1706,7 @@ actual data store (like the LDAP server).
Finally, we have generic get_sec_desc() and set_sec_desc() routines to allow external ACL manipulation. These do lookups based on SID. -
One of the primary tenants of the 'new SAM' is that it would not attempt to deal with 'what unix id for that'. This would be left to the 'SMS' (Sid Mapping System') or SID farm, and probably administered via @@ -1716,7 +1716,7 @@ Accounts not preexisting in unix would be served up via winbind.
This is an *optional* part, and my preferred end-game. We have a fare way to go before things like winbind up to it however. -
One of the things that the 'new SAM' work has tried to face is both compatibility with existing code, and a closer alignment to the SAMR interface. I consider SAMR to be a 'primary customer' to the this work, @@ -1741,11 +1741,11 @@ have *really* changed. 'conflicting' updates: Currently we don't deal with this (in passdb or the new sam stuff), but the design is sufficiently flexible to 'deny' a second update. I don't foresee locking records however. -
This is where smbd, samtest and whatever end-user replacement we have for pdbedit sits. They use only the SAM interface, and do not get 'special knowledge' of what is below them. -
This level 'owns' the various handle structures, the get/set routines on those structures and provides the public interface. The application layer may initialize a 'context' to be passed to all interface routines, @@ -1756,7 +1756,7 @@ abstraction to the modules below, and arrange for their initial loading.
We could possibly add ACL checking at this layer, to avoid discrepancies in implementation modules. -
These do not communicate with the application directly, only by setting values in the handles, and receiving requests from the interface. These modules are responsible for translating values from the handle's @@ -1764,13 +1764,13 @@ modules are responsible for translating values from the handle's to 'know' things like it's own domain SID, domain name, and any other state attached to the SAM. Simpler modules may call back to some helper routine. -
In order for there to be a smooth transition, kai is writing a module that reads existing passdb backends, and translates them into SAM replies. (Also pulling data from the account policy DB etc). We also intend to write a module that does the reverse - gives the SAM a passdb interface. -
This is the first of the SAM modules to be committed to the tree - mainly because I needed to coordinate work with metze (who authored most of it). This module aims to use Samba's libads code to provide an @@ -1782,7 +1782,7 @@ the construction of an Samba AD DC.
We also intend to construct a Samba 2.2/3.0 compatible ldap module, again using libads code. -
The 'new SAM' development effort also concerned itself with getting a sane implementation of memory management. It was decided that we would be (as much as possible) talloc based, using an 'internal talloc @@ -1811,7 +1811,7 @@ NT_USER_TOKEN *access_token, uint32 access_desired, const DOM_SID NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const NT_USER_TOKEN *access_token, const DOM_SID *domainsid, uint16 acct_ctrl, int32 *account_count, SAM_ACCOUNT_ENUM **accounts) -
Testing is vital in any piece of software, and Samba is certainly no exception. In designing this new subsystem, we have taken care to ensure it is easily tested, independent of outside protocols. @@ -1840,13 +1840,13 @@ Because the 'new SAM' is NT ACL based, there will be a command to specify an arbitrary NT ACL, but for now it uses 'system' by default.
Table of Contents
19 Apr 1999
Table of Contents
With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able to validate user connections in exactly the same way as a LanManager or Windows NT server.
This document describes how the SMB password encryption algorithm works and what issues there are in choosing whether you want to use it. You should read it carefully, especially - the part about security and the "PROS and CONS" section.
LanManager encryption is somewhat similar to UNIX + the part about security and the "PROS and CONS" section.
LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a hashed value of a user's password. This is created by taking the user's plaintext password, capitalising it, and either @@ -1883,7 +1883,7 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default. know the correct password and is denied access.
Note that the Samba server never knows or stores the cleartext of the user's password - just the 16 byte hashed values derived from it. Also note that the cleartext password or 16 byte hashed values - are never transmitted over the network - thus increasing security.
In order for Samba to participate in the above protocol + are never transmitted over the network - thus increasing security.
In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. Unfortunately, as the UNIX password value is also a one way hash function (ie. it is impossible to retrieve the cleartext of the user's @@ -1940,10 +1940,10 @@ bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: to enable this on your server.
Note : This file should be protected very carefully. Anyone with access to this file can (with enough knowledge of the protocols) gain access to your SMB server. The file is thus more - sensitive than a normal unix /etc/passwd file.
Table of Contents
Table of Contents
The new modules system has the following advantages:
Transparent loading of static and shared modules (no need -for a subsystem to know about modules) |
Simple selection between shared and static modules at configure time |
"preload modules" option for increasing performance for stable modules |
No nasty #define stuff anymore |
All backends are available as plugin now (including pdb_ldap and pdb_tdb) |
+for a subsystem to know about modules)
Some subsystems in samba use different backends. These backends can be either statically linked in to samba or available as a plugin. A subsystem should have a function that allows a module to register itself. For example, @@ -1953,7 +1953,7 @@ NTSTATUS smb_register_passdb(int version, const char *name, pdb_init_function in
This function will be called by the initialisation function of the module to register itself. -
+
The modules system compiles a list of initialisation functions for the static modules of each subsystem. This is a define. For example, it is here currently (from include/config.h): @@ -1963,7 +1963,7 @@ it is here currently (from include/config.h):
These functions should be called before the subsystem is used. That should be done when the subsystem is initialised or first used. -
If a subsystem needs a certain backend, it should check if it has already been registered. If the backend hasn't been registered already, the subsystem should call smb_probe_module(char *subsystem, char *backend). @@ -1973,7 +1973,7 @@ is a slash, smb_probe_module() tries to load the module from the absolute path specified in 'backend'.
After smb_probe_module() has been executed, the subsystem should check again if the module has been registered. -
Each module has an initialisation function. For modules that are included with samba this name is 'subsystem_backend_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()). The prototype for these functions is: @@ -1988,7 +1988,7 @@ smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam); smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua); return NT_STATUS_OK; } -
+
Some macros in configure.in generate the various defines and substs that are necessary for the system to work correct. All modules that should be built by default have to be added to the variable 'default_modules'. @@ -2009,13 +2009,13 @@ Practically, this means all c files that contain static_init_
There currently also is a configure.in command called SMB_MODULE_PROVIVES(). This is used for modules that register multiple things. It should not -be used as probing will most likely disappear in the future.
Table of Contents
Table of Contents
This document describes how to make use the new RPC Pluggable Modules features of Samba 3.0. This architecture was added to increase the maintainability of Samba allowing RPC Pipes to be worked on separately from the main CVS branch. The RPM architecture will also allow third-party vendors to add functionality to Samba through plug-ins. -
When an RPC call is sent to smbd, smbd tries to load a shared library by the name librpc_<pipename>.so to handle the call if it doesn't know how to handle the call internally. For instance, LSA calls @@ -2032,7 +2032,7 @@ NTSTATUS rpc_pipe_register_commands(int version, const char *clnt, const char *s argument.
the Client name of the named pipe
the Server name of the named pipe
a list of api_structs that map RPC ordinal numbers to function calls
the number of api_structs contained in cmds
See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of how to use this library. -
Table of Contents
Table of Contents
Each VFS operation has a vfs_op_type, a function pointer and a handle pointer in the struct vfs_ops and tree macros to make it easier to call the operations. (Take a look at include/vfs.h and include/vfs_macros.h.) @@ -2128,7 +2128,7 @@ DO NOT ACCESS conn->vfs.ops.* directly !!! (tofd), (fsp), (fromfd), (header), (offset), (count))) ... -
These values are used by the VFS subsystem when building the conn->vfs and conn->vfs_opaque structs for a connection with multiple VFS modules. Internally, Samba differentiates only opaque and transparent layers at this process. @@ -2157,7 +2157,7 @@ typedef enum _vfs_op_layer { SMB_VFS_LAYER_SCANNER /* - Checks data and possibly initiates additional */ /* file activity like logging to files _inside_ samba VFS */ } vfs_op_layer; -
As each Samba module a VFS module should have a
NTSTATUS vfs_example_init(void);
function if it's staticly linked to samba or
NTSTATUS init_module(void);
function if it's a shared module. @@ -2197,7 +2197,7 @@ NTSTATUS init_module(void) { return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, "example", example_op_tuples); } -
Each VFS function has as first parameter a pointer to the modules vfs_handle_struct. +
Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
typedef struct vfs_handle_struct { struct vfs_handle_struct *next, *prev; @@ -2298,7 +2298,7 @@ you can set this function pointer to NULL.
Some useful MAC (handle)->vfs_next.handles.sendfile,\ (tofd), (fsp), (fromfd), (header), (offset), (count))) ... -
Add "vfs_handle_struct *handle, " as first parameter to all vfs operation functions. e.g. example_connect(connection_struct *conn, const char *service, const char *user); -> example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user); @@ -2422,7 +2422,7 @@ remember the struct smb_vfs_handle_struct.
(Only for 3.0alpha* modules) Check if your vfs_done() function contains needed code. -
If NOT you can remove the vfs_done() function. | |||||||
If YES decide if you can move the code to the example_disconnect() operation. Otherwise register a SMB_EXIT_EVENT with smb_register_exit_event(); (Described in the modules section) And then remove vfs_done(). e.g. the freeing of private data should go to example_disconnect().
+
Check if you have any global variables left. @@ -2561,7 +2561,7 @@ for your module. Compiling & Testing...
- Avoid writing functions like this: @@ -2572,7 +2572,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd) Overload only the functions you really need to! - If you want to just implement a better version of a default samba opaque function (e.g. like a disk_free() function for a special filesystem) @@ -2592,12 +2592,12 @@ static int example_rename(vfs_handle_struct *handle, connection_struct *conn, errno = ENOSYS; return -1; } - Table of Contents Table of Contents Please, please update the version number in source/include/version.h to include the versioning of your package. This makes it easier to distinguish standard samba builds from custom-build samba builds (distributions often patch packages). For example, a good version would be: Version 2.999+3.0.alpha21-5 for Debian - Samba now has support for building parts of samba as plugins. This makes it possible to, for example, put ldap or mysql support in a seperate package, thus making it possible to have a normal samba package not depending on ldap or mysql. To build as much parts of samba @@ -2631,11 +2631,11 @@ as a plugin, run: with one that had issues. | |||||||
Make sure your patch complies to the samba coding style as suggested in the coding-suggestions chapter. |
Bugfixes to bugs in samba should be submitted to samba's
- bugzilla system,
+
Send feature patches along with a description of what the
patch is supposed to do to the
- Samba-technical mailinglist and possibly to a samba team member who is (one of the) 'owners'
+
The Samba-Team would like to express sincere thanks to the many people who have with or without their knowledge contributed to this update. The size and scope of this @@ -34,49 +34,16 @@ insignificant number of ideas for inclusion (if not content itself) has been obt 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
List of Figures
List of Tables
List of Examples
Table of Contents
List of Figures
List of Tables
List of Examples
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 -
David Lechnyr <david@lechnyr.com>
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
Karl Auer
John H. Terpstra <jht@samba.org>
Server Types and Security Modes
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
John H. Terpstra <jht@samba.org>
Gerald (Jerry) Carter <jerry@samba.org>
David Bannon <dbannon@samba.org>
John H. Terpstra <jht@samba.org>
Volker Lendecke <Volker.Lendecke@SerNet.DE>
John H. Terpstra <jht@samba.org>
Jeremy Allison <jra@samba.org>
Gerald (Jerry) Carter <jerry@samba.org>
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
MS Windows Network Configuration Guide
John H. Terpstra <jht@samba.org>
Samba / MS Windows Network Browsing Guide
John H. Terpstra <jht@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Gerald (Jerry) Carter <jerry@samba.org>
Jeremy Allison <jra@samba.org>
John H. Terpstra <jht@samba.org>
Olivier (lem) Lemaire <olem@IDEALX.org>
Mapping MS Windows and UNIX Groups
Jean François Micouleau
Gerald (Jerry) Carter <jerry@samba.org>
John H. Terpstra <jht@samba.org>
File, Directory and Share Access Controls
John H. Terpstra <jht@samba.org>
Jeremy Allison <jra@samba.org>
Jelmer R. Vernooij <jelmer@samba.org> (drawing)
Jeremy Allison <jra@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
Eric Roseme <eric.roseme@hp.com>
Andrew Tridgell <tridge@samba.org>
John H. Terpstra <jht@samba.org>
Interdomain Trust Relationships
John H. Terpstra <jht@samba.org>
Rafal Szczesniak <mimir@samba.org>
Jelmer R. Vernooij <jelmer@samba.org> (drawing)
Stephen Langasek <vorlon@netexpress.net>
Hosting a Microsoft Distributed File System tree on Samba
Shirish Kalele <samba@samba.org>
Kurt Pfeifle <kpfeifle@danka.de>
Gerald (Jerry) Carter <jerry@samba.org>
CUPS Printing Support in Samba 3.0
Kurt Pfeifle <kpfeifle@danka.de>
Ciprian Vizitiu <CVizitiu@gbif.org> (drawings)
Jelmer R. Vernooij <jelmer@samba.org> (drawings)
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)
John H. Terpstra <jht@samba.org>
John H. Terpstra <jht@samba.org>
John H. Terpstra <jht@samba.org>
PAM based Distributed Authentication
John H. Terpstra <jht@samba.org>
Stephen Langasek <vorlon@netexpress.net>
Integrating MS Windows networks with Samba
John H. Terpstra <jht@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
TAKAHASHI Motonobu <monyo@home.monyo.com>
John H. Terpstra <jht@samba.org>
John H. Terpstra <jht@samba.org>
Upgrading from Samba-2.x to Samba-3.0.0
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
Gerald (Jerry) Carter <jerry@samba.org>
Migration from NT4 PDC to Samba-3 PDC
John H. Terpstra <jht@samba.org>
SWAT - The Samba Web Administration Tool
John H. Terpstra <jht@samba.org>
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Analysing and solving samba problems
Gerald (Jerry) Carter <jerry@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
David Bannon <dbannon@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Andrew Tridgell <tridge@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
Jim McDonough <jmcd@us.ibm.com> (OS/2)
Paul Cochrane <paulc@dth.scot.nhs.uk>
Jelmer R. Vernooij <jelmer@samba.org>
John H. Terpstra <jht@samba.org>
DNS and DHCP Configuration Guide
John H. Terpstra <jht@samba.org>
Jelmer R. Vernooij <jelmer@samba.org>
This section of the Samba-HOWTO-Collection contains general info on how to install samba
+distribution. A copy can be found on-line at
David Lechnyr <
Andrew Tridgell <
Jelmer R. Vernooij <
John H. Terpstra <
Karl Auer <
Dan Shearer <
John H. Terpstra <
Andrew Tridgell <
Jelmer R. Vernooij <
John H. Terpstra <
John H. Terpstra <
Gerald (Jerry) Carter <
David Bannon <
Guenther Deschner <
John H. Terpstra <
Volker Lendecke <
Guenther Deschner <
John H. Terpstra <
Jeremy Allison <
Gerald (Jerry) Carter <
Andrew Tridgell <
Jelmer R. Vernooij <
Guenther Deschner <
John H. Terpstra <
John H. Terpstra <
John H. Terpstra <
Jelmer R. Vernooij <
Jelmer R. Vernooij <
John H. Terpstra <
Gerald (Jerry) Carter <
Jeremy Allison <
Guenther Deschner <
Olivier (lem) Lemaire <
John H. Terpstra <
Jean François Micouleau
Gerald (Jerry) Carter <
John H. Terpstra <
Jeremy Allison <
Jelmer R. Vernooij <
Jeremy Allison <
Jelmer R. Vernooij <
John H. Terpstra <
Eric Roseme <
Andrew Tridgell <
John H. Terpstra <
John H. Terpstra <
Rafal Szczesniak <
Jelmer R. Vernooij <
Stephen Langasek <
Shirish Kalele <
John H. Terpstra <
Kurt Pfeifle <
Gerald (Jerry) Carter <
John H. Terpstra <
Kurt Pfeifle <
Ciprian Vizitiu <
Jelmer R. Vernooij <
Jelmer R. Vernooij <
John H. Terpstra <
Tim Potter <
Simo Sorce (original vfs_skel README)
Alexander Bokovoy (original vfs_netatalk docs)
Stefan Metzmacher (Update for multiple modules)
Tim Potter <
Andrew Tridgell <
Naag Mummaneni <
John Trostel <
Jelmer R. Vernooij <
John H. Terpstra <
John H. Terpstra <
John H. Terpstra <
John H. Terpstra <
John H. Terpstra <
Stephen Langasek <
John H. Terpstra <
Jelmer R. Vernooij <
John H. Terpstra <
TAKAHASHI Motonobu <
John H. Terpstra <
John H. Terpstra <
Jelmer R. Vernooij <
John H. Terpstra <
Gerald (Jerry) Carter <
John H. Terpstra <
John H. Terpstra <
Andrew Tridgell <
Jelmer R. Vernooij <
Dan Shearer <
Gerald (Jerry) Carter <
Jelmer R. Vernooij <
David Bannon <
Dan Shearer <
John H. Terpstra <
Jelmer R. Vernooij <
Andrew Tridgell <
Jelmer R. Vernooij <
John H. Terpstra <
Andrew Tridgell <
Jelmer R. Vernooij <
John H. Terpstra <
Jelmer R. Vernooij <
John H. Terpstra <
Dan Shearer <
Jim McDonough <
Paul Cochrane <
Jelmer R. Vernooij <
John H. Terpstra <
John H. Terpstra <
Jelmer R. Vernooij <
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
“ +PLEASE read this.
“ "If you understand what you're doing, you're not learning anything." -- Anonymous ”
@@ -85,7 +52,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. -
+
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 @@ -111,7 +78,7 @@ 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? -
+
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 @@ -160,8 +127,8 @@ 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). -
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.
@@ -181,9 +148,9 @@ Again, it's important to note that these are implementations for client filesyst 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
+
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 @@ -213,9 +180,9 @@ up a single file. In general, SMB sessions are established in the following orde to a service type (e.g., IPC$ named pipe)
A good way to examine this process in depth is to try out
-SecurityFriday's SWB program.
+
“ 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 @@ -243,222 +210,238 @@ not the completely clueless user who probably sits there shivering thinking ”
“ That's what's really irritating to me." ”
-- -Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -
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. -
Table of Contents
+ Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some packages available at - the samba homepage. -
If you need to compile samba from source, check - 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.
- Samba's configuration is stored in the smb.conf file,
- that usually resides in /etc/samba/smb.conf
+
If you need to compile Samba from source, check + .
+ Samba's configuration is stored in the smb.conf file, which + 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. -
+ tools that are available, such as the Web-based interface SWAT, that + is included with Samba. +
The smb.conf file uses the same syntax as the various old + .ini files in Windows 3.1: Each file consists of various sections, + which are started by putting the section name between brackets ([]) + on a new line. Each contains zero or more key/value-pairs seperated by an + equality sign (=). The file is just a plain-text file, so you can + open and edit it with your favorite editing tool.
Each section in the smb.conf file represents a share + on the Samba server. The section “global” is special, since it + contains settings that apply to the whole Samba server and not + to one share in particular.
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. + distribution. It is suggested you read them carefully so you can see how the options + go together in practice. See the man page for all the options. + It might be worthwhile to start out with the smb.conf.default + configuration file and adapt it to your needs. It contains plenty of + comments.
- The simplest useful configuration file would be something like this: + The simplest useful configuration file would contain something like shown in + .
-
Example 2.1. Simplest possible smb.conf file
[global] |
workgroup = MIDEARTH |
[homes] |
guest ok = no |
read only = no |
Example 2.2. Another simple 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. - (Note that the workgroup that Samba must also be set.) + their login name or homes as the service name. + (Note: The workgroup that Samba should appear in must also be set. The default + workgroup name is WORKGROUP.)
- Make sure you put the smb.conf file in the correct place - (usually in /etc/samba). + Make sure you put the smb.conf file in the correct place.
For more information about security settings for the [homes] share please refer to - "Securing Samba". -
- 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. -
- Make sure it runs OK and that the services look reasonable before proceeding. -
- Always run testparm again when you change smb.conf! -
- 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 - on compiling, installing and configuring swat from source. -
- To launch SWAT just run your favorite web browser and - point it at http://localhost:901/. Replace - localhost - with the name of the computer you are running samba on if you - are running samba on a different computer than your browser. -
- Note that you can attach to SWAT from any IP connected - 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. -
+ . ++ It's important to validate the contents of the smb.conf file using the testparm program. + If testparm runs correctly, it will list the loaded services. If not, it will give an error message. + Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command: +
+ root# testparm /etc/samba/smb.conf +Testparm will parse your configuration file and report + any unknown parameters or incorrect syntax.
+ Always run testparm again whenever the smb.conf file is changed! +
+ + SWAT is a Web-based interface that can be used to facilitate the configuration of Samba. + SWAT might not be available in the Samba package that shipped with your platform, + but in a separate package. Please read the SWAT manpage + on compiling, installing and configuring SWAT from source. +
+ To launch SWAT, just run your favorite Web browser and point it to
+
+ SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote + machine leaves your connection open to password sniffing as passwords will be sent over the wire in the clear. +
More information about SWAT can be found in .
+ To list shares that are available from the configured Samba server execute the + following command: +
$ smbclient -L yourhostname -
You should get back a list of shares available on - your server. If you don't then something is incorrectly setup. - Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).
If you choose user level security then you may find - that Samba requests a password before it will list the shares. - 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)
+
You should see a list of shares available on your server. If you do not, then + something is incorrectly configured. This method can also be used to see what shares + are available on other SMB servers, such as Windows 2000.
If you choose user-level security you may find that Samba requests a password + before it will list the shares. See the smbclient man page for details. + You can force it to list the shares without a password by adding the option + -N to the command line.
+ Enter the following command:
$ smbclient //yourhostname/aservice -
Typically the yourhostname - would be the name of the host where you installed smbd. - The aservice is - any service you have defined in the smb.conf - file. Try your user name if you just have a [homes] - section - in smb.conf.
For example if your unix host is bambi - and your login name is fred you would type:
+
Typically yourhostname is the name of the host on which smbd + has been installed. The aservice is any service that has been defined in the smb.conf + file. Try your user name if you just have a [homes] section in the smb.conf file.
Example: If the UNIX host is called bambi and a valid login name + is fred, you would type:
$ smbclient //bambi/fred -
Now that Samba is working correctly locally, you can try to + access it from other clients. Within a few minutes, the Samba host + should be listed in the Network Neighborhood on all Windows + clients of its subnet. Try browsing the server from another client + or 'mounting' it.
Mounting disks from a DOS, Windows or OS/2 client can be done by running a command such as:
C:\> net use d: \\servername\service -
Try printing. eg:
+
Try printing, e.g.
C:\> net use lpt1: \\servername\spoolservice
C:\> print filename -
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.
-The following questions and issues get raised on the samba mailing list over and over again. -
-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 -handles communication with Domain Controllers. -
-If your system is NOT running as a WINS server, then there will be one (1) single instance of +
You might want to read . + If you are still stuck, refer to . + Samba has been successfully installed at thousands of sites worldwide. + It is unlikely that your particular problem is unique, so it might be + productive to perform an Internet search to see if someone else has encountered + your problem and has found a way to overcome it.
+The following questions and issues are raised repeatedly on the Samba mailing list. +
+Samba consists of three core programs: nmbd, smbd, and winbindd. nmbd is the name server message daemon, +smbd is the server message daemon, and winbindd is the daemon that handles communication with Domain Controllers. +
+If Samba is not running as a WINS server, then there will be one single instance of nmbd running on your system. If it is running as a WINS server then there will be -two (2) instances - one to handle the WINS requests. +two instances one to handle the WINS requests.
-smbd handles ALL connection requests and then spawns a new process for each client -connection made. That is why you are seeing so many of them, one (1) per client connection. +smbd handles all connection requests. It spawns a new process for each client +connection made. That is why you may see so many of them, one 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). -
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.
- This error can be caused by one of these misconfigurations: -
Table of Contents
An error message is observed in the log files when smbd is started: “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 is configured correctly. 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.
+ 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.
Table of Contents
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
Table of Contents
+
Table of Contents
Table of Contents
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 -administrator mean. This means that it is essential also to define how critical security -modes function BEFORE we get into the details of how to configure the server itself. +configured to be. A Microsoft network administrator who wishes to migrate to or +use Samba will want to know the meaning, within a Samba context, of terms familiar to MS Windows +administrator. This means that it is essential also to define how critical security +modes function before we get into the details of how to configure the server itself.
The chapter provides an overview of the security modes of which Samba is capable -and how these relate to MS Windows servers and clients. +and how they 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 are positive towards Samba. The benefit may be on the side of our competition. +
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 -can turn that into a precious gem and some day it will make a princess very happy! +and fury befitting his anguish. The other looked at the stone and said, “This is a garnet. +I can turn that into a precious gem and some day it will make a princess very happy!”
The moral of this tale: Two men, two very different perspectives regarding the same stone. Like it or not, Samba is like that stone. Treat it the right way and it can bring great -pleasure, but if you are forced upon it and have no time for its secrets then it can be +pleasure, but if you are forced to use it and have no time for its secrets, then it can be a source of discomfort.
Samba started out as a project that sought to provide interoperability for MS Windows 3.x clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides features and functionality fit for large scale deployment. It also has some warts. In sections -like this one we will tell of both. +like this one we tell of both.
-So now, what are the benefits of features mentioned in this chapter? +So, what are the benefits of features mentioned in this chapter?
- Samba-3 can replace an MS Windows NT4 Domain Controller + Samba-3 can replace an MS Windows NT4 Domain Controller.
- Samba-3 offers excellent interoperability with MS Windows NT4 - style domains as well as natively with Microsoft Active - Directory domains. + Samba-3 offers excellent interoperability with MS Windows NT4-style + domains as well as natively with Microsoft Active Directory domains.
- Samba-3 permits full NT4 style Interdomain Trusts + Samba-3 permits full NT4-style Interdomain Trusts.
Samba has security modes that permit more flexible authentication than is possible with MS Windows NT4 Domain Controllers.
- Samba-3 permits use of multiple account database backends + Samba-3 permits use of multiple account database backends.
The account (password) database backends can be distributed and replicated using multiple methods. This gives Samba-3 greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. -
+ +Administrators of Microsoft networks often refer to three +different type of servers:
Domain Controller
Domain Member 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. -
+ + +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.
-In the SMB/CIFS networking world, there are only two types of security: USER Level -and SHARE Level. We refer to these collectively as security levels. In implementing these two security levels Samba provides flexibilities -that are not available with Microsoft Windows NT4 / 200x servers. Samba knows of five (5) -ways that allow the security levels to be implemented. In actual fact, Samba implements -SHARE Level security only one way, but has four ways of implementing -USER Level security. Collectively, we call the Samba implementations -Security Modes. These are: SHARE, USER, DOMAIN, -ADS, and SERVER -modes. They are documented in this chapter. -
- A SMB server tells the client at startup what security level -it is running. There are two options: share level and -user level. Which of these two the client receives affects -the way the client then tries to authenticate itself. It does not directly affect -(to any great extent) the way the Samba server does security. This may sound strange, -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. -
-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. -This contains a username and password. The server can either accept or reject that -username/password combination. Note that at this stage the server has no idea what +In the SMB/CIFS networking world, there are only two types of security: User Level +and Share Level. We refer to these collectively as security levels. +In implementing these two security levels, Samba provides flexibilities +that are not available with Microsoft Windows NT4/200x servers. In actual fact, Samba implements +Share Level security only one way, but has four ways of implementing +User Level security. Collectively, we call the Samba implementations +Security Modes. They are known as: SHARE, USER, +DOMAIN, ADS, and SERVER modes. +They are documented in this chapter. +
+An SMB server tells the client at startup what security level it is running. There are two options: +Share Level and User Level. Which of these two the client receives affects the way the client then +tries to authenticate itself. It does not directly affect (to any great extent) the way the Samba +server does security. This may sound strange, 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. +
+We will describe User Level Security first, as its simpler. +In User Level Security, the client will send a +session setup request directly following protocol negotiation. +This request provides a username and password. The server can either accept or reject that +username/password combination. At this stage the server has no idea what share the client will eventually try to connect to, so it can't base the accept/reject on anything other than: -
The username/password
The name of the client machine
+
the username/password.
the name of the client machine.
If the server accepts the username/password then the client expects to be able to mount shares (using a tree connection) without specifying a password. It expects that all access rights will be as the username/password @@ -468,53 +451,57 @@ 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). -
-The smb.conf parameter that sets User Level Security is: +
+In Share Level security, the client authenticates +itself separately for each share. It sends a password along with each +tree connection (share mount). It does not explicitly send a username with this operation. The client expects a password to be associated with each share, independent of the user. This means that Samba has to work out what username the client probably wants to use. It is never explicitly sent the username. Some commercial SMB servers such as NT actually associate passwords directly with -shares in share level security, but Samba always uses the unix authentication scheme +shares in Share Level security, but Samba always uses the UNIX authentication scheme where it is a username/password pair that is authenticated, not a share/password pair.
-To gain understanding of the MS Windows networking parallels to this, one should think +To understand the MS Windows networking parallels, one should think in terms of MS Windows 9x/Me where one can create a shared folder that provides read-only or full access, with or without a password.
-Many clients send a session setup even if the server is in share -level security. They normally send a valid username but no password. Samba records -this username in a list of possible usernames. When the client -then does a tree connection it also adds to this list the name +Many clients send a session setup even if the server is in Share Level security. They +normally send a valid username but no password. Samba records 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 -in turn against these possible usernames. If a match is found +listed in the user parameter in the smb.conf file. +The password is then checked in turn against these possible usernames. If a match is found then the client is authenticated as that user. -
-The smb.conf parameter that sets Share Level Security is: +
-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. -
+ +When Samba is operating in security = domain mode, +the Samba server has a domain security trust account (a machine account) and causes +all authentication requests to be passed through to the Domain Controllers. +In other words, this configuration makes the Samba server a Domain Member server. +
Samba as a Domain Member Server
+ This method involves addition of the following parameters in the smb.conf file:
security = domain |
workgroup = MIDEARTH |
In order for this method to work, the Samba server needs to join the MS Windows NT security domain. This is done as follows: -
On the MS Windows NT domain controller, using + + +
On the MS Windows NT Domain Controller, using the Server Manager, add a machine account for the Samba server. -
Next, on the UNIX/Linux system execute:
root# net rpc join -U administrator%password
-Samba-2.2.4 and later can auto-join a Windows NT4 style Domain just by executing: +
On the UNIX/Linux system execute:
root# net rpc join -U administrator%password
+Samba-2.2.4 and later can auto-join a Windows NT4-style Domain just by executing:
root# smbpasswd -j DOMAIN_NAME -r PDC_NAME \ -U Administrator%password @@ -529,97 +516,97 @@ It is not necessary with Samba-3 to specify the DOMAI
Use of this mode of authentication does require there to be a standard UNIX account for each user in order to assign a UID once the account has been authenticated by -the remote Windows DC. This account can be blocked to prevent logons by clients other than +the remote Windows DC. This account can be blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in the /etc/passwd entry.
An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the chapter about winbind. +presented in .
- For more information of being a domain member, see the chapter about domain membership. -
+Both Samba-2.2, and Samba-3 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 -popular belief. The only thing that Active Directory in native mode -prohibits is Backup Domain Controllers running NT4. +native mode perfectly allows NT4-style Domain Members. This is contrary to +popular belief. Active Directory in native mode prohibits only the use of +Backup Domain Controllers running MS Windows NT4.
If you are using Active Directory, starting with Samba-3 you can join as a native AD member. Why would you want to do that? Your security policy might prohibit the use of NT-compatible authentication protocols. All your machines are running Windows 2000 -and above and all use Kerberos. In this case Samba as a NT4-style +and above and all use Kerberos. In this case Samba as an NT4-style domain would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos tickets. -
realm = your.kerberos.REALM |
security = ADS |
+
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 +
password server = your.kerberos.server |
+Please refer to and for more information regarding this configuration option. -
-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: -
Potential Account Lockout on MS Windows NT4/200x password servers
Lack of assurance that the password server is the one specified
Does not work with Winbind, particularly needed when storing profiles remotely
This mode may open connections to the password server, and keep them open for extended periods.
Security on the Samba server breaks badly when the remote password server suddenly shuts down
With this mode there is NO security account in the domain that the password server belongs to for the Samba server.
-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. +
+Server Security Mode is 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 drawbacks that include: +
Potential Account Lockout on MS Windows NT4/200x password servers.
Lack of assurance that the password server is the one specified.
Does not work with Winbind, which is particularly needed when storing profiles remotely.
This mode may open connections to the password server, and keep them open for extended periods.
Security on the Samba server breaks badly when the remote password server suddenly shuts down.
With this mode there is NO security account in the domain that the password server belongs to for the Samba server.
+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 -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. +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 client's connection. This allows the Samba server to use another SMB +server as the password server.
-You should also note that at the very start of all this, where the server tells the client +You should also note that at the 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 +does, 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. -That real authentication server can be another Samba server or can be a Windows NT server, -the later natively capable of encrypted password support. +parameter password server that points to the real authentication server. +The real authentication server can be another Samba server, or it can be a Windows NT server, +the latter being natively capable of encrypted password support.
-When Samba is running in server security mode it is essential that +When Samba is running in Server Security Mode it is essential that the parameter password server is set to the precise NetBIOS machine -name of the target authentication server. Samba can NOT determine this from NetBIOS name -lookups because the choice of the target authentication server is arbitrary and can not +name of the target authentication server. Samba cannot determine this from NetBIOS name +lookups because the choice of the target authentication server is arbitrary and cannot 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 +Server Security Mode is operating in what used to be known as workgroup mode. -
+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" |
-There are two ways of identifying whether or not a username and password pair was valid. +There are two ways of identifying whether or not a username and password pair is valid. One uses the reply information provided as part of the authentication messaging process, the other uses just an error code.
-The down-side of this mode of configuration is the fact that for security reasons Samba +The downside of this mode of configuration is the fact that for security reasons Samba will send the password server a bogus username and a bogus password and if the remote server fails to reject the username and password pair then an alternative mode of identification of validation is used. Where a site uses password lock out after a certain number of failed authentication attempts this will result in user lockouts.
-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. -
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, -the password is passed over the network either in plain text or encrypted, but +authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or cleartext strings for simple +password-based authentication. It should be realized that with the SMB protocol, +the password is passed over the network either in plain-text or encrypted, but not both in the same authentication request.
When encrypted passwords are used, a password that has been entered by the user is encrypted in two ways: -
An MD4 hash of the UNICODE of the password - string. This is known as the NT hash. +
An MD4 hash of the unicode of the password + string. This is known as the NT hash.
The password is converted to upper case, - and then padded or truncated to 14 bytes. This string is + 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 @@ -633,324 +620,340 @@ connection that has been dropped, the client re-establishes the connection using a cached copy of the password.
When Microsoft changed the default password mode, support was dropped for caching -of the plain text password. This means that when the registry parameter is changed -to re-enable use of plain text passwords it appears to work, but when a dropped -service connection mapping attempts to revalidate it will fail if the remote -authentication server does not support encrypted passwords. This means that it -is definitely not a good idea to re-enable plain text password support in such clients. -
-The following parameters can be used to work around the issue of Windows 9x clients -upper casing usernames and password before transmitting them to the SMB server -when using clear text authentication. +of the plain-text password. This means that when the registry parameter is changed +to re-enable use of plain-text passwords it appears to work, but when a dropped +service connection mapping attempts to revalidate, this will fail if the remote +authentication server does not support encrypted passwords. It is definitely not +a good idea to re-enable plain-text password support in such clients. +
+The following parameters can be used to work around the issue of Windows 9x/Me clients +upper-casing usernames and passwords before transmitting them to the SMB server +when using cleartext 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 +By default Samba will convert to 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 characters, 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 -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 -insensitive passwords as seen from Windows users. This will also result in longer +This means that in order for a user on a Windows 9x/Me client to connect to a Samba +server using cleartext authentication, the password level +must be set to the maximum number of upper case letters that 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 +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).
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 +Samba is used. Most attempts to apply the registry change to re-enable plain-text passwords will eventually lead to user complaints and unhappiness. -
-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 +
+We all make mistakes. It is okay to make mistakes, as long as they are made in the right places +and at the right time. A mistake that causes lost productivity is seldom tolerated, however a mistake made in a developmental test lab is expected.
Here we look at common mistakes and misapprehensions that have been the subject of discussions -on the Samba mailing lists. Many of these are avoidable by doing you homework before attempting -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 +on the Samba mailing lists. Many of these are avoidable by doing your homework before attempting +a Samba implementation. Some are the result of a misunderstanding of the English language. The +English language, which has many phrases that are potentially vague and may be highly confusing to those for whom English is not their native tongue. -
-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 -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. -
-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! -
-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. -
+
+To some the nature of the Samba security mode is obvious, but entirely +wrong all the same. It is assumed that security = server means that Samba +will act as a server. Not so! This setting means that Samba will try +to use another SMB server as its source for user authentication alone. +
+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. +
+Guess! So many others do. But whatever you do, do not think that security = user +makes Samba act as a Domain Member. Read the manufacturer's manual before the warranty expires. See + for more information. +
“ -Why does server_validate() simply give up rather than re-establishing its connection to the +Why does server_validate() simply give up rather than re-establish its connection to the password server? Though I am not fluent in the SMB protocol, perhaps the cluster server process passes along to its client workstation the session key it receives from the password 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.” +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. -
Table of Contents
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. +
Table of Contents
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. +That's okay, 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 that is already available.
-The reader is advised NOT to tackle this section without having first understood +The reader is advised not to tackle this section without having first understood and mastered some basics. MS Windows networking is not particularly forgiving of misconfiguration. Users of MS Windows networking are likely to complain of persistent niggles that may be caused by a broken network configuration. -To a great many people however, MS Windows networking starts with a domain controller -that in some magical way is expected to solve all ills. -
+To a great many people, however, MS Windows networking starts with a Domain Controller +that in some magical way is expected to solve all network operational ills. +
+The diagram in shows a typical MS Windows Domain Security +network environment. Workstations A, B and C are representative of many physical MS Windows +network clients. +
From the Samba mailing list one can readily identify many common networking issues. If you are not clear on the following subjects, then it will do much good to read the sections of this HOWTO that deal with it. These are the most common causes of MS Windows networking problems: -
Basic TCP/IP configuration
NetBIOS name resolution
Authentication configuration
User and Group configuration
Basic File and Directory Permission Control in UNIX/Linux
Understanding of how MS Windows clients interoperate in a network - environment
+
Basic TCP/IP configuration.
NetBIOS name resolution.
Authentication configuration.
User and group configuration.
Basic file and directory permission control in UNIX/Linux.
Understanding how MS Windows clients interoperate in a network + environment.
Do not be put off; on the surface of it MS Windows networking seems so simple that anyone can do it. In fact, it is not a good idea to set up an MS Windows network with inadequate training and preparation. But let's get our first indelible principle out of the -way: It is perfectly OK to make mistakes! In the right place and at -the right time, mistakes are the essence of learning. It is very much -not ok to make mistakes that cause loss of productivity and impose an avoidable financial -burden on an organisation. +way: It is perfectly okay to make mistakes! In the right place and at +the right time, mistakes are the essence of learning. It is very much not okay to make +mistakes that cause loss of productivity and impose an avoidable financial burden on an +organization.
-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 +Where is the right place to make mistakes? Only out of harm's way. If you are going to +make mistakes, then please do it 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. -
-What is the key benefit of Microsoft Domain security? +
+ +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 -grail of MS Windows NT and beyond networking. SSO allows users in a well designed network +In a word, Single Sign On, or SSO for short. To many, this is the Holy +Grail of MS Windows NT and beyond networking. SSO allows users in a well-designed network to log onto any workstation that is a member of the domain that their user account is in (or in a domain that has an appropriate trust relationship with the domain they are visiting) -and they will be able to log onto the network and access resources (shares, files, and printers) +and they will be able to log onto the network and access resources (shares, files and printers) as if they are sitting at their home (personal) workstation. This is a feature of the Domain -security protocols. +Security protocols.
-The benefits of Domain security are available to those sites that deploy a Samba PDC. + +The benefits of Domain Security are available to those sites that deploy a Samba PDC. A Domain provides a unique network security identifier (SID). Domain user and group security identifiers are comprised of the network SID plus a relative identifier (RID) that is unique to the account. User and Group SIDs (the network SID plus the RID) can be used to create Access Control Lists (ACLs) attached to network resources to provide organizational access control. UNIX systems -know only of local security identifiers. +recognize only local security identifiers.
-Network clients of an MS Windows Domain security environment must be Domain members to be -able to gain access to the advanced features provided. Domain membership involves more than just +Network clients of an MS Windows Domain Security Environment must be Domain Members to be +able to gain access to the advanced features provided. Domain Membership involves more than just setting the workgroup name to the Domain name. It requires the creation of a Domain trust account -for the workstation (called a machine account). Please refer to the chapter on -setting up samba as a domain member for more information. +for the workstation (called a machine account). Refer to +for more information.
The following functionalities are new to the Samba-3 release:
- Windows NT4 domain trusts + Windows NT4 domain trusts.
+ Adding users via the User Manager for Domains. This can be done on any MS Windows - client using the Nexus toolkit that is available from Microsoft's web site. + client using the Nexus.exe toolkit that is available from Microsoft's Web site. Samba-3 supports the use of the Microsoft Management Console for user management.
Introduces replaceable and multiple user account (authentication) - back ends. In the case where the back end is placed in an LDAP database, - Samba-3 confers the benefits of a back end that can be distributed, replicated, + backends. In the case where the backend is placed in an LDAP database, + Samba-3 confers the benefits of a backend that can be distributed, replicated and is highly scalable.
- Implements full Unicode support. This simplifies cross locale internationalisation + Implements full Unicode support. This simplifies cross locale internationalization support. It also opens up the use of protocols that Samba-2.2.x had but could not use due to the need to fully support Unicode.
-The following functionalities are NOT provided by Samba-3: +The following functionalities are not provided by Samba-3:
+ + SAM replication with Windows NT4 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa). This means samba + (i.e., a Samba PDC and a Windows NT BDC or vice versa). This means Samba cannot operate as a BDC when the PDC is Microsoft-based or - replicate account data to Windows-BDC's. + replicate account data to Windows BDCs.
- Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) - In point of fact, Samba-3 DOES have some + Acting as a Windows 2000 Domain Controller (i.e., Kerberos and + Active Directory). In point of fact, Samba-3 does have some Active Directory Domain Control ability that is at this time - purely experimental AND that is certain - to change as it becomes a fully supported feature some time - during the Samba-3 (or later) life cycle. However, Active Directory is - more then just SMB - it's also LDAP, Kerberos, DHCP and other protocols - (with proprietary extensions, of course). + purely experimental that is certain to change as it becomes a + fully supported feature some time during the Samba-3 (or later) + life cycle. However, Active Directory is more then just SMB + it's also LDAP, Kerberos, DHCP, and other protocols (with proprietary + extensions, of course). +
+ The Windows 200x/XP MMC (Computer Management) Console can not be used + to manage a Samba-3 server. For this you can use only the MS Windows NT4 + Domain Server manager and the MS Windows NT4 Domain User Manager. Both are + part of the SVRTOOLS.EXE package mentioned later.
-Windows 9x / Me / XP Home clients are not true members of a domain for reasons outlined -in this chapter. The protocol for support of Windows 9x / Me style network (domain) logons -is completely different from NT4 / Win2k type domain logons and has been officially supported +Windows 9x/Me/XP Home clients are not true members of a domain for reasons outlined +in this chapter. The protocol for support of Windows 9x/Me style network (domain) logons +is completely different from NT4/Windows 200x type domain logons and has been officially supported for some time. These clients use the old LanMan Network Logon facilities that are supported in Samba since approximately the Samba-1.9.15 series.
-Samba-3 has an implementation of group mapping between Windows NT groups +Samba-3 implements group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space). This is -discussed more fully in the chapter on group mapping. +discussed more fully in .
+ Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store -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. -
+user and Machine Trust Account information in a suitable backend datastore. +Refer to . With Samba-3 there can be multiple +backends for this. A complete discussion of account database backends can be found in +. +
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: -
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 -network, the domain controllers should be the most powerful and most capable machine in the network. -As strange as it may seem to say this here, good over all network performance dictates that -the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-Alone -(or Domain Member) servers than in the domain controllers. -
-In the case of MS Windows NT4 style domains, it is the PDC that initiates a new Domain Control database. -This forms a part of the Windows registry called the SAM (Security Account Manager). It plays a key -part in NT4 type domain user authentication and in synchronisation of the domain authentication +there are three basic types of Domain Controllers. +
Primary Domain Controller
Backup Domain Controller
ADS Domain Controller
+The Primary Domain Controller or PDC plays an important role in MS +Windows NT4. In Windows 200x Domain Control architecture, this role is held by Domain Controllers. +Folklore dictates that because of its role in the MS Windows +network, the Domain Controller should be the most powerful and most capable machine in the network. +As strange as it may seem to say this here, good overall network performance dictates that +the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-alone +(Domain Member) servers than in the Domain Controllers. +
+ +In the case of MS Windows NT4-style domains, it is the PDC that initiates a new Domain Control database. +This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key +part in NT4-type domain user authentication and in synchronization of the domain authentication database with Backup Domain Controllers.
-With MS Windows 200x Server based Active Directory domains, one domain controller initiates a potential -hierarchy of domain controllers, each with their own area of delegated control. The master domain -controller has the ability to override any down-stream controller, but a down-line controller has -control only over it's down-line. With Samba-3 this functionality can be implemented using an -LDAP based user and machine account back end. +With MS Windows 200x Server-based Active Directory domains, one Domain Controller initiates a potential +hierarchy of Domain Controllers, each with their own area of delegated control. The master domain +controller has the ability to override any downstream controller, but a downline controller has +control only over its downline. With Samba-3, this functionality can be implemented using an +LDAP-based user and machine account backend.
-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] +New to Samba-3 is the ability to use a backend database that holds the same type of data as +the NT4-style SAM database (one of the registry files)[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. -On a network segment that has a BDC and a PDC the BDC will be most likely to service network +On a network segment that has a BDC and a PDC, the BDC will most likely service network logon requests. The PDC will answer network logon requests when the BDC is too busy (high load). -A BDC can be promoted to a PDC. If the PDC is on line at the time that a BDC is promoted to -PDC, the previous PDC is automatically demoted to a BDC. With Samba-3 this is NOT an automatic -operation; the PDC and BDC must be manually configured and changes need to be made likewise. +A BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to +PDC, the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic +operation; the PDC and BDC must be manually configured and changes also need to be made.
-With MS Windows NT4, it is an install time decision what type of machine the server will be. -It is possible to change the promote a BDC to a PDC and vice versa only, but the only way -to convert a domain controller to a domain member server or a stand-alone server is to +With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be. +It is possible to promote a BDC to a PDC and vice versa. The only way +to convert a Domain Controller to a Domain Member server or a Stand-alone Server is to reinstall it. The install time choices offered are: -
Primary Domain Controller - The one that seeds the domain SAM
Backup Domain Controller - One that obtains a copy of the domain SAM
Domain Member Server - One that has NO copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.
Stand-Alone Server - One that plays NO part is SAM synchronisation, has it's own authentication database and plays no role in Domain security.
-With MS Windows 2000 the configuration of domain control is done after the server has been +
Primary Domain Controller the one that seeds the domain SAM.
Backup Domain Controller one that obtains a copy of the domain SAM.
Domain Member Server one that has no copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.
Stand-alone Server one that plays no part is SAM synchronization, has its own authentication database and plays no role in Domain Security.
+With MS Windows 2000, the configuration of Domain Control is done after the server has been installed. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active Directory domain.
-New to Samba-3 is the ability to function fully as an MS Windows NT4 style Domain Controller, -excluding the SAM replication components. However, please be aware that Samba-3 support the -MS Windows 200x domain control protocols also. + +New to Samba-3 is the ability to function fully as an MS Windows NT4-style Domain Controller, +excluding the SAM replication components. However, please be aware that Samba-3 also supports the +MS Windows 200x Domain Control protocols.
At this time any appearance that Samba-3 is capable of acting as an Domain Controller in native ADS mode is limited and experimental in nature. -This functionality should not be used until the Samba-Team offers formal support for it. +This functionality should not be used until the Samba Team offers formal support for it. At such a time, the documentation will be revised to duly reflect all configuration and 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
-
-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 +
+
+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, more commonly called Domain members.
-It should be noted that Workgroup membership involve no special configuration -other than the machine being configured so that the network configuration has a commonly used name -for it's workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this -mode of configuration there are NO machine trust accounts and any concept of membership as such -is limited to the fact that all machines appear in the network neighbourhood to be logically -grouped together. Again, just to be clear: workgroup mode does not involve any security machine +It should be noted that Workgroup membership involves no special configuration +other than the machine being configured so the network configuration has a commonly used name +for its workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this +mode of configurationi, there are no Machine Trust Accounts and any concept of membership as such +is limited to the fact that all machines appear in the network neighborhood to be logically +grouped together. Again, just to be clear: workgroup mode does not involve security machine accounts.
-Domain member machines have a machine account in the Domain accounts database. A special procedure -must be followed on each machine to affect Domain membership. This procedure, which can be done -only by the local machine Administrator account, will create the Domain machine account (if -if does not exist), and then initializes that account. When the client first logs onto the +Domain Member machines have a machine account in the Domain accounts database. A special procedure +must be followed on each machine to effect Domain Membership. This procedure, which can be done +only by the local machine Administrator account, will create the Domain machine account (if it does +not exist), and then initializes that account. When the client first logs onto the Domain it triggers a machine password change.
-When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured -as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the -Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to -the chapter on domain membership for information regarding HOW to make your MS Windows clients Domain members. +When Samba is configured as a Domain Controller, secure network operation demands that +all MS Windows NT4/200x/XP Professional clients should be configured as Domain Members. +If a machine is not made a member of the Domain, then it will operate like a workgroup +(Stand-alone) machine. Please refer to for +information regarding Domain Membership.
-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
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
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
+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.
Consistent configuration of Name Resolution[2].
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.
Network Logon Configuration (since Windows 9x/Me/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.
Roaming Profiles and System/Network policies are advanced network administration topics -that are covered in the Profile Management and -Policy Management chapters of this document. However, these are not +that are covered in the and + chapters of this document. However, these are not necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.
A Domain Controller is an SMB/CIFS server that:
Registers and advertises itself as a Domain Controller (through NetBIOS broadcasts as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast, - to a WINS server over UDP unicast, or via DNS and Active Directory) + to a WINS server over UDP unicast, or via DNS and Active Directory).
- Provides the NETLOGON service (actually a collection of services that runs over - a number of protocols. These include the LanMan Logon service, the Netlogon service, - the Local Security Account service, and variations of them) + Provides the NETLOGON service. (This is actually a collection of services that runs over + mulitple protocols. These include the LanMan Logon service, the Netlogon service, + the Local Security Account service, and variations of them.)
- Provides a share called NETLOGON + 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 -(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 -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, +It is rather easy to configure Samba to provide these. Each Samba Domain Controller must provide +the NETLOGON service that Samba calls the domain logons functionality +(after the name of the parameter in the smb.conf file). Additionally, one server in a Samba-3 +Domain must advertise itself as the Domain Master Browser[3]. +This causes the Primary Domain Controller to claim a domain-specific NetBIOS name that identifies it as a +Domain Master Browser for its given domain or workgroup. Local master browsers in the same domain or 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. -
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. +in smb.conf. An example smb.conf for acting as a PDC can be found in .
-
Example 5.1. smb.conf for being a PDC
[global] |
netbios name = BELERIAND |
workgroup = MIDEARTH |
passdb backend = ldapsam, guest |
os level = 33 |
preferred master = yes |
domain master = yes |
local master = yes |
security = user |
encrypt passwords = yes |
domain logons = yes |
logon path = \\%N\profiles\%u |
logon drive = H: |
logon home = \\homeserver\%u\winprofile |
logon script = logon.cmd |
[netlogon] |
path = /var/lib/samba/netlogon |
read only = yes |
write list = ntadmin |
[profiles] |
path = /var/lib/samba/profiles |
read only = no |
create mask = 0600 |
directory mask = 0700 |
+
Example 5.1. smb.conf for being a PDC
[global] |
netbios name = BELERIAND |
workgroup = MIDEARTH |
passdb backend = tdbsam |
os level = 33 |
preferred master = yes |
domain master = yes |
local master = yes |
security = user |
domain logons = yes |
logon path = \\%N\profiles\%u |
logon drive = H: |
logon home = \\homeserver\%u\winprofile |
logon script = logon.cmd |
[netlogon] |
path = /var/lib/samba/netlogon |
read only = yes |
write list = ntadmin |
[profiles] |
path = /var/lib/samba/profiles |
read only = no |
create mask = 0600 |
directory mask = 0700 |
-The basic options shown above are explained as follows: -
+The basic options shown in are explained as follows: +
This contains all the user and group account information. Acceptable values for a PDC - are: smbpasswd, tdbsam, ldapsam. The 'guest' entry provides needed - default accounts.
- Where is is intended to use backup domain controllers (BDCs) the only logical choice is - to use LDAP so that the passdb backend can be distributed. The tdbsam and smbpasswd files - can not effectively be distributed and therefore should not be used. -
+ are: smbpasswd, tdbsam, and ldapsam. The “guest” entry provides + default accounts and is included by default, there is no need to add it explicitly.
+ Where use of backup Domain Controllers (BDCs) is intended, the only logical choice is + to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files + cannot effectively be distributed and therefore should not be used. +
The parameters os level, preferred master, domain master, security, - encrypt passwords, domain logons play a central role in assuring domain + encrypt passwords, and domain logons play a central role in assuring domain control and network logon support.
- The os level must be set at or above a value of 32. A domain controller - must be the domain master browser, must be set in user mode security, - must support Microsoft compatible encrypted passwords, and must provide the network logon - service (domain logons). Encrypted passwords must be enabled, for more details on how - to do this, refer to the chapter on account information databases. -
- The parameters logon path, logon home, logon drive, logon script are + The os level must be set at or above a value of 32. A Domain Controller + must be the Domain Master Browser, must be set in user mode security, + must support Microsoft-compatible encrypted passwords, and must provide the network logon + service (domain logons). Encrypted passwords must be enabled. For more details on how + to do this, refer to . +
+ The parameters logon path, logon home, logon drive, and logon script are environment support settings that help to facilitate client logon operations and that help to provide automated control facilities to ease network management overheads. Please refer to the man page information for these parameters. -
- The NETLOGON share plays a central role in domain logon and domain membership support. - This share is provided on all Microsoft domain controllers. It is used to provide logon +
+ The NETLOGON share plays a central role in domain logon and Domain Membership support. + This share is provided on all Microsoft Domain Controllers. It is used to provide logon scripts, to store Group Policy files (NTConfig.POL), as well as to locate other common - tools that may be needed for logon processing. This is an essential share on a domain controller. -
- This share is used to store user desktop profiles. Eash user must have a directory at the root - of this share. This directory must be write enabled for the user and must be globally read enabled. - Samba-3 has a VFS module called 'fake_permissions' that may be installed on this share. This will - allow a Samba administrator to make the directory read only to everyone. Of course this is useful + tools that may be needed for logon processing. This is an essential share on a Domain Controller. +
+ This share is used to store user desktop profiles. Each user must have a directory at the root + of this share. This directory must be write-enabled for the user and must be globally read-enabled. + Samba-3 has a VFS module called “fake_permissions” that may be installed on this share. This will + allow a Samba administrator to make the directory read-only to everyone. Of course this is useful only after the profile has been properly created.
The above parameters make for a full set of parameters that may define the server's mode @@ -959,69 +962,69 @@ of operation. The following smb.conf parameters are th
netbios name = BELERIAND |
workgroup = MIDEARTH |
domain logons = Yes |
domain master = Yes |
security = User |
The additional parameters shown in the longer listing above just makes for -more complete explanation. -
+Samba-3 is not, and cannot act as, an Active Directory Server. It cannot 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 -only basis. Please do NOT expect Samba-3 to support these protocols. Do not depend -on any such functionality either now or in the future. The Samba-Team may remove these -experimental features or may change their behaviour. This is mentioned for the benefit of those -who have discovered secret capabilities in samba-3 and who have asked when this functionality will be -completed. The answer is: Maybe or maybe never! -
-To be sure: Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4 style -domain controllers have. Samba-3 does NOT have all the capabilities of Windows NT4, but it does have +of Active Directory Domain Controllers has been partially implemented on an experimental +only basis. Please do not expect Samba-3 to support these protocols. Do not depend +on any such functionality either now or in the future. The Samba Team may remove these +experimental features or may change their behavior. This is mentioned for the benefit of those +who have discovered secret capabilities in Samba-3 and who have asked when this functionality will be +completed. The answer is maybe or maybe never! +
+To be sure, Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4-style +Domain Controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have 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 +is not Windows Server 200x, it is not an Active Directory server. We hope this is plain and simple enough for all to understand. -
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. -
+
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. -
+
+To be completely clear: If you want MS Windows XP Home Edition to integrate with your +MS Windows NT4 or Active Directory Domain Security, understand it cannot be done. +The only option is to purchase the upgrade from MS Windows XP Home Edition to +MS Windows XP Professional. +
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 +Security facility. Unlike MS Windows 9x/Me, MS Windows XP Home Edition also completely lacks the ability to log onto a network.
-To be completely clear: If you want MS Windows XP Home Edition to integrate with your -MS Windows NT4 or Active Directory Domain security understand - IT CAN NOT BE DONE. -Your only choice is to buy the upgrade pack from MS Windows XP Home Edition to -MS Windows XP Professional. -
-Now that this has been said, please do NOT ask the mailing list, or email any of the -Samba-Team members with your questions asking how to make this work. It can't be done. +Now that this has been said, please do not ask the mailing list or email any of the +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. -
A domain and a workgroup are exactly the same in terms of network -browsing. The difference is that a distributable authentication +browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a -network. Also, different access rights can be granted to users if they +network. Also, different access rights can be granted to users if they successfully authenticate against a domain logon server. Samba-3 does this -now in the same way that MS Windows NT/2K. +now in the same way as MS Windows NT/200x.
The SMB client logging on to a domain has an expectation that every other server in the domain should accept the same authentication information. Network browsing functionality of domains and workgroups is identical and is explained in this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support. +It should be noted that browsing is totally orthogonal to logon support.
Issues related to the single-logon network model are discussed in this -section. Samba supports domain logons, network logon scripts, and user -profiles for MS Windows for workgroups and MS Windows 9X/ME clients +section. Samba supports domain logons, network logon scripts and user +profiles for MS Windows for workgroups and MS Windows 9X/ME clients, which are the focus of this section.
When an SMB client in a domain wishes to logon, it broadcasts requests for a -logon server. The first one to reply gets the job, and validates its +logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but ill advised ) to create a domain where the user -database is not shared between servers, i.e. they are effectively workgroup -servers advertising themselves as participating in a domain. This +database is not shared between servers, i.e., they are effectively workgroup +servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely involved with domains.
@@ -1029,121 +1032,119 @@ Using these features you can make your clients verify their logon via the Samba server; make clients run a batch file when they logon to the network and download their preferences, desktop and start menu.
-MS Windows XP Home edition is NOT able to join a domain and does not permit +MS Windows XP Home edition is not able to join a domain and does not permit the use of domain logons.
Before launching into the configuration instructions, it is -worthwhile to look at how a Windows 9x/ME client performs a logon: +worthwhile to look at how a Windows 9x/Me client performs a logon:
The client broadcasts (to the IP broadcast address of the subnet it is in) a NetLogon request. This is sent to the NetBIOS name DOMAIN<#1c> at the - NetBIOS layer. The client chooses the first response it receives, which + NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER.
- The client then connects to that server, logs on (does an SMBsessetupX) and + The client connects to that server, logs on (does an SMBsessetupX) and then connects to the IPC$ share (using an SMBtconX).
- The client then does a NetWkstaUserLogon request, which retrieves the name + The client does a NetWkstaUserLogon request, which retrieves the name of the user's logon script.
- The client then connects to the NetLogon share and searches for said script - and if it is found and can be read, is retrieved and executed by the client. + The client then connects to the NetLogon share and searches for said script. + If it is found and can be read, it is retrieved and executed by the client. After this, the client disconnects from the NetLogon share.
- The client then sends a NetUserGetInfo request to the server, to retrieve + The client sends a NetUserGetInfo request to the server to retrieve the user's home share, which is used to search for profiles. Since the response to the NetUserGetInfo request does not contain much more than - the user's home share, profiles for Win9X clients MUST reside in the user + the user's home share, profiles for Windows 9x clients must reside in the user home directory.
- The client then connects to the user's home share and searches for the + The client connects to the user's home share and searches for the user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.winprofile. If the profiles are found, they are implemented.
- The client then disconnects from the user's home share, and reconnects to + The client then disconnects from the user's home share and reconnects to the NetLogon share and looks for CONFIG.POL, the policies file. If this is found, it is read and implemented.
-The main difference between a PDC and a Windows 9x logon server configuration is that +The main difference between a PDC and a Windows 9x/Me logon server configuration is:
- Password encryption is not required for a Windows 9x logon server. But note + Password encryption is not required for a Windows 9x/Me logon server. But note that beginning with MS Windows 98 the default setting is that plain-text password support is disabled. It can be re-enabled with the registry - changes that are documented in the chapter on Policies. + changes that are documented in .
- Windows 9x/ME clients do not require and do not use machine trust accounts. + Windows 9x/Me clients do not require and do not use Machine Trust Accounts.
-A Samba PDC will act as a Windows 9x logon server; after all, it does provide the -network logon services that MS Windows 9x / Me expect to find. +A Samba PDC will act as a Windows 9x/Me logon server; after all, it does provide the +network logon services that MS Windows 9x/Me expect to find.
Use of plain-text passwords is strongly discouraged. Where used they are easily detected using a sniffer tool to examine network traffic. -
-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 -modes other than USER. The only security mode -which will not work due to technical reasons is SHARE -mode security. DOMAIN and SERVER -mode security are really just a variation on SMB user level security. +
+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 it is okay to configure Samba as a Domain +Controller in security modes other than user. The only security mode that will +not work due to technical reasons is share-mode security. Domain and server mode +security are really just a variation on SMB User Level Security.
Actually, this issue is also closely tied to the debate on whether -or not Samba must be the domain master browser for its workgroup -when operating as a DC. While it may technically be possible +Samba must be the Domain Master Browser for its workgroup +when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons are two distinctly different functions), it is not a good idea to do -so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS -name. This is the name used by Windows clients to locate the DC. +so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS +name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. -A DMB is a Domain Master Browser - see Domain Master Browser. -For this reason, it is very wise to configure the Samba DC as the DMB. -
-Now back to the issue of configuring a Samba DC to use a mode other -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. -99% of the time, this other host is a domain controller. Now -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! +A DMB is a Domain Master Browser see . +For this reason, it is wise to configure the Samba DC as the DMB. +
+Now back to the issue of configuring a Samba DC to use a mode other than +security = user. If a Samba host is +configured to use another SMB server or DC in order to validate user connection requests, +it is a fact that some other machine on the network (the password server) +knows more about the user than the Samba host. About 99% of the time, this other host is +a Domain Controller. Now 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, 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. -
+A machine account, typically stored in /etc/passwd, takes the form of the machine +name with a “$” appended. FreeBSD (and other BSD systems) will not create a user with a +“$” in the name.
The problem is only in the program used to make the entry. Once made, it works perfectly. -Create a user without the '$'. Then use vipw to edit the entry, adding -the '$'. Or create the whole entry with vipw if you like; make sure you use a unique User ID! -
-The UNIX tool vipw is a common tool for directly editting the /etc/passwd file. -
“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 +Create a user without the “$”. Then use vipw to edit the entry, adding +the “$”. Or create the whole entry with vipw if you like; make sure you use a unique user login ID. +
+The UNIX tool vipw is a common tool for directly editing the /etc/passwd file. +
+“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 will remove all network drive connections:
C:\> net use * /d
-Further, if the machine is already a 'member of a workgroup' that +
+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 +get this message. Change the workgroup name to something else, it does not matter what, reboot, and try again. -
“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.” +
“I joined the domain successfully but after upgrading +to a newer version of the Samba code I get the message, `The system +cannot log you on (C000019B), Please try again or consult your +system administrator when attempting to logon.'”
+ This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a change in domain SID is when the domain name and/or the server name (NetBIOS name) is changed. @@ -1151,141 +1152,142 @@ The only way to correct the problem is to restore the original domain SID or remove the domain client from the domain and rejoin. The domain SID may be reset using either the net or rpcclient utilities.
-The reset or change the domain SID you can use the net command as follows: +To reset or change the domain SID you can use the net command as follows:
root# net getlocalsid 'OLDNAME' root# net setlocalsid 'SID'
-Workstation machine trust accounts work only with the Domain (or network) SID. If this SID changes -then domain members (workstations) will not be able to log onto the domain. The original Domain SID +Workstation Machine Trust Accounts work only with the Domain (or network) SID. If this SID changes +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. -
- “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 +
+“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 +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 accounts then this would indicate that it has not worked. Ensure the domain admin user system is working.
-Alternatively if you are creating account entries manually then they +Alternately, if you are creating account entries manually then they have not been created correctly. Make sure that you have the entry -correct for the machine trust account in smbpasswd file on the Samba PDC. +correct for the Machine Trust Account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd utility, make sure that the account name is the machine NetBIOS name -with a '$' appended to it ( i.e. computer_name$ ). There must be an entry +with a “$” appended to it (i.e., computer_name$). There must be an entry in both /etc/passwd and the smbpasswd file.
-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. -
“When I attempt to login to a Samba Domain from a NT4/W2K workstation, - I get a message about my account being disabled.”
+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. +
“When I attempt to login to a Samba Domain from a NT4/W200x 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. -
“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. -
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 - client schannel, server schannel, client signing, server signing by executing: - testparm -v | more and looking for the value of these parameters. -
- Also use the Microsoft Management Console - Local Security Settings. This tool is available from the - Control Panel. The Policy settings are found in the Local Policies / Securty Options area and are prefixed by - 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
Table of Contents
-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. -
-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 +. This is normally done as an account is created. +
“Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'”
+A Domain Controller has to announce its role on the network. This usually takes a while. Be patient for up to fifteen minutes, +then try again. +
+ + +After successfully joining the domain, user logons fail with one of two messages: one to the +effect that the Domain Controller cannot be found; the other claims 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 client schannel, server schannel, client signing, server signing +by executing: +
+testparm -v | more and looking for the value of these parameters. +
+
+Also use the Microsoft Management Console Local Security Settings. This tool is available from the +Control Panel. The Policy settings are found in the Local Policies/Securty Options area and are prefixed by +Secure Channel: ..., and Digitally sign ..... +
+It is important that these be set consistently with the Samba-3 server settings. +
Table of Contents
+Before you continue reading this section, please make sure that you are comfortable +with configuring a Samba Domain Controller as described in . +
+This is one of the most difficult chapters to summarize. 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
effectively using a totally different approach. In the event that you should have a persistent
-concern that is not addressed in this book then please email
-John H Terpstra clearly setting out your requirements
-and / or question and we will do our best to provide a solution.
+concern that is not addressed in this book, please email
-Samba-3 is capable of acting as a Backup Domain Controller to another Samba Primary Domain -Controller. A Samba-3 PDC can operate with an LDAP Account backend. The LDAP backend can be + +Samba-3 is capable of acting as a Backup Domain Controller (BDC) to another Samba Primary Domain +Controller (PDC). A Samba-3 PDC can operate with an LDAP Account backend. The LDAP backend can be either a common master LDAP server, or a slave server. The use of a slave LDAP server has the -benefit that when the master is down clients may still be able to log onto the network. -This effectively gives samba a high degree of scalability iand is a very sweet (nice) solution -for large organisations. +benefit that when the master is down, clients may still be able to log onto the network. +This effectively gives Samba a high degree of scalability and is an effective solution +for large organizations. Do not use an LDAP slave server for a PDC, this may cause serious +stability and operational problems.
+ While it is possible to run a Samba-3 BDC with non-LDAP backend, the administrator will -need to figure out precisely what is the best way to replicate (copy / distribute) the -user and machine Accounts backend. +need to figure out precisely what is the best way to replicate (copy/distribute) the +user and machine accounts' backend.
-The use of a non-LDAP backend SAM database is particularly problematic because Domain member -servers and workstations periodically change the machine trust account password. The new + +The use of a non-LDAP backend SAM database is particularly problematic because Domain Member +servers and workstations periodically change the Machine Trust Account password. The new password is then stored only locally. This means that in the absence of a centrally stored -accounts database (such as that provided with an LDAP based solution) if Samba-3 is running -as a BDC, the BDC instance of the Domain member trust account password will not reach the -PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs this results in -overwriting of the SAM that contains the updated (changed) trust account password with resulting +accounts database (such as that provided with an LDAP-based solution) if Samba-3 is running +as a BDC, the BDC instance of the Domain Member trust account password will not reach the +PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs, this results in +overwriting the SAM that contains the updated (changed) trust account password with resulting breakage of the domain trust.
-Considering the number of comments and questions raised concerning how to configure a BDC -lets consider each possible option and look at the pro's and con's for each theoretical solution: -
Backup Domain Backend Account Distribution Options
- Solution: Passwd Backend is LDAP based, BDCs use a slave LDAP server -
- Arguments For: This is a neat and manageable solution. The LDAP based SAM (ldapsam) - is constantly kept up to date. -
- Arguments Against: Complexity -
- 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. -
- Arguments For: It would be a nice solution -
- Arguments Against: It does not work because Samba-3 does not support the required - protocols. This may become a later feature but is not available today. -
- Make use of rsync to replicate (pull down) copies of the essential account files -
- Arguments For: It is a simple solution, easy to set up as a scheduled job -
- Arguments Against: This will over-write the locally changed machine trust account - passwords. This is a broken and flawed solution. Do NOT do this. -
- Operate with an entirely local accounts database (not recommended) -
- Arguments For: Simple, easy to maintain -
- 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. -
+Considering the number of comments and questions raised concerning how to configure a BDC, +let's consider each possible option and look at the pros and cons for each possible solution. + lists possible design configurations for a PDC/BDC infrastructure. + + + + +
Table 6.1. Domain Backend Account Distribution Options
PDC Backend | BDC Backend | Notes/Discussion |
---|---|---|
Master LDAP Server | Slave LDAP Server | The optimal solution that provides high integrity. The SAM will be + replicated to a common master LDAP server. |
Single Central LDAP Server | Single Central LDAP Server | + A workable solution without fail-over ability. This is a useable solution, but not optimal. + |
tdbsam | tdbsam + net rpc vampire | + Does not work with Samba-3.0.0; may be implemented in a later release. The downside of this solution + is that an external process will control account database integrity. This solution may appeal to sites + that wish to avoid the complexity of LDAP. The net rpc vampire is used to + synchronize domain accounts from the PDC to the BDC. + |
tdbsam | tdbsam + rsync | + Do not use this configuration. + Does not work because the TDB files are live and data may not have been flushed to disk. + Use rsync to synchronize the TDB database files from the PDC to the BDC. + |
smbpasswd file | smbpasswd file | + Do not use this configuration. + Not an elegant solution due to the delays in synchronization. + Use rsync to synchronize the TDB database files from the PDC to the BDC. + Can be made to work using a cron job to synchronize data from the PDC to the BDC. + |
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.
-When MS Windows NT3.10 was first released, it supported an new style of Domain Control +When MS Windows NT3.10 was first released, it supported a new style of Domain Control and with it a new form of the network logon service that has extended functionality. 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. -
-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 -does not validate against the account information that has been stored in the Domain -Control database (the SAM, or Security Account Manager database) then a set of error +changed with the evolution of MS Windows NT and today provides a complex array of +services that are implemented over an intricate spectrum of technologies. +
+Whenever a user logs into a Windows NT4/200x/XP Professional Workstation, +the workstation connects to a Domain Controller (authentication server) to validate that +the username and password the user entered are valid. If the information entered +does not match account information that has been stored in the Domain +Control database (the SAM, or Security Account Manager database), a set of error codes is returned to the workstation that has made the authentication request.
-When the username / password pair has been validated, the Domain Controller +When the username/password pair has been validated, the Domain Controller (authentication server) will respond with full enumeration of the account information that has been stored regarding that user in the User and Machine Accounts database for that Domain. This information contains a complete network access profile for @@ -1296,9 +1298,10 @@ network access time limits, account validity information, machine names from whi user may access the network, and much more. All this information was stored in the SAM in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0).
+ The account information (user and machine) on Domain Controllers is stored in two files, one containing the Security information and the other the SAM. These are stored in files -by the same name in the C:\WinNT\System32\config directory. These +by the same name in the C:\Windows NT\System32\config directory. These are the files that are involved in replication of the SAM database where Backup Domain Controllers are present on the network.
@@ -1310,139 +1313,240 @@ There are two situations in which it is desirable to install Backup Domain Contr
At each remote site, to reduce wide area network traffic and to add stability to remote network operations. The design of the network, the strategic placement of - Backup Domain Controllers, together with an implementation that localises as much - of network to client interchange as possible will help to minimise wide area network + Backup Domain Controllers, together with an implementation that localizes as much + of network to client interchange as possible will help to minimize wide area network bandwidth needs (and thus costs).
-The PDC contains the master copy of the SAM. In the event that an administrator makes a -change to the user account database while physically present on the local network that -has the PDC, the change will likely be made directly to the PDC instance of the master -copy of the SAM. In the event that this update may be performed in a branch office the -change will likely be stored in a delta file on the local BDC. The BDC will then send -a trigger to the PDC to commence the process of SAM synchronisation. The PDC will then -request the delta from the BDC and apply it to the master SAM. The PDC will then contact -all the BDCs in the Domain and trigger them to obtain the update and then apply that to -their own copy of the SAM. -
-Thus the BDC is said to hold a read-only of the SAM from which -it is able to process network logon requests and to authenticate users. The BDC can +The inter-operation of a PDC and its BDCs in a true Windows NT4 environemt is worth +mentioning here. The PDC contains the master copy of the SAM. In the event that an +administrator makes a change to the user account database while physically present +on the local network that has the PDC, the change will likely be made directly to +the PDC instance of the master copy of the SAM. In the event that this update may +be performed in a branch office, the change will likely be stored in a delta file +on the local BDC. The BDC will then send a trigger to the PDC to commence the process +of SAM synchronization. The PDC will then request the delta from the BDC and apply +it to the master SAM. The PDC will then contact all the BDCs in the Domain and +trigger them to obtain the update and then apply that to their own copy of the SAM. +
+Samba-3 can not participate in true SAM replication and is therefore not able to +employ precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will +not create SAM update delta files. It will not inter-operate with a PDC (NT4 or Samba) +to synchronize the SAM from delta files that are held by BDCs. +
+Samba-3 cannot function as a BDC to an MS Windows NT4 PDC, and Samba-3 can not +function correctly as a PDC to an MS Windows NT4 BDC. Both Samba-3 and MS Windows +NT4 can function as a BDC to its own type of PDC. +
+The BDC is said to hold a read-only of the SAM from which +it is able to process network logon requests and authenticate users. The BDC can continue to provide this service, particularly while, for example, the wide area -network link to the PDC is down. Thus a BDC plays a very important role in both -maintenance of Domain security as well as in network integrity. -
-In the event that the PDC should need to be taken out of service, or if it dies, then -one of the BDCs can be promoted to a PDC. If this happens while the original PDC is on -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. -
-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 |
+network link to the PDC is down. A BDC plays a very important role in both the +maintenance of Domain Security as well as in network integrity. +
+In the event that the NT4 PDC should need to be taken out of service, or if it dies, +one of the NT4 BDCs can be promoted to a PDC. If this happens while the original NT4 PDC is on +line, it is automatically demoted to an NT4 BDC. This is an important aspect of Domain +Controller management. The tool that is used to effect a promotion or a demotion is the +Server Manager for Domains. It should be noted that Samba-3 BDCs can not be promoted +in this manner because reconfiguration of Samba requires changes to the smb.conf file. +
+Beginning with 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. +Refer to for an example of the minimum required settings. +
Example 6.1. Minimal smb.conf for a PDC in Use With a BDC LDAP Server on PDC.
workgroup = MIDEARTH |
passdb backend = ldapsam://localhost:389 |
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. -
+When configuring a master and a slave LDAP server, it is advisable to use the master LDAP server +for the PDC and slave LDAP servers for the BDCs. It is not essential to use slave LDAP servers, however, +many administrators will want to do so in order to provide redundant services. Of course, one or more BDCs +may use any slave LDAP server. Then again, it is entirely possible to use a single LDAP server for the +entire network. +
+When configuring a master LDAP server that will have slave LDAP servers, do not forget to configure +this in the /etc/openldap/slapd.conf file. It must be noted that the DN of a +server certificate must use the CN attribute to name the server, and the CN must carry the servers' +fully qualified domain name. Additional alias names and wildcards may be present in the +subjectAltName certificate extension. More details on server certificate names are in RFC2830. +
+It does not really fit within the scope of this document, but a working LDAP installation is +basic to LDAP enabled Samba operation. When using an OpenLdap server with Transport Layer Security +(TLS), the machine name in /etc/ssl/certs/slapd.pem must be the +same as in /etc/openldap/sldap.conf. The Red Hat Linux startup script +creates the slapd.pem file with hostname “localhost.localdomain.” +It is impossible to access this LDAP server from a slave LDAP server (i.e., a Samba BDC) unless the +certificate is recreated with a correct hostname. +
+Do not install a Samba PDC on a OpenLDAP slave server. Joining client machines to the domain +will fail in this configuration because the change to the machine account in the LDAP tree +must take place on the master LDAP server. This is not replicated rapidly enough to the slave +server that the PDC queries. It therfore gives an error message on the client machine about +not being able to set up account credentials. The machine account is created on the LDAP server +but the password fields will be empty. +
+Possible PDC/BDC plus LDAP configurations include: +
+ PDC+BDC -> One Central LDAP Server. +
+ PDC -> LDAP master server, BDC -> LDAP slave server. +
+ PDC -> LDAP master, with secondary slave LDAP server. +
+ BDC -> LDAP master, with secondary slave LDAP server. +
+ PDC -> LDAP master, with secondary slave LDAP server. +
+ BDC -> LDAP slave server, with secondary master LDAP server. +
+In order to have a fall-back configuration (secondary) LDAP server one would specify +the secondary LDAP server in the smb.conf file as shown in . +
+
Example 6.2. Multiple LDAP Servers in smb.conf
... |
passdb backend = ldapsam:ldap://master.quenya.org |
ldapsam:ldap://slave.quenya.org |
... |
+
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 +can be delegated. Samba-3 is not able to be a Domain Controller within an Active Directory +tree, and it cannot be an Active Directory server. This means that Samba-3 also cannot act as a Backup Domain Controller to an Active Directory Domain Controller. -
-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. +
+Every machine that is a Domain Controller for the domain MIDEARTH has to register the NetBIOS +group name MIDEARTH<#1c> with the WINS server and/or by broadcast on the local network. +The PDC also registers the unique NetBIOS name MIDEARTH<#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. -
-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 -of the machines it gets back from the queries is a domain controller and can answer logon -requests. To not open security holes both the workstation and the selected domain controller +implementation requires the Domain Master Browser to be on the same machine as the PDC. +
+Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to + for more information regarding TCP/IP network protocols and how + SMB/CIFS names are handled. +
+There are two different mechanisms to locate a domain controller, one method is used when +NetBIOS over TCP/IP is enabled and the other when it has been disabled in the TCP/IP +network configuration. +
+Where NetBIOS over TCP/IP is disabled, all name resolution involves the use of DNS, broadcast +messaging over UDP, as well as Active Directory communication technologies. In this type of +environment all machines require appropriate DNS entries. More information may be found in +. +
+An MS Windows NT4/200x/XP Professional workstation in the domain MIDEARTH that wants a +local user to be authenticated has to find the Domain Controller for MIDEARTH. It does this +by doing a NetBIOS name query for the group name MIDEARTH<#1c>. It assumes that each +of the machines it gets back from the queries is a Domain Controller and can answer logon +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. -
-Several things have to be done: +password) to the local Domain Controller for validation. +
+An MS Windows NT4/200x/XP Professional workstation in the realm quenya.org +that has a need to affect user logon authentication will locate the Domain Controller by +requerying DNS servers for the _ldap._tcp.pdc.ms-dcs.quenya.org record. +More information regarding this subject may be found in . +
+The creation of a BDC requires some steps to prepare the Samba server before +smbd is executed for the first time. These steps are outlines as follows: +
- The domain SID has to be the same on the PDC and the BDC. This used to - be stored in the file private/MACHINE.SID. This file is not created - since Samba 2.2.5. Nowadays the domain SID is stored in the file - private/secrets.tdb. Simply copying the secrets.tdb - from the PDC to the BDC does not work, as the BDC would - generate a new SID for itself and override the domain SID with this - new BDC SID.
+ The domain SID has to be the same on the PDC and the BDC. In Samba versions + pre-2.2.5, the domain SID was stored in the file private/MACHINE.SID. + The domain SID is now stored in the file private/secrets.tdb. This file + is unique to each server and can not be copied from a PDC to a BDC, the BDC will generate + a new SID at start-up. It will over-write the PDC domain SID with the newly created BDC SID. + There is a procedure that will allow the BDC to aquire the Domain SID. This is described here. +
To retrieve the domain SID from the PDC or an existing BDC and store it in the - secrets.tdb, execute: + secrets.tdb, execute:
root# net rpc getsid
+ Specification of the ldap admin dn is obligatory. + This also requires the LDAP administration password to be set in the secrets.tdb + using the smbpasswd -w mysecret. +
+ Either ldap suffix or + ldap idmap suffix must be specified in + the smb.conf file. +
+ The UNIX user database has to be synchronized from the PDC to the - BDC. This means that both the /etc/passwd and /etc/group have to be - replicated from the PDC to the BDC. This can be done manually - whenever changes are made, or the PDC is set up as a NIS master - server and the BDC as a NIS slave server. To set up the BDC as a - mere NIS client would not be enough, as the BDC would not be able to - access its user database in case of a PDC failure. NIS is by no means - the only method to synchronize passwords. An LDAP solution would work - as well. -
- The Samba password database has to be replicated from the PDC to the BDC. - As said above, though possible to synchronise the smbpasswd - file with rsync and ssh, this method is broken and flawed, and is - therefore not recommended. A better solution is to set up slave LDAP - servers for each BDC and a master LDAP server for the PDC. -
- Any netlogon share has to be replicated from the PDC to the + BDC. This means that both the /etc/passwd and + /etc/group have to be replicated from the PDC + to the BDC. This can be done manually whenever changes are made. + Alternately, the PDC is set up as an NIS master server and the BDC as an NIS slave + server. To set up the BDC as a mere NIS client would not be enough, + as the BDC would not be able to access its user database in case of + a PDC failure. NIS is by no means the only method to synchronize + passwords. An LDAP solution would also work. +
+ The Samba password database must be replicated from the PDC to the BDC. + Although it is possible to synchronize the smbpasswd + file with rsync and ssh, this method + is broken and flawed, and is therefore not recommended. A better solution + is to set up slave LDAP servers for each BDC and a master LDAP server for the PDC. +
+ The netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login scripts are changed, - or it can be done automatically together with the smbpasswd - synchronization. -
-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 |
+ or it can be done automatically using a cron job + that will replicate the directory structure in this share using a tool + like rsync. +
+Finally, the BDC has to be found by the workstations. This can be done by setting Samba as shown in . +
Example 6.3. Minimal setup for being a BDC
workgroup = MIDEARTH |
passdb backend = ldapsam:ldap://slave-ldap.quenya.org |
domain master = no |
domain logons = yes |
idmap backend = ldapsam:ldap://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.
+ + The idmap backend will redirect the winbindd utility to use the LDAP database to resolve all UIDs and GIDs for UNIX accounts.
+ Samba-3 has introduced a new ID mapping facility. One of the features of this facility is that it -allows greater flexibility in how user and group IDs are handled in respect of NT Domain User and Group -SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Linux UID and GID values +allows greater flexibility in how user and group IDs are handled in respect to NT Domain User and Group +SIDs. One of the new facilities provides for explicitly ensuring that UNIX/Linux UID and GID values 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. -
-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. -
-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 +regarding its behavior. +
+The use of the idmap backend = ldap://master.quenya/org +option on a BDC only make sense where ldapsam is used on a PDC. The purpose for an LDAP based idmap backend is +also to allow a domain-member (without its own passdb backend) to use winbindd to resolve Windows network users +and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on Domain +Member servers. +
+As this is a rather new area for Samba, there are not many examples that we may refer to.
+Updates will be published as they become available and may be found in later Samba releases or
+from the Samba web
+ +This problem will occur when the passdb (SAM) files are copied from a central +server but the local Backup Domain Controller is acting as a PDC. This results in the application of +Local Machine Trust Account password updates to the local SAM. Such updates are not copied back to the central server. The newer machine account password is then over -written when the SAM is copied from the PDC. The result is that the Domain member machine -on start up will find that it's passwords does not match the one now in the database and +written when the SAM is re-copied from the PDC. The result is that the Domain Member machine +on start up will find that its passwords do not match the one now in the database and since the startup security check will now fail, this machine will not allow logon attempts 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. -
-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. -
-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. -
+The solution is to use a more robust passdb backend, such as the ldapsam backend, setting up +a slave LDAP server for each BDC, and a master LDAP server for the PDC. +
+ +No. The native NT4 SAM replication protocols have not yet been fully implemented. +
+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. +
+ 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. @@ -1450,154 +1554,156 @@ has to be replicated to the BDC. So replicating the smbpasswd file very often is As the smbpasswd file contains plain text password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. -Ssh itself can be set up to accept only rsync transfer without requiring the user -to type a password. +ssh itself can be set up to accept only +rsync transfer without requiring the user 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 +accounts will go out of sync, resulting in a broken domain. This method is not recommended. Try using LDAP instead. -
-The simple answer is YES. Samba's pdb_ldap code supports binding to a replica +
Table of Contents
-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 +
Table of Contents
+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, -otherwise it would not be capable of offering a viable option for many users. +otherwise it would not be able to offer a viable option for many users.
-This chapter covers background information pertaining to domain membership, -Samba configuration for it, and MS Windows client procedures for joining a -domain. Why is this necessary? Because both are areas in which there exists +This chapter covers background information pertaining to Domain Membership, +the Samba configuration for it, and MS Windows client procedures for joining a +domain. Why is this necessary? Because both are areas in which there exists 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 +misinformation, incorrect understanding and a lack of knowledge. Hopefully this chapter will fill the voids. -
-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 +
+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 chapter describes the process that must be followed to make a workstation -(or another server - be it an MS Windows NT4 / 200x -server) or a Samba server a member of an MS Windows Domain security context. +(or another server be it an MS Windows NT4 / 200x +server) or a Samba server a member of an MS Windows Domain Security context.
-Samba-3 can join an MS Windows NT4 style domain as a native member server, an + +Samba-3 can join an MS Windows NT4-style domain as a native member server, an MS Windows Active Directory Domain as a native member server, or a Samba Domain -Control network. -
-Domain membership has many advantages: +Control network. Domain Membership has many advantages:
- MS Windows workstation users get the benefit of SSO + + MS Windows workstation users get the benefit of SSO.
- Domain user access rights and file ownership / access controls can be set - from the single Domain SAM (Security Account Manager) database - (works with Domain member servers as well as with MS Windows workstations - that are domain members) + Domain user access rights and file ownership/access controls can be set + from the single Domain Security Account Manager (SAM) database + (works with Domain Member servers as well as with MS Windows workstations + that are Domain Members).
- Only MS Windows NT4 / 200x / XP Professional - workstations that are Domain members - can use network logon facilities + Only MS Windows NT4/200x/XP Professional + workstations that are Domain Members can use network logon facilities.
Domain Member workstations can be better controlled through the use of Policy files (NTConfig.POL) and Desktop Profiles.
Through the use of logon scripts, users can be given transparent access to network - applications that run off application servers + applications that run off application servers.
Network administrators gain better application and user access management abilities because there is no need to maintain user accounts on any network 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) -
-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." -
-The password of a machine trust account acts as the shared secret for -secure communication with the Domain Controller. This is a security + (either NT4/Samba SAM style Domain, NT4 Domain that is backended with an + LDAP directory, or via an Active Directory infrastructure). +
+ +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.” The purpose of the machine account +is to prevent a rogue user and Domain Controller from colluding to gain access to a +domain member workstation. +
+The password of a Machine Trust Account acts as the shared secret for +secure communication with the Domain Controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group -accounts. Windows NT, 200x, XP Professional clients use machine trust -accounts, but Windows 9x / Me / XP Home clients do not. Hence, a -Windows 9x / Me / XP Home client is never a true member of a domain -because it does not possess a machine trust account, and thus has no -shared secret with the domain controller. +accounts. Windows NT/200x/XP Professional clients use machine trust +accounts, but Windows 9x/Me/XP Home clients do not. Hence, a +Windows 9x/Me/XP Home client is never a true member of a Domain +because it does not possess a Machine Trust Account, and, thus, has no +shared secret with the Domain Controller.
-A Windows NT4 PDC stores each machine trust account in the Windows Registry. +A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry. The introduction of MS Windows 2000 saw the introduction of Active Directory, -the new repository for machine trust accounts. -
-A Samba PDC, however, stores each machine trust account in two parts, +the new repository for Machine Trust Accounts. A Samba PDC, however, stores +each Machine Trust Account in two parts, 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.
The older format of this data is the smbpasswd database - which contains the UNIX login ID, the UNIX user identifier (UID), and the + that contains the UNIX login ID, the UNIX user identifier (UID), and the LanMan and NT encrypted passwords. There is also some other information in this file that we do not need to concern ourselves with here.
- The two newer database types are called ldapsam, - tdbsam. Both store considerably more data than the + The two newer database types are called ldapsam, and + tdbsam. Both store considerably more data than the older smbpasswd file did. The extra information - enables new user account controls to be used. + enables new user account controls to be implemented.
A corresponding UNIX account, typically stored in - /etc/passwd. Work is in progress to allow a + /etc/passwd. Work is in progress to allow a 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: +
+ +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 + + 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 as 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. -
-The first step in manually creating a machine trust account is to manually +
+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: - - - - +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 machines -d /dev/null -c "machine nickname" \ -s /bin/false machine_name$ root# passwd -l machine_name$
-
In the above example above there is an existing system group “machines” which is used +as the primary group for all machine accounts. In the following examples the “machines” group has +numeric GID equal 100.
+ 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:Windows 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 -home directory. For example a machine named 'doppy' would have an +with a “$” appended, will not 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:
doppy$:x:505:100:machine_nickname:/dev/null:/bin/false @@ -1605,13 +1711,13 @@ 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. +this as a Machine Trust Account.Now that the corresponding UNIX account has been created, the next step is to create the Samba account for the client containing the well-known initial -machine trust account password. This can be done using the +Machine Trust Account password. This can be done using the smbpasswd command as shown here:
@@ -1620,267 +1726,282 @@ as shown here:
where machine_name is the machine's NetBIOS -name. The RID of the new machine account is generated from the UID of +name. The RID of the new machine account is generated from the UID of the corresponding UNIX account.
- 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! -
+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 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! +
+A working add machine script script is essential +for machine trust accounts to be automatically created. This applies no matter whether +one uses automatic account creation, or if one wishes to use the NT4 Domain Server Manager. +
+ 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. -When executed in the target directory this will unpack SrvMge.exe +MS Windows NT4 workstation or MS Windows 200x/XP Professional, +the tool of choice is the package called SRVTOOLS.EXE. +When executed in the target directory it will unpack SrvMgr.exe and UsrMgr.exe (both are domain management tools for MS Windows NT4 workstation).
+ If your workstation is a Microsoft Windows 9x/Me family product you should download the Nexus.exe package from the Microsoft web site. When executed from the target directory this will unpack the same tools but for use on this platform.
Further information about these tools may be obtained from the following locations: -http://support.microsoft.com/default.aspx?scid=kb;en-us;173673 -http://support.microsoft.com/default.aspx?scid=kb;en-us;172540 +
+
Launch the srvmgr.exe (Server Manager for Domains) and follow these steps:
Procedure 7.1. Server Manager Account Machine Account Management
- From the menu select
+ From the menu select .- Click on
+ Click .- Click on the name of the domain you wish to administer in the + Click the name of the domain you wish to administer in the Select Domain panel and then click .
- Again from the menu select
+ Again from the menu select .- Select
+ Select .- In the dialog box, click on the radio button to + In the dialog box, click the radio button to Add NT Workstation of Server, then - enter the machine name in the field provided, then click the + enter the machine name in the field provided, and click the button. -
+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. -
Since each Samba machine trust account requires a corresponding UNIX account, a method +
Since each Samba Machine Trust Account requires a corresponding UNIX account, a method for automatically creating the UNIX account is usually supplied; this requires configuration of the -add machine script option in -smb.conf. This method is not required, however; corresponding UNIX +add machine script option in smb.conf. This method is not required, however, corresponding UNIX 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 |
-The procedure for making an MS Windows workstation of server a member of the domain varies -with the version of Windows: -
- When the user elects to make the client a domain member, Windows 200x prompts for +Here is an example for a Red Hat Linux system. +
[global] |
# <...remainder of parameters...> |
add machine script = /usr/sbin/useradd -d /dev/null -g 100 \ |
-s /bin/false -M %u |
+The procedure for making an MS Windows workstation or server a member of the domain varies +with the version of Windows. +
+ 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 + A Samba Administrator Account (i.e., a Samba account that has root privileges on the Samba server) must be entered here; the operation will fail if an ordinary user account is given.
- Note: For security reasons the password for this administrative account should be set - to a password that is other than that used for the root user in the - /etc/passwd. -
- 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. -
- 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. -
- If the machine trust account was created manually, on the + For security reasons, the password for this Administrator Account should be set + to a password that is other than that used for the root user in /etc/passwd. +
+ 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 in the file named in the smb.conf parameter + username map = /etc/samba/smbusers. +
+ The session key of the Samba Administrator 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. +
+ 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. - In this case, the existing machine trust account is used to join the machine + In this case, the existing Machine Trust Account is used to join the machine to the domain.
- If the machine trust account is to be created - on-the-fly, on the Identification Changes menu enter the domain - name, and check the box Create a Computer Account in the - Domain. In this case, joining the domain proceeds as above - for Windows 2000 (i.e., you must supply a Samba administrative account when + If the Machine Trust Account is to be created on-the-fly, on the Identification Changes menu enter the domain + name and check the box Create a Computer Account in the Domain. In this case, joining + the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba Administrator Account when prompted). -
Joining a Samba client to a domain is documented in - the domain member chapter. +
This mode of server operation involves the Samba machine being made a member of a domain security context. This means by definition that all user authentication will be done from a centrally defined authentication regime. -The authentication regime may come from an NT3/4 style (old domain technology) +The authentication regime may come from an NT3/4-style (old domain technology) server, or it may be provided from an Active Directory server (ADS) running on MS Windows 2000 or later.
-Of course it should be clear that the authentication back end itself could be +Of course it should be clear that the authentication backend itself could be from any distributed directory architecture server that is supported by Samba. -This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory -Server, etc. +This can be LDAP (from OpenLDAP), or Sun's iPlanet, or NetWare Directory +Server, and so on. -
-Please refer to the chapter on setting up a PDC -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. -
-
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. +
+Please refer to , for more information regarding +how to create a domain machine account for a Domain Member server as well as for +information on how to enable the Samba Domain Member machine to join the domain +and be fully trusted by it. +
lists names that have been used in the remainder of this chapter.
Table 7.1. Assumptions
NetBIOS name: | SERV1 |
Windows 200x/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 |
-as this is the name of the domain we are joining. +This is the name of the domain we are joining.
-You must also have the parameter -encrypt passwords set to yes - in order for your users to authenticate to the NT PDC. +You must also have the parameter encrypt passwords +set to yes in order for your users to authenticate to the NT PDC. +This is the defaulty setting if this parameter is not specified. There is no need to specify this +parameter, but if it is specified in the smb.conf file, it must be set to Yes.
-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 |
-These are the primary and backup domain controllers Samba +These are the primary and backup Domain Controllers Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load -among domain controllers. +among Domain Controllers.
-Alternatively, if you want smbd to automatically determine -the list of Domain controllers to use for authentication, you may +Alternately, if you want smbd to automatically determine +the list of Domain Controllers to use for authentication, you may set this line to be:
password server = * |
-This method allows Samba to use exactly the same mechanism that NT does. This -method either broadcasts or uses a WINS database in order to -find domain controllers to authenticate against. +This method allows Samba to use exactly the same mechanism that NT does. The +method either uses broadcast-based name resolution, performs a WINS database +lookup in order to find a Domain Controller against which to authenticate, +or locates the Domain Controller using DNS name resolution.
-In order to actually join the domain, you must run this command: +To join the domain, run this command:
-root# net rpc join -S DOMPDC -UAdministrator%password +root# net join -S DOMPDC -UAdministrator%password
-If the -S DOMPDC argument is not given then -the domain name will be obtained from smb.conf. -
-As we are joining the domain DOM and the PDC for that domain -(the only machine that has write access to the domain SAM database) -is DOMPDC, we use it for the -S option. -The Administrator%password is -the login name and password for an account which has the necessary -privilege to add machines to the domain. If this is successful -you will see the message: +If the -S DOMPDC argument is not given, the domain name will be obtained from smb.conf.
+The machine is joining the domain DOM, and the PDC for that domain (the only machine +that has write access to the domain SAM database) is DOMPDC, therefore use the -S +option. The Administrator%password is the login name and +password for an account that has the necessary privilege to add machines to the +domain. If this is successful, you will see the message in your terminal window the +text shown below. Where the older NT4 style domain architecture is used: +
Joined domain DOM. -or Joined 'SERV1' to realm 'MYREALM' +
+
+Where Active Directory is used: +
+Joined SERV1 to realm MYREALM. +
-in your terminal window. See the -net man page for more details. +Refer to the net man page for further information.
This process joins the server to the domain without having to create the machine trust account on the PDC beforehand.
-This command goes through the machine account password -change protocol, then writes the new (random) machine account -password for this Samba server into a file in the same directory -in which an smbpasswd file would be stored - normally: -
+This command goes through the machine account password change protocol, then writes +the new (random) machine account password for this Samba server into a file in the +same directory in which a smbpasswd file would be normally stored: +
/usr/local/samba/private/secrets.tdb +or +/etc/samba/secrets.tdb. +
-This file is created and owned by root and is not -readable by any other user. It is the key to the domain-level -security for your system, and should be treated as carefully +This file is created and owned by root and is not readable by any other user. It is +the key to the Domain-level security for your system, and should be treated as carefully as a shadow password file.
-Finally, restart your Samba daemons and get ready for -clients to begin using domain security! The way you can restart your -samba daemons depends on your distribution, but in most cases running +Finally, restart your Samba daemons and get ready for clients to begin using domain +security. The way you can restart your Samba daemons depends on your distribution, +but in most cases the following will suffice:
- root# /etc/init.d/samba restart +root# /etc/init.d/samba restart
-does the job. -
-Currently, domain security in Samba doesn't free you from +
+Currently, domain security in Samba does not 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 - attaches to your domain security Samba server, there needs +to your server. This means that if Domain user DOM\fred + attaches to your Domain Security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX -filesystem. This is very similar to the older Samba security mode -security = server, +file system. This is similar to the older Samba security mode +security = server, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would.
- Please refer to the chapter on winbind for information on a system -to automatically assign UNIX uids and gids to Windows NT Domain users and groups. +Please refer to , for information on a system +to automatically assign UNIX UIDs and GIDs to Windows NT Domain users and groups.
-The advantage to domain-level security is that the -authentication in domain-level security is passed down the authenticated +The advantage to Domain-level security is that the +authentication in Domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in 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, +as is necessary to authenticate the user and then drop the connection, thus conserving PDC connection resources.
And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such -as the user SID, the list of NT groups the user belongs to, etc. +as the user SID, the list of NT groups the user belongs to, and so on.
-Much of the text of this document -was first published in the Web magazine -LinuxWorld as the article Doing -the NIS/NT Samba. -
-This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a -Windows2000 KDC. A familiarity with Kerberos is assumed. -
-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 = your.kerberos.server |
+Much of the text of this document was first published in the Web magazine
+
+ + + + +This is a rough guide to setting up Samba-3 with Kerberos authentication against a +Windows 200x KDC. A familiarity with Kerberos is assumed. +
+You must use at least the following three options in smb.conf: +
realm = your.kerberos.REALM |
security = ADS |
# The following parameter need only be specified if present. |
# The default setting is not present is Yes. |
encrypt passwords = yes |
+In case samba cannot correctly identify the appropriate ADS server using the realm name, use the +password server option in smb.conf: +
password server = your.kerberos.server |
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 -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. -
+ + +With both MIT and Heimdal Kerberos, this is unnecessary, and may be detrimental. All ADS +domains will automatically create SRV records in the DNS zone _kerberos.REALM.NAME for +each KDC in the realm. MIT's, as well as Heimdal's, KRB5 libraries default to checking +for these records, so they will automatically find the KDCs. In addition, +krb5.conf only allows specifying a single KDC, even there if there is more +than one. Using the DNS lookup allows the KRB5 libraries to use whichever KDCs are available. +
+When manually configuring krb5.conf, the minimal configuration is:
[libdefaults] default_realm = YOUR.KERBEROS.REALM @@ -1889,92 +2010,146 @@ The minimal configuration for krb5.conf is: YOUR.KERBEROS.REALM = { kdc = your.kerberos.server } -
+
+When using Heimdal versions before 0.6 use the following configuration settings: +
+[libdefaults] + default_realm = YOUR.KERBEROS.REALM + default_etypes = des-cbc-crc des-cbc-md5 + default_etypes_des = des-cbc-crc des-cbc-md5 + + [realms] + 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. +
+With Heimdal versions earlier than 0.6.x you only can use newly created accounts +in ADS or accounts that have had the password changed once after migration, or +in case of Administrator after installation. At the +moment, a Windows 2003 KDC can only be used with a Heimdal releases later than 0.6 +(and no default etypes in krb5.conf). Unfortunatly this whole area is still +in a state of flux.
-The realm must be uppercase or you will get Cannot find KDC for -requested realm while getting initial credentials error (Kerberos +The realm must be in uppercase or you will get “Cannot find KDC for +requested realm while getting initial credentials” error (Kerberos is case-sensitive!).
-Time between the two servers must be synchronized. You will get a -kinit(v5): Clock skew too great while getting initial credentials +Time between the two servers must be synchronized. You will get a +“kinit(v5): Clock skew too great while getting initial credentials” if the time difference is more than five minutes.
+Clock skew limits are configurable in the Kerberos protocols. The default setting is +five minutes. +
You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that this reverse lookup maps to -must either be the NetBIOS name of the KDC (ie. the hostname with no -domain attached) or it can alternatively be the NetBIOS name -followed by the realm. +must either be the NetBIOS name of the KDC (i.e., the hostname with no +domain attached) or it can alternately be the NetBIOS name followed by the realm.
The easiest way to ensure you get this right is to add a /etc/hosts entry mapping the IP address of your KDC to -its NetBIOS name. If you don't get this right then you will get a +its NetBIOS name. If you do not get this correct then you will get a local error when you try to join the realm.
If all you want is Kerberos support in smbclient then you can skip -straight to Test with smbclient now. -Creating a computer account -and testing your servers -is only needed if you want Kerberos support for smbd and winbindd. -
-As a user that has write permission on the Samba private directory -(usually root) run: +directly to now. + and +are needed only if you want Kerberos support for smbd and winbindd. +
+As a user who has write permission on the Samba private directory (usually root), run:
root# net ads join -U Administrator%password
-
+
+When making a Windows client a member of an ADS domain within a complex organization, you +may want to create the machine account within a particular organizational unit. Samba-3 permits +this to be done using the following syntax: +
+root# kinit Administrator@your.kerberos.REALM
+root# net ads join “organizational_unit”
+
+
+For example, you may want to create the machine account in a container called “Servers” +under the organizational directory “Computers\BusinessUnit\Department” like this: +
+root# net ads join "Computers\BusinessUnit\Department\Servers" +
+
Samba must be reconfigured (remove config.cache) and recompiled - (make clean all install) after the Kerberos libs and headers are installed. + (make clean all install) after the Kerberos libiraries and headers files are installed.
You need to login to the domain using kinit USERNAME@REALM. USERNAME must be a user who has rights to add a machine - to the domain.
-
+ to the domain.
+ Make sure that the /etc/krb5.conf is correctly configured + for the type and version of Kerberos installed on the system. +
+
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 ? -
+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 encryption type of DES-CBC-MD5? +
+ 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. -
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. -
-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" -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. -
-“ A Windows workstation was reinstalled. The original domain machine +install, to create the right encryption types. +
+Windows 200x does not seem to create the _kerberos._udp and _ldap._tcp in +the default DNS setup. Perhaps this will be fixed later in service packs. +
+Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs). +These mappings are done by the idmap subsystem of Samba. +
+In some cases it is useful to share these mappings between Samba Domain Members, +so name->id mapping is identical on all machines. +This may be needed in particular when sharing files over both CIFS and NFS. +
To use the LDAP ldap idmap suffix, set:
ldap idmap suffix = ou=Idmap,dc=quenya,dc=org |
See the smb.conf man page entry for the ldap idmap suffix +parameter for further information.
+Do not forget to specify also the ldap admin dn +and to make certain to set the LDAP administrative password into the secrets.tdb using: +
+root# smbpasswd -w ldap-admin-password +
+In the process of adding/deleting/re-adding Domain Member machine accounts, there are +many traps for the unwary player and 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” +MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type +of problem. The real solution is often quite simple and with an understanding of how MS Windows +networking functions, it is easy to overcome. +
+“A Windows workstation was re-installed. 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 -exists on the network - I know it doesn't. Why is this failing?” +exists on the network I know it does not. 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 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 +deletion before adding that same name as a Domain Member again. The best advice is to delete +the old account and then add the machine with a new name. +
+“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 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 its 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.
@@ -1982,98 +2157,101 @@ Possible causes include:
The script does not actually exist, or could not be located in the path specified.
- Corrective Action: Fix it. Make sure that when run manually - that the script will add both the UNIX system account _and_ the Samba SAM account. + Corrective action: Fix it. Make sure when run manually + that the script will add both the UNIX system account and the Samba SAM account.
- The machine could not be added to the UNIX system accounts file /etc/passwd + The machine could not be added to the UNIX system accounts file /etc/passwd.
- Corrective Action: Check that the machine name is a legal UNIX - system account name. ie: If the UNIX utility useradd is called + Corrective action: Check that the machine name is a legal UNIX + system account name. If the UNIX utility useradd is called, 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. -
Table of Contents
-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 +
+The add machine script does not create the +machine account in the Samba backend database, it is there only to create a UNIX system +account to which the Samba backend database account can be mapped. +
Windows 2003 requires SMB signing. Client side SMB signing has been implemented in Samba-3.0. + Set client use spnego = yes when communicating + with a Windows 2003 server.
Table of Contents
+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. -
-Stand-Alone servers can be as secure or as insecure as needs dictate. They can +
+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. +Domain Security they remain a common installation.
If all that is needed is a server for read-only files, or for -printers alone, it may not make sense to affect a complex installation. +printers alone, it may not make sense to effect a complex installation. For example: A drafting office needs to store old drawings and reference -standards. No-one can write files to the server as it is legislatively -important that all documents remain unaltered. A share mode read-only stand-alone -server is an ideal solution. +standards. Noone can write files to the server as it is legislatively +important that all documents remain unaltered. A share mode read-only Stand-alone +Server is an ideal solution.
Another situation that warrants simplicity is an office that has many printers 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 +to the printers, there is no need to effect any access controls and no files will +be served from the print server. Again, a share mode Stand-alone Server makes a great solution. -
+The term Stand-alone Server means that it will provide local authentication and access control for all resources that are available from it. In general this means that there will be a -local user database. In more technical terms, it means that resources +local user database. In more technical terms, it means resources on the machine will be made available in either SHARE mode or in USER mode.
No special action is needed other than to create user accounts. Stand-alone -servers do NOT provide network logon services. This means that machines that -use this server do NOT perform a domain logon to it. Whatever logon facility -the workstations are subject to is independent of this machine. It is however -necessary to accommodate any network user so that the logon name they use will -be translated (mapped) locally on the stand-alone server to a locally known +servers do not provide network logon services. This means that machines that +use this server do not perform a domain logon to it. Whatever logon facility +the workstations are subject to is independent of this machine. It is, however, +necessary to accommodate any network user so the logon name they use will +be translated (mapped) locally on the Stand-alone Server to a locally known user name. There are several ways this can be done.
Samba tends to blur the distinction a little in respect of what is -a stand-alone server. This is because the authentication database may be -local or on a remote server, even if from the Samba protocol perspective -the Samba server is NOT a member of a domain security context. +a Stand-alone Server. This is because the authentication database may be +local or on a remote server, even if from the SMB protocol perspective +the Samba server is not a member of a domain security context.
-Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher, which maintains the unix user database) the source of authentication may reside on +Through the use of Pluggable Authentication Modules (PAM) and the name service switcher (NSSWITCH), +which maintains the UNIX-user database) the source of authentication may reside on another server. We would be inclined to call this the authentication server. This means that the Samba server may use the local UNIX/Linux system password database (/etc/passwd or /etc/shadow), may use a -local smbpasswd file, or may use -an LDAP back end, or even via PAM and Winbind another CIFS/SMB server +local smbpasswd file, or may use an LDAP backend, or even via PAM and Winbind another CIFS/SMB server for authentication. -
-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. +
+The examples, , and link linkend="SimplePrintServer"/>, +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.
-Configuration of a read-only data server that EVERYONE can access is very simple. -Here is the smb.conf file that will do this. Assume that all the reference documents -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 |
-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 -unprivileged account names to be used. Given that there is a WINS server on this network -we do use it. +Configuration of a read-only data server that everyone can access is very simple. + is the smb.conf file that will do this. Assume that all the reference documents +are stored in the directory /export, and the documents are owned by a user other than +nobody. No home directories are shared, and there are no users in the /etc/passwd +UNIX system database. This is a 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 |
+In above, the machine name is set to GANDALF, the workgroup is set to the name +of the local workgroup (MIDEARTH) so the machine will appear together with systems with +which users are familiar. The only password backend required is the “guest” backend to allow default +unprivileged account names to be used. As there is a WINS server on this networki, we of obviously make use of it.
-Configuration of a simple print server is very simple if you have all the right tools +Configuration of a simple print server is easy if you have all the right tools on your system.
Assumptions:
- The print server must require no administration + The print server must require no administration.
The print spooling and processing system on our print server will be CUPS. - (Please refer to the chapter about CUPS for more information). + (Please refer to for more information).
- All printers that the print server will service will be network - printers. They will be correctly configured, by the administrator, - in the CUPS environment. + The print server will service only network printers. The network administrator + will correctly configure the CUPS environment to support the printers.
- All workstations will be installed using postscript drivers. The printer - of choice is the Apple Color LaserWriter. + All workstations will use only postscript drivers. The printer driver + of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.
In this example our print server will spool all incoming print jobs to /var/spool/samba until the job is ready to be submitted by @@ -2082,12 +2260,12 @@ the anonymous (guest) user, two things will be required:
Enabling Anonymous Printing
The UNIX/Linux system must have a guest account. The default for this is usually the account nobody. - To find the correct name to use for your version of Samba do the + To find the correct name to use for your version of Samba, do the following:
$ testparm -s -v | grep "guest account"
- Then make sure that this account exists in your system password + Make sure that this account exists in your system password database (/etc/passwd).
The directory into which Samba will spool the file must have write @@ -2099,236 +2277,221 @@ 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 |
-
+The contents of the smb.conf file is shown in . +
+
Example 8.2. smb.conf for Anonymous Printing
# Global parameters |
[global] |
workgroup = MIDEARTH |
netbios name = GANDALF |
security = SHARE |
passdb backend = guest |
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 |
+
+ + +On CUPS-enabled systems there is a facility to pass raw data directly to the printer without +intermediate processing via CUPS print filters. Where use of this mode of operation is desired, +it is necessary to configure a raw printing device. It is also necessary to enable the raw mime +handler in the /etc/mime.conv and /etc/mime.types +files. Refer to . +
Table of Contents
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
Table of Contents
+
Table of Contents
Table of Contents
This document contains detailed information as well as a fast track guide to -implementing browsing across subnets and / or across workgroups (or domains). +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 -NOT involved in browse list handling except by way of name to address resolution. +not involved in browse list handling except by way of name to address resolution.
-MS Windows 2000 and later can be configured to operate with NO NetBIOS -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 +MS Windows 2000 and later versions can be configured to operate with no NetBIOS +over TCP/IP. Samba-3 and later versions also support this mode of operation. +When the use of NetBIOS over TCP/IP has been disabled, 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. -
-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!. -
+
+Someone once referred to the past in these words “It was the best of times, +it was the worst of times.” The more we look back, the 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 lusty features, NetBIOS is like Paterson's Curse.
-For those not familiar with botanical problems in Australia: Paterson's curse, -Echium plantagineum, was introduced to Australia from Europe during the mid-nineteenth +For those not familiar with botanical problems in Australia, Paterson's Curse, +Echium plantagineum, was introduced to Australia from Europe during the mid-nineteenth century. Since then it has spread rapidly. The high seed production, with densities of -thousands of seeds per square metre, a seed longevity of more than seven years, and an +thousands of seeds per square meter, a seed longevity of more than seven years, and an ability to germinate at any time of year, given the right conditions, are some of the features which make it such a persistent weed.
-In this chapter we explore vital aspects of SMB (Server Message Block) networking with +In this chapter we explore vital aspects of Server Message Block (SMB) networking with a particular focus on SMB as implemented through running NetBIOS (Network Basic -Input / Output System) over TCP/IP. Since Samba does NOT implement SMB or NetBIOS over -any other protocols we need to know how to configure our network environment and simply +Input/Output System) over TCP/IP. Since Samba does not implement SMB or NetBIOS over +any other protocols, we need to know how to configure our network environment and simply remember to use nothing but TCP/IP on all our MS Windows network clients.
Samba provides the ability to implement a WINS (Windows Internetworking Name Server) and implements extensions to Microsoft's implementation of WINS. These extensions -help Samba to affect stable WINS operations beyond the normal scope of MS WINS. +help Samba to effect stable WINS operations beyond the normal scope of MS WINS.
-Please note that WINS is exclusively a service that applies only to those systems -that run NetBIOS over TCP/IP. MS Windows 200x / XP have the capacity to turn off -support for NetBIOS, in which case WINS is of no relevance. Samba supports this also. +WINS is exclusively a service that applies only to those systems +that run NetBIOS over TCP/IP. MS Windows 200x/XP have the capacity to operate with +support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
-For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) +For those networks on which NetBIOS has been disabled (i.e., WINS is not required) the use of DNS is necessary for host name resolution. -
-To most people browsing means that they can see the MS Windows and Samba servers +
+To most people browsing means 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.
-What seems so simple is in fact a very complex interaction of different technologies. -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
+What seems so simple is in fact a complex interaction of different technologies. +The technologies (or methods) employed in making all of this work include: +
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. -
-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. -
-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. +an (*) are the only options that commonly may need to be modified. Even if none of these +parameters is set, nmbd will still do its job. +
+All MS Windows networking uses SMB-based messaging. SMB messaging may be implemented with or without NetBIOS. +MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing +out NetBIOS support. +
+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 +effect 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, -wherever possible nmbd should be configured on one (1) machine as the WINS +wherever possible nmbd should be configured on one machine as the WINS 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 +segment is configured with its 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 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. + +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.
-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 + +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 of the Samba-3.0.0 release. Hopefully, this will become a supported feature of one of the Samba-3 release series.
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 +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 -to affect browse list collation across all segments. Note that this means clients +remote browse sync and remote announce +to effect 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 on other subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario). +consideration (i.e., an “if all else fails” scenario).
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. -
- - - -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 -the Internet usable. DNS based host name resolution is supported by nearly all TCP/IP -enabled systems. Only a few embedded TCP/IP systems do not support DNS. -
-When an MS Windows 200x / XP system attempts to resolve a host name to an IP address +minutes to stabilize, particularly across network segments. +
+ + + +All TCP/IP-enabled systems use various forms of host name resolution. The primary +methods for TCP/IP hostname resolution involve either a static file (/etc/hosts) +or the Domain Name System (DNS). DNS is the technology that makes +the Internet usable. DNS-based host name resolution is supported by nearly all +TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS. +
+When an MS Windows 200x/XP system attempts to resolve a host name to an IP address it follows a defined path:
Checks the hosts file. It is located in - C:\WinNT\System32\Drivers\etc. + C:\Windows NT\System32\Drivers\etc.
- Does a DNS lookup + Does a DNS lookup.
- Checks the NetBIOS name cache + Checks the NetBIOS name cache.
- Queries the WINS server + Queries the WINS server.
- Does a broadcast name lookup over UDP + Does a broadcast name lookup over UDP.
- 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 + Looks up entries in LMHOSTS. It is located in + C:\Windows NT\System32\Drivers\etc. +
+ +Windows 200x/XP can register its host name with a Dynamic DNS server. You can +force register with a Dynamic DNS server in Windows 200x/XP using: +ipconfig /registerdns.
With Active Directory (ADS), a correctly functioning DNS server is absolutely essential. In the absence of a working DNS server that has been correctly configured, -MS Windows clients and servers will be totally unable to locate each other, +MS Windows clients and servers will be unable to locate each other, so 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) +the use of BIND9 is preferred for its ability to adequately support the SRV (service) records that are needed for 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 to use BIND version 8 or 9, but it will almost certainly be necessary to create service records -so that MS Active Directory clients can resolve host names to locate essential network services. +so MS Active Directory clients can resolve host names to locate essential network services. The following are some of the default service records that Active Directory requires: -
_ldap._tcp.pdc.ms-dcs.Domain
- This provides the address of the Windows NT PDC for the Domain. -
_ldap._tcp.pdc.ms-dcs.DomainTree
- Resolves the addresses of Global Catalog servers in the domain. -
_ldap._tcp.site.sites.writable.ms-dcs.Domain
- Provides list of domain controllers based on sites. -
_ldap._tcp.writable.ms-dcs.Domain
- Enumerates list of domain controllers that have the writable - copies of the Active Directory data store. -
_ldap._tcp.GUID.domains.ms-dcs.DomainTree
- Entry used by MS Windows clients to locate machines using the - Global Unique Identifier. -
_ldap._tcp.Site.gc.ms-dcs.DomainTree
- Used by MS Windows clients to locate site configuration dependent - Global Catalog server. -
+
+ This provides the address of the Windows NT PDC for the Domain. +
+ Resolves the addresses of Global Catalog servers in the domain. +
+ Provides list of Domain Controllers based on sites. +
+ Enumerates list of Domain Controllers that have the writable copies of the Active Directory datastore. +
+ Entry used by MS Windows clients to locate machines using the Global Unique Identifier. +
+ Used by MS Windows clients to locate site configuration dependent Global Catalog server. +
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 +(i.e., the machine name for each service type in operation) on start-up. +The exact method by which this name registration takes place is determined by whether or not the MS Windows client/server has been given a WINS server address, whether or not LMHOSTS lookup is enabled, or if DNS for NetBIOS name resolution is enabled, etc. @@ -2336,27 +2499,27 @@ is enabled, or if DNS for NetBIOS name resolution is enabled, etc. In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by +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 and thus WINS allows name resolution to function across routed networks.
During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local +Local Master Browser if one does not already exist. On each NetBIOS network +one machine will be elected to function as the Domain Master Browser. This +domain browsing has nothing to do with MS security Domain Control. +Instead, the Domain Master Browser serves the role of contacting each local master browser (found by asking WINS or from LMHOSTS) and exchanging browse list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election +list of all machines that are on the network. Every 11 to 15 minutes an election is held to determine which machine will be the master browser. By the nature of the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser. +most senior protocol version or other criteria, will win the election +as Domain Master Browser.
Clients wishing to browse the network make use of this list, but also depend on the availability of correct name resolution to the respective IP @@ -2366,358 +2529,318 @@ Any configuration that breaks name resolution and/or browsing intrinsics 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. -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 -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. -This mechanism could be via DNS, /etc/hosts, -and so on. -
-To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* +Samba supports a feature that allows forced synchronization 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 synchronization. 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 synchronization 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. This mechanism +could be via DNS, /etc/hosts, and so on. +
+To configure cross-subnet browsing on a network containing machines +in a WORKGROUP, not an NT Domain, you need to set up one +Samba server to be the Domain Master Browser (note that this is not the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presence of a domain master browser that makes -cross subnet browsing possible for a workgroup. -
-In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, +same machine plays both roles). The role of a Domain Master Browser is +to collate the browse lists from Local Master Browsers on all the +subnets that have a machine participating in the workgroup. Without +one machine configured as a Domain Master Browser, each subnet would +be an isolated workgroup unable to see any machines on another +subnet. It is the presence of a Domain Master Browser that makes +cross-subnet browsing possible for a workgroup. +
+In a WORKGROUP environment the Domain Master Browser must be a +Samba server, and there must only be one Domain Master Browser per +workgroup name. To set up a Samba server as a Domain Master Browser, set the following option in the [global] section -of the smb.conf file : +of the smb.conf file:
domain master = yes |
-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 |
-
-The domain master browser may be the same machine as the WINS -server, if you require. -
-Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -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 |
-
-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 -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 -be the local master browser then you can disable Samba from -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 |
-
-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 -is also the Domain master browser for that domain, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN<1B>) +The Domain Master Browser should 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 as shown in . +
+
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 necessary. +
+Next, you should ensure that each of the subnets contains a machine that can act as +a Local Master Browser for the workgroup. Any MS Windows NT/200x/XP machine should +be able to do this, as will Windows 9x/Me machines (although these tend to get +rebooted more often, so it is not such a good idea 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 as +shown in : +
+
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 +parameter sets Samba high enough so it should win any browser elections. +
+If you have an NT machine on the subnet that you wish to be the Local Master Browser, you can disable Samba from +becoming a Local Master Browser by setting the following options in the [global] section of the +smb.conf file as shown in : +
+
Example 10.3. smb.conf for not being a Master Browser
[global] |
domain master = no |
local master = no |
preferred master = no |
os level = 0 |
+
+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 is also the Domain Master Browser for that domain. Network +browsing may break if a Samba server registers the domain master browser NetBIOS name (DOMAIN<1B>) with WINS instead of the PDC.
-For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -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 |
-
-If you wish to have a Samba server fight the election with machines -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 -Forcing Samba to be the master browser -below. -
-If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -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 |
-
-Who becomes the master browser is determined by an election -process using broadcasts. Each election packet contains a number of parameters -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 -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 -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 -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 -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 -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. -
-It is possible to configure two Samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other Samba servers will -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. -
-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 -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 -workgroup that has the same name as an NT Domain. -
-When Samba is the domain master and the master browser, it will listen -for master announcements (made roughly every twelve minutes) from local -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 -startup. -
-Note that all your servers (including Samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur: +For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as Local Master Browsers as +described. To make a Samba server a Local Master Browser, set the following options in the [global] section +of the smb.conf file as shown in : +
+
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 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 refer to . +
+If you have Windows NT machines that are members of the domain on all subnets and you are +sure they will always be running, you can disable Samba from taking part in browser elections +and ever becoming a Local Master Browser by setting the following options in the +[global] section of the smb.conf file as shown in : +
+
Example 10.5. smb.conf for not being a master browser
[global] |
domain master = no |
local master = no |
preferred master = no |
os level = 0 |
+
+Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters +that determine what precedence (bias) a host should have in the election. By default Samba uses a low precedence and thus loses +elections to just about every Windows network server or client. +
+If you want Samba to win elections, set the os level +global option in smb.conf to a higher number. It defaults to zero. Using 34 would make it win +all elections every other system (except other samba systems). +
+An os level of two would make it beat Windows for Workgroups and Windows 9x/Me, but not MS Windows +NT/200x Server. An MS Windows NT/200x Server Domain Controller uses level 32. The maximum os level is 255. +
+If you want Samba to force an election on startup, set the +preferred master global option in smb.conf to yes. +Samba will then have a slight advantage over other potential master browsers that are not Perferred Master Browsers. +Use this parameter with care, as if you have two hosts (whether they are Windows 9x/Me or +NT/200x/XP or 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 +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. +
+It is possible to configure two Samba servers to attempt to become the Domain Master Browser for a domain. The first server that comes +up will be the Domain Master Browser. All other Samba servers will attempt to become the Domain Master Browser every five 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. +
+The domain master is responsible for collating the browse lists of multiple subnets so browsing can occur between subnets. You can +make Samba act as the Domain Master by setting domain master = yes +in smb.conf. By default it will not be a Domain Master. +
+Do not set Samba to be the Domain Master for a workgroup that has the same name as an NT/200x Domain. +If Samba is configured to be the Domain Master for a workgroup that is present on the same +network as a Windows NT/200x domain that has the same name, network browsing problems will +certainly be experienced. +
+When Samba is the Domain Master and the Master Browser, it will listen for master +announcements (made roughly every twelve minutes) from Local Master Browsers on +other subnets and then contact them to synchronize browse lists. +
+If you want Samba to be the domain master, you should 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 startup. +
+All servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your +clients are only using broadcasting to resolve NetBIOS names, then two things will occur:
- your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. + Local Master Browsers will be unable to find a Domain Master Browser, as they will be looking only on the local subnet.
- if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. + If a client happens to get hold of a domain-wide browse list and a user attempts to access a + host in that list, it will be unable to resolve the NetBIOS name of that host.
If, however, both Samba and your clients are using a WINS server, then:
- your local master browsers will contact the WINS server and, as long as - Samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive Samba's IP address - as its domain master browser. -
- when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - 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. -
-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. -
-Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces -option in smb.conf to configure them. -
-The remote announce parameter of + Local master browsers will contact the WINS server and, as long as Samba has registered that it is a Domain Master Browser with the WINS + server, the Local Master Browser will receive Samba's IP address as its Domain Master Browser. +
+ When a client receives a domain-wide browse list and a user attempts to access a host in that list, it will contact the WINS server to + 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. +
+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 zeros broadcast and you will probably find that browsing and name lookups will not work. +
+Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will +need to use the interfaces option in smb.conf to configure them. +
+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] ... |
where: -
- - - - is either the LMB (Local Master Browser) IP address -or the broadcast address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network, every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.
is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided. -
-
-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 +
+ + + is either the LMB (Local Master Browser) IP address or the broadcast address of the remote network. + i.e., the LMB is at 192.168.1.10, or the address could be given as 192.168.1.255 where the netmask + is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast + address of the remote network, every host will receive our announcements. This is noisy and therefore + undesirable but may be necessary if we do not know the IP address of the remote LMB. +
is optional and can be either our own workgroup or that of the remote network. If you use the + workgroup name of the remote network, our NetBIOS machine names will end up looking like + they belong to that workgroup. This may cause name resolution problems and should be avoided. +
+
+The remote browse sync parameter of +smb.conf is used to announce to another LMB that it must synchronize its NetBIOS name list with our +Samba LMB. This 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. -
+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. -eg: It registers its name directly as a unique (the type 0x03) name. +It registers its name directly as a unique (the type 0x03) name. It also registers its name if it is running the LanManager compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name.
All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any +is added to the end of the name, thus creating a 16 character name. Any name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the +character. Thus, all NetBIOS names are 16 characters long (including the name_type information).
-WINS can store these 16 character names as they get registered. A client +WINS can store these 16-character names as they get registered. A client that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS or via statically configured -lmhosts files that must reside on all clients in the +name resolution cannot be used across network segments this type of +information can only be provided via WINS or via a statically configured +lmhosts file that must reside on all clients in the absence of WINS.
-WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The +WINS also serves the purpose of forcing browse list synchronization by all +LMBs. LMBs must synchronize their browse list with the DMB (Domain Master +Browser) and WINS helps the LMB to identify its DMB. By definition this +will work only within a single workgroup. Note that the Domain Master Browser +has nothing to do with what is referred to as an MS Windows NT Domain. The later is a reference to a security environment while the DMB refers to the master controller for browse list information only.
-Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, +WINS will work correctly only if every client TCP/IP protocol stack +has been configured to use the WINS servers. Any client that has not been +configured to use the WINS server will continue to use only broadcast-based +name registration so WINS may never get to know about it. In any case, machines that have not registered with a WINS server will fail name to address 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.
-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! -
-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 : -in the [global] section add the line -
-
wins support = yes |
+Never use both wins support = yes together +with wins server = a.b.c.d +particularly not using its own IP address. Specifying both will cause nmbd to refuse to start! +
+Either a Samba Server or a Windows NT Server machine may be set up +as a WINS server. To configure a Samba Server to be a WINS server you must +add to the smb.conf file on the selected Server the following line to +the [global] section: +
+
wins support = yes |
Versions of Samba prior to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is +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. +least set the parameter to “no” on all these machines.
-Machines with wins support = yes will keep a list of +Machines configured 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 +It is strongly recommended to set up only one WINS server. Do not set the +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 -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuses to document these replication protocols, Samba cannot currently -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. -
-After the WINS server has been configured you must ensure that all + +To configure Windows NT/200x Server as a WINS server, install and configure +the WINS service. See the Windows NT/200x documentation for details. +Windows NT/200x WINS servers can replicate to each other, allowing more +than one to be set up in a complex subnet environment. As Microsoft +refuses to document the replication protocols, Samba cannot currently +participate in these replications. It is possible in the future that +a Samba-to-Samba WINS replication protocol may be defined, in which +case more than one Samba machine could be set up as a WINS server. +Currently only one Samba server should have the +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 -of this WINS server. If your WINS server is a Samba machine, fill in +of this WINS server. If your WINS server is a Samba machine, fill in the Samba machine IP address in the Primary WINS Server field of the Control Panel->Network->Protocols->TCP->WINS Server dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files : +in Windows 9x/Me or Windows NT/200x. To tell a Samba server the IP address +of the WINS server, add the following line to the [global] section of +all smb.conf files:
-
wins server = <name or IP address> |
+
wins server = <name or IP address> |
where <name or IP address> is either the DNS name of the WINS server 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 -nmbd will fail to start. +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 +nmbd will fail to start.
-There are two possible scenarios for setting up cross subnet browsing. -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 +There are two possible scenarios for setting up cross-subnet browsing. +The first details setting up cross-subnet browsing on a network containing +Windows 9x/Me, Samba and Windows NT/200x 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. -
+ 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 +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. -
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.
-Entries in wins.dat take the form of +Entries in wins.dat take the form of:
"NAME#TYPE" TTL ADDRESS+ FLAGS @@ -2728,61 +2851,61 @@ time-to-live as an absolute time in seconds, ADDRESS+ is one or more addresses corresponding to the registration and FLAGS are the NetBIOS flags for the registration.-A typical dynamic entry looks like: +A typical dynamic entry looks like this:
"MADMAN#03" 1055298378 192.168.1.2 66R-To make it static, all that has to be done is set the TTL to 0: +To make it static, all that has to be done is set the TTL to 0, like this:
"MADMAN#03" 0 192.168.1.2 66R
-Though this method works with early Samba-3 versions, there's a +Though this method works with early Samba-3 versions, there is a possibility that it may change in future versions if WINS replication is added. -
The following hints should be carefully considered as they are stumbling points for many new network administrators. -
-Do NOT use more than one (1) protocol on MS Windows machines +
+Do not use more than one protocol on MS Windows machines.
-A very common cause of browsing problems results from installing more than +A common cause of browsing problems results from installing more than one protocol on an MS Windows machine.
Every NetBIOS machine takes part in a process of electing the LMB (and DMB) every 15 minutes. A set of election criteria is used to determine the order 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. +Windows NT will be biased so the most suitable machine will predictably +win and thus retain its role.
-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 +The election process is “fought out” so to speak over every NetBIOS network +interface. In the case of a Windows 9x/Me 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/Me machine is the only one with both protocols then the LMB may be won on the NetBIOS interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will +9x/Me will insist it knows who the LMB is. Samba will then cease to function +as an LMB and thus browse list operation on all TCP/IP-only machines will fail. -
-Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and +
+Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me. +The Windows NT4, 200x, and XP use common protocols. These are roughly +referred to as the Windows NT family, but it should be recognized that 2000 and XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support +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! -
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: -
WINS: the best tool!
LMHOSTS: is static and hard to maintain.
Broadcast: uses UDP and can not resolve names across remote segments.
-Alternative means of name resolution includes: -
/etc/hosts: is static, hard to maintain, and lacks name_type info
DNS: is a good choice but lacks essential name_type info.
-Many sites want to restrict DNS lookups and want to avoid broadcast name +
+Alternative means of name resolution include: +
+Many sites want to restrict DNS lookups and avoid broadcast name resolution traffic. The name resolve order parameter is of great help here. The syntax of the name resolve order parameter is:
name resolve order = wins lmhosts bcast host |
@@ -2790,482 +2913,546 @@ 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. -
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 -list is heavily used by all SMB clients. Configuration of SMB +machines that aren't currently able to do server tasks. The browse +list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.
-MS Windows 2000 and later, as with Samba 3 and later, can be +MS Windows 2000 and later versions, as with Samba-3 and later versions, can be configured to not use NetBIOS over TCP/IP. When configured this way, it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution +configured and operative. Browsing will not work if name resolution from SMB machine names to IP addresses does not function correctly.
-Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +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. -
-Samba facilitates browsing. The browsing is supported by nmbd +that cannot be provided by any other means of name resolution. +
+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 to support domain logons and scripts is now available.
-Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to +Samba can also act as a Domain Master Browser for a workgroup. This +means that it will collate lists from Local Master Browsers into a +wide area network server list. In order for browse clients to resolve the names they may find in this list, it is recommended that both Samba and your clients use a WINS server.
-Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service. +Do not set Samba to be the Domain Master for a workgroup that has the same +name as an NT Domain. On each wide area network, you must only ever have one +Domain Master Browser per workgroup, regardless of whether it is NT, Samba +or any other type of domain master that is providing this service.
-Nmbd can be configured as a WINS server, but it is not -necessary to specifically use Samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and Samba environment on +nmbd can be configured as a WINS server, but it is not +necessary to specifically use Samba as your WINS server. MS Windows +NT4, Server or Advanced Server 200x can be configured as +your WINS server. In a mixed NT/200x server and Samba environment on a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a Samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server. +WINS server capabilities. In a Samba-only environment, it is +recommended that you use one and only one Samba server as the 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 -smb.conf man page. -
-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 +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 +smb.conf man page. +
+If something does not work, the log.nmbd file will help +to track down the problem. Try a log level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored in text form in a file called browse.dat.
-Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then -hit enter and filemanager should display the list of available shares. +If it does not work, you should still be able to +type the server name as \\SERVER in filemanager, then +press 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 -IPC$ connection that lists the shares is done as guest, and thus you must -have a valid guest account. -
-MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the +Some people find browsing fails because they do not have the global +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. +
+MS Windows 2000 and later (as with Samba) can be configured to disallow +anonymous (i.e., guest account) access to the IPC$ share. In that case, the MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse +name of the currently logged-in user to query the IPC$ share. MS Windows +9x/Me clients are not able to do this and thus will not be able to browse 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) -
+ +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.
-To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic), you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines +To see browse lists that span TCP/IP subnets (i.e., networks separated +by routers that do not pass broadcast traffic), you must set up at least +one WINS server. The WINS server acts as a DNS for NetBIOS names. This will +allow NetBIOS name-to-IP address translation to be completed by a direct +query of the WINS server. This is done via a directed UDP packet on +port 137 to the WINS server machine. The WINS server avoids the necessity +of default NetBIOS name-to-IP address translation, which is done +using UDP broadcasts from the querying machine. This means that machines on one subnet will not be able to resolve the names of machines on another subnet without using a WINS server.
Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address +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. -
-Cross subnet browsing is a complicated dance, containing multiple -moving parts. It has taken Microsoft several years to get the code +(for Windows 9x/Me and Windows NT/200x/XP, this is in the TCP/IP Properties, under Network +settings); for Samba, this is in the smb.conf file. +
+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. -Samba is capable of cross subnet browsing when configured correctly. -
- Consider a network set up as in the diagram below. -
-Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicity's sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as +Samba is capable of cross-subnet browsing when configured correctly. +
+Consider a network set up as . +
+This consists of 3 subnets (1, 2, 3) connected by two routers +(R1, R2) which do not pass broadcasts. Subnet 1 has five machines +on it, subnet 2 has four machines, subnet 3 has four machines. Assume +for the moment that all machines are configured to be in the +same workgroup (for simplicity's sake). Machine N1_C on subnet 1 +is configured as Domain Master Browser (i.e., it will collate the +browse lists for the workgroup). Machine N2_D is configured as WINS server and all the other machines are configured to register their NetBIOS names with it.
-As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine +As these machines are booted up, elections for master browsers +will take place on each of the three subnets. Assume that machine N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master +subnet 3. These machines are known as Local Master Browsers for +their particular subnet. N1_C has an advantage in winning as the +Local Master Browser on subnet 1 as it is set up as Domain Master Browser.
On each of the three networks, machines that are configured to offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will +these services. The Local Master Browser on each subnet will receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines +the machine is offering a service. This list of records is +the basis of the browse list. For this case, assume that +all the machines are configured to offer services, so all machines will be on the browse list.
-For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'. +For each network, the Local Master Browser on that network is +considered “authoritative” for all the names it receives via +local broadcast. This is because a machine seen by the Local Master +Browser via a local broadcast must be on the same network as the +Local Master Browser and thus is a “trusted” +and “verifiable” resource. Machines on other networks that +the Local Master Browsers learn about when collating their +browse lists have not been directly seen. These records are +called “non-authoritative.”
-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). +At this point the browse lists appear as shown in (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
Subnet | Browse Master | List |
---|---|---|
Subnet1 | N1_C | N1_A, N1_B, N1_C, N1_D, N1_E |
Subnet2 | N2_B | N2_A, N2_B, N2_C, N2_D |
Subnet3 | N3_D | N3_A, N3_B, N3_C, N3_D |
+
Table 10.1. Browse Subnet Example 1
Subnet | Browse Master | List |
---|---|---|
Subnet1 | N1_C | N1_A, N1_B, N1_C, N1_D, N1_E |
Subnet2 | N2_B | N2_A, N2_B, N2_C, N2_D |
Subnet3 | N3_D | N3_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. +At this point all the subnets are separate, and no machine is seen across any of the subnets.
-Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server +Now examine subnet 2. As soon as N2_B has become the Local +Master Browser it looks for a Domain Master Browser with which to synchronize +its browse list. It does this by querying the WINS server (N2_D) for the IP address associated with the NetBIOS name -WORKGROUP<1B>. This name was registered by the Domain master -browser (N1_C) with the WINS server as soon as it was booted. +WORKGROUP<1B>. This name was registered by the Domain Master +Browser (N1_C) with the WINS server as soon as it was started.
-Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This +Once N2_B knows the address of the Domain Master Browser, it +tells it that is the Local Master Browser for subnet 2 by +sending a MasterAnnouncement packet as a UDP port 138 packet. +It then synchronizes with it by doing a NetServerEnum2 call. This tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -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
Subnet | Browse Master | List | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Subnet1 | N1_C | N1_A, N1_B, N1_C, N1_D, N1_E,
+names it knows about. Once the Domain Master Browser receives
+the MasterAnnouncement packet, it schedules a synchronization
+request to the sender of that packet. After both synchronizations
+are complete the browse lists look as shown in :
+ Table 10.2. Browse Subnet Example 2
- -Servers with a (*) after them are non-authoritative names. +Servers with an (*) after them are non-authoritative names. At this point users looking in their network neighborhood on subnets 1 or 2 will see all the servers on both, users on subnet 3 will still only see the servers on their own subnet. The same sequence of events that occurred for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) +for the Local Master Browser on subnet 3 (N3_D). When it +synchronizes browse lists with the Domain Master Browser (N1_A) 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
|