WINDOWS 1002000 PROFESSIONAL RESOURCE KIT [Electronic resources] نسخه متنی

Troubleshooting

Connectivity between Windows 2000 Professional and UNIX hosts requires correct configuration on both computers. This section lists the common UNIX connectivity errors that occur when you configure both Windows 2000 Professional and Services for UNIX.

Commonly Encountered Errors

Following are some common error messages and troubleshooting suggestions.

"An error ocurred while attempting to communicate with the Client for NFS service."

Check if Client for NFS is started. Do this by typing net start at the DOS prompt and see if the Client for NFS service is running.

"NFS will use anonymous UID (-2), GID (-1), and factory default mount options."

If UID is -2 and GID is -1, the user is probably authenticated as an anonymous user. Verify that your mapping server is configured correctly and set to connect correctly to the NIS server or PCNFSD server. Also check if your NIS server or PCNFSD server is configured correctly and functioning.

"Owner is nobody or group is nogroup"

This error message can occur when accessing files and the file permissions are incorrectly reported. Use the following steps to troubleshoot the problem.

Ensure that local or domain users are correctly mapped by means of the Username Mapping Server and that Services for UNIX is configured to use the correct mapping server.

Check the /etc/exports file on the UNIX server and make sure it isn't configured to only allow anonymous connections.

If using PCNFSD, make sure that the UIDs and GIDs match on the mapping server and the UNIX server.

If the problem is with an NFS server running Services for UNIX, make sure that the Server for NFS Authentication component is installed on Windows 2000 Professional. If you have a domain environment and are using domain accounts for mapping, the Server for NFS Authentication component must be installed on all domain controllers in the domain.

If you are unable to access an NFS volume with Windows 2000 Professional that is running Services for UNIX, use the following steps to troubleshoot the problem.

Check the /etc/exports file to ensure that there aren't any host restrictions that are preventing you from mounting the NFS volume.

Make sure the file system is properly exported by running the following command:

showmount -e <IP address of UNIX host>

Make sure that the daemons mountd, nfsd, and rpcbind are running by running the following command:

rpcinfo -p <IP address of UNIX host>

Some versions of UNIX might incorrectly report that they support NFS version 3. You might need to force the Services for UNIX client to use NFS version 2. To force the client to use NFS version 2, add the registry entry DisableV3 to the following registry subkey:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftClient for NFS
CurrentVersionDefault

Set DisableV3 to data type REG_DWORD with a value of 0x1.

CAUTION

---

Do not use a registry editor to edit the registry directly unless you have no alternative. The registry editors bypass the standard safeguards provided by administrative tools. These safeguards prevent you from entering conflicting settings or settings that are likely to degrade performance or damage your system. Editing the registry directly can have serious, unexpected consequences that can prevent the system from starting and require that you reinstall Windows 2000. To configure or customize Windows 2000, use the programs in Control Panel or Microsoft Management Console (MMC) whenever possible.

Cannot Telnet into my UNIX server as root

If you are unable to log into a UNIX server as root by using telnet, verify that your version of UNIX is configured to allow a root user to log in remotely. For example, Sun Solaris requires editing the /etc/default/login file.

Cannot map a drive after using Telnet to access a Services for UNIX Telnet Server

If you cannot map a drive by using net use after using Telnet to connect to a Services for UNIX Telnet Server and using NTLM authentication, read the following to troubleshoot the problem.

When you are within the Telnet session, you cannot connect to network resources by using your implied user credentials. You must explicitly specify your credentials when making network connections from within the Telnet session. There is no mechanism in Windows NT to perform delegation of security, known as passthrough, for network logon attempts. As a workaround, explicitly specify credentials when mapping drives, that is, do as follows:

net use <server><share name> /user:<domainname><username> password

Password synchronization isn't working properly

If the Services for UNIX Password Synchronization component is not working properly, follow the proceeding steps to troubleshoot the problem.

Ensure that SSOD is running on the UNIX server and that the Password Synchronization component has been installed on a computer running Windows 2000 (or on all domain controllers within a domain).

Ensure that the port number and passwords match on both the Windows 2000 computer and the UNIX server.

If you are using shadow passwords, edit the Ssod.config file and change the line USE_SHADOW=0 to USE_SHADOW=1

If you are using NIS, be sure that the SSOD is installed on the NIS master and that the Ssod.config file is configured with the correct path for the Makefile for password push.