smb is configured to user users in smbpasswd and all shares use force user and force group to nobody/nogroup to ensure files are shareable by anyone.

Two shares exhibting odd behaviour now.

[barry]
   comment = Barry's Files
   path = /data/barry
   guest ok = no
   browseable = yes
   read only = no
   force user = nobody
   force group = nogroup
   valid users = barry

[repo]
   comment = Shared Files
   path = /data/share
   guest ok = no
   browseable = yes
   read only = yes
   force user = nobody
   force group = nogroup
   write list = barry

Previously this worked correctly (before the package upgrade to 2:4.1.13 (was previously 2:4.1.11).
Correct behaviour allows use barry to have write access to both shares.

After the upgrade the [barry] share offers NO write access. The [repo] allows creation of files, but not files within newly created directories.

Disk permissions havent changed and are chown -R nobody.nogroup with write permission on all directories. Newly created directories are writable by nobody.

Shares work from Windows 7.Shares FAIL from Debian clients.
I have tried mount -t cifs and smb4k with dolphin and command line cp/touch. All fail to access to write - where with the same credentials the windows system succeeds.

Were you using the same kernel version before and after the upgrade of Samba?

Can you try mounting with "-o nounix"? I suspect this is related to the fact
that the UNIX extensions expose the actual UIDs.

Cheers,

Jelmer