Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!VM.IBT.DK!IBTJLL From: IBTJLL@VM.IBT.DK ("Jesper L. Lauritsen") Newsgroups: comp.protocols.tcp-ip Subject: Re: Bridge Terminal Server Message-ID: <8907201856.AA25243@ucbvax.Berkeley.EDU> Date: 20 Jul 89 18:57:11 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 31 X-Unparsable-Date: Thu, 20 Jul 89 13:46:06 DST >Has anyone had any luck connecting a printer to a bridge terminal >server?? We have a printer connect like this (cs/200 is a bridge terminal server): mini --> cs/200 <--> net <--> cs/200 --> printer This uses the permanent virtual circut facility and has proven to be very robust. I have also experimented with a connection like this: mini <--> net <--> cs/200 --> printer This should definitly be feasible but will require changes in the host spooler depending on the operating system. >Also, We have a spectrometer that will run kermit. I'd like to be able >to have it run kermit and be connected to a port on a bridge terminal >server. My question is: Could any other node on the ethernet gain access >to the spectrometer, assuming it was running kermit and in "server" >mode? Don't know much about this, but the cs/200 can be highly invisible. If you can connect two PCs directly with a RS232 cable you should be able to put two cs/200's and a net in between. I believe a cs/100 is functionally equivalent to a cs/200. --Jesper --------------------------------------------------- Jesper L. Lauritsen, system programmer Domain addr: ibtjll@vm.ibt.dk; BITNET/EARN: IBTJLL AT DKIBT K:benhavns Universitet / University of Copenhagen Center for Anvendt Datalogi / Center for Applied Datalogy Studiestr{de 6 o.g. / Studiestraede 6 o.g. 1455 K:benhavn K / DK-1455 Copenhagen K, Denmark 33 12 01 15 / +45 33 120115