search for: openoffice2

...t if a Linux client creates the lock, we get either two or more Linux clients being able to open the same file for writing (SMBFS) or the other extreme, if one Linux client opens the file none of the others can't even open it in read-only mode (CIFS). The main application used on the network is OpenOffice2. I have been doing some testing using the cifs and smbfs kernel modules on one FC4 and one Debian client (both 2.6 kernels), plus a Windows 2000 machine. I used a simple test program that opens a file on a mounted Samba share and tries to set a write lock. I noticed that depending on the client...

...do with rights, that can cause read/write right conflicts on the new system for Windows. On the new test system, at present I have the problem that I can not read or write to Windows Office products (MS0) over SMB shares in the Windows Network on the Samba Server, neither can I read or write with OpenOffice2 (OO2) products directly on the NFS-Server shares. On the Samba side in the windows network, a username for 'Workgroup' is asked where all passwords are rejected (even though the workgroup has been named as eg. "ABC" in the new Samba server), and I get a read only error on the NFS...