Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!VAXB!MOLTA From: MOLTA@VAXB.ACS.UNT.EDU Newsgroups: bit.listserv.novell Subject: RE: best way to connect novell lan to Tcp/ip net Message-ID: Date: 5 Feb 90 18:46:00 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Lines: 38 Approved: NETNEWS@PSUVM Gateway X-VMS-To: IN%"NOVELL%SUVM@pucc.PRINCETON.EDU" X-To: NOVELL%SUVM@pucc.PRINCETON.EDU > I seem to remember this question being asked as while back, >but I can't remember the answer, and of course, now, I need it. :-) >Situation: > One room Lab with about 18 computers (AT class or less) as > workstations. (thinnet) > Server is 386SX based running SFT (I don't remember the > version, but it's very recent) > The ethernet backbone cable (to tcp/ip hosts) is running down > the hall right outside the lab. >Question: what's the best way and/or least expensive way to get to > the tcp/ip hosts: > 1. use a bridge from thinnet to thicknet and packet drivers > at the workstations. ?? > 2. use another nic in the server to tie to the backbone, and > some gateway software (which software?) ?? > 3. some other method ?? Barb, I'd suggest that a MAC-level bridge connecting the lab directly to the Ethernet would be the best solution. You could then run NCSA Telnet with the packet drivers and provide your users with both Telnet VT-100 emulation and TN-3270 emulation. As far as a particular bridge to go with, Retix is always a safe choice, but I personally like the Cabletron bridges. A gateway solution, such as the Racal Interlan TCP/IP Gateway, will provide you with outgoing Telnet (not TN3270), outgoing FTP, AND incoming FTP. If the latter is important, you may want to consider a gateway. However, be forewarned that Racal Interlan's support for this product is about the worst I have ever experienced. Whenever a new release's documentation includes 6 or 8 pages of bug notes, you have to wonder a little. Hope this helps. Dave Molta University of North Texas