MS-DRSR 4.1.23 IDL_DRSReplicaSync has some great pseudo-code in 4.1.23.2 Server Behavior of the IDL_DRSReplicaSync Method. However, it finishes with this text statement:
Perform a replication cycle as a client of IDL_DRSGetNCChanges. 4.1.10.4.1) to form the first request and send it. If not DRS_MAIL_REP in r.options, then wait for the response, process it, send the next request (section 4.1.10.6), etc., until the replication cycle is complete. This is great, but I need to know what parameters are passed in to 4.1.10.4.1 ReplicateNCRequestMsg In particular, I'm trying to chase down an issue in our RODC case, where the SPECIAL_SECRETS_PROCESSING flag isn't being sent by our RODC to GetNCChanges. I know how I *could* force it, but I don't know if it should always be forced, for example. For example, should the server sending DsReplicaSync tell the RODC to request it, or should the RODC add it (and remove WRIT_REP) on it's own? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
