test

Solstice NFS Client 3.2 User's Guide for Microsoft Windows 95 and Windows NT

Troubleshooting

Table 3-1 lists problems that might occur using network file services on a computer running Solstice NFS Client.

Table 3-1 Problems Using Network File Services

Problem 

Possible Cause 

Solution 

Cannot log in to Solstice NFS Client Login dialog box.

One or more TCP/IP settings are incorrect.  

Click Cancel on the Solstice NFS Client Login dialog box to log in without networking enabled. 

Click Start, point to Settings, click Control Panel, and then double-click Network. 

In Windows 95, double-click TCP/IP. Refer to "Checklist for TCP/IP Settings on Windows 95".

In Windows NT, click the Protocols tab, then double-click TCP/IP Protocol. Refer to "Checklist for TCP/IP Settings on Windows NT".

On Windows 95, you tried to enter a UNC file name in the Map Network Drive dialog box and received the error message, "The following error occurred while trying to connect drive to server. Resource not found."

The UNC name for the network resource you tried to access does not exist.  

Use NFS format in the Map Network Drive dialog box, or browse the network resources listed in Network Neighborhood. As you select each network resource, the Network Provider creates a UNC name for it. 

You tried to map a drive on Windows NT using the Connect As feature and received the error message: The credentials supplied conflict with an existing set of credentials.

You tried to connect as a different user. 

The Connect As feature is not supported by Solstice NFS Client, so you should leave this field blank. 

You logged in to Solstice NFS Client, but when you browse NFS Servers, no servers are listed.

No NFS servers are running on the same subnet as Solstice NFS Client. 

Open Network Neighborhood and double-click Entire Network. In Windows NT, double-click Solstice_NFS_Client. 

In both environments, select NFS Servers and click the right mouse button.  

Click Add/Remove NFS Servers. 

Type the name of an NFS Server outside the local subnet, and then click Add.  

Click OK to close the dialog box. 

Attempting to copy a directory on which you only have read permission from one NFS server to another using Explorer, Windows 95, or Windows NT fails with the message, Cannot create or replace directory_name. Access is denied.

The directory was copied read-only and then none of the contents could be copied into it. 

Open a DOS prompt window and use the xcopy command to copy the directory.

 

Checklist for TCP/IP Settings on Windows 95

If you cannot log in to Solstice NFS Client, follow these steps to troubleshoot the problem:

  1. Right-click on the Network Neighborhood icon and click Properties to open the Network dialog box.

  2. Click the Configuration tab and double-click TCP/IP.

  3. If your site uses DNS:

    1. Click the DNS Configuration tab and make sure Enable DNS is selected.

    2. Make sure the DNS domain name is correct.

    3. Make sure the number listed in DNS Server Search Order is the correct address of your DNS server.

  4. If your site uses DHCP to automatically generate IP addresses for clients, click the IP Address tab and make sure Obtain An IP Address Automatically is selected.

  5. If your site does not use DHCP:

    1. Click the IP Address tab and make sure Specify An IP Address is selected and the number typed in the IP Address box is correct.

    2. Click the Gateway tab and make sure the number listed in Installed Gateways is the correct address of a gateway on your local subnet.

  6. Check the authentication server:

    1. In the Network dialog box, double-click the Solstice NFS Client.

    2. Click the Security tab and check the authentication server.

      If Broadcast For An Authentication Server is selected, make sure there is a server running the pcnfsd daemon on the same local subnet as the computer running Solstice NFS Client. Do this by entering the following command from a Solaris system on the subnet:


      rpcinfo -b 150001 2

    3. If no server on the subnet is running the pcnfsd daemon, select Use A Specific Authentication Server and type the IP address of an authentication server outside the local subnet.

Checklist for TCP/IP Settings on Windows NT

If you cannot log in to Solstice NFS Client, follow these steps to troubleshoot the problem:

  1. Right-click on the Network Neighborhood icon and click Properties to open the Network dialog box.

  2. Click the Protocols tab and double-click TCP/IP Protocol.

  3. In the IP address tab, check the following:

    1. If you use DHCP for dynamic configuration, verify that the Obtain An IP Address From A DHCP Server option is selected.

    2. If you don't use DHCP, verify that the Specify An IP Address option is selected. Make sure correct values are entered for the IP Address of your computer, the subnet mask used in your subnetwork, and the IP address of the default gateway server.

  4. If your site uses DNS, click the DNS tab and check that:

    1. The name of your system appearing in the Host Name field is correct.

    2. The name listed in the Domain field is correct.

    3. The IP addresses of DNS servers are correct in the DNS Service Search Order.

  5. Click OK to close TCP/IP Properties.

  6. Click Services, and double-click Solstice NIS/NIS+ Naming Service.

    1. If you have selected NIS or NIS+, the name service you selected should be enabled. Be sure you have entered an IP address and domain name for the NIS or NIS+ name server. If there is an asterisk (*) in the IP address field, you must replace it with a real address.

    2. The name service domain name is case-sensitive. Be sure you have entered the name correctly.

  7. Verify the authentication server:

    1. In the Services tab of the Network dialog box, double-click Solstice NFS Client.

    2. Click the Security tab and verify the authentication server.

      If Broadcast For An Authentication Server is selected, make sure there is a server running the pcnfsd daemon on the same local subnet as Solstice NFS Client. Do this by entering the following command from a Solaris system on the subnet:


      rpcinfo -b 150001 2

    3. If no server on the subnet is running the pcnfsd daemon, select Use A Specific Authentication Server and type the IP address of an authentication server outside the local subnet.