Mystery solved

John Seal wrote:
> Any ideas what can trigger this error?

I left some information out of my initial post. The client machine runs
Solaris 9, but the host machine runs Windows 2000 Server. It has 3
ethernet ports, and the software that runs on it requires that a network
drive be mapped. But, sometimes the box has to run standalone (isolated
from the network) and someone had decided that the only way to make it
think that there *was* a network so you could map a drive was to connect
two of the net ports with a crossover cable! When we actually placed
the box on the network by connecting the 3rd port, it would eventually
get confused. Unplugging the crossover cable fixed the problem... ping
works, comm works, everything's OK.
Received on Sun Apr 30 02:18:00 2006