Path: utzoo!attcan!uunet!wuarchive!mailrus!tut.cis.ohio-state.edu!ucbvax!AHWAHNEE.STANFORD.EDU!dcrocker
From: dcrocker@AHWAHNEE.STANFORD.EDU (Dave Crocker)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  XNS / TCP gateway??
Message-ID: <8909230252.AA23000@ucbvax.Berkeley.EDU>
Date: 22 Sep 89 21:04:58 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21

(You're not going to like this...)

What you need is something in the category, called "application gateway".  You
do not simply need translation between the transport-and-below lower layers,
but rather have a difference at every level, except perhaps media.  Hence, you
need to translate every layer.  In reality, this means that you need something
that is "dual stack" running both ENTIRE sets of protocols and a translation
device in between.  For software application gateways, this normally means a single
application, running on top of the two transport stacks, where the application
does BOTH application protocols and translates between them.

In this particular case, there is a different solution.  It is the part you might
not like:

Take one XNS-based terminal server and one TCP-based terminal server and back
them up to each other.  Connect the serial ports.  Play with it until the 
configurations are right.

You now have a terminal protocol translator.

Dave