[Samba] Migration from Samba 2.2 to Samba 3.020b

[Raik Steuding]

Hello,

we migrate from Samba 2.2 to Samba 3.020b. We have the problem now,
that some clients can not connect to the Samba Server. In
the log there are messages like that:

[2006/02/23 08:49:20, 2] smbd/sesssetup.c:setup_new_vc_session(704)
  setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
[2006/02/23 08:49:20, 2] auth/pampass.c:smb_pam_auth(514)
  smb_pam_auth: PAM: Athentication Error for user raik
[2006/02/23 08:49:20, 2] auth/pampass.c:smb_pam_error_handler(73)
  smb_pam_error_handler: PAM: Authentication Failure : Authentication failure
[2006/02/23 08:49:20, 0] auth/pampass.c:smb_pam_passcheck(810)
  smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User raik !
[2006/02/23 08:49:20, 2] auth/auth.c:check_ntlm_password(317)
  check_ntlm_password:  Authentication for user [raik] -> [raik] FAILED with error NT_STATUS_WRONG_PASSWORD
[2006/02/23 08:49:20, 2] smbd/server.c:exit_server(612)
  Closing connections

At the moment the passwords are unencrypted, but we will switch to
encrypted passwords with the 'update encrypted' option. We have this
problem with different client systems (98, XP, ...).

On "identical" systems the login into the Samba-Server goes without problems
(and the same username).
At the moment we need the unencrypted passwords, because we have here many
users and the migration from unencrypted passwords to encrypted
passwords goes not so easy (as the samba experts also know for
certain).

Can somebody help me, this one I am a bit helpless at the moment.
I think the problem is the authentication of the wrong working
clients. the question is why is the authentication wrong and how I can
change this.

I am grateful for every help.

Regards,
Raik