[cifs-protocol] RE: [Pfif] Microsoft Client tool expectatations
abartlet at samba.org
Tue Sep 9 06:28:55 GMT 2008
On Mon, 2008-09-08 at 09:24 -0700, Edgar Olougouna wrote:
> Good morning Andrew,
> Thank you for your request concerning the Windows Client tool
> expectations. I have created a case for this (see info below); one of
> my colleagues will be in touch with you.
> SRX080908600475 - ProtoDoc 99999: [MS-ADTS]: Microsoft Client tool
This should probably be split into two cases.
> > Similarly, against our current GIT tree, the Win2k3 admin pack on
> > WinXP won't launch 'Active Directory Users and Computers' against
> > Samba4. The error seems to be in response to our return value for the
> > cn=aggregate schema.
While we still have the problem of 'how do I get past cryptic client
messages', the particular case here was easily solved by a comparative
trace with windows.
The issue is that we would include an entry:
objectClasses: ( 126.96.36.199 NAME 'top' SUP top ABSTRACT..
The MMC Active Directory Users and Computers snap in presumably
objected to the 'loop' this would present. The fixed entry is:
objectClasses: ( 188.8.131.52 NAME 'top' ABSTRACT...
Now, the new resolution I would like is for this someone to find where
this should be documented in MS-ATDS and to call out the semantics here
very carefully (that top must not be SUP 'top', despite being so
indicated in the full schema).
Also, an indication of the semantics of modifyTimeStamp on this entry
would be worthwhile. I generate these attributes on the fly, so this
value will not normally change (even with schema updates) - but ADUC
very specifically reads this value. Does it implement a cache of some
kind, and therefore how must this change after schema updates?
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/cifs-protocol/attachments/20080909/3eb474ab/attachment.bin
More information about the cifs-protocol