Client for NFS on Windows 2008 R2 does not work properly

Consider this scenario -

• On Windows 2008 R2 based system, you have installed Client for NFS component
• In the Client for NFS configuration, all three security flavors are selected - sys, kerb5, kerb5i

In this scenario, when you mount a NFS share from a NFS server and try to access it, you get the following error message:

Invalid drive letter.

With UNIX systems that can negotiate for Kerberos authentication, Client for NFS will negotiate over Kerb5 or Kerb5i before using AUTH_UNIX (sys). If the UNIX systems are not authenticating against Active Directory, this negotiation fails and "sys" security type negotiation never used.

The resolution is to select only �sys� option and reboot the system.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.