Forgot to include the smb.conf file, and also say that wbinfo -u and -g
both return results ok..
# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2008/01/24 17:37:46
[global]
log file = /var/log/samba/%m.log
idmap gid = 16777216-33554431
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
obey pam restrictions = Yes
winbind use default domain = Yes
realm = DOMAINNAME.LOCAL
passwd program = /usr/bin/passwd %u
template shell = /bin/bash
dns proxy = No
cups options = raw
server string = S3 SVN Server
invalid users = root
idmap uid = 16777216-33554431
password server = ubiq-serv1.domainname.local
unix password sync = Yes
template homedir = /home/%U
workgroup = DOMAINNAME
os level = 20
auto services = centos
printcap name = /etc/printcap
security = ads
preferred master = no
winbind separator = #
max log size = 50
pam password change = Yes
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[centos]
comment = Centos 4 & 5 Repository
path = /var/www/html/centos
guest ok = Yes
-----Original Message-----
From: samba-bounces+adrian.marsh=domainname.com@lists.samba.org
[mailto:samba-bounces+adrian.marsh=domainname.com@lists.samba.org] On
Behalf Of Adrian Marsh
Sent: 11 April 2008 12:51
To: samba@lists.samba.org
Subject: [Samba] Fileshares failing
Hi,
I used to have a set of samba shares working fine on a Centos 4 machine,
accessed by XP clients and authenticated against a 2003 SBS server. Then
I did a yum upgrade and a week later noticed that the seldom-used SMB
shares have stopped working. No other changes to the Centos server, and
no domain changes. The XP clients now just keep prompting for
authentication.
A wireshark trap shows I'm getting a STATUS_LOGON_FAILURE (0xc000006d)
returned to the client.
The log for that PC gives the below. I also login to the server using
SSH, which is turn uses PAM to authenticate as well, and that succeeds
ok. So I'm guessing this might be a computer account problem, rather
than a user access problem.
What would the next debug steps be?
[2008/04/11 12:15:59, 0] auth/pampass.c:smb_pam_error_handler(73)
smb_pam_error_handler: PAM: session setup failed : System error
[2008/04/11 12:15:59, 1] smbd/session.c:session_claim(143)
pam_session rejected the session for domainname#marsh [smb/25659/101]
[2008/04/11 12:15:59, 1] smbd/password.c:register_vuid(310)
Failed to claim session for vuid=101
[2008/04/11 12:15:59, 0] auth/pampass.c:smb_pam_error_handler(73)
smb_pam_error_handler: PAM: session setup failed : System error
[2008/04/11 12:15:59, 1] smbd/session.c:session_claim(143)
pam_session rejected the session for domainname#marsh [smb/25660/101]
[2008/04/11 12:15:59, 1] smbd/password.c:register_vuid(310)
Failed to claim session for vuid=101
[2008/04/11 12:15:59, 0] auth/pampass.c:smb_pam_error_handler(73)
smb_pam_error_handler: PAM: session setup failed : System error
[2008/04/11 12:15:59, 1] smbd/session.c:session_claim(143)
pam_session rejected the session for domainname#marsh [smb/25661/101]
[2008/04/11 12:15:59, 1] smbd/password.c:register_vuid(310)
Failed to claim session for vuid=101
[2008/04/11 12:15:59, 0] auth/pampass.c:smb_pam_error_handler(73)
smb_pam_error_handler: PAM: session setup failed : System error
[2008/04/11 12:15:59, 1] smbd/session.c:session_claim(143)
pam_session rejected the session for domainname#marsh [smb/25661/103]
[2008/04/11 12:15:59, 1] smbd/password.c:register_vuid(310)
Failed to claim session for vuid=103
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba