[Samba] 2.2.3a PDC sometimes stops accepting logons

[Marshall, Joshua]

I have a Samba 2.2.3a PDC with LDAP backend which now and then stops 
working for logons from Windows machines. File sharing, WINS lookups and 
browsing still works great but Windows logons just stop. Interestingly, 
logon packets are still being logged in the log.nmbd

To fix it I generally have to restart nmbd. The logs show:

Before restart:

[2002/04/02 11:04:08, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 10.10.10.167: code = 0x0
[2002/04/02 11:04:24, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 10.10.10.167: code = 0x0

After restart:

[2002/04/02 11:07:35, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 10.10.10.167: code = 0x0
[2002/04/02 11:08:07, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 10.10.10.167: code = 0x7


It can take a few days before the server starts showing these effects. It 
doesn't seem to have excessively high cpu usage, low memory or disk space. 
It doesn't seem to stop at any point in time. The logs above were taken 
with debug level 2. I don't wish to bump this up since it affects 
performance badly, and only fails after a few days of operation.

Is there a way to find out what the codes above are? They definitely come 
in pairs and when you get a pair of 0x0's it fails and when you get a 0x7 
it works.

Another question is: Is there a way to test for a logon using smbclient or 
similar tool? I'd like to be able to get a job in cron to test whether 
it's working and alert me before the windows users start to complain.

Regards,

Joshua Marshall