| commit | 86f24908c395cc832ae87b04c9da3d32449acad3 | |
| author | Gerald Carter <jerry@samba.org> | |
| Wed, 14 Jan 2004 16:26:14 +0000 (14 16:26 +0000) | ||
| committer | Gerald Carter <jerry@samba.org> | |
| Wed, 14 Jan 2004 16:26:14 +0000 (14 16:26 +0000) | ||
| tree | cf296c16dd11c795674fcd4a80da301229a88ded | treesnapshot (tar.gz zip) |
| parent | 72d8eea25dbb54d7ef78264cd6f419220dc85fb6 | commitdiff |
* Revert to using rpc for mixed mode AD domains.
The reason for this are:
(a) the set_dc_type_and_flags() cannot tell the different
between connecting to an NT4 domain and an NT4 BDC
of a mixed mode domain.
(b) the connection management for the rpc backend only
provides on named pipe per cli_state. So it is possible
to connect to an NT4 BDC for netlogon and an AD mixed mode
DC for lsarpc. RPC is the lowest common demonimator here.
(c) Issue with the sequence number value between the
highestCommittedUSN LDAP attribute and the seq_num returned
via RPC.
We will revisit this later, but the changes need to make this
work right now are too broad and risky.
The reason for this are:
(a) the set_dc_type_and_flags() cannot tell the different
between connecting to an NT4 domain and an NT4 BDC
of a mixed mode domain.
(b) the connection management for the rpc backend only
provides on named pipe per cli_state. So it is possible
to connect to an NT4 BDC for netlogon and an AD mixed mode
DC for lsarpc. RPC is the lowest common demonimator here.
(c) Issue with the sequence number value between the
highestCommittedUSN LDAP attribute and the seq_num returned
via RPC.
We will revisit this later, but the changes need to make this
work right now are too broad and risky.
| source/nsswitch/winbindd_cache.c | diffblobblamehistory |