Topic: Problem Word and Excel 2007 with Samba

[Geo]

Hello,

I use a SME Server 7.0 since little time as domain server without problem. From Windows work station, i used Office 2003 and now i use Office 2007.

When i modify and save a file from SME Server with Word or Excel 2007, the properties of file are modified. The new owner is me and the file is now read only   

Apparently, this is a bug in Office 2007 (even with updates). But can not i bypass this bug by setting SME or Samba ?

Thank you very much

Geo

[zatnikatel]

have you tried setting up groups in SME server
the only way i would know how to fix this is to add a cron job in SME or any Linux and change the permission via a script
chown 777 file name and chgrp 777 file name and have a script run every few minets read up on crontab on how to add the script or download the crontab addin for SME server
the only other way is to right click on the file and change it but that would be a total pain

i was thinking of using office 2007 but i think i will stay with 2003 now trust MS to screw things up 

[zatnikatel]

to add i think you are able to do this with samba but i am not sure you can use creat mode on the ibay so it keeps the permisson correct as well but i am not sure of what to add to a custom template some one else on the forums may know

[dm]

I've just checked your remark, as I have also office 2007 with other users and files on SME ibays.
The permissions are indeed changed, but the other users can still modify the files.

My server isn't a domain controller, so I presume it is a problem in sme....

[Geo]

Thank you for your response,

I use already a script for reconfigure the ACL rigths. I use the ACL rigths on ibays that are shared with Windows stations.
The ibays are numerous and with different rights for the users.

I think that Samba ACL that combined with Office 2007 is problem.
But,    i don't know configured Samba 

Thank you for your help.

[zatnikatel]

security mask

Essentially, zero bits in the security mask mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change.
If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file.
To make sure that a windows-user can never change the access right for "other" we define the security-mask to be 0770:
this goes in to SMB.conf file 
security mask = 0770

ths would have to be done though custom templates

[Geo]

Thank you,

I watched in SMB.CONF but i don't finded "security mask" 

But, if my file is in my home directory then no problem with Office 2007 because this folder isn't configured with ACL (Octal permission: 0660). But only folder configured with ACL have the problem. Rigths are modified after saving with Word or Ecxel 2007 (Before modification, octal permission: 0770 - After modification , octal permission: 0470).
Thus, I strongly think to a link between Office 2007 and the ACL which is failed. As ACL is managed by Samba, i want tested configuration of Samba. The last upadte for Office 2007 did nothing changed 

Thanks

[zatnikatel]

yep i would say it is the ACL problem
with things like this your best friend can be google you may need to add this to youe SMB.CONF file but with SME you will need to add a custom-template
have a look in you user manual if you are not sure i will have a look at this myself tomorrow night it is late here in australia and i need sleep
also have a look on samba web site as well go the australian they made up samba 

[Geo]

Thank you,

I searched on the Internet and the answers were few and ineffective.

But from Samba's documentation,
I think i finded a solution with SMB.conf. I adjusted the following parameters:

create mode = 0770
force create mode = 0770
inherit permissions = no
nt acl support = no ; Apparently, just no visible by windows
profile acls = yes

Now, i'm finding a good combination with these parameters.
Then, i test if everything goes well with different versions of Office.
It's on the right track 

Thanks for your help

[Geo]

A last information,

Just say "nt acl support = no" is ok.

My problem is resolved!

 

   
Thanks again for your quick answers.

[byte]

the only way i would know how to fix this is to add a cron job in SME or any Linux and change the permission via a script
chown 777 file name and chgrp 777 file name and have a script run every few minets read up on crontab on how to add the script or download the crontab addin for SME server

It's always been common practice not to use 777 as its a security risk and not recommended.

[byte]

Hello,

I use a SME Server 7.0 since little time as domain server without problem. From Windows work station, i used Office 2003 and now i use Office 2007.

First thing I would do is upgrade the server to the latest SME Server 7.3 as major changes have happened since, then if you still have an issue raise a bug report.

[zatnikatel]

byte
geo said it it is a bug with office 2007 not really a SME problem i know that 777 is a risk that is why i put at the bottom of it was to use 0770
so it is an MS problem not sme as there was no problem with office 2003

[byte]

geo said it it is a bug with office 2007

OK - Geo do you have a reference as to why/how you think it's a bug ?

not really a SME problem i know that 777 is a risk that is why i put at the bottom of it was to use 0770
so it is an MS problem not sme as there was no problem with office 2003

It still could be a problem with the need to upgrade samba as the original reporter is running SME Server 7.0 which is an old release and we have since made major changes in SME Server 7.1, 7.2 and 7.3 - So I'd still recommend upgrading to latest SME Server 7.3 and seeing if the problem still exists.

[Geo]

OK - Geo do you have a reference as to why/how you think it's a bug ?

Hello,

After many test,
There aren't problem of rights with the Office 2000 and 2003.
Working with Open Office, there aren't problem too.
The problem was the strange change rights of files from Office 2007 alone.
Then, i think it's a bug from Office 2007 to Samba.

See you