> We want to know what's involved to have a NFS mount > from one of our VM ID's to a Windows Server. > Basically what it does is it allows VM to see a > Windows folder as if it's a VM mini disk. Or vice > versa, from windows, a vm minidisk appears as if it is > a folder on the windows machine. It's a more secure > protocol then FTP.
In the general case, NFS is *less* secure than FTP. The FTP protocol requires the equivalent of a login and password. NFS requires no authentication at all -- just presentation of a numeric UID value, which, with two exceptions, is accepted without question (uid 0 and 32768 are the exceptions). Both are unencrypted on the wire. The CMS implementation of NFS is unusual in that it requires a userid and password to do much of anything. This is not the usual case. > I am looking for instructions on how > to set up a client on a WINDOWS 2000 workstation to > access the data. The instructions I found on the IBM > website pertain to Windows/NT. I may be restricted > here on doing the setup, just want to be sure that the > Windows/NT instructions pertain to Windows 2000 also. The instructions for the Windows setup will be peculiar to your NFS client implementation. Check with the NFS client vendor for details on that one. Once you've done it, most of the NFS clients just present a NFS resource as a drive letter, and the usual Windows stuff appears. > Is there a way for a VM userid to see a windows > folder?? If the Windows server has the MS Tools for Unix installed (or another NFS server product like the one in hummingbird), then Windows file structures can be exported and mounted via NFS. In that case, any NFS client can use them, including the CMS NFS client.
