Step 3: Modify the Configuration

HP CIFS Server requires configuration modifications for the following functionality:

ACL Support
Case Sensitivity for the Client and Server for UNIX Extensions
DOS Attribute Mapping
Print Services for version A.01.07
Print Services for version A.01.08 (current version)
Distributed File System (DFS) Support
Configure MC/ServiceGuard High Availability (HA)
German Character Support
Japanese Character Support

Configure ACL Support (for version A.01.07)

Two ACL schemes are currently supported: unix UNIX file permissions and hpux_posix VxFS POSIX ACLs on HP-UX.

Example values are shown below:

Example one:
acl schemes = unix
This is the default ACL scheme. This ignores UNIX ACL capabilities and uses UNIX file permissions.
Example two:
acl schemes = none
This example turns off all ACL support for the share and an error will be returned whenever the client tries to get to or set ACL information on any file system on the share.
Example three:
acl schemes = hpux_posix
This example supports only VxFS POSIX ACLs on the entire share. Attempts to get or set ACLs from the client will only succeed if VxFS POSIX ACLs are supported on that file system. If only UNIX permissions are supported, attempts to get or set ACLs from the client will fail.
Example four:
acl schemes = hpux_posix unix
HP CIFS will attempt to use VxFS POSIX ACLs. If ACLs are not present, it will use UNIX permissions.

Configure ACL Support (for version A.01.08)

HP CIFS Server, version A.01.08, provides a share level variable called “nt acl support.” The possible values for this variable are “yes” and “no.” This variable defaults to “yes.” Using this variable, users can turn on/off ACL support on a per-share basis. Refer to chapter 3 in this manual for more information about ACLs.




	IMPORTANT: VxFS POSIX ACL file permissions only work when JFS 3.3 or disk layout version 4 is installed on your system. Learn how to install JFS 3.3 on HP-UX 11.0 in the HP JFS 3.3 and HP OnLineJFS 3.3 Release Notes (MPN B3929-90007), located at www.docs.hp.com. Learn about installing and upgrading disk layout versions in the HP JFS 3.3 and HPOnLineJFS 3.3 VERITAS File System 3.3 System Administrator’s Guide (MPN B3929-90011) also located at www.docs.hp.com.

Configure Case Sensitivity

By default, the HP CIFS Server is configured to be case insensitive, like DOS and NT.




	NOTE: HP recommends that when using CIFS Extensions for UNIX, both the CIFS Client and Server be configured to be case sensitive.

For the CIFS Server, edit the server configuration file: /etc/opt/samba/smb.conf as follows.

case sensitive = yes

For the CIFS Client, in the /etc/opt/cifsclient/cifsclient.cfg file, ensure the following default is set:

caseSensitive = yes

Configure DOS Attribute Mapping

There are three parameters, map system, map hidden, and map archive, that can be configured in Samba to map DOS file attributes to owner, group, and other execute bits in the UNIX file system.

When using the CIFS Client, you may want to have all three of these parameters turned off. If the map archive parameter is on, any time a user writes to a file, the owner execute permission will be set. This is usually not desired behavior for HP CIFS clients or UNIX clients in general.

By default, map system and map hidden are off, and map archive is on.

To turn map archive off, modify /etc/opt/samba/smb.conf as follows:

map archive = no

Configuring Print Services for HP CIFS Version A.01.07

This section provides information about configuring Print Services on systems running HP CIFS version A.01.07. Please refer to the next section if you are running HP CIFS version A.01.08.

Configure Print Services

The minimal printing setup is shown below. Refer to chapter 7 in Using Samba for more detailed information on how to set up printing in Samba servers.

To configure a printer share, modify /etc/opt/samba/smb.conf as follows:

printable=yes
printer=printer_name_string

Where printer_name_string is the name of an HP-UX-defined printer under the control of the LP spooler.

Configure A Printer Share

This is a special share to automatically create printing services. Refer to chapter 7 in Using Samba for more detailed information on how to set up printing in Samba servers.If you create a share named [printers] in the smb.conf file, the server will automatically read in your printer capabilities file and create a printing share for each printer that appears in that file.

Add the following information to the global and printers sections of the smb.conf file:

[printers]
printable=yes

Manually Set Up Printer Drivers

Each client needs to install the appropriate driver for each printer it wants to use. Refer to chapter 7 in Using Samba for more detailed information on how to set up printing in Samba servers. Invoke the Windows Add Printer Wizard dialog by double-clicking on the printer icon in the Network Neighborhood.

Enter the name of the printer. If you selected an uninstalled printer, Windows will ask you to select the printer manufacturer and model.

Windows should load the appropriate driver.

Automatically Set Up Printer Drivers

Printer drivers can be automatically set up for a specific printer. There are four steps:

Install the drivers for the printer on a Windows client.
Create a printer definition file from the information on a Windows machine.
Create a PRINTER$ share where the resulting driver files can be placed.
Modify the smb.conf file

Refer to chapter 7 in Using Samba for more detailed information on how to set up printing in Samba servers.

Install Printer Drivers.

Install the drivers using a Windows 95/98 client only. Other versions of Windows clients will be supported in future releases. The printer does not have to be attached to the machine to install the drivers.This step is getting the appropriate driver files into the Windows directory.

Go to the Printers windows of My Computer and double-click on the Add Printer icon.

Follow the Add Printer Wizard dialogs, providing the name or manufacturer and model of the printer.

Create a Printer Definition File.

Copy the following four files from a Windows client:

C:\WINDOWS\INF\MSPRINT.INF
C:\WINDOWS\INF\MSPRINT2.INF
C:\WINDOWS\INF\MSPRINT3.INF
C:\WINDOWS\INF\MSPRINT4.INF

These files contain specific printer driver files. If the printer driver starts with the letter A-K, use either MSPRINT or MSPRINT3. If it begins with L-Z, user MSPRINT2 or MSPRINT4 in the next step.

Use the make_printerdef script located in /opt/samba/bin Directory and the appropriate printer driver INF file to create a printer definition file:

$make_printerdef MSPRINT3.INF HP DeskJet 560C Printer printers.def

Create a PRINTER$ Share.

Create a PRINTER$ share in the smb.conf file that points to an empty directory on the CIFS server as follows:

[PRINTER$]
path = /opt/samba/print

This is where the resulting driver files will be placed.

Copy the files noted in step 2 to this location. Typically these files can be found in the C:\WINDOWS\SYSTEM directory.

Copy the printers.def file that you created in step 2 to this location as well.

Modify the smb.conf file.

Modify the smb.conf file by adding three options:

Printer driver
Printer driver file
Printer driver location

Example smb.conf entries:

[global]
printer driver file = /opt/samba/print/printers.def

[hpdeskjet]
printer driver=HP DeskJet 560C Printer
printer driver=Hp DeskJet 560C Printer
printer driver location=\\%L\PRINTERS$

Configuring Print Services for HP CIFS Version A.01.08

This section provides information about configuring Print Services on systems running HP CIFS version A.01.08. Please refer to the previous section if you are running HP CIFS version A.01.07.

These enhancements are new for version A.01.08. The HP CIFS Server now provides the following NT printing functionality:

Printer driver files may be downloaded to Windows NT, 2000 and XP clients that do not have them
Printer driver files may be uploaded using the Windows NT/XP/2000 Add Printer wizard
Support for NT Access Control Lists (ACL) on printer objects

Information about setting up and configuring each of the Print Services (except ACLs) is shown in the following sections. Information about configuring ACL Support is discussed in a previous section.

Configuring a [printers] share

The following is a minimal printing setup. Use either one of the following two procedures to create a [printers] share:

SWAT (Samba Administration Tool)
-or-
Create a [printers] share in the /etc/opt/samba/smb.conf file. Refer to the following example:
[hpdeskjet]
path = /tmp
printable = yes
Where “hpdeskjet” is the name of the printer to be added.

Creating a [printers] share

Configure a [printers] share in the /etc/opt/samba/smb.conf file. Refer to the following example:

[printers]
path = /tmp
printable = yes
browseable = no

This share is required if you want the printer’s list to be displayed in SWAT, which is not defined in the smb.conf file, but exists on the HP CIFS Server. If this share is not defined, the printer’s list will display only those printer shares which are defined in the smb.conf file.

Setup Server for automatically uploading printer driver files

In order to add a new driver to your Samba host using version A.01.08 of the software, one of two conditions must hold true:

The account used to connect to the Samba host must have a uid of 0 (i.e. a root account), or...
The account used to connect to the Samba host must be a member of the printer admin list. This will require a [global] smb.conf parameter as follows:
printer admin = netadmin

The connected account must still possess access to add files to the subdirectories beneath [print$]. Keep in mind that all files are set to ‘read only’ by default, and that the ‘printer admin =’ parameter must also contain the names of all users or groups that are going to be allowed to upload drivers to the server, not just ‘netadmin’.

The following is an example of the other parameters required:

Create a [print$] share in the smb.conf file that points to an empty directory named “/etc/opt/samba/printers” on the HP CIFS Server. Refer to the following example:
[print$]
path = /etc/opt/samba/printers
browseable = yes
guest ok = yes
read only = yes
write list = netadmin
In this example, the parameter “write list” specifies that administrative lever user accounts will have write access for updating files, on the share.
Create the subdirectory tree, under the [print$] share, for each architecture that needs to be supported. Refer to the following example:
cd /etc/opt/samba/printers
mkdir W32X86
mkdir Win40
There are two possible locations (subdirectories) for keeping driver files, depending upon what version of Windows the files are for:
For Windows NT, XP or Windows 2000 driver files, the files will be stored in the /etc/opt/samba/printers/W32X86 subdirectory.
For Windows 9x driver files, the files will be stored in the /etc/opt/samba/printers/Win40/0 subdirectory.

Setup Client for automatically uploading of printer drivers

Printer driver files can be automatically uploaded from disk to the printers on a HP CIFS Server. Here are the steps:

Invoke the Windows Add Printer Wizard dialog by double-clicking on the printer icon in Network Neighborhood.
Enter the printer share name for an installed printer on the HP CIFS Server. Viewing the printer properties which has the default driver assigned will result in the error message:
Device settings can not be displayed. The driver for the specified printer is not installed, only spooler properties will be displayed. Do you want to install the driver now?
Click “yes” in the error dialog and the printer properties window will be displayed, with an APW.
Select the printer driver e.g. hp LaserJet 5i. You will be asked for the driver files. Give the path where the driver files are located. The driver files will be uploaded from the disk, and stored into the subdirectories under the [print$] share.

Migrating Printing Services From version A.01.07 to A.01.08

The following are some typical reasons for migrating from a HP CIFS Server, version A.01.07, to version A.01.08:

If you do not intend to use the new Windows NT/XP/2000 print driver support feature, nothing should be done. All of the existing configuration parameters for printer services will continue to work the same way.
If you want to take advantage of the new NT/XP/2000 printer driver support, but do not want to migrate the Windows 9x drivers to the new setup, then use the existing printers.def file.
If you install a Windows 9x driver for a printer on a HP CIFS Server, the new setup information will take precedence and the three old parameters (printer driver, printer driver file and printer driver location) will be ignored.
If you have a printer installed on a HP CIFS Server version A.01.07 or below, and you migrate to Server version A.01.08, you must reboot the Windows client in order to make the printer work under version A.01.08.

Setting Up Distributed File System (DFS) Support

This section will provide the procedures for:

Setting up a DFS Tree on a HP CIFS Server
Setting up DFS Links in the DFS root directory on a HP CIFS Server




	NOTE: HP does not recommend filesharing of the root. Only subdirectories under the root should be set up for filesharing.

Setting Up a DFS Tree on a HP CIFS Server

After the DFS Tree is set up using this procedure, users on DFS clients can browse the DFS tree located on the HP CIFS Server at \\servername\DFS.

Select a HP CIFS Server to act as the Distributed File System (DFS) root directory.
Configure a HP CIFS server as a DFS server by modifying the smb.conf file to set the global parameter host msdfs to yes. Example:
[global]
host msdfs = yes
Create a directory to act as a DFS root on the HP CIFS Distributed File System (DFS) Server.
Create a share and define it with the parameter path = directory of DFS root in the smb.conf file. Example:
[DFS]
path = /export/dfsroot
Modify the smb.conf file and set the msdfs root parameter to yes. Example:
[DFS]
path = /export/dfsroot
msdfs root = yes

Setting Up DFS Links in the DFS Root Directory on a HP CIFS Server

A Distributed File System (DFS) root directory on a HP CIFS Server can host DFS links in the form of symbolic links which point to other servers.

Before setting up DFS links in the DFS root directory, you should set the permissions and ownership of the root directory so that only designated users can create, delete or modify the DFS links.

Symbolic link names should be all lowercase. All clients accessing a DFS share should have the same user name and password.

An example for setting up DFS links follows:

Use the ln command to set up the DFS links for “linka” and “linkb” on the /export/dfsroot directory. Both “linka” and “linkb” point to other servers on the network. Example commands:
cd /export/dfsroot
chown root /export/dfsroot
chmod 775 /export/dfsroot
ln -S msdfs:serverA\\shareA linka
ln -S msdfs:serverB\\shareB serverC\\shareC linkb
If you use the ls -l command on the /export/dfsroot directory, it should show an output similar to this one:
lrwxrwxrwx l root sys 24 Oct 30 10:20
linka -> msdfs:serverA\\shareA
lrwxrwxrwx l root sys 30 Oct 30 10:25
linkb -> msdfs:serverB\\shareB, serverC\\shareC
In this example, “serverC” is the alternate path for “linkb”. Because of this, if “serverB” goes down, “linkb” can still be accessed from “serverC”. “linka” and “linkb” are share names. Accessing either one will take users directly to the appropriate share on the network.
Refer to the following screen snapshot for an example:

Figure 2-1 Link Share Names Example

MC/ServiceGuard High Availability Support

Highly Available HP CIFS Server allows the HP CIFS Server product to run on an MC/ServiceGuard cluster of nodes. MC/ServiceGuard allows you to create high availability clusters of HP 9000 server computers.

Template files for version A.01.08 have been revised to allow any number of cluster nodes and other advantages over previous schemes.

Follow the configuration procedures provided in Chapter 6.

Configure for German Character Support

Modify the parameters below in the smb.conf file for German character support:

character set = ISO8859-1
client code page = 850

In order to view the file and directory names and contents correctly from the UNIX side, you must set the locale to ISO 8859-1 as follows:

export LANG=de_DE.iso88591

Refer to the Internationalization section later in this chapter for more detailed information.

Configure for Japanese Character Support

To enable HP CIFS Japanese capabilities, start HP CIFS with the smb.conf variables set as follows:

codingsystem = SJIS
client code page = 932

In order to view the file and directory names and contents correctly from the UNIX side, you must set the locale to Shift-JIS like this:

export LANG=ja_JP.SJIS