User`s guide
Table Of Contents
- Ascend Customer Service
- How to use this guide
- What you should know
- Documentation conventions
- How to use the on-board software
- Manual set
- Configuring WAN Connections
- Configuring IP Routing
- Introduction to IP routing on the Pipeline
- Managing the routing table
- Parameters that affect the routing table
- Static and dynamic routes
- Configuring static routes
- Specifying default routes on a per-user basis
- Enabling the Pipeline to use dynamic routing
- Route preferences
- Viewing the routing table
- Fields in the routing table
- Removing down routes to a host
- Identifying Temporary routes in the routing table
- Configuring IP routing connections
- Ascend Tunnel Management Protocol (ATMP)
- IP Address Management
- Connecting to a local IP network
- BOOTP Relay
- DHCP services
- Dial-in user DNS server assignments
- Local DNS host address table
- Network Address Translation (NAT) for a LAN
- Configuring IPX Routing
- How the Pipeline performs IPX routing
- Adding the Pipeline to the local IPX network
- Working with the RIP and SAP tables
- Configuring IPX routing connections
- Configuring the Pipeline as a Bridge
- Defining Filters and Firewalls
- Setting Up Pipeline Security
- Pipeline System Administration
- Pipeline 75 Voice Features
- IDSL Implementations
- APP Server utility
- About the APP Server utility
- APP Server installation and setup
- Configuring the Pipeline to use the APP server
- Using App Server with Axent SecureNet
- Creating banner text for the password prompt
- Installing and using the UNIX APP Server
- Installing and using the APP Server utility for DO...
- Installing and using the APP Server utility for Wi...
- Installing APP Server on a Macintosh
- Troubleshooting
- Upgrading system software
- What you need to upgrade system software
- Displaying the software load name
- The upgrade procedure
- Untitled
Configuring IPX Routing
How the Pipeline performs IPX routing
4-10 Preliminary January 30, 1998 Pipeline User’s Guide
and drops any SPX-watchdog keep-alive packets from the LAN, without sending
them on to the WAN. You do not need to set any parameters to enable this
function; however, note that routers on both ends of the connection must support
this feature for it to function.
WAN considerations for NetWare client software
In most cases, NetWare clients on a wide-area network do not need special
configuration. But the following issues sometimes affect NetWare clients in an
IPX routing environment:
• Preferred servers
If the local IPX network supports NetWare servers, configure NetWare
clients with a preferred server on the local network, not at a remote site. If
the local Ethernet does not support NetWare servers, configure local clients
with a preferred server on the network that requires the least expensive
connection costs. (For more information, see your NetWare documentation.)
• Local copy of LOGIN.EXE
Due to possible performance issues, executing programs remotely is not
recommended. You should put LOGIN.EXE on each client’s local drive.
• Packet Burst (NetWare 3.11)
Packet Burst lets servers send a data stream across the WAN before a client
sends an acknowledgment. It is included automatically in server and client
software for NetWare 3.12 or later. If local servers are running NetWare
3.11, they should have PBURST.NLM loaded. (For more information, see
your NetWare documentation.)
• Macintosh or UNIX clients
Both Macintosh and UNIX clients can use IPX to communicate with servers.
However, both types of clients have native support for AppleTalk
(Macintosh) or TCP/IP (UNIX).
If Macintosh clients need to access NetWare servers across the WAN using
AppleTalk (rather than MacIPX), the WAN link must support bridging, or
else the AppleTalk packets will not make it across the connection.
If UNIX clients need to access NetWare servers using TCP/IP (rather than
UNIXWare), the Pipeline must be configured as a bridge or IP router, or else
the TCP/IP packets will not make it across the connection.