Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!ucbvax!UCCVMA.UCOP.EDU!SPGDRP From: SPGDRP@UCCVMA.UCOP.EDU ("Donald R. Proctor") Newsgroups: comp.protocols.tcp-ip Subject: Re: SLIP, IP Routers and Named Pipes Message-ID: <9010041120.AA01416@ucbvax.Berkeley.EDU> Date: 3 Oct 90 21:12:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 33 >A project have come up around here that require multiple >PCs to get dial-in access to the TCP/IP network. One of the >major requirements is support for Named Pipes down to the PC. >Current plan is to use SLIP and a router with dial-in ports. > >Would someone care to recommend a PC package that would do good >SLIP emulation and a router that would be suitable for this job? > Alex: We intend on implementing a similar system here, although we don't have the named pipes requirement. We have a cisco terminal server that can be configured with several dial-in ports. The software angle is a bit more complex. As I understand it, the remote PC user will need to use a communications package like kermit or xmodem to connect to the terminal server. A commercial (such as FTP's PC/TCP) or public domain (such as NCSA telnet) TCP-IP package can then be run over SLIP. FTP's package can be ordered with SLIP, and there is a SLIP driver in Clarkson's pd packet driver distribution. I should point out that cisco's box can provide the telnet connection itself, so that a remote PC user can dial in and start a telnet session from the server without having the TCP-IP software installed on the PC. However, if need 3270 emulation (as we do), the current release of the cisco's software won't do the job. I hope my more knowledgeable colleagues will correct me if I have made any egregious errors... Don Proctor Information Systems & Computing University of California 415/987-0356