samba - May 2010 - permission issues between 3.4.0 & 3.0.3?

Hi all!!

I'm experimenting a set of problems when trying to connect Samba client to
windows. I don't have admin rights on the windows side, so I should trust
all my winSA admin is telling me.

Windows side (server):
In the server Side (win2k3), the SA defined a shared resource.
The share-permissions tab the "domain users" group has typical
permissions,
and in the security permissions tab the "domain users" has "read
& exec",
"show" and "read".

In the server the structure is
\\w2k3server\share1\dir1\dir2\target

the "share" resource maps to c:\share, with the permissions described
above.
Both folders dir1 and dir2 haven't any permissions to the user I'm using
to
connect (test-user)
"Target" folder has permissions to allow test-user to read, list,
write,
modify ... all but full control.


Linux side (clients)

First try with CentOS 4.7 -includes samba 3.0.X-.

mount -t cifs //w2k3server/share1 /mnt/smb
cd /mnt/smb
ls -> OK
cd dir1/dir2/target -> "dir1" doens't exists for this client

same behaviour if mounting directly as:
mount -t cifs //w2k3server/share1/dir1/dir2/target /mnt/smb
cd /mnt/smb
ls -> "." doesn't exist

Second try with Ubuntu -samba 3.4.0-
mount -t cifs //w2k3server/share1/dir1/dir2/target /mnt/smb
cd /mnt/smb
ls -> works fine
> testfile1.txt -> works fine
But I should use the CentOS box, so I compiled from sources the RPM of
3.4.0, 3.4.1, 3.4.8 ... same results with 3 versions -> identical as the
first try.

I can't figure out what is failing here, the "bug" is still live
with CentOS
+ samba-common/samba-client 3.4.X, while works properly with Ubuntu +
samba-common/client 3.4.0. Should I upgrade the kernel "cifs" module
or
other component?

Any clue will be appreciatted.

Thanks.

-- 
3rd Law of Computing:
Anything that can go wrSegmentation fault -- core dumped.

In addition to my original post:
http://lists.samba.org/archive/samba/2010-May/155924.html

In the server side (windows 2k3) with a share "share1" and the
following dir
structure:

c://share1/dir1/dir2/target

c:/share1: sharing tab= test_user can read/write; permission tab: test_user
has all but full control;
dir1/dir2: none of them have any permision to the test_user directly or
inherited.
target: test_user can read/write ... (all but full control).

I tested the same with CentOS 3.X, 4.x, 5.x (none of them could list the
share nor create new files)
And with Ubuntu 8.04, 9.10, 10.?: with Ubuntu 8.04 can't read the share, but
on 9.10 yes.

I want to get this working on CentOS, but I still don't know which component
has the bug/contraint/missing feature. Maybe samba? samba-client? cifs
kernel module? kernel version?

I need to identify which component is causing this behaviour in order to
patch/upgrade it in a CentOS 4.8.

Thanks.

-- 
3rd Law of Computing:
Anything that can go wrSegmentation fault -- core dumped.