SFU enables the use of Windows and Linux resources-Linux Enterprise applications-Linux server application information. The following is a detailed description. Due to the flexibility and stability of Linux and the ease of use of Windows, in many enterprises, the hybrid network of Linux + Windows is increasing, and the mutual access between the two operating systems is also becoming more and more frequent. When talking about the use of Windows and Linux resources, many people immediately think about Samba in Linux. Indeed, Samba is easy to configure and its stability is also mentioned, but it is not so convenient for clients.
First, the client needs to modify the Registry. Not every customer can modify the Registry. On the other hand, Samba also requires Windows 98 users to have Linux access permissions. However, considering the popularity and usage of Linux, it is still difficult for Linux to take on the management of enterprise users. Therefore, Samba can only meet the requirements of individual users to access Linux resources, and does not allow more users in the enterprise to access Linux. To solve this problem, try Windows Services for UNIX (SFU). I use version 2.
SFU 2.0's access to Linux is mainly based on Network File System (NFS). It provides a method to share files or directories of computers on the Network, it makes the user feel like accessing the local file system when accessing these files. For Red Hat Linux, it is very easy to configure the NFS service. You only need to declare the directory to be shared in the "directory hostname (options)" format in the/etc/exports file.
SFU 2.0 provides two methods for users to access Linux's NFS file system. One way is to provide users with an NFS client component. After installing this component, users can directly access Linux through the files and directories shared by NFS. This component can be used on Windows NT or Windows 2000. Another method is that SFU 2.0 provides an NFS Gateway component that enables Windows NT (2000) Server to map Linux shared directories to the directories of the cost machines, and share the directory as a Windows directory. In this way, other clients access common Windows shared resources. However, this method requires that the machines that install SFU 2.0 must be Windows NT Server or Windows 2000 Server, in this way, shared directories can be used by Windows 98/95, NT, 2000, and other users. Therefore, the second method is more suitable for enterprises with complex network environments and centralized user management.
Let's take a look at how SFU 2.0 works. The first is software installation. We recommend that you make a choice when the interface appears.
(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // tech.ccidnet.com/col/attachment/2002/10/41030.gif'); ">
Select custom installation
If "Client for NFS" is selected, the NFS Client component is installed on the computer. After this component is installed, the interface appears when the user accesses the network neighbor again. In this case, you can access the NFS files and directories shared by Linux.
(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // tech.ccidnet.com/col/attachment/2002/10/42431.gif'); ">
Install the NFS client component on the computer
If the NFS client is not selected during installation, the "Gateway for NFS"-NFS Gateway component is selected, after the component is installed, you can run "Start> program> Windows Services for UNIX-Gateway for NFS Configuration" to display the interface.
(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // tech.ccidnet.com/col/attachment/2002/10/42432.gif'); ">
Select NFS gateway Components
Enter the Share Name in "Share Name", select the Resource to be mapped in the "Network Resource" window, and click "Permissions... "to configure the access permission for the shared directory, as shown in figure 4.
(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // tech.ccidnet.com/col/attachment/2002/10/42433.gif'); ">
Add users and groups
In this way, the shared directory "\ tmp \ data" in Linux is mapped to the shared directory "data sharing" in Windows 2000 Server ", all customers can access Linux shared data just like accessing shared data in Windows networks. As for access permission management, this is related to the restrictions of Windows 2000 Server, but not Linux. That is to say, users' access permissions are not restricted by Linux.
In fact, SFU 2.0 not only provides a way for Windows to access Linux NFS, but also shares Windows directories with NFS. If you select "Server for NFS" during installation, the Linux host can access Windows data.
(400) {this. resized = true; this. width = 400; this. alt = 'click here to open new window';} "onmouseover =" if (this. resized) this. style. cursor = 'hand'; "onclick =" window. open ('HTTP: // tech.ccidnet.com/col/attachment/2002/10/41034.gif'); ">
Share Windows directories with NFS
For example, NFS sharing is performed on a directory on the host whose IP address is 10.12.110.35. You can right-click the shared directory, select "NFS Sharing", and select "Share this folder" and "Permissions", as shown in Figure 5. Finally, complete NFS sharing. To access this shared resource on a Linux host, run the following command: "mount 10.12.110.35: \ document \ tmp \ data ". When you access the \ tmp \ data directory, you are actually accessing the Windows NFS directory. Note that the \ tmp \ data DIRECTORY must exist beforehand.
SFU 2.0 has far more functions than that. It can also move the Unix Network Information Service (NIS) source files from the NIS domain to the Windows 2000 Active Directory Service for unified account management; it can synchronize the passwords of the two platforms, it makes maintenance easier for users. It can associate Windows and Unix user names, allowing users to connect to NFS resources without having to log on to the Unix system ...... It has far more functions than Samba. If you are interested, explore it yourself! However, we would like to remind you that you must pay attention to access permission restrictions when configuring NFS. Do not leave security risks.
