| Event Id | 1064 |
| Source | nfssvr |
| Description | Server for NFS was unable to register a protocol on a port. One or more NFS services, including Server for NFS, may not be available. |
| Event Information | According to Microsoft : CAUSE: A required network port is not available.NFS uses the Network Lock Manager (NLM) protocol to provide file locking, the Network Status Manager (NSM) protocol to provide file locking status services, and the mount protocol to provide file share mounting services.If Server for NFS cannot register one of these protocols on their port, NFS clients may not be able to mount shares, establish locks, or even access Server for NFS. Another program may be blocking the port or may have registered it for its own use. By default, mount uses port 1048, NLM uses port 1047, and NSM uses port 1039. RESOLUTION: You should either close the program that registered the port or specify different ports for NLM, NSM, or mount using the nfsadmin command-line tool. For more information about using nfsadmin, type nfsadmin /? at the command prompt. You then need to start Server for NFS. Click Start and then click Control Panel. In Control Panel, double-click Administrative Tools, then double-click Microsoft Services for NFS. Click Microsoft Services for NFS. In the Action menu, click Start. |
| Reference Links | Event ID:1064 Of Source ID:nfssvr |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.