لطفا منتظر باشید ...
Configuring Services for UNIX on Windows 2000 Professional
There are different ways to implement the components included with Services for UNIX on Windows 2000 Professional. One scenario is to implement Services for UNIX on Windows 2000 Professional-based computers in an environment without Windows 2000 Server. To do this, install and configure the following Services for UNIX components: Username Mapping Server, Client for NFS, and Password Synchronization. Then, install and configure LPR printing on each of the Windows 2000 Professional-based computers. With these components installed on Windows 2000 Professional, you can now be authenticated and access NFS files on UNIX computers, synchronize passwords, and print to a UNIX printer from Windows 2000 Professional. In this scenario, Username Mapping Server depends upon a UNIX NIS server or a UNIX PCNFSD server. Figure 25.8 illustrates this scenario.
Figure 25.8 Scenario I
Another scenario for implementing Services for UNIX on Windows 2000 Professional-based computers is to install and configure Client for NFS, Password Synchronization, and LPR printing on each of the Windows 2000 Professional-based computers. Then, for the ability to migrate UNIX NIS maps into Active Directory, install Server for NIS on Windows 2000 Server (configured as a domain controller). With these components installed on Windows 2000 Professional and Windows 2000 Server, you can authenticate users on your network, grant access to NFS files on UNIX computers, synchronize passwords, and print to a UNIX printer from Windows 2000 Professional. Figure 25.9 illustrates this scenario.
Figure 25.9 Scenario II
For user authentication and mapping in both of the preceding scenarios, you can use either Server for PCNFS or Server for NIS components from Services for UNIX, or PCNFSD server or NIS server on a UNIX computer.The Services for UNIX components that are used in the preceding scenarios and that you can install on Windows 2000 Professional (Server for PCNFS, Client for NFS, Password Synchronization, and Username Mapping Server) are described in greater detail in the following sections.
Configuring Server for PCNFS
When configuring Server for PCNFS on Windows 2000 Professional, you have the ability to define both users and groups. The users and groups that you define when you configure the Server for PCNFS, must already be defined on the UNIX hosts from which you access files. If you do not know the user name, user identifier (UID), or group identifier (GID), you can acquire this information from the UNIX host. For more information about how to determine the user name, UID, and GID, see your UNIX software documentation. To access Server for PCNFS
Click the Start button, point to Programs, and then click Windows Services for UNIX.Click Services for UNIX Administration.Double-click Server for PCNFS.You can configure Server for PCNFS from this screen.
Configuring Client for NFS
When configuring Client for NFS on Windows 2000 Professional, you only need to know the name of the mapping server that you use for authenticating and mapping users.You can use Nfsadmin.exe, a command-line utility, for configuration and administration of Client for NFS. Nfsadmin uses the following syntax:
nfsadmin client computer-name option=valuewhere client indicates that you want to configure the NFS Client and computer-name is the name of the computer which is running the NFS Client.Table 25.8 lists the command-line options that you can use with Nfsadmin to configure Client for NFS.Table 25.8 Nfsadmin Command-Line Options
| Option | Value |
|---|---|
| mapsvr | Computer name of the mapping server. |
| preferTCP | YES or NO, to indicate whether to use TCP. |
| mtype | HARD or SOFT, to indicate the type of mount. |
| retry | Number of retries for a soft mount. The default value is 5. |
| timeout | Time-out, in seconds, for an RPC call. |
| perf | MANUAL or DEFAULT, to indicate the method of determining performance parameters. |
| rsize | Size of the read buffer, in kilobytes. |
| wsize | Size of the write buffer, in kilobytes. |
| fileaccess | UNIX file permissions for reading, writing, and executing. For more information about UNIX file permissions, see Services for UNIX Help. |
To access Client for NFS
Click the Start button, point to Programs, and then click Windows Services for UNIX.Click Services for UNIX Administration.Double-click Client for NFS.You can configure Client for NFS from this screen.
After you configure Client for NFS, you can mount files directly from UNIX hosts in Windows 2000 Professional by using either Windows Explorer or the command prompt. To access NFS Files and Directories with Windows Explorer
In Windows Explorer, double-click My Network Places.Double-click Entire Network.Double-click NFS Network.Double-click the appropriate NFS LAN, for example, Default LAN.A list of available NFS servers appears.Double-click the appropriate NFS server.A list of exported NFS shares appears. Select the file and/or folders you want to open.
NOTE
When you attempt to access NFS files and directories from Windows 2000 Professional and do not see any NFS volumes available, it is likely that the NFS directories and files have not been configured to be exported on your UNIX host. Refer to your UNIX documentation for more information about exporting NFS directories and files.
NOTETo access NFS Files and Directories from the Command Prompt
If your user name exists in the authentication domain (PCNFSD/NIS), you are able to access the NFS resources with proper credentials. If your user name does not exist in the NIS/PCNFSD domain, you must access the resources as an anonymous user. However, you can change logon credentials by selecting Connect using a different user name. You can then provide the NIS/PCNFSD credentials you want to use to access Server for NFS.
At the command prompt, type the following command:mount [switches] [network path] [drive | *]where switches is one or more of the switches listed in Table 25.9, network path is the network path to the NFS volume you want to mount, and drive is the drive letter to assign to the mounted volume (asterisk indicates the next available letter).
Table 25.9 Mount Parameters and Descriptions
| Switches | Description |
|---|---|
| -u:[user name][password | *] | User name and password are the user name and password to use for mounting the NFS volume. If you use an asterisk for password, you are prompted for the password. |
| -o rsize=n | Size of the read buffer, in kilobytes. |
| -o wsize=n | Size of the write buffer, in kilobytes. |
| -o timeout=n | Time-out for NFS connections, in tenths of a second. |
| -o retry=n | Number of times to attempt a soft mount. Default value is 5. |
| -o mtype=[ soft | hard ] | Specify soft or hard mount. |
| -o anon | Mount as anonymous user. |
| -o nolock | Disable locking. This option improves performance if you only need to read files. |
| -o EUC | Enable extended UNIX code set (EUC). |
Configuring Password Synchronization
When configuring Password Synchronization on Windows 2000 Professional, you need to specify the name of the Windows 2000 computer that is running the Password Synchronization service. You also need to know the name of the UNIX host with which you synchronize passwords. To access Password Synchronization
Click the Start button, point to Programs, and then click Windows Services for UNIX.Click Services for UNIX Administration.Double-click Password Synchronization.You can configure Password Synchronization from the Password Synchronization dialog box.
NOTE
It is also necessary to verify that the single sign-on daemon (SSOD), which is on the UNIX host where you synchronize passwords, is installed and configured correctly. For more information about SSOD, see "Installing Password Synchronization" earlier in this chapter.
Configuring Username Mapping Server
When configuring Username Mapping Server on Windows 2000 Professional, there are two ways to specify how mappings can occur. Username Mapping Server allows either simple user maps or advanced user maps.With simple user maps, the accounts with the same user name in the Windows domains and the UNIX domains are mapped. You can use either a PCNFSD server, where password and group files reside, or an NIS server for authentication. This is true for both simple and advanced user maps; you only need to know the name of the authentication server.Advanced user maps do not require that the user names match. When using advanced user maps, you only need to know the name of the Windows domain and the UNIX domain for the users that need service from Username Mapping Server. After you enter the correct names, a listing of defined users in each domain is displayed from which you can map users between both domains.
Configuring LPR Printing
To print to a remote UNIX printer configured with Line Printer Daemon (LPD), you must first configure Windows 2000 Professional to print with Line Printer (LPR). Do this by installing Print Services for UNIX and installing and configuring a print driver to print with LPR as the printer port. To install Print Services for UNIX
In Control Panel, double-click the Network and Dial-up Connections icon.On the Advanced menu, click Optional Networking Components.In the Components list, click Other Network File and Print Services, and then click Details.Click Print Services for UNIX, and then click OK.
To add an LPR port
In Control Panel, double-click the Printers icon.Double-click Add Printer, and then click Next.Click Local printer, clear the Automatically detect my printer check box, and then click Next.Click Create a new port, and then click Standard TCP/IP Port.Click Next, and follow the instructions on the screen to finish installing the TCP/IP printer.
