[Samba] valid user and password authentication using smbpasswd

[Xu, Ying (Houston)]

I figured it out.  It seems that it doesn't like the given password, but
it didn't give me the error either.  It starts working after I changed
the samba password.  Any password with numbers doesn't work.  Is it a
bug or something?  It is 3.0.25a on x86.


Thanks
 
Ying Xu <yxu at littonloan.com>
Unix Group
Office: 713-218-4508
BB: 832-671-6633
4828 Loop Central Dr. Houston TX 77081
 

-----Original Message-----
From: samba-bounces+ying.xu=littonloan.com at lists.samba.org
[mailto:samba-bounces+ying.xu=littonloan.com at lists.samba.org] On Behalf
Of Xu, Ying (Houston)
Sent: Monday, June 08, 2009 2:06 PM
To: samba at lists.samba.org
Subject: [Samba] valid user and password authentication using smbpasswd

 
I have a very simple samba setup on one of the solaris servers.  Only
pwxuser is allowed to access a share. I have created a passwd entry for
it using smbpasswd.  I verified on another solaris server that pwxuser
could access the share via "smbclient \\\\server\share -U pwxuser"
However, I wasn't able to access to the share from windows XP.  I need
to change the user when mapping the drive.  According to the log, it
doesnt seem to use smbpasswd file at all.  I have several similar
configuration on other solaris servers and they work file.


bash-3.00# cat /etc/sfw/smb.conf
# Samba config file created using SWAT
# from 172.30.102.139 (172.30.102.139)
# Date: 2009/06/08 13:39:02

[global]
        security = SHARE
        restrict anonymous = 2
        log level = 3
        log file = /var/log/samba/log.%m
        ldap ssl = no

[infa_shared]
        path = /app/informatica/PowerCenter/server/infa_shared
        valid users = pwxuser
        read only = No

[2009/06/08 13:40:31, 3] smbd/sec_ctx.c:(356)
  pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2009/06/08 13:40:31, 2] auth/auth.c:(319)
  check_ntlm_password:  Authentication for user [pwxuser] -> [pwxuser]
FAILED wi th error NT_STATUS_WRONG_PASSWORD
[2009/06/08 13:40:31, 2] smbd/service.c:(638)
  Invalid username/password for [infa_shared]
[2009/06/08 13:40:31, 3] smbd/error.c:(106)
  error packet at smbd/reply.c(514) cmd=117 (SMBtconX)
NT_STATUS_WRONG_PASSWORD
[2009/06/08 13:40:31, 3] smbd/process.c:(1328)
  timeout_processing: End of file from client (client has disconnected).
[2009/06/08 13:40:31, 3] smbd/sec_ctx.c:(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2009/06/08 13:40:31, 3] smbd/connection.c:(69)

What might be the issue?  

Thanks
 
Ying Xu
------------------------------------------------------------------------
-------------------

DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email in error
please notify the sender by replying to this message and then delete it
from your system. Use, dissemination or copying of this message by
unintended recipients is not authorized and may be unlawful. Please note
that any views or opinions presented in this email are solely those of
the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability for any damage
caused by any virus transmitted by this email.


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

-------------------------------------------------------------------------------------------

DISCLAIMER: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the sender
by replying to this message and then delete it from your system. Use,
dissemination or copying of this message by unintended recipients is not
authorized and may be unlawful. Please note that any views or opinions
presented in this email are solely those of the author and do not necessarily
represent those of the company. Finally, the recipient should check this email
and any attachments for the presence of viruses. The company accepts no
liability for any damage caused by any virus transmitted by this email.