home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:4952 comp.unix.misc:3591 comp.misc:3626
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!uwm.edu!ogicse!reed!romulus!trost
- From: trost@romulus.reed.edu (Bill Trost)
- Newsgroups: comp.unix.admin,comp.unix.misc,comp.misc
- Subject: Re: What is the best way to communicate remotely?
- Message-ID: <TROST.92Sep8212231@romulus.reed.edu>
- Date: 9 Sep 92 04:22:40 GMT
- Article-I.D.: romulus.TROST.92Sep8212231
- References: <1992Sep04.172530.22261@wap.oau.org>
- Sender: news@reed.edu (USENET News System)
- Distribution: usa
- Organization: Reed College
- Lines: 26
- In-Reply-To: bdixon@wap.oau.org's message of 4 Sep 92 17:25:30 GMT
-
- In article <1992Sep04.172530.22261@wap.oau.org> bdixon@wap.oau.org (Bill Dixon) writes:
- My current hardware configuration is:
- IBM RS/6000 model 320
- Datability Vista Terminal Server (ethernet-attach)
- Wyse 60 terminals
- Assorted printers
-
- I just found out that my company plans to open up warehouses out of state
- in the next 2 or 3 months, and of course they want terminals and printers
- there.
-
- Hmm...I'm surprised no one has suggested you get another terminal
- server for the warehouse, and then simply run SLIP or PPP between the
- warehouse and the main office. Several terminal servers are also
- capable of doubling as routers. Then you can hang terminals,
- printers, and even ethernet off the terminal server to your heart's
- content.
-
- With any luck, your RS/6000 might even be able to serve as a router on
- the main-office end, although you might be limited by the number of
- serial ports on the workstation. Since a majority of your packets are
- headed there anyway, you'd save a *whole ethernet hop* over using a
- terminal server in the main office! :-)
- --
- Bill Trost <trost@reed.edu> Space is nature's way of keeping everything from
- happening all in one spot.
-