Xref: utzoo bit.listserv.ibm-nets:206 comp.protocols.tcp-ip:16742 comp.protocols.tcp-ip.ibmpc:6270 comp.dcom.lans:8481 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!news.cs.indiana.edu!arizona.edu!hamblin.math.byu.edu!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!keith Newsgroups: bit.listserv.ibm-nets,bit.listserv.ibmcp-l,comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,comp.dcom.lans Subject: Re: Telnet from DOS - UNIX box via serial port & Message-ID: <1991Jun26.211509.8113@novell.com> From: keith@ca.excelan.com (Keith Brown) Date: 27 Jun 91 03:19:07 MST Sender: news@novell.com ( Lines: 54 The News Manager) Nntp-Posting-Host: ca Reply-To: keith@ca.excelan.com (Keith Brown) Organization: Novell, Inc. San Jose, California References: <1991Jun01.012032.3364@actrix.gen.nz> Date: Wed, 26 Jun 1991 21:15:09 GMT In article <1991Jun01.012032.3364@actrix.gen.nz> john@actrix.gen.nz (John Vorstermans) writes: > >I am looking for software that will allow a user dialing in via modem >to a DOS box to login to a UNIX box via a small local ethernet. > This is exactly what some of us are in the habit of doing here. How? Well, about a year ago I had an idea (not had one since but I am working on it :-)). We (Novell) have a product called the Access Server. To cut an entire slide presentation down to one sentance, the Access Server is basically 16 PCs in a single 80386 PC, each virtual PC being able to be dialled into over serial lines from a variety of devices including terminals and remote PCs and each virtual PC is NetWare enabled (ie. you can dial into an Access Server, become a virtual PC, switch to a network drive and login to a NetWare server). Terrific.... We also have a product called the LAN WorkPlace for DOS. This is our TCP/IP offering for DOS PCs that contains a fully re-entrant TCP/IP stack that hangs together splendidly under both Windows 3.0 and, more importantly in this case, Desqview. The way the Access Server does it's multiple virtual PC on one 386 processor trick (and its memory management) is via a "specialish" version of Desqview. Given that the LAN WorkPlace works with Desqview, it doesn't take a giant leap of the imagination to conclude that the LAN WorkPlace and the Access Server can be used in conjunction with each other. This is basically what I did and it worked like a charm. You can dial into an Access Server and telnet and FTP your way out onto the LAN. The trick...... Before the AS fires up, load up and configure the LAN WorkPlace TCP/IP transport TSR (and its underlying ODI driver, of course). You also need to load our Int 14h redirector (TELAPI) if you wish to use telnet from inside the DOS boxes, which I imagine everyone will? Then, edit the various batch files that initialise the Access Servers RAM disk to copy the various LAN WorkPlace utilities into the appropriate directories so they will be available to the virtual PCs. This is actually optional as you could just keep the LAN WorkPlace utilities on a server somewhere and get at them that way after logging in to said server. Finally, execute the batch files that start up the Access Server and Bob is, as they say, your uncle. Now for the bad news. You need two LAN adaptors. Yes, yes, I know! :-( :-( The reason is that LAN WorkPlace uses the ODI and the Access Server doesn't. Please don't flame me, it's not my fault. Still, if you do have an extra LAN adaptor handy....... Keith - Keith Brown Phone: (408) 473 8308 Novell San Jose Development Centre Fax: (408) 433 0775 2180 Fortune Dr, San Jose, California 95131 Net: keith@novell.COM