Novell NETWARE 6, Manual

Page: 42 / 152

42
Internetwork Packet Exchange
Internetwork Packet Exchange
103-000176-001
August 29, 2001
Novell Confidential
Manual 99a
38
July 17, 2001
NOTE:
Before you can configure IPX to run over a WAN connection, you must
configure the WAN board, a network interface, and at least one WAN call
destination.
To configure static routes and services for a permanent or on-demand call,
refer to
“Configuring Static Routes and Services” on page 53 .
To configure watchdog packet spoofing, refer to “Configuring Watchdog
Spoofing” on page 65 .
To configure routed or static on-demand calls, refer to “Configuring
Routed or Static On-Demand Calls” on page 67 .
To configure header compression, refer to “Configuring IPX and NCP
Header Compression” on page 69 .
Š Whether to use NLSP, RIP/SAP, or both
NetWare Link Services Protocol
TM
(NLSP
TM
) software is the Novell link
state routing protocol for IPX internetworks; Routing Information
Protocol (RIP) and Service Advertising Protocol (SAP) are the traditional
NetWare routing and service advertising protocols.
To configure NLSP on your router, refer to “Configuring NLSP” on page
72 .
To configure RIP and SAP on your router, refer to “Configuring RIP and
SAP” on page 77 .
Š Whether to configure file server proxying on a dedicated router
File server proxying is useful when you have a dedicated router—a PC
running Novell Internet Access Server 4.1 over a two-user version of
NetWare 4.11—and several NetWare workstations operating on the same
network. Proxying enables the dedicated router to reply to workstations'
Get Nearest Server requests with the name of a NetWare file server
instead of its own. This enables the server, which has multiple connection
slots, to handle simultaneous NCP connection requests from the
workstations.
To configure file server proxying, refer to “Proxying a NetWare File
Server” on page 84 .