Technical Notes |
|
Reflection NFS Client supports multiple concurrent NFS logons. This technical note explains how to use this advanced feature in version 13.0 or higher.
Note: The Reflection NFS Client standalone product is also included as a component of several Reflection products. For details, refer to Technical Note 3000.
For information about using this feature in Reflection NFS Client versions 10.0 through 12.x, see Technical Note 1082.
Several options are available to simplify authentication to multiple NFS hosts. Review the following information to determine which approach is best for your environment.
To configure NFS to use the user credentials from a single NFS host running PCNFSD for all NFS host access, select "Obtain user identification (UID/GID) from only this host."
Use this procedure if you use PCNFSD authentication and you don’t want to log on separately to each NFS host. With this configuration, the NFS Client logs you onto a specified primary host the first time you try to access any NFS server. This logon uses your default user name and password. (Depending on your configuration, the default user name and password may be the credentials you enter in the initial NFS logon window, saved credentials, or your Windows credentials.) If the initial logon is successful, you can access any other NFS hosts that recognize the same user identification values (UID/GID) as the primary host. For this to work as expected, UID and GID values must be synchronized throughout the network.
For non-anonymous authentication to an NFS host, NFS requires the host to be running the PCNFSD server daemon.
To use a single logon to access multiple NFS hosts:
Note: If you try to access files on a host that does not recognize your user identification information, you will be denied access. If you need to log onto a particular NFS host using a different user name and password, you can do this by mapping a drive. Use the option to "Connect using a different user name" when you map the drive.
When configuring Reflection NFS to use NIS maps for authentication, you must specify an NIS domain and server for binding. The NIS domain must be specified by name. The NIS server can be specified by name, or Reflection can be configured to broadcast (whole network or local subnet only) for the first available NIS server in the NIS domain.
To configure NIS authentication:
The credentials that the NFS client uses to log onto the NIS host depend on your configuration, and may be any of the following:
LDAP (Lightweight Directory Access Protocol) is a set of protocols used to access information directories. If LDAP is supported at your site, you can configure the NFS Client to authenticate using information stored in an LDAP directory.
Using an LDAP-enabled directory server for NFS authentication is similar to using NIS; it provides a central location for storing and accessing user and system information.
To configure LDAP authentication:
The credentials that the NFS client uses to log onto the LDAP host depend on your configuration, and may be any of the following: