Yep. Exactly what I've observed and exactly as documented by MS. >He tries to set it to an NT server, also...but >somehow he realizes that it doesn't get set and changes all the acls to >match, rather than relying on inheritance.
Because the client knows that NT4 servers don't do acl inheritence propogation for him, but 2k servers do. This behavior is documented pretty well in Keith Brown's book. ERX >-----Original Message----- >From: Jim McDonough [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, October 02, 2002 2:50 PM >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: RE: ACL inheritance mess with win2k clients... > > > >>Maybe this one is set improperly? >> >>SE_DACL_AUTO_INHERITED >Well, the 2k client tries to set it, but we don't honor it, and when he >queries, it's not set. He tries to set it to an NT server, also...but >somehow he realizes that it doesn't get set and changes all the acls to >match, rather than relying on inheritance. >---------------------------- >Jim McDonough >IBM Linux Technology Center >Samba Team >6 Minuteman Drive >Scarborough, ME 04074 >USA > >[EMAIL PROTECTED] >[EMAIL PROTECTED] > >Phone: (207) 885-5565 >IBM tie-line: 776-9984 >
