NFS Services Administrator's Guide (B.11.31.03) August 2008

/sbin/init.d/nfs.server stop
/sbin/init.d/lockmgr stop
/sbin/init.d/lockmgr start
/sbin/init.d/nfs.server start
3. Configure the firewall based on the port numbers configured.
Sharing directories across a firewall using the NFSv4 protocol
NFSv4 is a single protocol that handles mounting, and locking operations for NFS
clients and servers. The NFSv4 protocol runs on port 2049, by default.
To override the default port number (2049) for the NFSv4 protocol, modify the port
number for the nfsd entry in the/etc/services file.
Configure the firewall based on the port number set.
Sharing directories across a firewall using the WebNFS Feature
The WebNFS service makes files in a directory available to clients using a public file
handle. The ability to use this predefined file handle reduces network traffic, by avoiding
the MOUNT protocol.
How WebNFS works
This section compares the process of communication between an NFS client and an
NFS server across LANs and WANs. Table 2-4 compares the NFS session across a LAN
with a WebNFS session across a WAN.
Table 2-4 NFS Session Versus WebNFS Session
How WebNFS works across WANsHow NFS works across LANs
NFS servers register on port 2049. WebNFS clients
contact the WebNFS server on port 2049.
NFS servers must register their port assignments
with the portmapper service that is registered on
port 111, although the NFS server uses 2049 as
the destination port.
A WebNFS client can use the PUBLIC file handle as
an initial file handle, rather than using the MOUNT
protocol.
The MOUNT service is not registered on a specific
port. The NFS client must use the portmapper
service to locate the MOUNT port. Once the port
is located, the client must issue a request for a file
handle corresponding to the requested path.
Figure 2-2 shows a sample WebNFS session.
44 Configuring and Administering NFS Services