Select from following list to get the help you need.

To export a drive

With the NFS server user interface open, following steps show you how to export Windows resources to remote NFS clients:

1. Click on the New button to start defining a new exported path. NFS Server then uses this information to export the resource you have defined when you restart the NFS Server.
   
   
2. In the NFS Server Export dialog box, select the path to be exported, including drive and directory.
   
   
   

   By default, the Export to All Clients box is checked. If this path is restricted to certain remote hosts for access, uncheck the Export to All Clients and enter the host names (or IP) which you have previously defined in the Host Editor to be Authorized Clients.

   If you want to export your file system to specific users use Export to Users (this option is only available for Win95/98/ME version of NFS Server). Please refer to the Security Mapping section.

3. The Directory Access Rights privilege setting defaults to Read Only for all authorized clients. You can grant read/write privilege to all authorized clients by selecting Read/Write radio button.
   

   When read/write privilege are to be granted to specific clients, select the R/W List radio button, and double click on the client in the list below. Any authorized client not selected in the R/W List setting will have Read Only privilege. Notice that each authorized client granted the Read and Write privilege is separated by a comma (,).

4. When all the parameters are correctly entered, press OK to save all definitions. The NFS Server window will then show the parameters that you have defined.
   
   
5. The changes to the export function will not be operational until NFS Server restarts.
   
   
6. You can repeat the procedure to define as many export paths as you require. You may modify existing resource definitions that you need to change by clicking on the Edit button.

Setup Mapping

You may specify each user’s read and write permission to your exported path. To add users with specific read/write permission, click on the Mapping button from the main NFS Server interface or click on Export to Users button on the NFS Server Export dialog.

A user’s authorization always takes precedence over a host’s authorization. For example, if a user can read and write to a directory, then both read and write permission are authorized to this user, regardless of the permission authorized to the host from which the user is connected.

Working with Security

In order to keep the security structure of both the NFS Server and UNIX based system on the same ground, the security mapping structure is designed as UNIX file and security permission.

Assuming c:/temp has been mounted to /mnt on UNIX machine with Read/Write permission.

Unix Information Table

User / UID	Groups / (GID )
Root / 0	Sys / 2, root / 0, bin / 3, user / 20, staff /50
John / 100	user / 20
Mary / 103	user / 20, staff /50

NT Information Table

User	Groups
Administrator	Administrators, Power User, User, Operator, Engineer
John	User
Amy	User, Engineer

GID Mapping

UNIX GID	NT Group
0	Administrators
20	User
50	Engineer

NT File Permission

C:\temp (owner = Administrators)

Everyone full control

For Omni NFS server, once the drive is mounted, anyone who is on the mapping list will have Read/Write permission. Others will only have read permission since NFS Server cannot determine file permission setting with incomplete user information.

If root on UNIX machine creates a file, then the file security structure will be:

On UNIX	On NT
Owner = root, group = root	Owner = Administrators, group = Administrators
(permission depends on UNIX file mask)

If you would like to have a group of users to access a specific directory, you can either assigned one user account for all the members of the group, perform mapping for each member and set the group permission accessible, or setup universal account for any file transaction.

eg. John creates a Staff directory on the mounted volume and set the group permission to read/write/execute. Since John’s default group is set to User, the directory will be accessible to members in user group; therefore, any user with User default group is included.

If the owner or the group is viewed as Nobody or numbers on the UNIX client, then the mapping is either incomplete or failed. Please check the correct ownership of the file or directory for proper access permission.

Even if you are a super user account on the UNIX machine, you have to perform the security mapping to gain the proper permission.

Options for NFS Server

By pressing the Option button, the following dialog box appears:

This dialog allows you to enable or disable NFS version 3.0, PCNFSD, Network Locking Manager, Xlink Port Mapper or Auto DOS to UNIX file conversion. You can specify the buffer size as well. After you have changed these options, you must restart the NFS Server service to have the changes take effect. The default setting is everything enabled. You can also modify the buffer size at run time from Performance Tips program (please refer to Appendix C for more detail information).

Setup NFS Printer

You may setup NFS printer server on your system by clicking on the Export button from the NFS Server main interface. On the Exported Printer dialog, click on New button to add an NFS printer server entry. You may modify or remove any existing entry with the corresponding buttons. To view the print job queue for any defined NFS printer server, click on the Queue button from the NFS Server main interface. You may pause, remove, resume or modify printer setting on NFS Printer Queue dialog.

Utility for NFS Server

Clicking the Client button will allow you to browse and modify two things: current mounts and current locks.

Current mounts will show you who is currently connected to the NFS Server.

Current locks will show you the file locks currently held by remote clients.

The mounts are saved in the file mountd.list. Sometimes if a client does not mount or unmount when it cannot access the NFS server across the network, or an unmount request is not sent correctly, a stale entry can be left in the mountd.list file. When you are sure there are no clients connecting to your NFS server, you can click "Clear All" to remove all the stale entries. Clear mount entries will cause the NFS Server to rebuild its internal file caching structure. Make sure to disconnect any NFS links prior to clearing mount entries.

The current locks show all the locks currently held by remote clients. These locks will recover themselves after a server crash or restart. If the clients crash or restart, they can still hold some locks and in this case, you must remove the locks manually from this dialog page. The removed locks will be removed from the system the next time you start the NFS server service.

Auto Start NFS Server Service

NFS Server on Windows 98/95/ME can be set to start at boot time by checking the “Restart at Boot Time” option with the NFS Server service icon in the system tray.