Connection between WinNT, Linux, Unix, and other servers

Connection between WinNT, Linux, Unix, and other servers-Linux Enterprise Application-Linux server application information. For details, refer to the following section. Since Novell NetWare uses the IPX/SPX protocol, access to NetWare resources in Windows NT is converted through the Protocol. The Windows NT Server provides the GSNW gateway service, allowing Dos/Windows users to indirectly access NetWare resources by accessing the Windows NT Server.
　　
　　　　 1. configuration of the Novell NetWare Server
　　
First, create a user group called NTGATEWAY on the NetWare server, and grant some permissions to the NTGATEWAY user group on the directory you want to share. Then, include the user used as the gateway account in the NTGATEWAY group. You can use NetWare's NETADMIN (Dos version) or NWADMIN (Windows Version) utility to create user groups and users.
　　
　　　　 2. Windows NT Server Configuration
　　
GSNW service of Windows NT server requires Nwlinnk network protocol support. Therefore, you must first add the Nwlink protocol on Windows NT Server. Run the NetWare program in the Control Panel on the NT Server and choose to install the Nwlink Protocol. Note that, the frame type used by Nwlink should match the frame type used on the Novell NetWare server to be accessed. Then, install the GSNW service, run the NetWare program in the Control Panel, and select to install the GSNW service. After the installation is complete, restart the computer and a GSNW icon appears in the Control Panel to select the default NetWare server and NetWare print queue. Use the GSNW icon of the Control Panel to activate the NetWare gateway service program, in the Default Tree and Contex options, enter the Tree name and User Account of the NetWare server (User Account in the NTGATEWAY group. After this configuration, the NT Server can share the NetWare resources and map the NetWare resources to the local disk. the NT clients (Dos, Win95/98, NT Workstation, and NT Server) you can access the disk to indirectly access NetWare resources.
　　
　　　　 The advantages of using GSNW are:
　　
The client only needs to log on to the Microsoft Network.
　　
The gateway only wants to log on to a NetWare user, but many users share the NetWare resources. In this way, the access permission to the NetWare server is legally extended, without additional NetWare licenses-the client only needs a client software package, especially in memory-constrained MS-DOS systems, which saves much memory.
　　
· Reduces the management burden by eliminating the need to support multiple client request programs.
　　
　　　　 The disadvantage of using GSNW is:
　　
Because the client must access NetWare resources through the GSNW gateway of NT, the efficiency is not very high and is suitable for the case where the NetWare server is not frequently accessed.
　　
Interconnection between Unix and Linux servers and Windows NT servers
　　
Both Linux and Unix hosts use the TCP/IP protocol. To share information with other Linux Hosts or Unix hosts, there are many convenient and mature tools such as FTP or NFS. Similarly, Windows NT supports the TCP/IP protocol. Therefore, the exchange of information between the NT Server and the Linux host or the Unix host can also be over FTP or NFS. However, FTP and NFS are not intuitive enough. To facilitate information sharing between Windows, Linux, and Unix, we can use the Samba service program provided by Linux, just like between Windows and Windows. Samba is a set of programs that allow your Linux to understand the SMB protocol (server message block. The SMB protocol is widely used in OS/2, Windows NT, Windows 95, Windows for workgroups, and other Windows series. It is mainly used for file and printer sharing. So that your Linux will appear in "Network Neighborhood", just like other Windows machines. Windows users can log on to your Linux machine and use their permissions to communicate with the Unix File System in two ways. They can also submit jobs to the Linux printer.

2.1 Samba Composition
　　
A samba server actually contains two server programs: smbd and nmbd. Smbd is the core of samba. It establishes dialog processes, verifies user identities, and provides access mechanisms to file systems and printers. Nmbd implements the "network browser" function. It is used to publish services available to samba servers. Nmbd enables the samba server to appear in "Network Neighborhood" (Network neighbor) of Windows 95 or Windows NT and allows the client to browse accessible resources. You can start the samba server process without running nmbd. However, in addition to the NetBIOS Name of the samba server, you may also want to see the services that the samba server can provide.
　　
2.2 Samba Configuration
　　
Because SMB is a very complex protocol, it is very complicated to configure samba. About 170 configuration items appear in the smb. conf file. In RedHat and Debian, the default location of the Smb. conf file is under/etc/. All samba programs must refer to this configuration file. Its structure is very similar to the Windows *. ini file. Each section of the file starts with an identifier enclosed by square brackets, such as [global], [home], and [printers].
　　
Each configuration parameter is either a global parameter (affecting or controlling the entire server) or a service parameter (affecting or controlling a service provided by the server ). In the [global] section, set global options and some default service options. [Home] is used to dynamically map to the home Directory of each user. The [printers] section is used to share a printer configured according to the system printcap file to a specified user.
　　
2.3 A simple smb. conf
　　
The smb. conf below depicts a simple but working Configuration:
　　
[Global]
Netbios name = ABC workgroup = WORKGROUP server string = Linux
Security = user printing = lprng
　　
[Homes]
Comment = Home Directory browseable = no read only = no
　　
In the [global] section, set the netbios Name of the host, the Group Name of the Working group where the host is located, and the prompt string that will appear in the browse list. The security parameter prompts samba to use the "user level" (user level) security level. SMB has two security levels: share (share level, password protection for each specific resource, and specifying that each user has different access permissions) and user level (user level ). However, in most cases, you use user-level security. Because no special encryption method is specified, samba uses the standard unix password verification method by default to verify each connection. If you use the PAM module in linux, you must modify the PAM Configuration so that samba can verify the password in the password database. RadHat automatically performs these operations.
　　
The settings in the [homes] section are used to control the sharing of each user's home directory. Comment parameter indicates the string in the browse list. The browseable parameter controls whether the service appears in the browse list.
　　
The following configuration allows each user who can log on to the samba server to use a printer defined in the system printcap file.
　　
[Printers]
Browseable = no guest OK = yes printable = yes
　　
After completing the configuration of the smb. conf file, you can use the Testparm command to quickly check the syntax error of the smb. conf file. Through the above configuration, run the Samba service programs: smbd and nmbd on the Linux host. Windows, Unix, and Linux can easily exchange data.