Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!NRC!LARRY.H.BRADLEY From: LARRY.H.BRADLEY@NRC.CA Newsgroups: bit.listserv.novell Subject: Re: TCP/IP gateways Message-ID: Date: 10 Jan 90 16:45:13 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Organization: NATIONAL RESEARCH COUNCIL OF CANADA Lines: 30 Approved: NETNEWS@PSUVM Gateway In-Reply-To: Message of Wed, 10 Jan 90 10:48:00 EST from Peter, a solution that we are playing with here (not in production yet) is the WIN/ROUTE and WIN/TCP packages from Wollongong. WIN/TCP is a standard TCP/IP package that runs on the workstation, EXCEPT that it has a TCP/IP driver for Novell's IPX ... it sends TCP/IP packets over whatever network cabling system you have ... Ethernet, ARCnet, Token-Ring. WIN/ROUTE is a router (gteway) that runs not in the file server but in a gateway PC (preferable, in my opinion, to running in the server ... the server has enough to worry about!). It connects to both your TCP/IP network and your Novell network (e.g. ARCnet), and acts as the gateway. It works! The current version of the router has one problem ... it does not support a default route (i.e. you can't just point it to another router in your system to handle things that are not in the WIN/ROUTE tables. The next release (which is in beta, I am awaiting copy) solves this problem. So far, I am pleased with the Wollongong solution. *------------------------------------+----------------------* |Larry Bradley | LARRY@VM.NRC.CA | |Communications Manager | Larry.Bradley@NRC.CA | |National Research Council of Canada | LARRY@NRCVM01 | |Networks Branch | | |M60, Montreal Road | (613)993-0240 | |Ottawa, Canada K1A 0R6 | FAX:(613) 954-2561 | *------------------------------------+----------------------*