Interoperability with UNIX

Microsoft s primary interoperability solution for UNIX is Microsoft Windows Services for UNIX. At the time of this writing, the current version is Microsoft Windows Services for UNIX 3.0.

Microsoft Windows Services for UNIX provides a comprehensive set of services, tools, and applications that allow you to integrate Windows-based computers, including Windows XP Professional-based computers, into your existing UNIX environment. Windows Services for UNIX supports flexible file sharing between Windows-based and UNIX-based computers. Additionally, Windows network administrators can use Windows Services for UNIX to manage Network Information Service (NIS) domains.

Windows Services for UNIX 3.0 includes the following components:

• Interix. A comprehensive implementation of a POSIX-compliant environment that includes the C and Korn command shells and over 350 utilities. These utilities enable you to leverage your existing scripts and UNIX knowledge to administer Windows computers and run UNIX applications directly on Windows computers.

  Note 

  Some of the Interix utilities are covered by the GNU General Public License (GPL), and you may choose not to install these GPL utilities. Note, however, that if you do not install these utilities, the overall functionality of Interix will be limited.

• Interix Software Development Kit. Using the tools, libraries, and documentation provided in the Interix Software Development Kit (SDK), you can port your UNIX applications to run on Windows computers through the Interix subsystem. Some of the SDK tools are covered by the GPL; you may choose not to install these tools.

• User Name Mapping. This component provides centralized mapping between Windows user accounts and UNIX accounts for Client for NFS, Server for NFS, Gateway for NFS, and Interix. With User Name Mapping, Windows and UNIX users can access files on each other s computers transparently and without compromising security. User Name Mapping can use UNIX accounts from Personal Computer Network File System (PCNFS) servers or Network Information System (NIS) servers.

• Client for NFS. With Client for NFS, Windows-based computers can map an exported NFS share to a drive letter. This lets users access files on the file system as though they were on a local disk drive. They can also access NFS shares using Universal Naming Convention (UNC) names. Users can receive UNIX authentication credentials through User Name Mapping or from a PCNFS server (either UNIX based PCNFS daemon (PCNFSD) or Server for PCNFS running on a Microsoft Windows NT based or Microsoft Windows 2000 based computer).

• Server for NFS. The administrator of a Windows computer can use Server for NFS to share directories as NFS exported file systems, which makes it possible for UNIX-based clients to mount a shared directory just as they would an exported file system located on a UNIX server. User-level security is maintained because, in conjunction with Server for NFS Authentication, User Name Mapping maps the UNIX client s user identifier (UID) and group identifier (GID) to existing Windows user accounts. This ensures that UNIX clients are given appropriate access to files on Windows-based servers.

• Gateway for NFS. With Gateway for NFS, Windows users can access exported file systems on NFS without running special client software on their computers. The Windows server running Gateway for NFS mounts exported file systems on UNIX-based NFS servers and then shares those mounted file systems as Windows networking shared folders. Gateway for NFS relies on User Name Mapping to provide the appropriate UID and GID for the Windows user, which allows transparent access to UNIX-based files without requiring users to log on to Windows and UNIX systems separately.

  Note 

  Gateway for NFS runs only on Windows Server servers. It does not run on Windows XP Professional based computers.

• Server for PCNFS. This component is similar to a PCNFS daemon (PCNFSD) running on a UNIX server. Windows users running PCNFS or Windows Services for UNIX Client for NFS version 1.0 software on their computers can access NFS file systems by providing the required UNIX user name and password when they attempt to access an NFS file.

• Server for NIS. This component completely integrates UNIX Network Information System (NIS) networks with Windows Active Directory . Windows Services for UNIX includes a wizard that a Windows domain administrator can use to export NIS domain maps to Active Directory entries. Once this is done, an Active Directory domain controller running Server for NIS becomes the master server for the NIS domain.

  Note 

  Server for NIS runs only on Windows Server servers. It does not run on Windows XP Professional based computers.

• Password Synchronization. This feature automatically changes a user s password on the UNIX network when the user changes his or her Windows password, or vice versa. This allows users to maintain just one password for both networks.

• Telnet Client and Telnet Server. Windows users are given command-line access to UNIX systems through the popular Telnet terminal protocol. By taking advantage of Windows authentication, users of Telnet Client can log on directly to computers running Telnet Server, eliminating the need to send unencrypted passwords over the network.

  Note 

  Telnet Server runs only on Windows Server servers. It does not run on Windows XP Professional based computers.

• The Windows-based Remote Shell service. Users of remote computers use the Windows-based Remote Shell service to carry out commands on the server.

• The Windows-based Cron service. Runs commands scheduled using the crontab utility.

• ActiveState ActivePerl. Allows Perl scripts to run on a Windows computer.

For more detailed information about Windows Services for UNIX, see http://www.microsoft.com/windows/sfu/