samba - Jul 2006 - FW: Problem using 3.0.23 client in a domain with a Samba 3.0.20c PDC. -- REVISED I am using V3.x.x

Ah....sorry for the last note I meant 3.0.23 NOT 2.0.23




=========================================
M. D. Parker
Systems Administrator
General Atomics / Electromagnetic Systems
+1 858 455 2877
mike.parker@ga.com


-----Original Message-----
From: M. D. Parker [mailto:mike.parker@ga.com] 
Sent: Tuesday, July 11, 2006 4:07 PM
To: 'samba@lists.samba.org'
Subject: Problem using 3.0.23 client in a domain with a Samba 3.0.20c PDC.
Importance: High

I have a samba PDC running 3.0.20c 

I installed Samba 3.0.23 on a client joined to the domain.

With this combination, when I attempt to connect to a share on this client
from any host even the localhost results in the following:

$ smbclient //localhost/atest -U auser
Password:
Domain=[DOMAIN] OS=[Unix] Server=[Samba 3.0.23-SerNet-RedHat] tree connect
failed: NT_STATUS_ACCESS_DENIED

Windows clients will similarly NOT connect.

This situation does not happen on other NON-3.0.23 clients containing
shares.  I have traced the problem to the line in the smb.conf file that I
have been using for years:

[atest]
.
.
"valid users = auser"
.
.

If I remove this line, I get connected to the share, however, of course I
lose any username protection.  I have tried using write list = or even admin
users = ... All to no avail.

The log file indicates seems to recoginze my id but then finally at the end
gets some type of deny message:

[2006/07/11 15:38:34, 2] lib/access.c:check_access(324)
  Allowed connection from  (127.0.0.1)
[2006/07/11 15:39:37, 2] auth/auth.c:check_ntlm_password(309)
  check_ntlm_password:  authentication for user [auser] -> [auser] ->
[auser] succeeded
[2006/07/11 15:39:37, 2] lib/access.c:check_access(324)
  Allowed connection from  (10.10.32.200)
[2006/07/11 15:39:37, 2] lib/access.c:check_access(324)
  Allowed connection from  (10.10.32.200)
[2006/07/11 15:39:37, 2] smbd/service.c:make_connection_snum(571)
  user 'auser' (from session setup) not permitted to access this share
(atest)

I have had this problem on all the "RC" versions of 3.0.23 and thought
that
this was something that would probably be fixed at release time.  Wrong
assumption.

Got a fix or a workaround for this problem?  I really need this to work
before being able to upgrade to this revision.

=========================================
M. D. Parker
Systems Administrator
General Atomics / Electromagnetic Systems
+1 858 455 2877
mike.parker@ga.com