David C. Rankin wrote:
Ok, I think the following patch should fix the issues
you're seeing. It should apply on top of, or in place
of my previous patch - shouldn't matter.
It causes all opens requiring SEC_RIGHT_SYSTEM_SECURITY
to fail as Windows does with NT_STATUS_PRIVILEGE_NOT_HELD,
which
On Tue, Mar 10, 2009 at 07:23:26AM +0100, Thomas Bork wrote:
David C. Rankin wrote:
Ok, I think the following patch should fix the issues
you're seeing. It should apply on top of, or in place
of my previous patch - shouldn't matter.
It causes all opens requiring SEC_RIGHT_SYSTEM_SECURITY
to
Jeremy Allison wrote:
On Wed, Mar 04, 2009 at 07:29:15PM +0100, Michele Petrazzo - Unipex srl wrote:
Jeremy Allison wrote:
Ok, that's very helpful and also tells me why I've
seen few problem reports of this.
Can you try the test patch for 3.3.1 I just
published ?
The error changes:
before
On Wed, Mar 04, 2009 at 08:47:25AM +0100, Olivier Doremieux wrote:
Hello,
I have the same problem with samba 3.3.0 and 3.3.1. I use to be able to
edit some MS Word file on a shared network.
What should I do to fix this problem? Is there a way to change some
config file?
Can you get me a
On Thu, Feb 26, 2009 at 12:26:52AM +0100, François Legal wrote:
To be honnest, I did not really understand what SACL is. Are you talking
about file and directories ACLs ?
How do I know if my users have the SE_SECURITY_NAME priviledge. My users
(especially the one who is accessing the file
On Wed, Mar 04, 2009 at 08:47:25AM +0100, Olivier Doremieux wrote:
Hello,
I have the same problem with samba 3.3.0 and 3.3.1. I use to be able to
edit some MS Word file on a shared network.
What should I do to fix this problem? Is there a way to change some
config file?
Can you try this
François Legal wrote:
Same here.
My env are all inside virtualized machines: win2k server, debian lenny with
3.3.1 as servers and joined into win2k domain, win2k pro and win xp pro
(both joined) as clients.
I have 1 share (called test) where I made my tests.
xp has office 2k7 and
On Wed, Mar 04, 2009 at 06:56:40PM +0100, Michele Petrazzo - Unipex srl wrote:
François Legal wrote:
Same here.
My env are all inside virtualized machines: win2k server, debian lenny with
3.3.1 as servers and joined into win2k domain, win2k pro and win xp pro
(both joined) as clients.
I
Jeremy Allison wrote:
Ok, that's very helpful and also tells me why I've
seen few problem reports of this.
Can you try the test patch for 3.3.1 I just
published ?
The error changes:
before I had a Access Deny and now a there's been a network error
here is the picture:
On Wed, Mar 04, 2009 at 07:29:15PM +0100, Michele Petrazzo - Unipex srl wrote:
Jeremy Allison wrote:
Ok, that's very helpful and also tells me why I've
seen few problem reports of this.
Can you try the test patch for 3.3.1 I just
published ?
The error changes:
before I had a Access Deny
On Wed, Mar 04, 2009 at 08:47:25AM +0100, Olivier Doremieux wrote:
Hello,
I have the same problem with samba 3.3.0 and 3.3.1. I use to be able to
edit some MS Word file on a shared network.
What should I do to fix this problem? Is there a way to change some
config file?
Ok, I think I
On Wed, Mar 04, 2009 at 07:29:15PM +0100, Michele Petrazzo - Unipex srl wrote:
Jeremy Allison wrote:
Ok, that's very helpful and also tells me why I've
seen few problem reports of this.
Can you try the test patch for 3.3.1 I just
published ?
The error changes:
before I had a Access Deny
On Tue, Feb 24, 2009 at 09:33:56PM +0100, François Legal wrote:
Hello,
I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the
other) to samba 3.3.0 then samba 3.3.1, and apart from the problem
with winbindd and trusted domain, my users are not able to modify any
ms word
Jeremy Allison wrote:
Ok, I think the following patch should fix the issues
you're seeing. It should apply on top of, or in place
of my previous patch - shouldn't matter.
YES!
It's the right one!
Just tried with xp and Office2k7 and it correctly opens and save a .docx
file!
Thanks a lot!
Hello,
I have the same problem with samba 3.3.0 and 3.3.1. I use to be able to
edit some MS Word file on a shared network.
What should I do to fix this problem? Is there a way to change some
config file?
Thanks in advance,
Olivier DOREMIEUX
--
To unsubscribe from this list go to the
On Tue, Feb 24, 2009 at 09:33:56PM +0100, François Legal wrote:
Hello,
I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the
other) to samba 3.3.0 then samba 3.3.1, and apart from the problem
with winbindd and trusted domain, my users are not able to modify any
ms word
Ok, looking in the log I've found the problem. The application
is asking for an access mask of 0x102, which maps to
READ_CONTROL_ACCESS (which we grant) and SEC_RIGHT_SYSTEM_SECURITY
(ie. access to the system security ACL - the audit ACL) on the
file.
From this page:
Hello,
I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the
other) to samba 3.3.0 then samba 3.3.1, and apart from the problem
with winbindd and trusted domain, my users are not able to modify any
ms word document (excel does the same).
You can open the file correctly, modify
On Tue, Feb 24, 2009 at 09:33:56PM +0100, François Legal wrote:
Hello,
I tried this week to upgrade my samba 3.2.4 (2 PDCs one trusting the
other) to samba 3.3.0 then samba 3.3.1, and apart from the problem
with winbindd and trusted domain, my users are not able to modify any
ms word
19 matches
Mail list logo
