http://www.oreillynet.com/cs/user/view/cs_msg/15337
Someone pointed to a Microsoft package:
http://www.microsoft.com/windows/sfu/default.asp
http://www.microsoft.com/technet/interopmigration/unix/sfu/default.mspx
It's free from microsoft, but you have to provide personal information (address).
http://www.microsoft.com/technet/interopmigration/unix/sfu/nfsauth.mspx
Introduction
Microsoft Windows Services for UNIX version 3.0 (SFUv3) includes key filesystem interoperability components that allow Microsoft Windows computers to function effectively in a Network File System (NFS) environment. These include Client for NFS, Server for NFS and Gateway for NFS. To enable these components to work effectively, SFUv3 must be able to accurately identify and authenticate users against both their native operating system and the remote operating system as appropriate. By default, NFS uses the UNIX method of identifying and authenticating users.
Note: Throughout this document, we refer to resources and authentication of UNIX users and computers. This is shorthand for UNIX and Linux users and computers.
Components
There are a number of components to Services for UNIX that are either involved in the authentication, or dependent on it. These include:
| • | User Name Mapping Server – Maps UNIX users to Windows users and vice versa. Even when a user has exactly the same name on both systems, it is not actually the same user, so some mechanism is necessary to let the other components of SFUv3 know that Windows user jdoe is the same as UNIX user johnd. |
| • | Server for NFS Authentication – This isn't a server at all, but an authentication component used by Server for NFS. Install this component on any Windows server that might be involved in user authentication. |
| • | Server for PCNFS – This server is not used by other components of SFUv3, but can be used by other NFS programs that expect to see PCNFSD, including SFUv1. |
| • | Client for NFS – The Windows NFS client component of SFUv3. Client for NFS allows the machine on which it is installed to access and use NFS resources anywhere on the network. |
| • | Gateway for NFS – A special NFS client that enables a single Windows Server to provide access to NFS resources for other Windows computers that don't have any SFUv3 components installed at all. (Note: Client for NFS and Gateway for NFS are mutually exclusive – only one or the other may be installed on a machine.) |
| • | Server for NFS – The Windows NFS server component of SFUv3. Server for NFS allows the machine on which it is installed to provide file system resources to NFS clients anywhere on the network. |
What Needs To Be Installed?
To use any of the NFS components in SFUv3, you will need to install and configure User Name Mapping Server. This is true whether you are using PCNFS or NIS for authentication. User Name Mapping Server is the core component that is required for any authentication of NFS in SFUv3.
You will also need to install the appropriate client and server components of the Services for UNIX NFS suite. To share files from a Windows server or workstation to UNIX clients, you will need to install Server for NFS on the machine providing the file services. To use files stored on UNIX hosts, you will need to install either Client for NFS or Gateway for NFS on a Windows server or workstation. You cannot install both – they are mutually exclusive. Client for NFS is appropriate for individual workstations or servers and provides access to files on the remote host for that workstation or server only. Gateway for NFS can only be installed on a server class Windows product. It provides access to files on the remote host to all Windows computers on the network, without requiring additional software on the downstream Windows computers.
HOW TO: Configure the User Name Mapping Service
How to install Client for NFS on Windows for a UNIX-to-Windows migration
What I actually did:
1. download "Window Services for UNIX": filename: SFU35SEL_EN.exe
2. run SFU35SEL_EN.exe, it is a self-extracting compressed file.
3. from the un-compressed directory, run installer: SfuSetup.msi
4. from installer GUI, select (a) User Name Mapping Server (b) NFS Client to install, igore other packages.
5. During installation, choose to use passwd and group file for authentication becaseu I am not using NIS at home. This requires /etc/passwd and /etc/groupd files to be copied from Linux NFS server to local XP machine. Provide the location of these 2 file (I copied them to c:\etc\) on the XP machine to the installation utility.
6. After installation, goto Start-> Windows Services for UNIX -> Services for UNIX Administration, which is a GUI for configuring the User Name Mapping Server and NFS Client.
7. Use simple setup for User Name Mapping Server because it is installed on the local XP machine. Use this Admin utility to automatically generate mapping config files.
8. Setup is done. Goto file explore and mount the network drive at xx.x.x.x:\mhe\amd900_export, which looks the same as Samba mount.
Viola.
No comments:
Post a Comment