HP-UX HB v13.00 Ch-20 - CIFS

HP-UX Handbook – Rev 13.00 Page 14 (of 40)
Chapter 20 CIFS
October 29, 2013
Share: \\NTSERV\PUBLIC
rw /cifs_mnt
cifslist is a command to view which shares and servers are connected and which user is logged
in. Users normally need to validate against the NT-server by using the cifslogin command to be
able to access the share.
cifslogout <server>:
A user needs to use cifslogout to end his session with a dedicated server. An option available is
"-a" which will log the user out from all their current sessions.
cifsumount {<mountpoint>|-a}; umount:
cifsmount is used to unmount a cifs filesystem. Usually you specify a mountpoint but you can as
well use -a to unmount all connected cifs filesystems. You have the -d option available to
remove an entry from the database file so that share is not remounted after restarting cifsclientd.
You can as well keep users logged in to the windows-server, if several shares are mounted, and
you only unmount one of those. This is done by the -k option.
Guest account
It is possible to setup a “guest” user in CIFS Client if you have a mount point what you want to
allow any user on the HP-UX server to access with no authentication. With the CIFS Client
product on HP-UX, if not guest access is permitted then each Unix user or process has to be
individually authenticated as a Windows/SMB user. This is different from other CIFS Client
type applications, like the OpenSource smbmount (smbfs). If a share is mounted on linux using
smbmount all unix users can access the files on the share. However, cifsclientd has a separate
authentication mechanism that verifies access permissions with the windows server where the
share is shared.
The following /etc/opt/cifsclient/cifsclient.cfg parameters are what is used to setup guest access
to a mount:
# guestPassword = "guest";
# guestRemoteUser = "guest";
The guestUser configuration solves the following problem: Each Unix user must be logged in at
the windows server, that means being authenticated as a user on the Windows/SMB server, in
order to access anything, even if the share is public. It may be impractical to log in each user if
there's a large number of Unix users who want to access a public share where access permissions
are not important. If you define a "guestRemoteUser", all Unix users that are not logged in to the
windows-server are treated as if they were the given Windows/SMB username behind
guestRemoteUser. The “guestPassword” must be the valid password for the Windows/SMB
user account specified.