Error when installing NFS service on Windows 2016
Q: Any idea what can I check to solve this?
A: You can force WS2016 to work as NFS server but it won't be any good: Performance isn't great, and Microsoft (OK, University of Chicago actually) Windows NFS server stack is missing from major HCLs (VMware, Citrix etc). It would be a better idea to a) enable Hyper-V role, and b) install FreeBSD or Linux to make one of these guys work as a compatible and high performing NFS server.
After some research I discover that Portmapper need to bind the port 111 during the installation process. In my case the Veeam vPower NFS Service was using the port. after stopping the service Veeam vPower NFS Service
-
Check if something is listening on the port Open a command prompt and type:
netstat -aon | findstr 111
-
Stop the process responsible of using the port.
WARNING: If your server is in production, stopping a service may have some side effect. If you are unsure, your best bet is to plan an intervention off production time.
-
Install the NFS service.
-
Restart the service stopped in the step 2.