Client for NFS fails to restart - Event ID: 16387 - Windows(R) failed a request to initialize the Network File System (NFS) redirector
I have seen this issue out there in a few threads but a definitive solution has not been posted by Microsoft that I can find. So here is the simple answer. The long answer why this doesn't work on a default install of MSNFS is going to have to come from Microsoft and should be in the form of a hotfix.
On boot, Client for NFS starts and remains running. If an attempt is made to restart the service from the MMC or nfsadmin, an error occurs and nfsclnt fails to start.
Event log error:
Log Name: Application
Date: 7/7/2011 2:39:51 PM
Event ID: 16387
Task Category: None
Windows(R) failed a request to initialize the Network File System (NFS) redirector <[d:\w7rtm\base\fs\remotefs\nfs\client\nfsclient\service.c:199] : 0: The operation completed successfully.
Client for NFS cannot start.
Windows may be low on system resources. Try increasing available system resources by closing programs, then start Client for NFS manually.
PROBLEM CAUSED BY: When shutting down Client for NFS using the Services GUI, Client for NFS Redirector is not shut down
SOLUTION: Stop NFS Redirector - 'sc stop NfsRdr' - Then start NFS client service - 'nfsadmin start client'
Use 'nfsadmin client stop' to correctly shut down both the Client for NFS service and the Client for NFS Redirector.
'Network File System (NFS) redirector' is actually "Client for NFS Redirector" and not listed as a service even though "Client for NFS" requires it.
Using 'sc', details on the hidden NfsRdr system component can be queried and then used to stop the redirector so that nfsclnt.exe can reload it on start up using the Services GUI.
C:\Windows\System32>sc GetDisplayName NfsRdr
[SC] GetServiceDisplayName SUCCESS
Name = Client for NFS Redirector
C:\Windows\System32>sc qdescription NfsRdr
[SC] QueryServiceConfig2 SUCCESS
DESCRIPTION: Kernel-side part of Client for NFS. Enables a Windows based computer to access NFS server shares
Hope this thread is helpful !!
- Changed type T_W_Black Thursday, July 07, 2011 11:41 PM Lack of useful responses from MS
Thanks lot. I have restarted NFS client service successfully!
I am taking this forum further to highlight on my issue as restarting of both NFS client and NFS server didn't fixed my issue.
- Enabled NFS share on the directory in Windows Server 2008 R2 where both NFS client and NFS server services are running.
- And this NFS shared directory is mounted on to LINUX machine and application team used to execute their sql jobs and those jobs were visible in the windows machine in a text file format. This was fine for some time but from last week apps team unable to access this mounted shared directory from the Linux machine.
[odiadmin@oradb510 mnt]$ cd job
-bash: cd: job: Permission denied
- From windows side I have verified the permissions of files under NFS client -> it is set to read write execute for owner, groups and others as UNIX style permission. I have restarted both NFS services as well as told in the beginning.
- From Linux side we have unmounted and remounted again but still same error.
-Request your inputs on this and possible way to fix this issue. Other folks reply to this thread will be greatly helpful.
Your issue is a little outside the topic of this thread because it isn't to do with the nfs client not starting or the nfs redirector but rather NFS Authentication. You make no mention of how you are authorizing the Linux Users on Windows. If you have not created the local passwd/group mapping files or using AD / NIS integration, Linux users cannot be authenticated to access the share. Anonymous would be the only option and that's not very secure.
Start here to setup/confirm that the user mapping is working.
Hope that helps.
= NBU Guy =