auth required /lib/security/$ISA/pam_env.so

auth 

sufficient 

/lib/security/$ISA/pam_unix.so likeauth nullok

auth

sufficient /lib/security/$ISA/pam_winbind.so 

use_first_pass

auth

sufficient /lib/security/$ISA/pam_smb_auth.so 

use_first_pass 

nolocal

auth

required /lib/security/$ISA/pam_deny.so

account

required /lib/security/$ISA/pam_unix.so

account sufficient

/lib/security/$ISA/pam_winbind.so

........................

session

optional

/lib/security/$ISA/pam_mkhomedir skel=/etc/skel umask=0022

Now we can enter the user name and password on the Gnome welcome screen, 

a home directory is created, and so the complete Gnome desktop is available.

We log on using the ID:

ITSOAUSNT+AUSRES06

The login user name has the format:

.

So the Gnome desktop shows an icon with 

ITSOAUSNT+AUSRES06's home

. 

Unfortunately, it is not possible to separate the domain and user name on a 

standard Gnome installation; the winbind separator will always be visible.

Mounting Windows file shares

After enabling domain user logon, it should also be possible to use the file shares 

on the Windows servers. Our example client needs to map three different file 

shares using the same credentials. We will have to store the user credentials in 

order to use them for interactively use of the 

mount

 command. The

smbmount

command allows the use of a credentials file. For security reasons we placed this 

in root's home directory and set the file permission in a way that only root has 

access to the file. The file /root/.credentials looks like Example 6 6.

Example 6 6   Credentials file for mounting shares

username = ausres06

password = password

domain = itsoausnt

The most logical place for such a mount execution is in /etc/fstab, where it is 

possible to define the file system to smbfs ,and the file shares would be mounted 

at the same time as the local file systems.

Example 6 7   Mounting file shares in /etc/fstab

/dev/hda1            /                    reiserfs   acl,user_xattr        1 1

 Chapter 6. Client migration scenario 

121