test

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

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.