samba - Aug 2006 - W2k logged out workstations keep 'alive' at smbstatus (3.0.23a)

Hi,

     At first my context now:
     -Slackware 10.2 ( no PAM ), Samba 3.0.23a, OpenLdap 2.3.24,
smbldap-tools 0.9.2.

     and before:
     -Slackware 10.0, Samba 3.0.10, Openldap 2.2.x, smbldap-tools 0.8x

     After adjustments in the LDAP configuration and smb.conf, my
Samba is running. Workstations are ( almost completely ) W2K. I have
already included, deleted and changed new users. I had to solve a
problem ( envolving Squid ) because smbldap-useradd doesn't include
uid as memberUid in Domains Users and so. Because this features are
working, I think my setup is correct ( or almost ).

     Before upgrading, I was using a solution to deny simultaneous
logins, using a solution that is very similar to the solution in the
Chapter 25: limiting logon connect, of the book The Official Samba-3
HOWTO and Reference Guide. Results were not  'precise' for the known
reasons, but used to do the job.

     After upgrading, even after logoffs, smbstatus still reports
users as logged, so, the confusion was made. I had to disable my
control, and the problems with simultaneous logins came back ( this
behaviour is not accepted by company politics). I have read
Changelogs, including samba.wiki and tried some searchs at google and
lists archive. I think I was unhappy with strings I used to search,
because I couldn't get a tip to solve the problem.

     So, could someone help me with this problem? Have I missed
something important? Some reading recommended? What kind of additional
information I can provide to help without polluting the list?

     Its very important to solve this behaviour, because the company politics.

     I thank you for your attention.

Regards,

Freitas.

Hi,

     I am still trying to solve the following problem.

     At first my context now:
     -Slackware 10.2 ( no PAM ), Samba 3.0.23a, OpenLdap 2.3.24,
smbldap-tools 0.9.2.

     and before:
     -Slackware 10.0, Samba 3.0.10, Openldap 2.2.x, smbldap-tools 0.8x

     Before upgrading, I was using a solution to deny simultaneous
logins, using a solution that is very similar to the solution in the
Chapter 25: limiting logon connect, of the book The Official Samba-3
HOWTO and Reference Guide. Results were not  'precise' for the known
reasons, but used to do the job.

     After upgrading, even after logoffs, smbstatus still reports
users as logged, so, the confusion was made. I had to disable my
control, and the problems with simultaneous logins came back ( this
behaviour is not accepted by company politics). I have read
Changelogs, including samba.wiki and tried some searchs at google and
lists archive. I think I was unhappy with strings I used to search,
because I couldn't get a tip to solve the problem.

     So, could someone help me with this problem? Have I missed
something important? Some reading recommended? What kind of additional
information I can provide to help without polluting the list?

     Its very important to solve this behaviour, because the company politics.

     I thank you for your attention.

Regards,

Freitas.