Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!sri-spam!rutgers!aramis.rutgers.edu!athos.rutgers.edu!latzko
From: latzko@athos.rutgers.edu (Alex )
Newsgroups: comp.dcom.lans
Subject: Re: ?srevreS lanimreT
Message-ID: <1073@athos.rutgers.edu>
Date: 2 Mar 88 00:24:59 GMT
References: <172100003@uxc.cso.uiuc.edu>
Reply-To: latzko@athos.rutgers.edu (Alex )
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 21

In article <172100003@uxc.cso.uiuc.edu> german@uxc.cso.uiuc.edu writes:
>
>
>Has anyone used a terminal server to front end a non-networking host?  I 
>         Greg German (german@uxc.CSO.UIUC.EDU) (217-333-8293)

Yes, you can use a terminal server to front for a non-networking host!
The general term for this type of device is a "milking machine". As
far as I know the two best servers for this type of function are the
cisco and bridge products.  Which is a better device for you depends
on the size of your general networking problem, although, I prefer cisco.

Both are able to set up a rotary to alias an ethernet address to a
group of ports.  

cisco: 1 415 326 1941
bridge:1 415 969 4400

have fun.......

/S*

#incude<standard disclaimer>