summaryrefslogtreecommitdiff
path: root/source3/rpc_server
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2004-01-14 16:26:14 +0000
committerGerald Carter <jerry@samba.org>2004-01-14 16:26:14 +0000
commit84b24610e5940fcf9e4a2f1813790b131dc7fbe7 (patch)
treec961ff81ea86af8d3d7834753c22f6de0022f2ab /source3/rpc_server
parent138c34e1506905ab97ca297c8cd697c1c8328276 (diff)
downloadsamba-84b24610e5940fcf9e4a2f1813790b131dc7fbe7.tar.gz
samba-84b24610e5940fcf9e4a2f1813790b131dc7fbe7.tar.bz2
samba-84b24610e5940fcf9e4a2f1813790b131dc7fbe7.zip
* 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. (This used to be commit 86f24908c395cc832ae87b04c9da3d32449acad3)
Diffstat (limited to 'source3/rpc_server')
0 files changed, 0 insertions, 0 deletions