semi-reproducible problem

[john marchant]

I have been able to "sort of" reproduce a problem with Samba for VMS 2.0.6.
In response to the:

[2001/12/17 17:45:46, 0] CMS_ROOT:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;2:(1035)
  getpeername failed. Error was socket is not connected
  Denied connection from UNKNOWN (0.0.0.0)
[2001/12/17 17:45:46, 1] CMS_ROOT:[SAMBA.SOURCE.SMBD]PROCESS.C;2:(607)
[2001/12/17 17:45:46, 0] CMS_ROOT:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;2:(1035)
  getpeername failed. Error was socket is not connected
  Connection denied from 0.0.0.0

errors, I changed smb.conf to:

name resolve order = hosts

from hosts wins

for one moment in the log files it appeared to authenticate and it used the
log.machine_name to log the activity.  However, I got a network is busy (as
I had been getting whether authentication took place or not) and the shares
did show up.  I just got my usual network is busy.  The second time around
using the "hosts" alone produced the error above.  I am only able to
reproduce this every so often and it is very very hard to reproduce.  When
it did resolve names, and it did authenticate, it did not produce the
shares, just network is busy.  Thanks again.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.306 / Virus Database: 166 - Release Date: 12/4/01