Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!rutgers!bellcore!faline!ulysses!gatech!itm!danny
From: danny@itm.UUCP (Danny)
Newsgroups: comp.protocols.tcp-ip
Subject: Bridge Terminal Server Problems
Message-ID: <1198@itm.UUCP>
Date: Tue, 10-Nov-87 15:30:52 EST
Article-I.D.: itm.1198
Posted: Tue Nov 10 15:30:52 1987
Date-Received: Fri, 13-Nov-87 06:36:24 EST
Reply-To: danny@itm.UUCP (Danny)
Distribution: na
Organization: In Touch Ministries, Atlanta, GA
Lines: 33
Summary: HELP!

Hear me O ye wise ones!  Incline thine ears, that ye may understand,
and save thy humble servant!

    I've a problem (no it's not my English).  We have a Bridge
Communications Server (CS100) which is connected to our ethernet.  Our
computer is a Celerity C1230 running BSD4.3.  Now, the Bridge box
assigns a IP address to each port, e.g.: port 0 is "77.0.0.100", and
the Celerity is "77.0.0.2".  We just want to hang printers off of the
Bridge box; so each printer has an address and host name of its own.

    Now, the problem.  I can connect to (for example) necc using telnet.
Everything's fine.  What I type on the terminal, is printed on the
Nec (5515).  We also run MDQS from BRL.  I wrote a short routine to
open a socket, connect it to a host (necc), and dup2 it as stdout (which
is what an MDQS server requires).  When I submit a request to necc,
the connection succeeds!  Then, usually, the server immediatly dies with
a SIGPIPE.  That's kinda OK.  FIRST, should the connection succeed?
I don't think so.

    Then, after a few rounds of the server restarting itself, it will
run to completion!  Where does the data go?  I thought that TCP
garentees delivery, but to where you wanted it to go.

    So, why is the Bridge box accepting two connections to the same
serial-port/address?  Why does the second then mysteriously fail?
Where does the data go when it succeeds?

    HELP!
    
                                            Danny
-- 
				Daniel S. Cox
				(seismo!gatech!itm!danny)