shepperd@dms.UUCP (Dave Shepperd) (04/26/91)
I don't get it. I have a single SCO Xenix/386 system that has been working perfectly for several years (SysV release 2.3.2 kid 5.53 for i80386). This system has SCO's TCP/IP for Xenix version 1.0.0 (I think). I also have an SCO ODT system which has TCP/IP version 1.0.0beta (or some such) and has been running right along with the Xenix system for the last couple of years with no problems (except I can't get the nameserver to work). I recently purchased an SCO Unix 3.2.2 and a companion SCO Unix TCP/IP package and installed it on yet another system. About 30 seconds after the TCP starts on this new system, the Xenix system hangs. No error messages appear anywhere, the Xenix system just "goes to sleep". SCO tech support says one of two things: either "...that's impossible..." or there is a "...duplicate key..." on one of the systems. I don't agree that it's impossible since I can watch it happen each time and every time. I also don't agree that there is a duplicate key since the SCO Unix keys are the ones fresh and crisp from the box in which the new products arrived AND they bear no resembalnce to the keys I used on the Xenix products. In addition, I recall several years ago when I inadvertantly used the same key on more than one of the Xenix systems we had then that I was greeted with a message on the console saying in effect "There is another mechanism...". It may have hung after that, I don't remember. The SCO ODT system continues to operate normally after the Xenix system hangs as do the ESIX, Sun, VAX and other nodes running TCP/IP. I've been informed that the version of TCP I have on the Xenix system is the only available version (i.e. there is no "update" that I've missed). For the time being, the new SCO stuff sits on the shelf and the new PC is running DOS (ouch) :-( Anybody have a clue what's happening here? Anybody have a fix for it? -- Dave Shepperd. shepperd@dms.UUCP or motcsd!dms!shepperd Atari Games Corporation, 675 Sycamore Drive, Milpitas CA 95035. Nobody knows what I'm saying. I don't even know what I'm saying.
mikes@iuvax.cs.indiana.edu (Michael Squires) (04/27/91)
In article <1236@dms.UUCP> shepperd@dms.UUCP (Dave Shepperd) writes: > >I recently purchased an SCO Unix 3.2.2 and a companion SCO Unix TCP/IP package >and installed it on yet another system. About 30 seconds after the TCP starts >on this new system, the Xenix system hangs. No error messages appear anywhere, >the Xenix system just "goes to sleep". > This is exactly what happened to me when I got my copy of SCO UNIX 3.2.0 and tried to connect to my XENIX 386 system with TCP/IP. The update to ODT 1.0 (UNIX 3.2.1) fixed it. SCO said that it was a problem with the 3.2.0 TCP/IP that was fixed in 3.2.1. There are PD Ethernet monitors such as Netwatch that will tell you what traffic is going on between the two systems (Netwatch is part of CMU PC/IP). Also, I don't think 1.0.0 is the most recent XENIX TCP/IP. I know that there were at least two updates to the original product. -- Mike Squires (mikes@iuvax.cs.indiana.edu) 812 855 3974 (w) 812 333 6564 (h) mikes@iuvax.cs.indiana.edu 546 N Park Ridge Rd., Bloomington, IN 47408 Under construction: mikes@sir-alan.cica.indiana.edu
chrisdu@sco.COM (Chris Durham) (04/28/91)
In article <1236@dms.UUCP> shepperd@dms.UUCP (Dave Shepperd) writes:
:
:I don't get it. I have a single SCO Xenix/386 system that has been working
:perfectly for several years (SysV release 2.3.2 kid 5.53 for i80386). This
:system has SCO's TCP/IP for Xenix version 1.0.0 (I think).
:
:I also have an SCO ODT system which has TCP/IP version 1.0.0beta (or some
:such) and has been running right along with the Xenix system for the last
:couple of years with no problems (except I can't get the nameserver to work).
:
:I recently purchased an SCO Unix 3.2.2 and a companion SCO Unix TCP/IP package
:and installed it on yet another system. About 30 seconds after the TCP starts
:on this new system, the Xenix system hangs. No error messages appear anywhere,
:the Xenix system just "goes to sleep".
This is a known issue with the Xenix TCP/IP release 1.0.0, which is indeed a
beta release. Customers who are registered with SCO Support with this release
are entitled to a free update to the current Xenix TCP/IP release 1.0.1.
--
chris durham chrisdu@sco.COM
Technical Support ...!{uunet,ucscc}!sco!chrisdu
The Santa Cruz Operation
"So the universe is not quite as you thought it was. You'd better rearrange
your beliefs, then, because you certainly can't rearrange the universe."
_Nightfall_ by Isaac Asimov & Robert Silverberg