Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!mikes@iuvax.cs.indiana.edu
From: mikes@iuvax.cs.indiana.edu (Michael Squires)
Newsgroups: comp.unix.sysv386
Subject: Re: Goofy problem with SCO Unix and Xenix
Summary: happened to me with 3.2.0
Keywords: XENIX TCP/IP
Message-ID: <1991Apr26.150449.24177@news.cs.indiana.edu>
Date: 26 Apr 91 20:04:26 GMT
Article-I.D.: news.1991Apr26.150449.24177
References: <1236@dms.UUCP>
Organization: Computer Science, Indiana University, Bloomington.
Lines: 25

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