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

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: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 :