7020795: How To Setup NetWare Server To Use NFS


By default Reload will use a NCPMount to backup the post offices or domains on the NetWare server. You may also use NFS to mount and backup the post office or domain on a NetWare server. This requires a bit of setup, but can provide another method of mounting from Linux to NetWare.One major advantage of using NFS rather than NCP is that NFS is a lot faster and can increase performance for backing up data.

To setup NFS for a NetWare system follow these steps:

1) On the NetWare system locate the exports file. Usually located under sys:/etc. Edit this file.

2) Add a line specifying the path to export, and the export options desired. It is easiest to append this line to the end of the file. Enter in the volume name where the post office or domain resides.

/volumeName -nwmode -rw -root
Note: It is NOT recommended to give rw access and especially root access to every machine, as the above syntax does. This allows any system to connect to the NFS mount, and for that system’s root user to be treated as a superuser on the exported file system. If you wish to secure it further you may specifiy which servers you wish to have connect to it and therefore restrict others. To do this add a = (equals) and then the server or subnet after the form of access you are restricting. For example:
“-rw=host1” or “-root=@192.168.100.0/24“. Please see comments in sys:/etc/export or NetWare online documentation for more information.

You may also specify the path down to the post office directory and domain directory. If that is the case you will need to enter two paths, one for the post office and one for the domain. For example:

/volumeName/domain -nwmode -rw -root
/volumeName/po -nwmode -rw -root

Make sure to save the changes of the exports file.

3) Locate the NFSTART.NCF file. This is usually located in the SYS:SYSTEM directory or where the NetWare and GroupWise NLM’s are located.

Change the line: “load xnfs” to “load xnfs -nodnscheck”

Save the changes.

4) Restart NFS.

In the system console screen type: nfsstop.ncf

Then type: nfsstart.ncf

5) Setup Reload to connect to the NFS.

If initially setting up a profile create the profile and use a Linux /NFS connection.

Go through the steps to create the profile as recorded in the documentation. Once you get to the option to choose the Server Platform follow the steps below.

If you have the profile already created modify the connectivity settings and change it over to NFS.

Select Connectivity.

Select Yes to modify the connectivity settings on the next screen.

Select Linux

On the next screen specify if it is standard or cluster.

Specify the exports path for Reload to use to connect to the post office or domain to connect. This is the path that was setup in the EXPORTS file on the NetWare server.

Proceed further to the next screens to test and refresh the profile. Once it is successful Reload will now backup the post office or domain using NFS.

Related:

RPC Port Mapper was unable to register on port 111. RPC Port Mapper was unable to start.

Details
Product: Windows Operating System
Event ID: 3002
Source: portmap
Version: 5.2.3790.1830
Message: RPC Port Mapper was unable to register on port 111. RPC Port Mapper was unable to start.
   
Explanation

The NFS protocol uses the RPC Port Mapper to enable NFS clients to discover the ports for various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM). If the RPC Port Mapper cannot register on TCP Port 111, Server for NFS will not start and NFS clients will not be able to access Server for NFS file shares.

Cause

Other software may have already registered network services on port 111.

   
User Action

Close any programs registering network services on port 111. Then start Server for NFS by clicking Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.

Details
Product: Windows Operating System
Event ID: 3000
Source: portmap
Version: 5.2.3790.1830
Message: A Windows subsystem failed a critical request. RPC Port Mapper was unable to start.
   
Explanation

The NFS protocol uses the RPC Port Mapper to enable NFS clients to discover the ports for various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM).

If the RPC Port Mapper cannot start, Server for NFS will not start and NFS clients will not be able to access Server for NFS file shares.

Cause

Windows may be low on system resources.

   
User Action

Try closing programs and restarting Server for NFS. Click Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

Server for NFS was unable to register with the RPC Port Mapper while attempting to start. Server for NFS is not started.

Details
Product: Windows Operating System
Event ID: 1062
Source: nfssvr
Version: 5.2.3790.1830
Message: Server for NFS was unable to register with the RPC Port Mapper while attempting to start. Server for NFS is not started.
   
Explanation

NFS services do not usually register on well-known ports. NFS utilizes the RPC Port Mapper services for NFS clients to discover the port numbers for the various NFS services, such as mount, Network Lock Manager (NLM), and Network Status Manager (NSM). If Server for NFS is unable to register with the RPC Port Mapper, NFS clients will not be able to access Server for NFS file shares.

Cause

Other software may already be registering with RPC Port Mapper.
   
User Action

Close the program registering with the RPC Port Mapper, then start Server for NFS.

 Click Start and then Control Panel. In Control Panel, double-click Administrative Tools, then click Services. Click Server for NFS. In the Action menu, click Start.

Related:

Server for NFS was unable to register a protocol on a port. One or more NFS services, including Server for NFS, may not be available.

Details
Product: Windows Operating System
Event ID: 1064
Source: nfssvr
Version: 5.2.3790.1830
Message: Server for NFS was unable to register a protocol on a port. One or more NFS services, including Server for NFS, may not be available.
   
Explanation
A required network port is not available.NFS uses the Network Lock Manager (NLM) protocol to provide file locking, the Network Status Manager (NSM) protocol to provide file locking status services, and the mount protocol to provide file share mounting services.If Server for NFS cannot register one of these protocols on their port, NFS clients may not be able to mount shares, establish locks, or even access Server for NFS.

Cause

Another program may be blocking the port or may have registered it for its own use.

By default, mount uses port 1048, NLM uses port 1047, and NSM uses port 1039.

   
User Action

You should either close the program that registered the port or specify different ports for NLM, NSM, or mount using the nfsadmin command-line tool. For more information about using nfsadmin, type nfsadmin /? at the command prompt.

You then need to start Server for NFS. Click Start and then click Control Panel. In Control Panel, double-click Administrative Tools, then double-click Microsoft Services for NFS. Click Microsoft Services for NFS. In the Action menu, click Start.

Related: