This page is a part of ProNFS online Help Manual.
|15. Network File System Client (NFS-Client)||< previous | content | next >|
To make the NFS-Client settings, you can double-click on the NFS Client Settings icon in the NFS Client Programs' folder:
This presents you with a dialog of several tab windows that allow you to view and modify the NFS-Client settings. They are described below.
When you click on the Default button in the dialog box, all parameters will be initialised to their default values.
The Save as button allows you to save the current settings from the box to a file with the standard Save As window. The Open button allows you to choose the settings file and load it in the box with the standard Open window.
By clicking Apply, the current settings in the dialog box will take effect immediately.
You can cancel any changes you have made to the dialog box and close it by pressing Cancel.
This tab allows you to choose a mode for requesting NFS servers. You can also manage an NFS Server List for specific hosts.
If this check box is enabled, then, to locate all available remote NFS servers in LAN, broadcast messages will be sent (in LAN only).
If this check box is enabled, then remote NFS servers specified in the list will only be requested (no matter in LAN or WAN).
If both the check boxes are disabled, then, when you want to mount an exported file system, the prompt dialog will appear for you to enter the IP address or host name to check accessibility of the NFS server (that will become the first item in the list).
If both the check boxes are enabled, then broadcast requests are first sent, followed by the NFS Server List requests (resulting in My Network Places items).
Use this button to change the tab into its editing form (see the next section). This form allows you to insert a new NFS server into the Remote NFS Server list. Or you can select an NFS server on the list and then edit its parameters displayed.
If this check box is disabled, then IP addresses of NFS servers are displayed with corresponding host names. This feature helps prevent you from timeouts because of possible DNS accessibility problems.
The Use UDP and Use TCP check boxes in the Transport group box let you enable the transport protocols NFS-Client will use. Auto Select will try to use TCP first, and then UDP (if an NFS server fails to support TCP).
The Use NFS2 and Use NFS3 check boxes in the NFS Protocol group box let you enable the NFS protocols NFS-Client will use. Auto Select will try to use NFS3 first, and then NFS2 (if an NFS server fails to support NFS3).
The Use WebNFS check box enabled allows NFS-Client to use the WEBNFS protocol for mounting a remote NFS. In the Web NFS alias entry field, you specify a name for a shared directory mounted with the WEBNFS protocol. Using the WEBNFS protocol, you can mount a shared directory directly (i.e., not using protocols PORTMAP and MOUNT).
To remove an NFS server from the list, highlight it and press the Remove button.
You can press Add to add an NFS server (with parameters specified) to the current list.
Pressing Set sets up new values of parameters specified for the current NFS server.
Pressing Details closes the Details group box with no changes and returns you to the main form of the tab.
In this edit field, you can enter an IP address or a host name for the NFS server you want to request.
If this check box is disabled, then you will perform NFS operations through direct insecure connection to the NFS server you select when mounting shared NFS resources.
If this check box is enabled, then you will be prompted to choose one of secure connection channels (using the SSH2 protocol) previously established between your PC and a remote SSH server. In this mode, NFS server must be in the NFS Server list and be accessible from the SSH server.
If this check box is enabled, then the NFS server specified will define ports for you to use.
If this check box is disabled, then you are prompted to define the following data that the NFS server specified will use:
Every NFS server in the list is shown with those values that you assigned to it.
You can choose one of the following authentication methods that NFS-Client will use under your MS Windows system:
This method allows you to directly specify the UserID and GroupID values that will be used for mounting to UNIX systems (without using PCNFSd). If the user exists in several groups, they can be specified in the Other Group ID field with the space or comma characters as separators.
Select the Ask Uid/Gid for each connecting attempt check box if you want to enter UID/GID for each new connection. Then you will be prompted to specify new UserID, GroupID, and Other Group ID values that will be used for mounting to UNIX systems.
You must enter proper UserID and GroupID values for mounting an exported resource, or you will be prompted to specify them (e.g., if access denied).
If you choose this method, then User Name and Password first entered when logging in will be used to authenticate the user (and to obtain the UserID and GroupID values).
When the authentication server entered in the PCNFSd Authentication Server field successfully authenticates you, then it will allow you to access exported resources, and your UserID and GroupID values (obtained by PCNFSd) will be used for mounting.
If authentication failed (the server does not respond, permission is denied, etc), then the default UserID and GroupID values displayed will be used to access your network resources.
If you want to be asked for authentication immediately after the user logs in, enable the Use NFS Authentication during MS Windows Login check box.
Select the Ask Authentication for each connecting attempt check box if you want to enter your authentication data for each new connection.
In the dialog box that comes up, you can use the Anonymous button that corresponds to UID=-2 and GID=-2 for Unix authentication.
NFS-Client incorporates support for accessing LDAP-based directories, getting information from LDAP servers about the services provided, and using corresponding services as needed. It is based on Lightweight Directory Access Protocol (LDAP).
The LDAP Authentication mode was implemented to access LDAP Active Directory Servers of MS Windows 2003 R2 Standard Edition and Enterprise Edition.
LDAP Active Directory of MS Windows 2003 R2 Standard Edition and Enterprise Edition have different Schemas and so require additional data for NFS-Client to authenticate you.
For LDAP Authentication, you need to fill in the following fields in the LDAP tab
that comes up:
- Authentication Server
- UserName Attribute Name
- Uid Attribute Name
- Gid Attribute Name
If LDAP Server is Server2003 R2 Standard Edition (Win2K3 AD Enterprise):
- UserName Attribute Name = "uid"
- Uid Attribute Name = "uidNumber"
- Gid Attribute Name = "gidNumber"
If LDAP Server is Server2003 R2 Enterprise Edition (Win2K3 AD Standard):
- UserName Attribute Name = msSFU30Name
- Uid Attribute Name = msSFU30UidNumber
- Gid Attribute Name = msSFU30GidNumber
When the LDAP evaluation time is over or the xwpldap.dll file is absent, the corresponding LDAP tab is invisible.
Select the Use MS Login Name/Password for NFS Authentication check box if you want NFS-Client to use the Microsoft Login User Name and Password for NFS authentication by LDAP.
You can find out UID/GID used for mounting. To do so, select a file or a directory on the mounted drive and right-click on it. In the pop-up menu, choose Properties, and then click the XWPNFS Attributes tab. For example,
In the Unix Attributes group box, you can see the owner (UID and GID) and permissions of the file. In the User group box, you can see the UID and GID used for mounting the file.
My Network Places/Entire Network/XwpNTrdr/Remote NFS Servers is used to browse your network for NFS file servers and to check for the available resources on these servers. Every time you access an NFS server, either to browse its exported resources or to mount a shared network folder, the server requires you to authenticate yourself so that it can verify your identity.
In an NFS network, once the user is authenticated, that user's access to network file resources is further defined by the permissions granted for certain files and folders. When browsing you will be able to see all the exported folders, however, viewing the contents of the folders as well as opening and editing files will depend on whether you have the correct permissions. (See section Mounting an NFS File System under MS Windows NT4/2000/XP below.)
To mount an exported file system, you can also use the NET USE utility of MS Windows (from the Start/Run dialog or from the command line in the MSDOS-shell). If you use the PCNFSd server for authentication, then you can specify a user name and a password as arguments. For example, the following command
NET USE Q: \\192.168.0.38\testnfs nnm111 /USER:nnm
will mount drive
Q on shared directory
testnfs of node
192.168.0.38 for user
nnm with password
nnm111. If you use directly UID/GID for authentication, then you can specify UID instead of user name and GID instead of password as arguments. For example, the following command
NET USE Q: \\192.168.0.38\testnfs 100 /USER:117
will do the same but for UID=117 with GID=100.
The following command line is an example of mounting a network node with the WEBNFS protocol:
NET USE Q: \\192.168.0.41\WebNFS
Some software tools are able to directly open files from the WebNFS-mounted directory. For example:
NotePad -> Open -> \\192.168.0.41\readme.txt
The Unix access permissions for new objects box contains a set of check boxes that allow you to specify access permissions for different users and new files and/or new directories NFS-Client will create and operate on a remote NFS system.
This check box must be enabled to block Write(), MKDIR(), CreateFile(), Rename(),
SetFileAttributes() operation on NFS Servers and to return STATUS_ACCESS_DENIED.
This is useful for ReadOnly exported resources, because it decreases the quantity of fault NFS-protocol requests.
This check box must be enabled for NFS-Client to specify NULL DACL (Directory Access Control List) as a parameter in any file operations (to follow security policy of modern MS Windows versions).
The Network Settings group box allows you to specify:
These parameters may need to be fine tuned to ensure that your NFS-Client is not sending requests faster than the server is able to reply resulting in further unnecessary network traffic.
The Network Caching group box allows you to specify the following 'Life Time' values for time-driven renovating of file/directory attributes stored in the NFS-Client's internal cache:
NFS-Client will preserve the original attributes for existing folders and files and will create new folders and files with the default attribute values. These are the standard UNIX file attributes.
In this group box, you can select a provider name from within the provider list box and then change its place in the list with the Client Up and Client Down buttons.
The Unix => Windows File Name Convert Mode group box allows you to specify file name conversion rules from the UNIX format to the MS Windows format.
If you enable this check box, then the UNIX file names that only differ by cases will be concatenated with a two-character suffix. The second character will be changed by incrementing its code by 1. You can specify an initial value for the suffix in the Suffix for equal file names field. Default is "-0".
If you disable this check box, then NFS-Client will display all file names but those beginning with a period. For the file names beginning with a period, it is desirable to substitute the first period character in the file name with another character. You can specify the character in the Use this symbol instead of '.' at 1st position of name field. Default is "_".
If you enable this check box, then NFS-Client will display files with illegal symbols in filename and files with names reserved in MS Windows.
In the Use this symbol instead of illegal symbols field, you can specify a value to be used instead of illegal symbols in filenames. Default is "~".
In the Use this symbol as prefix for reserved Windows names field, you can specify a value to be used as prefix to mark the reserved file names such as AUX, CON, NUL, etc. Default is "^".
The New Windows Name => Unix Name Convert Mode group box allows you to specify file name conversion rules from the MS Windows format to the UNIX format.
New names for files and directories created or renamed under MS Windows on NFS servers will be converted to upper/lower case or unchanged depending on the mode you choose: Convert to upper case, Convert to lower case, or Preserve the case of name symbols.
If you select this check box, then NFS-Client will attempt to display file and directory names using Unicode/UTF8 format. The mounting exports must still be in ANSI only.
Select this check box if you want NFS-Client to preserve long file names of files that MS Windows renamed or deleted during the first 15 seconds.
When an application creates a file or directory that has a long file name, the system automatically generates a corresponding short file name (alias) for that file or directory, using the standard 8.3 format. If the long file name follows the standard 8.3 format, the alias has the same name except that all lowercase letters are converted to uppercase.
If the long file name does not follow the standard 8.3 format, the system automatically generates an alias, using a numbering scheme to ensure that the alias has a unique name. Applications can override the default alias numbering scheme when creating a file or a directory. In a given directory, the long file name and its alias must uniquely identify a file.
If a file with a long file name is copied or edited, the alias for the resulting file may be different from the original alias. The system always generates new aliases during these operations and always chooses aliases that do not conflict with existing file names.
Applications can open, read, and write from a file using the alias without affecting the long file name. However, some operations on the alias, such as copy, move, backup, and restore, may result in the original long file name being destroyed. The system attempts to preserve a long file name, even when the file associated with it is edited by an application that is not aware of long file names.
When an application makes a system call to delete or rename an alias, the system first gathers and saves a packet of information about the file and then performs the delete or rename operation. The information saved includes the long file name as well as the creation date and time, the last modification date and time, and the last access date of the original file. After the system performs the delete or rename operation, the system watches for a short period of time (the default is 15 seconds) to see if a call is made to create or rename a file with the same name. If the system detects a create or rename operation of a recently deleted alias, it applies the packet of information that it had saved to the new file, thus preserving the long file name. (For more details, see the MSDN Library "File Name Aliases" article.)
In this tab, you can choose the mode NFS-Client will treat UNIX links.
In this mode, NFS-Client will not support and display links.
NFS-Client will display every link as a regular file with the Read-Only attribute.
For every link, NFS-Client will search for its real object. If the end object exists and is accessible, NFS-Client will display the link as the object found with its attributes. If the end object does not exist or it is not accessible, NFS-Client will not display that link.
With this check box enabled, NFS-Client will also display links with the 'Hidden' attribute as regular files but with another color. Otherwise, such links will not be displayed.
This check box enabled allows you to control multiple access to shared files and records on NFS servers with the Network Lock Manager protocol (versions 3 and 4, using Non-monitored Lock requests). Otherwise, Network Lock Manager will not be used.
This edit field lets you specify the maximal number of directories and files in an exported directory (in the range of 4000 : 128000) that will be displayed. The default value is 65000.
With this check box selected, you can mount a subdirectory of a shared directory (if the remote NFS-Server allows that).
You can choose Async for Asynchronous Write mode or Sync for Synchronous Write mode (for NFS-3 protocol version) that NFS-Client will use. This choice has critical influence on performance of write operations.
This tab contains reference information about the NFS-Client release, protocols and versions supported.
At present, NFS-Client supports the following protocols:
|15. Network File System Client (NFS-Client)||< previous | content | next >|
|Copyright © 1999 - 2009 LabtamTM Inc.|