[Samba] 64 Bit XP client unable to add ACE on 3.0.24 Samba

[malk at sidehack.sat.gweep.net]

Finally tried this today -- this is indeed fixed in 3.0.32.

The only change I had to make was to new config syntax for mapping
UIDs / GIDs by idmap rid.

3.0.24 was like this:

       idmap backend = rid:"BUILTIN=1000-1999,SS=3000-100000000"

3.0.32 for us works like this:

       idmap domains = SS
       idmap config SS:backend = rid
       idmap config SS:base_rid = 0
       idmap config SS:range = 2000-100000000

I built the Fedora 8 srpm package for 3.0.32 into binary rpms for
Fedora Core 6 so I could run 3.0.32 on my older production
server.

Thanks again.

-Eric

> 
> Jeremy-
> 
> Thanks a bunch for the quick reply!  I'll build up a 3.0.32 and try it.
> I'll also try to remember to reply with my results.
> 
> Thanks a bunch to you and the Samba team for the excellent work.
> 
> -Eric
> 
> > 
> > On Thu, Nov 06, 2008 at 06:14:38PM -0500, malk at sidehack.sat.gweep.net wrote:
> > > Hi all-
> > > 
> > > I searched quite a bit and couldn't really come up with anything, so I'm
> > > posting to the list to hopefully find out if I have any options.
> > > 
> > > I've got a production FC6 box running 3.0.24-7.fc6 build of samba server
> > > that's very stable for us.  It's a member of an ADS domain w/ server 2003
> > > domain controllers.
> > > 
> > > Recent 64 bit windows XP pro boxes are having the exact problem described
> > > in release notes I found for HP's CIFS server which I'm assuming uses some
> > > version of samba for it's implementation:
> > > 
> > > Problem
> > > 
> > > 64 bit Windows XP clients are unable to add a new ACE. Adding an ACE through
> > > Windows Explorer File->Properties->Security interface to a file or directory
> > > from a Windows XP Professional 64-bit edition results in an error that reads:
> > > 
> > > This program cannot open the required dialog box because the specified
> > > computer <samba servername> cannot be determined to belong to a domain.
> > > Try again.
> > > 
> > > Workaround
> > > 
> > > There is no known workaround at this time.
> > > 
> > > My question is - does anyone know if this is fixed in a more recent version
> > > of 3.0.X series or the 3.2 series of Samba?
> > 
> > I think this works in 3.0.32 but the only way to be sure
> > is set up a test server and try it.
> > 
> > Jeremy.
> > 
>