From: francis@kingston.ac.uk (Francis Bell)
Newsgroups: comp.sys.novell
Subject: Re: Routing TCP/IP through a Novell server
Summary: Anyone care to tell me how ??
Keywords: routing, TCP/IP
Date: 13 Aug 92 12:22:44 GMT
Followup-To: comp.sys.novell
Organization: Kingston University

In article <1992May9.172817.55355@cc.usu.edu> jrd@cc.usu.edu writes:
>In article <1992May9.214953.6692@willamette.edu>, dan@willamette.edu (Daneher D. Revel) writes:
>> I would like to be able to use a Netware server to route TCP/IP traffic
>> between a Novell LAN and our campus wide TCP/IP backbone, here's a
>> picture:
We're trying to do the same thing, and it's driving me nuts. We have a
Novell server running 3.11 and a pair of 3c507's installed. Are there
any known problems with 3c507s ?  The workstations on the local
(Novell) segment can "see" the first 3c507 but not the second. Yes
we do have tcpip forward=yes. We're using LAN workplace for DOS on
the workstations, and we can use tnvt220 to reach the "closer" of
the two boards on its test port, 19 (tnvt220 141.241.12.2 19 works fine).
The second (further) 3c507's test port does not respond, neither
does anything further down the main backbone. Tcpcon reports that
ipforwards = 0, even after several attempts,
which is reassuring, because at least it isn't saying
"Gateway functions disabled"

Here's a copy of the autoexec.ncf file :


file server name PALLAS
ipx internal net 204
rem board 1 at 300 sees local network
load c:3C507 port=300 mem=D0000 int=3 frame=ETHERNET_802.3 name=IPX_300
bind IPX to IPX_300 net=234
rem board at 320 sees main network
load c:3c507 port=320 mem=d8000 int=7 frame=ETHERNET_802.3 name=IPX_320
bind IPX to IPX_320 net=200

load c:3c507 port=300 mem=D0000 int=3 frame=ETHERNET_II name=IP_300
load c:3c507 port=320 mem=d8000 int=7 frame=ETHERNET_II name=IP_320

load tcpip forward=yes rip=yes
load snmplog

rem bind local board to segment 12
bind IP to IP_300 addr=141.241.12.2 mask=ff.ff.fc.00
rem bind remote board to segment 4
bind IP to IP_320 addr=141.241.4.28 mask=ff.ff.fc.00

mount all
load remote khpallas
load rspx
load tsa
load monitor
set timezone gmt0bst
set reply to get nearest server = on
load rarpserv


>---------------------------------------------------------------------> 

Our main network has IPX number 200. 141.241.4 has all our mainframe
services, so that side of the router should be able to see them.
Again our topology looks like this:
>>     
>>     LAN workplace         LAN workplace 
>>        for DOS             for DOS    Novell LAN (IPX & TCP/IP)
>>          -+---------+---------+- 141.241.12.*
>> 		 Netware
>> 		 Server
>> 	141.241.4.* +--------------> campus backbone TCP/IP 
>>                                   and IPX

Yours,
	Desperate.

Seriously it would be nice to know why this isn't working.
Please respond by e-mail if possible.

Newsgroups: comp.sys.novell
Subject: Re: Routing TCP/IP through a Novell server
Summary: 
Expires: 
Followup-To: 
Distribution: 
Organization: Kingston University
Keywords: 

In article <1992May9.172817.55355@cc.usu.edu> jrd@cc.usu.edu writes:
>In article <1992May9.214953.6692@willamette.edu>, dan@willamette.edu (Daneher D. Revel) writes:
>> I would like to be able to use a Netware server to route TCP/IP traffic
>> between a Novell LAN and our campus wide TCP/IP backbone, here's a
>> picture:
We're trying to do the same thing, and it's driving me nuts. We have a
Novell server running 3.11 and a pair of 3c507's installed. Are there
any known problems with 3c507s ?  The workstations on the local
(Novell) segment can "see" the first 3c507 but not the second. Yes
we do have tcpip forward=yes. We're using LAN workplace for DOS on
the workstations, and we can use tnvt220 to reach the "closer" of
the two boards on its test port, 19 (tnvt220 141.241.12.2 19 works fine).
The second (further) 3c507's test port does not respond, neither
does anything further down the main backbone. Tcpcon reports that
ipforwards = 0, even after several attempts,
which is reassuring, because at least it isn't saying
"Gateway functions disabled"

Here's a copy of the autoexec.ncf file :


file server name PALLAS
ipx internal net 204
rem board 1 at 300 sees local network
load c:3C507 port=300 mem=D0000 int=3 frame=ETHERNET_802.3 name=IPX_300
bind IPX to IPX_300 net=234
rem board at 320 sees main network
load c:3c507 port=320 mem=d8000 int=7 frame=ETHERNET_802.3 name=IPX_320
bind IPX to IPX_320 net=200

load c:3c507 port=300 mem=D0000 int=3 frame=ETHERNET_II name=IP_300
load c:3c507 port=320 mem=d8000 int=7 frame=ETHERNET_II name=IP_320

load tcpip forward=yes rip=yes
load snmplog

rem bind local board to segment 12
bind IP to IP_300 addr=141.241.12.2 mask=ff.ff.fc.00
rem bind remote board to segment 4
bind IP to IP_320 addr=141.241.4.28 mask=ff.ff.fc.00

mount all
load remote khpallas
load rspx
load tsa
load monitor
set timezone gmt0bst
set reply to get nearest server = on
load rarpserv


>---------------------------------------------------------------------> 

Our main network has IPX number 200. 141.241.4 has all our mainframe
services, so that side of the router should be able to see them.
Again our topology looks like this:
>>     
>>     LAN workplace         LAN workplace 
>>        for DOS             for DOS    Novell LAN (IPX & TCP/IP)
>>          -+---------+---------+- 141.241.12.*
>> 		 Netware
>> 		 Server
>> 	141.241.4.* +--------------> campus backbone TCP/IP 
>>                                   and IPX

Yours,
	Desperate.

Seriously it would be nice to know why this isn't working.
Please respond by e-mail if possible.
Newsgroups: comp.sys.novell
Subject: Re: Routing TCP/IP through a Novell server
Summary: 
Expires: 
Followup-To: 
Distribution: 
Organization: Kingston University
Keywords: 

In article <1992May9.172817.55355@cc.usu.edu> jrd@cc.usu.edu writes:
>In article <1992May9.214953.6692@willamette.edu>, dan@willamette.edu (Daneher D. Revel) writes:
>> I would like to be able to use a Netware server to route TCP/IP traffic
>> between a Novell LAN and our campus wide TCP/IP backbone, here's a
>> picture:
>> 
>> 
>> 
>> 
>>     
>>     LAN workplace         LAN workplace \
>>        for DOS             for DOS    /\Novell LAN (SPX/IPX & TCP/IP)
>>          -+---------+---------+-
>> 		 Netware
>> 		 Server
>> 		    +--------------> campus backbone (TCP/IP only)
>> 
>> Can it be done? and,
>	Yes, it's done all the time in many many places.
>> What do I need to do to acheive this?
>	Two things. First is NW 3.11, nothing less will do IP routing. Second
>is either TCP/IP experience or some long chats with your local TCP/IP
>Responsible Person to get the addressing and subnetting straight (which can
>be quite a puzzle sometimes). The NW server will be an IP router, not an
>IP bridge (though I keep recommending this option to Novell as a useful
>alternative), so one must divide the address space. You do not need to purchase
>the NFS.NLM to route IP, the needed materials are shipped with NW 3.11.
>	Joe D.
>> 
>> Thanks...
>> -- 
>> Dan Revel (dan@willamette.edu)					Nullum
>> Network and Technical Services Manager				Gratuitum
>> Willamette University						Prandium
Newsgroups: comp.sys.novell