[Samba] smbpasswd on solaris clients

[James Craig]

 	I may be mixing water and oil here, but with a recent upgrade
 	I am discovering our solaris clients aren't able to update samba
 	passwords.

 	Our server is running 2.2.12  (I intend to upgrade to 3.0.x when
 	I get LDAP working) with it's own password database.

 	If I use the smbpasswd that came with 2.2.12 on the solaris clients
 	everything works.  however if I use the smbpasswd that comes with
 	blastwave (3.0.23) on the x86 solaris machines,

 	I get this error:

Could not connect to machine xxx.xxx.xxx.xxx: NT_STATUS_LOGON_FAILURE
Failed to change password for username


 	the server throws this into the logs:

[2007/09/03 15:41:21, 1] smbd/password.c:pass_check_smb(545)
   Couldn't find user '\username' in passdb.
[2007/09/03 15:41:21, 2] smbd/reply.c:reply_sesssetup_and_X(997)
   NT Password did not match for user '\username'!
[2007/09/03 15:41:21, 2] smbd/reply.c:reply_sesssetup_and_X(1007)
   Defaulting to Lanman password for \username
[2007/09/03 15:41:21, 1] smbd/password.c:pass_check_smb(545)
   Couldn't find user '\username' in passdb.
[2007/09/03 15:41:21, 1] smbd/reply.c:reply_sesssetup_and_X(1023)
   Rejecting user '\username': authentication failed
[2007/09/03 15:41:21, 2] smbd/server.c:exit_server(511)
   Closing connections



 	I have not had to create machine accounts for the client machines
 	before.  Is this something I need to change?  Do I need to flesh
 	out the currently empty smb.conf on the client machines?
 	Is the problem due to my attempt to mix client and server versions,
 	or does blastwave compile their smbpassword to expect a certain style
 	of server?


jim craig