Xenix TCP/IP over terminal server?

[Adnan Yaqub]

>From article <4554 at bu-tyng.bu.edu>, by kleiner at bu-tyng.bu.edu (Ken Kleiner):
| 	Well, I finally got TCP/IP under Xenix running.
| 
| 	NOW, I'm trying to get it on our local area network.
| 	I have it on our ethernet, and I can ftp to it and telnet
| 	to it, stuff like that.  BUT, I'm trying to put it on our
| 	network as a local node.  We have Bridge cs100 communications
| 	servers (terminal servers).  When we usually add a node to our
| 	network, we just go to the communications server, map the name
| 	to a internet address and just do a "connect machine" on the
| 	comm. server.  
| 
| 	But, whenever we try to connect to the Xenix machine, we get
| 	the info before the login prompt (System V/Xenix message), but
| 	our network disconnects that session before the login: appears.
| 	Strange.   

I had the same problem when testing our terminal server with SCO
Xenix.  The problem turned out to be that the SCO telnet server would
tear down the connection if the terminal server's telnet client asked
the telnet server to do the echoing.  The fix is to not propose that
the host does the echoing.  Since the host eventually comes around to
offering to do the echo, no functionality is lost.  If your Bridge box
allows you to not propose remote echoing but to accept it (probably
doesn't), set it up like that.  Otherwise, beat on SCO to fix it.  (We
spent a long time with them on this, but they were not in a hurry to
investigate or fix the problem.)  BTW, the problem does not occur with
SCO Unix TCP/IP (which is several versions ahead of SCO Xenix TCP/IP).

--
Adnan Yaqub (adnan at sgtech.uucp)
Star Gate Technologies
29300 Aurora Rd, Solon, OH, 44139, USA, +1 216 349 1860