| Event Id | 1004 |
| Source | NFSsvr |
| Description | User Name Mapping not configured for Server for NFS. You can configure this using administration tools. |
| Event Information | When the Services for UNIX (SFU) NFS server starts, it contacts the Username Mapping service and caches a copy of the mapping information. Then, every 30 minutes, the NFS server checks with the Username Mapping service to determine whether any changes have been made to the mapping database. If so, the NFS server requests the changes. However, the SFU NFS server is not checking for changes with the Username Mapping service every 30 minutes. NFS Server incorrectly calculates the nextRefresh value, so it never updates the mapping cache. CAUSE The NFS server has a thread that basically sleeps for 30 minutes. The calculation that computes the time has a problem that causes the computed time to be much longer than 30 minutes. RESOLUTION A supported fix is now available from Microsoft. |
| Reference Links | NFS Server Incorrectly Calculates the nextRefresh Value and Never Updates the Mapping Cache |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.