Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925637

From BetaArchive Wiki
Knowledge Base


Event ID: 1003 occurs every 30 minutes after you install Microsoft Services for network file system on a Windows Server 2003 R2-based computer

Article ID: 925637

Article Last Modified on 10/12/2006



APPLIES TO

  • Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003 R2 Standard x64 Edition
  • Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
  • Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Datacenter x64 Edition



SYMPTOMS

Consider the following scenario. You install Microsoft Services for network file system (NFS) on a Microsoft Windows Server 2003 R2-based computer. However, the User Name Mapping component is not installed on the computer. In this scenario, you receive the following event in Event Viewer every 30 minutes even though a User Name Mapping server is running on the network:
Event Type: Warning
Event Source: NfsSvr
Event Category: None
Event ID: 1003
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Mapping information could not be obtained from User Name Mapping. Another attempt will be made after 30 minutes.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Note By default, the User Name Mapping component is not installed when you install Microsoft Services for NFS.

This issue occurs when you do not have the User Name Mapping component installed on the server that has Microsoft Services for NFS installed.

CAUSE

This issue occurs because the server that has Microsoft Services for NFS installed is configured to use Localhost as the User Name Mapping server after you install Microsoft Services for NFS.

RESOLUTION

To resolve this issue, modify the setting of Microsoft Services for NFS by using the Nfsadmin utility. To do this, run the following command at the command prompt:

nfsadmin mapping config mapsvr=SERVER_NAME

Note SERVER_NAME represents the name of the server that has the User Name Mapping service installed on the network. Additionally, SERVER_NAME can also represent the IP address of the User Name Mapping server. Notice that you do not include spaces between mapsvr and the equal sign (=) in this command.

STATUS

This behavior is by design.

MORE INFORMATION

When you experience this issue, you can examine the setting of the User Name Mapping server by running the following command at the command prompt:

nfsadmin mapping

The output may appear as follows:

The following are the settings on localhost

Mapping Server :  localhost
AD Lookup :  Disabled
AD Domain :

Keywords: kberrmsg kbprb kbtshoot KB925637