search for: wink2k

Hello, We are using Samba 2.0.4 on Solaris for a mixed set of NT4 and Win2K clients. Occasionally, the NT domain controller will lock the account from too many bad password attempts. One of our admins has suggested that this is due to samba sending a bogus password to 'verify' the existence of the account, before resending it with the 'correct' password. Has anyone heard of this

Hi, I posted this problem before in more detail (http://marc.theaimsgroup.com/?l=samba&m=104756899022766&w=2) but received no response. At the current state of Smaba 3.0 and Samba-TNG these two seem to be incomaptible. Samba 3.0 can't join a TNG controlled domain. I think this should affect a lot of installations as TNG as a controller and "stable" as file/printserver seem

...l samba 2. configure samba 3. add the user root to smbpasswd and do use a password 4. add the machine user in smbpasswd like you did with the '$' at the end 5. add the line 'add user script' that I sended to yout smb.conf or via SWAT 6. login as adminsitrator (local machine) in your Wink2k 7. disconnect all network drives 8. join the domain If you have RedHat, use this passwd chat: passwd program = /usr/bin/passwd %u passwd chat = *new*password* %n\n *new*password* %n\n *success* unix password sync = Yes Also I will recommend to read the HOWTO that is in the...

...use a password >>> 4. add the machine user in smbpasswd like you did with the '$' at >>> the end >>> 5. add the line 'add user script' that I sended to yout smb.conf or >>> via SWAT >>> 6. login as adminsitrator (local machine) in your Wink2k >>> 7. disconnect all network drives >>> 8. join the domain >>> >>> If you have RedHat, use this passwd chat: >>> passwd program = /usr/bin/passwd %u >>> passwd chat = *new*password* %n\n *new*password* %n\n *success* >>>...