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

Troubleshooting

Table 6-2 presents possible solutions to common problems that can occur in setting up and managing a user's work environment on clients running Windows NT.

Table 6-2 Troubleshooting on Windows NT


Problem	Possible Cause	Solution
A user logs in and sees the message, `Cannot` `create` `user's` `profile` `in` `\\server_name\ profile_path\.pds`	The client cannot mount the directory specified in the profile path. This might happen if you log in to the client with a different user name than your NT user name.	Make sure you typed correct UNC format for the `\\server_name\profile_path` and that the top-level directory exists and is shared from the server. Press Ctrl+Alt+Delete and log in using a user name that exists on both NT and Solaris.
The user profile cannot be downloaded from the server. The local copy is used instead.	The client is part of an NT domain, served by an NT domain controller and the user profile includes a file (for example, a bitmap for a background) that is not stored on the client.	Copy the included file to the client or remove it from the profile.
System policies are not downloaded from the server.	1. The system policy file (`ntconfig.pol`) is not in the `/opt/MSPolicy` directory on the user's authentication server. If you have more than one `authentication` server on a network and have not copied the `ntconfig.pol` file to all servers, the user might be authenticated by a server that does not store the system policy files.	Copy the `ntconfig.POL` file from an NT workstation or server to each Solaris server running the `pcnfsd` daemon on the network. Log in to the server and verify it is running a `pcnfsd` daemon. If you have more than one authentication server on a network, copy the `ntconfig.POL` file to each authentication server. Or, specify the authentication server that contains the `ntconfig.POL` file by Selecting Solstice NFS Client->Properties->Security->Use a Specific Authentication Server.
System policies are not downloaded from the server.	2. The client is part of an NT domain, served by an NT domain controller. Users cannot download system policies from a Solaris server to a Solstice Network Client machine that is part of an NT domain. This is true whether the user has a local or domain NT user account on the client.	Store the system policy file on the domain controller

Table 6-3 presents possible solutions to common problems that can occur in setting up and managing user profiles, system policies, and login scripts on clients running Windows 95.

Table 6-3 Troubleshooting on Windows 95


Problem	Possible Cause	Solution
System policies are not downloaded from the server.	The system policy file (`config.pol`) is not in the `/opt/MSPolicy` directory on the user's authentication server. If you have more than one authentication server on a network and have not copied the `config.pol` file to all servers, the user might be authenticated by a server that does not store the system policy files.	Copy the `config.POL` file from a Microsoft Windows 95 client to each server running the `pcnfsd` daemon on the network. 2. Log in to the server and check to see if it is running a `pcnfsd` daemon. 3. If you have more than one authentication server on a network, copy the `config.POL` file to each authentication server. Or, specify the authentication server that contains the `config.POL` file by selecting Solstice NFS Client->Properties->Security->Use a Specific Authentication Server. 4. Make sure the Solstice NFS Client is selected as the primary network logon in the Network dialog box.
User profiles are not downloaded from the server.	The Solstice NFS Client is not selected as the primary network logon.	In the Network option in Control Panel, select Solstice NFS Client as the primary network logon.
	NIS or NIS+ is not configured as the name service on the client. If you configure the DNS or Files-based name service but not NIS or NIS+, the Automounter does not automatically mount user's home directories, and user profiles stored in those directories are not downloaded to the client.	Make sure NIS or NIS+ is set up on the server and then select NIS or NIS+ as the name service on the client.