Accessing WebNFS Servers

The WebNFS^TM protocol is an extension of the NFS protocol. The WebNFS protocol enables clients to access a WebNFS server anywhere on the Internet. It makes information on NFS servers available to Web browsers and Java^TM applets. WebNFS also makes it easy to connect to Internet NFS servers through corporate firewalls.

About the WebNFS Protocol

The WebNFS protocol was designed to overcome some of the drawbacks to using NFS over an Internet connection. A WebNFS server implements the following features:

• Supports TCP transport - Firewalls can be easily configured for protocols that use TCP on well-known ports.

• Supports NFS v3 - NFS version 3 overcomes a number of limitations in version 2. It allows users to access larger files and larger transfer sizes. This results in much faster file access operations across a network.

• Supports the use of a well-known port - Clients can skip the Portmapper protocol and communicate directly with the server on port 2049.

• Exports files using a public file handle - A WebNFS server makes files available to clients with a public file handle. A WebNFS client uses this as an initial file handle to access files and directories, bypassing the Mount protocol.

• Supports multicomponent lookup - A WebNFS server can evaluate an entire path name with a single request when the path name is relative to the public file handle.

The Solaris 2.6 server is a WebNFS server.

About the WebNFS Client

The Solstice NFS Client can connect to a WebNFS server by mounting or by connecting with an NFS URL of the format nfs://host/path. The NFS URL can be used when mapping a drive using net use (Windows NT only), in the Map Network Drive dialog box, or with the script interpreter. Automount maps containing NFS URLs are also supported.

Using an NFS URL

When an NFS URL is used, the connection will be made using TCP transport, NFS version 3, port number 2049, and a public file handle. If any of these requirements cannot be met, the client uses a secondary option.

The WebNFS client connects to the server, following these rules:

• Use TCP protocol first. If the connection is refused, use UDP.

• Use NFS version 3. If rejected, use NFS version 2.

• Use port number 2049 on the server.

• Use a public file handle as an initial file handle with a lookup request. If the request is rejected, use the Mount protocol.

If the public file handle is used, locking/sharing will be disabled.

Using WebNFS Mount Option

You can select WebNFS as an option on the Advanced screen of the NFS Client Properties page or on a network server Properties page. If this option is selected, the client will connect to the NFS server using only the WebNFS protocol. No secondary options will be attempted. For example, if a public file handle request is refused, the mount will fail. Use this option to avoid delays when using WebNFS through a firewall.

Mapping a WebNFS Drive

You can map a drive on a WebNFS server using any of the methods already described for mapping drives. This includes mapping a drive from Network Neighborhood, from Windows Explorer, using the toolbar icon, and with the net use command (on Windows NT only).

When you are required to enter a path name, use the following syntax:

	nfs://server:port/path

The port is optional. If not specified, port number 2049 is assumed.

The path is evaluated by the server relative to the public file handle. Note that if the path begins with a slash, it is evaluated relative to the root directory on the server.

For example, if the public file handle is associated with the directory /home, then the URL

	nfs://server/charlie/dir1/dir2 

refers to the path /home/charlie/dir1/dir2, and the URL

	nfs://server//home/charlie/dir1/dir2 

refers to the same path relative to the root directory on the server.

To Map a Network Drive Using WebNFS

1. Click the Start button, point to Programs, and then click Windows Explorer.

2. From the Tools menu, click Map Network Drive.

   The Map Network Drive dialog box opens.

3. In the Path text entry box, type the WebNFS path. For example:

   nfs://spooky/fun/house 

Browsing WebNFS Servers

You can browse for a WebNFS server using the browsing mechanism described in "Browsing NFS Servers". WebNFS servers will be listed along with the servers running pcnfsd.

If you select a server on the list and click File ->Explore, the system will display all exported directories, those exported by mountd as well as a directory exported with a public file handle (the WebNFS directory).

If you have set the WebNFS option for this server, then you will see only the WebNFS directory, displayed with the export alias name webnfs.