Problem with NCSA 2.2/2.3b14 Telnet and SCO Xenix TCP/IP 1.0.1h

[Bill Blue]

In <3868 at mjbtn.JOBSOFT.COM> root at mjbtn.JOBSOFT.COM (Mark J. Bailey) writes:
}I am having a problem with Xenix TCP/IP that is about to drive me crazy!
}I have SCO Xenix 2.3.3 running TCP/IP 1.0.1h.  I have a 386 DOS system that
}is ethernetted to the Xenix system using WD8003e Ethercard Plus's.  The
}card is set on Interrupt 2, I/O Address 0x240, Mem Addres 0xD000.  I am 
}trying to use NCSA Telnet 2.2 and 2.3b14, WNQVTNET with Clarkson drivers,
}and CMU PCIP with Clarkson drivers.  I did have an old copy of Locus TCP/IP
}for MSDOS that I tried too.
}
}What is happening is this.  I also have an SCO Unix System (ODT 1.0 which
}is Unix 3.2.1) that contains TCP/IP 1.1 (SCO/Lachman).  If I go from the
}dos system to the ODT/Unix system, everything is *PERFECT*!!!!!  BUT, when
}i try to go from the DOS system to the Xenix system (using telnet), I get
}the "header" from the Xenix system:
}
}System V.2.3.3 XENIX (jcbmdpc.JOBSOFT.COM)
}
}but the login never shows up!  As a matter of fact, *ALL* of the packages
}above except the Locus package just drop back out to the DOS prompt with
}*NO* error messages.  That is normal behavior when you logout from a telnet
}session with the dos packages.  It is almost like the Xenix system is dropping
}out before the login prompt comes up.  As I said the Locus package stays in
}and you can login.  Another weird thing is that the NCSA/WNQVTNET programs
}will work the *FIRST* time you telnet the xenix system after the xenix system
}is newly booted.  If you try and open subseqeunt sessions with the one 
}successful one, they drop out before the login prompt as before.  Then if you
}logout the one session, and try to connect back, it fails from then on.
}Now, going from Unix-->Xenix and Xenix-->Unix works fine all the time.

Interestingly, I went through a similar experience just this week,
with Xenix tcp/ip and the ncsa telnet package.  Same cards, same
situation.  You'll probably find that if you do a netstat -i or -r it
will just hang.

The clue is that you can't 'ping localhost' but you can 'ping
127.0.0.1'.  The lack of name lookup, the inability to rlogin, telnet
or ftp TO the Xenix tcp/ip, and the hanging netstat is due to an entry
in resolve.conf which is read by routed when it starts up.  If you
have a 'nameserver' line in there, but the defined nameserver is not
active at the moment, all these things will happen.  Just delete or
rename the file, and it'll all work.

Of course, deleting or renaming the file is just to get you going.  I
haven't figured out how all the various config files and daemons
interract, and the docs don't really tell much of the story, so I
can't tell you much more than I have.

If anyone listening would care to provide an informative tutorial, I'm
sure a lot of people including myself would be greatly appreciative.

--Bill