This document attempts to answer frequently asked questions for the AccessNFS DiskAccess on running on the Microsoft Windows 95 and Windows 98 operating systems. This document should be used in conjunction with the on-line help.

Use the About utility to determine the version of the product you are running. Connect to the Shaffer Solutions Web site and check for the latest version that is available. To connect to the Shaffer Solutions Web sit, visit http://www.ssc-corp.com/nfs and select "Product Updates".

If authentication is being established with a PCNFSD service, the DiskAccess service may not have been able to contact the server running the pcnfsd service. Attempts should be made to contact the server with the ping.exe utility followed by the RPC Information utility. If the DiskAccess service is running and the ping and rpc information test are successful, then further investigation of why the authentication failed needs to take place. If assistance is needed, please contact Shaffer Solutions support services.

If authentication is being established with NIS, the DiskAccess service may not have been able to contact an NIS server serving the user's NIS domain. The diskaccess service relies on a NIS server to respond to an NIS broadcast which is used to discover any NIS servers of the given NIS domain. If no NIS servers respond to the broadcast or if an NIS server which has responded to the broadcast goes off line, then the above error message will be displayed. The network administrator will need to confirm the NIS server is working correctly. If the NIS server is working correctly and the DiskAccess services is running, then further investigation needs to take place. If assistance is needed, please contact Shaffer Solutions support services.

If you have another LanMan network printer which supports DOS printing, the CancelConnection request goes to the LanMan network printer instead of NFS network printer. And thus, it fails to delete the network printer from the Persistent registry key. You can manually end the printer port capture by going to the property sheet of any printer. Within the property sheet, go to the Details folder and click on End Capture. It will list all the ports captured. Select the one that you would like to delete and click OK. Or you can delete the registry key \\HKEY_CURRENT_USER\Network\Persistent\LPT# and reboot the system.

The installation program first calculates the amount of space needed for each file to be delivered with the installation option you selected. Then it looks to see if any of the files already exist in the installation directory on your system. If so, it subtracts the size of the existing file from the size of the new file. If files in the version you are installing are smaller than the older version currently on your system, the message could even show the disk space needed as a negative number.

By using the same "net use" command used to make LanMan connections. The syntax for connecting to an NFS resource is as follows:

net use <drive letter> <\\servername\sharename>

To disconnect, type:

net use /d <drive letter>

The Windows 9x NET USE command for mounting shares from the command line does not allow mounting share names longer than servername and a single sharename element, (e.g. net use e: \\server\dirname\subdirname causes NET.EXE to return a syntax error). Windows 9x NET.EXE makes the assumption that all network providers will only want to connect to a single sharename element. This has been identified by Microsoft as an operating system problem.

Workarounds include mounting to single path element sharenames only, mapping the longer names from Explorer or File Manager, or replacing all backslashes within the sharename with colons (e.g. from above, the syntax would be net use e: \\server\dirname:subdirname).

The NET USE command does not maintain case on sharenames, so all NFS mount sharenames are forced to lowercase. These have been reported to Microsoft as operating system problem.

Check the CONFIG.SYS file in the boot directory for a line that begins "LASTDRIVE". If the last drive is configured to a letter that is lexicographically less than the drive letter you are attempting to use, Windows 9x will not allow the mount. You should change the line in CONFIG.SYS to read "LASTDRIVE=Z", and then reboot the system before re-attempting the NFS mount.

There is a problem with the way Windows 9x handles connecting to servers that support more than one protocol understood by the client. Once Windows 9x determines that the server supports Windows LAN Manager networking, the OS will never again try to access the server using NFS until the client is rebooted. This occurs with any Windows 9x client connecting to a server that supports multiple protocols along with LAN Manager, not just NFS. Windows 9x may make IPC (InterProcess Communication) connections to LAN Manager servers from time to time unrelated to Map Network Drive attempts that will block NFS access to multiple protocol servers.

Windows 9x will never timeout its cache of servername to protocol once it determines a protocol the server supports on an access. This may also prevent LAN Manager access to the specific multiple protocol server once an NFS connection has been established. This has been identified by Microsoft as an operating system problem.

In addition to enabling locking on the clients, locking must be available and enabled on the server being accessed. The lock manager on the server must also support Network Lock Manager version 3 because this is the only version that supports PC type lock requests.

Enabling locking will slow the client down in any case because of the extra network traffic required to support locking. There are cases where the slow down could be extreme, however. There are two reasons this could happen. Either locking is not enabled on the server being accessed, or the server does not support Network Lock Manager version 3. In both of these cases, the client is attempting to contact the lock manager (version 3) on every access, timing out, and retrying. This behavior is required if the client is to recover automatically from a server crash.

The Explorer is a 32-bit application and Windows 9x is case preserving (but not case sensitive) for 32-bit applications. When a 32-bit application lists files it may use the long file name when displaying names. When a 16-bit application like Winfile or Word displays file names however, the short name is used (which may not be case preserving). A short file name must be generated for one (or both) of the files so they may be distinguished from each other.

This is due to a limitation in Windows 9x. Windows 9x does not preserve case for directory names. This results in the DiskAccess client having to do a case insensitive search of a directory for mixed case file/directory names. This means the first file/directory name that matches when performing this search is returned - leaving the second file/directory inaccessible.

Although the DiskAccess client is capable of supporting long file/directory names, the server may not support long file/directory names. In many cases, the server may truncate the name when creating or renaming files and directories.

The DiskAccess Network Provider DLL periodically issues a network broadcast to request a reply from each NFS server on the network. The name of each server that responds to this broadcast is placed in a list. This list is displayed when an application browses the NFS Network.

By default, the DiskAccess Network Provider issues this broadcast at system startup and again every five minutes. A new list of servers is generated with each broadcast. In this manner, servers that are no longer responding are eliminated from the list, and new servers are added to the list.

DiskAccess may be configured to only issue the broadcast once, at system startup. This method reduces the amount of network traffic. However, the NFS server list will never be updated and, therefore, may become inaccurate if servers are removed from or added to the network.

DiskAccess may be configured to only issue the broadcast when an application attempts to browse the NFS Network. This provides the most up-to-date list of NFS servers and only generates network traffic upon demand. However, this technique causes the browsing application to wait for the list to be generated.

There is a configurable timeout value that specifies the length of time the DiskAccess Network Provider will wait to receive replies from NFS servers responding to the broadcast. By default, this timeout value is set to 15 seconds. This long timeout period allows servers that are slow to respond, such as servers on distant LANs, to be included in the list. If DiskAccess is configured to only broadcast upon demand, it is recommended that this timeout value be set to one second. Although this will prevent slow responders from being added to the list, it will improve the browse response time.

By default, the DiskAccess Network Provider specifies the IP broadcast address 255.255.255.255 when issuing a browse broadcast request. This address indicates that the broadcast is to be sent to all nodes. If bridges or routers are present in the network configuration, the network administrator may have configured them to pass broadcast frames or filter them out. This will affect whether or not servers on remote LANs will appear in the NFS Network browse list.

You can edit the parameters of the Default Lan or set up other LAN's to Browse through ControlPanel-DiskAccess configuration and then choosing the Configured NFS LANS tab.

The parameters can be edited through ControlPanel-DiskAccess Configuration-Configured NFS LANs tab and editing the NFS LAN you wish to modify. There is Online Help for the options that are available.

The delay occurs because DiskAccess is trying to contact the PCNFSD or NIS server for NFS login authentication, but it is not yet available. Eventually, a timeout will occur and DiskAccess will return the login failure message. To avoid the delay, invoke the DiskAccess configuration dialog from the Control Panel and remove the authentication server name. If there is no server name present, DiskAccess will immediately return a login failure without attempting to contact the server. (NOTE: This means that all subsequent NFS logins that use the configured defaults will fail.)

Yes. DiskAccess can be configured so that NFS login is not attempted until an NFS mount is attempted. However, this means that browse connections (those done through Network Neighborhood without an associated drive letter) will use the factory defaults rather than the configured defaults. To configure DiskAccess to bypass NFS login at system login, go to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\SSC\DiskAccess\Default

and set the AuthenticateAtBoot value to 0.

The Microsoft documentation for the WNetAddConnection2 and WNetAddConnection3 lpPassword and lpUsername arguments is listed below. DiskAccess specific information has been inserted in italics.

lpPassword

Points to a null-terminated string that specifies a password to be used in making the network connection.

If lpPassword is NULL, the function uses the current default password associated with the user specified by lpUserName.

If lpPassword is NULL, the current default password specified by the DiskAccess configuration is used.

If lpPassword points to an empty string, the function does not use a password.

lpUsername

Points to a null-terminated string that specifies a user name to be used in making the connection.

The specified user name will be authenticated through the PCNFSD or NIS server specified by the DiskAccess configuration. If the specified user name and password are not correct, ERROR_LOGON_FAILURE will be returned. If no PCNFSD or NIS server is configured, ERROR_SUCCESS will be returned and UID -2 and GID -1 will be used.

If lpUserName is NULL, the function uses the default user name. The user context for the process provides the default user name. If a NULL pointer is specified, the current default user name and password specified by the DiskAccess configuration is used. The lpPassword argument is ignored. The default user name and password will be authenticated through the PCNFSD or NIS server specified by the DiskAccess Configuration. If the authentication fails, ERROR_LOGON_FAILURE will be returned. If no PCNFSD or NIS server is configured, ERROR_SUCCESS will be returned and UID -2 and GID -1 will be used.

If lpUserName points to an empty string ERROR_SUCCESS will be returned and UID -2 and GID -1 will be used. The lpPassword argument is ignored.

The file attributes are retrieved each time the NFS Attributes property sheet page becomes active. Any changes that were made to the page but were not applied to the file will be lost. This insures that each time the NFS Attributes page is displayed, the current file attributes are shown.

Yes. Shortcuts provide quick ways to get to the files you use most often. A shortcut essentially provides instructions to the operating system on how to access a particular item (file). The item may be available on your local system or on the network. When using shortcuts with DiskAccess, certain precautions must be taken because of limitations in Windows 9x and/or limitations on the target system. The following pointers are provided to help guide you when creating shortcuts to files found on drives mounted with DiskAccess.

If creating a shortcut to a file made accessible with DiskAccess, the shortcut must either be located at the mount point (the directory that is exported on the server), or the drive must be mapped to a drive letter. This may be done from Explorer by clicking on the Tools selection in the toolbar and choosing "Map Network Drive...". Please remember, unless you have selected this drive to "Reconnect at logon", the shortcut will be unavailable until the network drive is again mapped to that drive letter.

You need to keep in mind the limitations of the operating system you are connecting to when naming shortcuts. Some operating systems support longer file names than others (UNIX will support 14 character file names). Also, very few operating systems will allow spaces or other special characters in file names. This is important to keep in mind because Windows 9x will put spaces in shortcut names by default (e. g. "Shortcut to Printers").

 

In the registry, there is a value called "FirstContact" under the key:

HKEY_LOCAL_MACHINE\SOFTWARE\SSC\DiskAccess\Default

The number contained in "FirstContact" is the time to wait for an initial response when attempting to contact a new machine. The value is in tenths of a second and has a default value of 30 (3 seconds). If a machine has been removed from the net or doesn't support NFS, it will take 3 seconds for DiskAccess to error out. If you have placed a lot of (now defunct) UNC names in your path, e.g. PATH=\\oldnode1\path;\\deadnode\path123;\\lamebox2\bindir;c:\win95 then DiskAccess will timeout on each UNC name (3 seconds each) for every time the command prompt searches your path. But it gets worse. LanManager tries first and it may take up to 6 seconds to timeout.

A similar thing can happen with any application with a stale UNC name. If you mistype the nodename in the "Map Network Drive" box or have a stale Windows 9x shortcut ("\\deadnode\netpath") "FirstContact" determines the amount of time before DiskAccess gives up trying to contact that machine. Add this to the LanManager timeout and you have spelled SLOW!

The best solution is to remove invalid UNC names from your PATH and applications. If not possible, you can tune the value of "FirstContact" to timeout quicker.

However, a small value for "FirstContact" may not allow NFS connections to remote nodes (e. g. across the internet or next door but across a slow link) or to NFS servers that are slow (being saturated with network traffic).

The Explorer/Network Neighborhood does not support a null share name. If the DiskAccess Network Provider enumerates the share names on a server that has exported the root directory (/), the explorer does not properly handle the share name /.

As a compromise, the DiskAccess Network Provider enumerates the share name / but does not identify it as a share name. You will notice that when most share names are displayed by the Network Neighborhood, a folder icon appears next to the share name. A different icon appears next to the share name /. If you click on the share name /, an error dialog box will be displayed.

There is no problem with using the Explorer Map Network Drive to mount the share name /.

Therefore, you may use the Network Neighborhood to browse an NFS server to display the exported share names. However, you may only see the contents of the share name / by mapping a drive letter to that share name.

At this time, DiskAccess does not support the "My Briefcase" sync facility.

Because Microsoft does not provide any kernel facilities for translating network names into IP addresses and Ring 0 drivers such as DiskAccess' NFS redirector cannot safely call Ring 3 networking code, the IP address must be entered in the registry. Ring 0 drivers introduce the possibility of deadlocks when calling Ring 3 network routines. Shaffer Solutions has requested that Microsoft provide a kernel facility to allow Ring 0 VxDs to translate server names into addresses.

If DiskAccess is unable to locate the target of a symbolic link, the symbolic link is not presented to the user. This is done because DiskAccess is unable to obtain the file type or file attributes of the target of the symbolic link.

The NFS Attributes property sheet page displays attributes for the symbolic link while the Explorer displays attributes for the target of the symbolic link.

First of all, keep in mind that DiskAccess has always re-authenticated on persistent connections using the default NFS login for that connection. The difference is that now, if the user who is currently logged in has a different Windows 9x login name than the one who created the persistent connection, the user can be forced to reenter the NFS password before the authentication takes place. To enable this feature, go to the followingregistry key:

HKEY_LOCAL_MACHINE\SOFTWARE\SSC\DiskAccess

and set the value AuthenticateOnReconnect to 1.

PCNFSD has been ported to many different platforms. The following is a partial list of FTP sites for different versions:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Platform Location

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

SunOS 4.x, Solaris bcm.tmc.edu

Solbourne src.doc.ic.ac.uk

NeXTStep ftp.york.ac.uk:/pun/pv/pc-nfs/RPC.pcnfs/*

Ultrix 4.2 bcm.tmc.edu

IRIX/SYSV sgi.sgi.com:/support/pcnfsd.sysV [unsupported]

AIX 3.2 Call IBM and ask for PTF# U412556

AIX 3.2.1 Call IBM and ask for PTF# U419359

AIX 3.2.3 Call IBM and ask for PTF# U414701

MIPS platforms ftp.york.ac.uk:/pub/pc/pc-nfs/RPC.pcnfsd/*

IBM MVS Call IBM and ask for PTF# UY84244 [pcnfsd v1 only]

OpenVMS 5.5 DEC TCP/IP v3.0 [product]

SCO Unix v3.2 SCO NFS [product]

HP 9000 [HP-UX 9.x] HP-UX NFS [product]

There is a combined version of PCNFSD v2 for the following systems: Sun, Ultrix, MIPS,

SGI, BSD, SVR4 which is available from ftp.york.ac.uk:/pub/pc-nfs/RPC.pcnfs/pcnfsd.tar.Z.

Examples are included below for the following NFS servers: SSC's DiskShare, SunOS 4.x and Solaris 2.x:

The SSC DiskShare product lets NT systems act as NFS servers, making directories and printers available to NFS clients. All printers that are configured on a system running DiskShare are available to clients using PCNFSD printing; however, the printers cannot be browsed because DiskShare does not implement PCNFSD version 2 completely. PC-NFS clients will need to specify the server name and printer name explicitly to connect to a printer on a DiskShare server.

If you want the PC-NFS daemon (PCNFSD) to start automatically on a DiskShare server when the system is booted, perform the following steps:

1) In Control Panel, open the Services icon.

2) From the list of available services in the Services control panel, select pcnfsd; then

select the Startup... button.

3) In the Service dialog that is displayed, select a Startup Type of Automatic. Selecting

Manual will require you to start PCNFSD manually each time you reboot the system.

4) Close the Service dialog; then close the Services control panel.

It is recommended that the user refer to the SunOS documentation for LPR and the delivered manual page for rpc.pcnfsd(8) for more complete instructions on how to configure PCNFSD on the SUN Operating System. The following is a brief summary of the steps required.

To load the rpc.pcnfsd file on the Sun machine:

1) Copy the file rpc.pcnfsd to /usr/etc/rpc.pcnfsd

2) Make sure the permissions and ownership of the file are as follows:

-rwxr-xr-x 1 root 65536 Mar 17 1994 /usr/etc/rpc.pcnfsd

3) Add the following to the /etc/rc.local file after the entry for ifconfig -a:

#

if [ -f /usr/etc/rpc.pcnfsd ]; then

/usr/etc/rpc.pcnfsd -s /usr/spool/pcnfs;

echo 'rpc.pcnfsd' > /dev/console

#

4) Create the following file:

/usr/spool/pcnfs

Authentication:

When pcnfsd receives a PCNFSD_AUTH or PCNFSD2_AUTH request, it will "log in" the user by validating the username and password and returning the corresponding user ID, group IDs, home directory and default file permissions (umask). At this time, pcnfsd will also append a record to the /etc/wtmp database. To record PC "logins" in this way, you should add a line with the following format to the pcnfsd.conf file:

wtmp yes

The pcnfsd.conf file is delivered with the value of wtmp set to "no".

Printing:

The pcnfsd daemon supports a printing model that uses NFS to transfer the actual print data from the client to the server. The client system issues a PCNFSD_PR_INIT or PCNFSD2_PR_INIT request, and the server returns the path to a spool directory which is exported by NFS and which the client may use. The pcnfsd daemon creates a subdirectory for each of its clients: the parent directory is normally /usr/spool/pcnfsd and the subdirectory is the hostname of the client system. To use a different parent directory, add a line with the following format to the pcnfsd.conf file:

spooldir path

i.e. spooldir /home/spool

Once a client has mounted the spool directory using NFS and has transferred print data to a file in this directory, it issues a PNNFSD_PR_START or PCNFSD2_PR_START request. The pcnfsd daemon handles this, and most other print related requests, by constructing a command based on the printing services of the server operating system and executing the command using the identity of the PC user. Since this involves set-user-id privileges, pcnfsd must be run as root.

Every print request from the client includes the name of the printer that is to be used. To pcnfsd, a printer appears as either a destination serviced by the system print spooler, or as a virtual printer. Refer to the SunOS lpc(8) manual page for more information on setting up the system print spooler to handle a new printer. Virtual printers, known only to pcnfsd clients, are defined in the /etc/pcnfsd.conf file by a line with the following format:

printer name alias-for command

The printer name parameter is the name of the printer you want to define. The alias-for parameter specifies the name of a "real" printer which corresponds to this printer (you can define up to 16 virtual printers). For example, a request to display the queue for printer name will be translated into the corresponding request for the printer alias-for. If you have defined a printer in such a way that there is no "real" printer to which it corresponds, use a single dash (-) for this field (see the example for the printer named "test" below). The command parameter will be executed whenever a file is printed on printer name. This command is executed by the Bourne shell using the -c option. For complex operations, you should construct an executable shell program and invoke that in command. Within command, the following tokens will be replaced dynamically by pcnfsd:

$FILE Replaced by the full path name of the print data file. When the command has

been executed, the file will be unlinked.

$USER Replaced by the user name of the user logged into the client system.

$HOST Replaced by the host name of the client system.

$PRINTER Replaced by the real printer name.

Consider the following example pcnfsd.conf file:

printer aliasfuji fuji lpr -P fuji -J $USER -C $HOST $FILE

printer test - /usr/bin/cp $FILE /usr/tmp/$HOST-$USER

If a PC client system prints a job on the printer "aliasfuji", pcnfsd will execute the specified print job on the printer "fuji". If the client requests a list of the print queues for the printer "aliasfuji", the pcnfsd daemon will translate this into a request for a listing for the printer "fuji". The printer "test" is used only for testing. Any file sent to this printer will be copied into /usr/tmp. Any request to list the queue, check the status, etc. of printer "test" will be rejected because the alias-for has been specified as "-".

It is recommended that the user refer to the Solaris documentation for LP and LPR, and the manual page delivered with the rpc.pcnfsd(1M) daemon for more complete instructions on configuring PCNFSD on Solaris (SunOS 5.x) systems. The following is a brief summary of the steps required.

To install pcnfsd:

1) Copy the file rpc.pcnfsd to /usr/lib/nfs

2) chmod 777 and chown bin chgrp bin on the above file.

3) Copy the file pcnfs to /etc/init.d/pcnfs

4) chmod 777, chown root, chgrp other

5) Make a hard link to /etc/rc3.d and call the file S32pcnfs

# ln /etc/init.d/pcnfs /etc/rc3.d/S32pcnfs

When pcnfsd receives a PCNFSD_AUTH or PCNFSD2_AUTH request, it will "log in" the user by validating the username and password and returning the corresponding user ID, group IDs, home directory and default file permissions (umask). At this time, pcnfsd will also append a record to the /etc/wtmp database. To record PC "logins" in this way, you should add a line with the following format to the pcnfsd.conf file:

wtmp yes

The pcnfsd.conf file is delivered with the value of wtmp set to "no".

Printing:

The pcnfsd daemon supports a printing model that uses NFS to transfer the actual print data from the client to the server. The client system issues a PCNFSD_PR_INIT or PCNFSD2_PR_INIT request and the server returns the path to a spool directory which is exported by NFS and which the client may use. The pcnfsd daemon creates a subdirectory for each of its clients: the parent directory is normally /usr/spool/pcnfsd (for the LPR print system) or /usr/spool/lp/pcnfs (for the LP print system) and the subdirectory is the hostname of the client system. To use a different parent directory, add a line with the following format to the pcnfsd.conf file:

spooldir path

i.e. spooldir /usr/printspool

Once a client has mounted the spool directory using NFS and has transferred print data to a file in this directory, it issues a PNNFSD_PR_START or PCNFSD2_PR_START request. The pcnfsd daemon handles this, and most other print related requests, by constructing a command based on the printing services of the server operating system and executing the command using the identity of the PC user. Since this involves set-user-id privileges, pcnfsd must be run as root.

Every print request from the client includes the name of the printer that is to be used. To pcnfsd, a printer appears as either a destination serviced by the system print spooler or as a virtual printer. Refer to the lpadmin(1M) or lpc(1B) manual pages for more information on setting up the system print spooler to handle a new printer. Virtual printers, known only to pcnfsd clients, are defined in the /etc/pcnfsd.conf file by a line with the following format:

printer name alias-for command

The printer name parameter is the name of the printer you want to define. The alias-for parameter specifies the name of a "real" printer which corresponds to this printer (you can define up to 16 virtual printers). For example, a request to display the queue for printer name will be translated into the corresponding request for the printer alias-for. If you have defined a printer in such a way that there is no "real" printer to which it corresponds, use a single dash (-) for this field (see the example for the printer named "test" below). The command parameter will be executed whenever a file is printed on printer name. This command is executed by the Bourne shell using the -c option. For complex operations, you should construct an executable shell program and invoke that in command. Within command, the following tokens will be replaced dynamically by pcnfsd:

$FILE Replaced by the full path name of the print data file. When the command has

been executed, the file will be unlinked.

$USER Replaced by the user name of the user logged into the client system.

$HOST Replaced by the host name of the client system.

$PRINTER Replaced by the real printer name.

Consider the following example pcnfsd.conf file:

printer aliasfuji fuji lpr -P fuji -J $USER -C $HOST $FILE

printer test - /usr/bin/cp $FILE /usr/tmp/$HOST-$USER

If a PC client system prints a job on the printer "aliasfuji", pcnfsd will execute the specified print job on the printer "fuji". If the client requests a list of the print queues for the printer "aliasfuji", the pcnfsd daemon will translate this into a request for a listing for the printer "fuji". The printer "test" is used only for testing. Any file sent to this printer will be copied into /usr/tmp. Any request to list the queue, check the status, etc. of printer "test" will be rejected because the alias-for has been specified as "-".

If any part of the share name contains more than eight characters, WinZip will cause the Explore to crash. WinZip has documented known problems with long file and directory names on Windows 9x systems.

Yes, the product has utilities that can be run in a DOS window. All of the command line utilities have an equivalent graphical counterparts. See the online help for details on the command line options to run the command line utility with the "/?" option and an usage statement should be given.

ProductDir is defined as the directory name where the product has been installed. For example; c:\Program Files\DiskAccess

daconfig.exe ProductDir\bin Configure default NFS information

nfs.exe ProductDir\bin Mount/unmount NFS resources

lpr.exe ProductDir\dalpr Submit print jobs to a LPD server

lprm.exe ProductDir\dalpr Remove submitted LPR print jobs

lpq.exe ProductDir\dalpr Query LPR print job status

rpcinfo.exe ProductDir\Utilities ONC RPC server locator

showmount.exe ProductDir\Utilities Enumerates NFS Server's exported directories

dig.exe ProductDir\wdig Domain Name System (DNS) look-up client

finger.exe ProductDir\\wfinger Displays user information via finger protocol