| United States-English |
|
|
|
![]() |
HP 9000 Networking: NetWare 4.1/9000 Installation and Administration Guide > Chapter 8 Managing NetWareConfigure an IP Tunnelling Network |
|
IP tunnelling provides clients with access to NetWare servers that are connected over TCP/IP networks. A maximum of 16 remote systems (peers that are either NetWare servers or clients performing IP tunnelling directly) can be accessed from the NetWare 9000 server using IP tunnelling. NetWare 9000 provides IP tunnelling primarily for the purpose of limited wide area network communications over TCP/IP. Although IP tunnelling can be performed from PCs (for example, using Novell's LAN Workplace software) typically, it is intended for tunnelling between servers. NetWare 9000 does not provide dynamic IP tunnel attachment by default: all peer systems must be configured for IP tunnelling in SAM, as described in this section. Figure 8-1 shows an example network where IP tunnelling configuration can be used for a NetWare PC client (attached to Server 1) to access files on NetWare 9000 Server 2. The NetWare PC client shown in Figure 8-1 can map local drives to NetWare volumes on NetWare 9000 Server 2 only if IP tunnelling is active on both NetWare servers 1 and 2. With NetWare 4.1/9000, you can configure your NetWare server to support IP tunnelling as the only network, without using a default NetWare network as shown in Figure 7-2. The NetWare PC clients can map local drives to NetWare volumes on NetWare Server 2 only if IP tunnelling is activated on both NetWare servers 1 and 2. In this environment, there is no need to run the IPX/SPX protocol stack on NetWare Server 2. To configure IP routing of IPX packets, you create an IP tunnelling network between NetWare 9000 systems that will communicate using IP. To configure IP tunnelling:
Each step is described in the sections following. An IP Tunnelling Worksheet has been provided to help you configure your network. Complete the Worksheet:
|
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||