Cause: You do not have adequate privileges, or
the computer running User Name Mapping does not belong to a domain
trusted by the Windows-user domain.
Solution: Log on as a user in a domain trusted
by the domain to which the computer running User Name Mapping
belongs and that belongs to the Administrators group on the
computer running User Name Mapping.
Cause: When installing the Active Directory
domain controller, you chose the Permissions compatible with
Windows 2000 Server option.
Solution: Do one of the following:
If the computer running User Name Mapping is a member of the
domain, add the computer to the security group
Pre-Windows 2000 Compatible Access.
If the computer running User Name Mapping does not belong to
the domain (that is, it belongs to a trusted domain), add the
special group Everyone to the Pre-Windows 2000 Compatible
Access security group of the Active Directory domain.
You must restart the domain controller after adding the computer
or group to the security group.
If, for some reason, you cannot add Everyone or the computer or
running User Name Mapping to the Pre-Windows 2000 Compatible
Access security group, you can enable User Name Mapping to
enumerate users in the domain by running the User Name Mapping
service with an account that belongs to the Domain Admins group.
This method is less secure than the other two solutions, however,
and should be avoided if possible.
Cause: You have specified only the domain
name, and either the NIS server is on a different subnet, or the
NIS server is down.
Solution: Ensure that the NIS server is
running. Ensure that the computer running User Name Mapping and the
NIS server are on the same subnet, or specify the Internet Protocol
(IP) address of the NIS server.
Cause: The .maphosts file has not been
modified to specify trusted computers.
Solution: Ensure that the .maphosts file
specifies the names or Internet Protocol (IP) addresses of
computers that can map user accounts by using User Name Mapping.
For more information, see Controlling access to User
Name Mapping.
If users still cannot access NFS resources, see "Error message:
Unable to perform the requested operation as the mapping service
cannot be contacted" later in this topic.
Cause: The maximum number of concurrent client
connections has been exceeded.
Solution: If message appears frequently when
you are attempting to administer User Name Mapping, or if properly
mapped users cannot access NFS resources intermittently and other
troubleshooting steps have failed, you can increase the maximum
number of concurrent client connections that are allowed by
creating a DWORD registry value named
RpcMaxConcurrentConnectionsPerIp in the following
location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Services for
Unix\Global
The value must be between 16 (the default) and 64.
If the problem persists, or if NFS access performance noticeably
degrades, consider establishing a User Name Mapping server pool.
See Creating
a User Name Mapping server pool for more information.
Cause: Maps are saved to the registry, which
notifies User Name Mapping of the new map. Because this process can
take a minute or more, if you click Reload during that time,
you will not see current data.
Solution: Wait at least a minute, and then
click Reload again.
Cause: Maps have not been refreshed with new
or changed data in the Windows or UNIX user databases.
Solution: After adding or changing a user in
the Windows domain, the Network Information Service (NIS) domain,
or the PCNFS files, update User Name Mapping. On the
Configuration tab, click Synchronize Now, and then
click Apply.
Cause: The cluster service is not running, was
not running when User Name Mapping started, or failed after User
Name Mapping started.
Solution: Stop User Name Mapping, start the
cluster service if needed, and then restart User Name Mapping.
If replication consistently fails after the computer restarts,
it might be because User Name Mapping is starting before the
cluster service completes its start-up procedures. In this case,
use the Windows Services manager to make User Name Mapping
dependent on the cluster service.