Greetings from Russia with love :)
Excuse my English, I translate the text using googletranslate.
It seems I found the problem, which appeared in different versions of samba and the different operating systems.
I tested it on linux and freebsd.
In the following pattern: win2003(as a domain controller)+ samba(as a file server)+ winbind (authentication of users from Active Directory).
Files that are accessible over the network to be shared (*.doc, *.xls, *.txt, etc.) are not blocked for the second user.
How it works:
Exists shared folder "\\docs" on a file server samba (linux or freebsd).
The user1(Bob Smith) from computer1 (WinXp) opens a file called "document.doc" and start to edit it.
At this time user2(Jack Sparrow) from computer2 (WinXp) opens the same file.
In file server win2003 user2 sees a message that the file is locked and is read-only.
When working samba, the user2 does not sees in this message, it starts with an open file.
User, which the latter closes the file, save it changes.
Again, this happens only when user authentication via winbind in Active Directory.
If you use security = ads and auth methods = winbind, then files are not blocked.
If you use security = user and local authentication, the files are locked and everything is working correctly.
Hopefully, that clearly explained :)
Please answer me how to fix this error.
Do you have people who speak in Russian?
Thanks in advance.
This really happens with Samba 3.4? As Samba 3.4 is not released yet, what exact version out of the git tree are you using?
ubuntu server 7.10 from the repository
ubuntu server 8.10 from the repository
freebsd 6.0 from source samba-3.0.24.tar.gz, samba-3.0.25.tar.gz, ?
freebsd 7.0 from ports
I have not followed the versions, but they just have different.
no one can help?
Please upload debug level 10 logs of the succeeding smbd vs the failing one.