Downloads |
Document ID: 15004
Contents
Introduction
Prerequisites
Requirements
Components Used
Information
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document assumes a limited knowledge of TCP/IP. Even if you do not understand or have access to the NetWare TCP/IP Supervisor's Guide, you can still quickly add TCP support to your NetWare network that contains a LAN²LAN.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Information
Assume you have two NetWare v3.11 servers connected via LAN²LAN, and that one of these attaches to a dedicated IPX LAN, while the other attaches to a LAN which handles both IP and IPX traffic. The configuration is shown here. You can take advantage of NetWare and LAN²LAN multiprotocol support to let users on IPX Net A access services on the IP network.
+-----------+ +-----------+
| 3.11 | | 3.11 |
| ServerA | | ServerB |
+-----------+ +-----------+
+-----+-----+ +-----+-----+
| NIC | L2L | | L2L | NIC |
+-----+-----+ +-----+-----+
\ /
\ /
\ /
+---------------------+
| IPX Net B |
+---------------------+
|
|
+
/ \
/ \
/ \
+-----------+ +-----------+
| IPX Net A | | IPX Net C |
+-----------+ +-----------+
|
|
+--------------------------+
| Existing IP Net |
| 131.228.132 |
| sub-netted 255.255.255.0 |
+--------------------------+
Your new network might look like this:
+-----------+ +-----------+
| 3.11 | | 3.11 |
| ServerA | | ServerB |
+-----------+ +-----------+
+-----+-----+ +-----+-----+
| NIC | L2L | | L2L | NIC |
+-----+-----+ +-----+-----+
\ /
\ /
\ /
+---------------------------------+
| IPX Net B |
| 131.228.b.1 131.228.b.2 |
| 255.255.255.0 255.255.255.0 |
+---------------------------------+
|
|
+
/ \
/ \
/ \
+---------------+ +---------------+
| IPX Net A | | IPX Net C |
| 131.228.a.1 | | 131.228.132.x |
| 255.255.255.0 | | 255.255.255.0 |
+---------------+ +---------------+
|
|
+-------------------------+
| Existing IP Router |
| 131.228.132.021 |
+-------------------------+
NOTE: a and b are two sub-net addresses and x is a host address
assigned to you by the Administrator of network 131.228.
Your AUTOEXEC.NCF for Server A will be similar to this:
file server name SERVER_A ipx internal net A001 load tcpip forward=yes load NE2000 port=300 int=3 frame=ETHERNET_802.3 NAME=aipx bind ipx to aipx net=A load LAN2LAN port=258 mem=d80000 int=5 NAME=P258L1 bind ipx to P258L1 net=B bind ip to P258L1 addr=131.228.b.1 mask=255.255.255.0 load ne2000 port=300 int=3 frame=ETHERNET_II NAME=aip bind ip to aip addr=131.228.a.1 mask=255.255.255.0
Your AUTOEXEC.NCF for Server B will be similar to this:
file server name SERVER_B ipx internal net B001 load tcpip forward=yes load NE2000 port=300 int=3 frame=ETHERNET_802.3 NAME=bipx bind ipx to bipx net=C load LAN2LAN port=258 mem=d80000 int=5 NAME=P258L1 bind ipx to P258L1 net=B bind ip to P258L1 addr=131.228.b.2 mask=255.255.255.0 defroute=yes load ne2000 port=300 int=3 frame=ETHERNET_II NAME=bip bind ip to bip addr=131.228.132.x mask=255.255.255.0 gate=131.228.132.021
Note: The frame type for IP shown here as ETHERNET_II might be ETHERNET_SNAP on some networks. The parameter DEFROUTE on the BIND command for LAN2LAN for Server B broadcasts a default route for all traffic destined for unknown networks to Server B. The parameter GATE on the BIND command for the NIC on Server B creates a default router which routes all traffic for unknown networks to the indicated IP host, which is assumed to have a route to them.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for LAN |
| Network Infrastructure: LAN Routing and Switching |
| Network Infrastructure: Getting Started with LANs |
Related Information
| Updated: Oct 06, 2005 | Document ID: 15004 |