Mount on Windows client is a bit different. Here are the steps to mount
export on Windows:

1. Enable NFS Client on the Windows client system.

Step 1. Enable File Services Role. Go to Server Management – > Add Roles ->
File Services

Step 2. Install Services for Network File System. Go to File Services – >
Add Role Services

2. Mount the export, can use either mount command or "net use" command:
c:> mount * 192.168.111.158! <== note, "*" can also be a drive character
here
c:> net use Z: 192.168.111.158!

(there is a space between Z: and <IP-address>!

another important thing is ! mark, this does the trick. Withoutout !,
Windows NFS client doesn't work with root export "/")

There is a user mapping issue: map Windows users to Linux users.
Since NFS gateway doesn't recognize Windows users, it maps them to the
Linux user "nobody".

To do any data I/O test, you can create a directory on HDFS and give
everyone access permission.

In reality, most administrators use Windows AD server to manage the user
mapping between Windows and Linux systems so the user mapping is not an
issue in those environments.
 Thanks,
Brandon
On Fri, Dec 20, 2013 at 4:06 PM, Brandon Li <[EMAIL PROTECTED]> wrote:

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB