Re: [Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-04-18 Thread Gunnar Magnusson
Hi, I'm curious if you have any updates regarding this problem. I'm facing exactly the same issue. When I'm trying to make a backup with IBM TSM of a Samba share mounted under Windows, I keep receiving the error message that required NT privilege is not held. This problem started to appear when

[Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-02-18 Thread Adrian Berlin
Cc: samba@lists.samba.org Subject: Re: [Samba] BUG: SAMBA 3.5.x and IBM TSM Date: Thu, 17 Feb 2011 16:18:17 +0100 On Thu, Feb 17, 2011 at 03:55:43PM +0100, Adrian Berlin wrote: I am using SAMBA 3.5.x and it doesn't work with IBM TSM. IBM TSM works properly with SAMBA 3.2.15

Re: [Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-02-18 Thread Volker Lendecke
On Fri, Feb 18, 2011 at 09:42:08AM +0100, Adrian Berlin wrote: With SAMBA 3.5.x I got error from IBM TSM: required NT privilege is not held. I mount SAMBA share as user merc and user merc is added to superusers. with SAMBA 3.2.15 there isn't any problem Then I would highly recommend to

Re: [Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-02-18 Thread Michael Wood
Hi On 18 February 2011 10:42, Adrian Berlin g...@rock.com wrote:  With SAMBA 3.5.x I got error from IBM TSM: required NT privilege is not held. I mount SAMBA share as user merc and user merc is added to superusers. with SAMBA 3.2.15 there isn't any problem You need to describe exactly what

[Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-02-17 Thread Adrian Berlin
Hi! I am using SAMBA 3.5.x and it doesn't work with IBM TSM. IBM TSM works properly with SAMBA 3.2.15. Is there any chance to solve this issue in future SAMBA versions? Best regards /Adrian Berlin -- You Rock! Your E-Mail Should Too! Signup Now at Rock.com and get 2GB of Storage!

Re: [Samba] BUG: SAMBA 3.5.x and IBM TSM

2011-02-17 Thread Volker Lendecke
On Thu, Feb 17, 2011 at 03:55:43PM +0100, Adrian Berlin wrote: I am using SAMBA 3.5.x and it doesn't work with IBM TSM. IBM TSM works properly with SAMBA 3.2.15. Is there any chance to solve this issue in future SAMBA versions? What exactly does not work? Volker -- SerNet GmbH,