It appears that PAM converts the full username to lowercase, resulting in certain problems with mis-matched interpretations of the username. One example of this is trying to use pam_mount to mount a share at login time (to more or less emulate login scripts under linux). pam_mount can mount shares at login time using the supplied username and password, according to a config file, which can contain wildcards. For example, the line: volume * smb granite mail /home/&/mail Would mount //granite/mail on /home/domain+username/mail (since pam_mount expands & to the username from pam), whereas Winbind (via pam_mkhomedir) has created /home/DOMAIN+username (with template homedir = /home/%D+%U). The other issue is that mail spool files are also typically lowercased. Thus, would it not be preferable for winbind to return the full username in lowercase? It is probably possible to fix pam_mount to expand a home directory, but if pam is lowercasing usernames, either pam needs to be fixed so it does not lowercase usernames, or winbind should no use uppercase in the username. Support for a default domain would actually solve this problem in most cases. -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 808 2497 ext 202 Stellenbosch Automotive Engineering http://www.cae.co.za