Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!usc!nic.csu.net!beach.csulb.edu!csus.edu!wuarchive!sdd.hp.com!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!brian
From: brian@la.excelan.com (Brian Meek)
Newsgroups: comp.sys.novell
Subject: Re: TCP/IP packets through Novell 386 Server
Summary: IP routing is a standard feature of NetWare v3.11
Message-ID: <1991Feb16.152315.2418@novell.com>
Date: 17 Feb 91 07:13:21 GMT
Sender: news@novell.com (
Lines: 33

The News Manager)
Nntp-Posting-Host: la
Reply-To: brian@novell.com (Brian Meek)
Organization: Novell, Inc., San Jose, Califonia
References: <1233@taeva.UUCP>
Date: Sat, 16 Feb 1991 15:23:15 GMT

In article <1233@taeva.UUCP> hans@triumph-adler.de (Hans von Kleist-Retzow) writes:
>We have a novell 386 server installed which connects two ethernet
>segments. One ethernet segment is connected with a cisco gateway
>to the Internet.
>
>All the PCs on the segment connected to the cisco can either send
>TCP/IP packets (with telnet,  ftp, ...) or can use the Novell
>server. But the PCs connected to the second segment are not able
>to send TCP/IP packets. The TCP/IP packets are not forwarded
>from the Novell server.
>
>Is there a possibility to allow all the PCs in the second segment
>to use TCP/IP?
>
>Thanks, 
>Hans

IP routing is one of the features provided by the TCP/IP NLM that
is (will be) bundled with NetWare v3.11.  It can forward IP packets 
across multiple Ethernet, Token-Ring and ARCnet LAN segments attached 
to the server.  The IP routing feature need not be enabled.  If enabled,
it can use RIP, be configured statically at load time, be configured
interactively via SNMP -- or all of the above.

brian
____________________________________________________________________________
         Brian Meek       Novell, Inc. - 2180 Fortune Dr. San Jose, CA 95131
Internet Mail: brian@novell.COM                        Phone: (408) 473-8375