Re: Problem in synchronising from WIN2K AD to win2k3 ADAM using ADAMSync
- From: "Lee Flight" <lef@xxxxxxxxxxxxxxx>
- Date: Tue, 6 Feb 2007 17:45:11 -0000
Hi
inline below...
"Lakshman" <lakshmanaraja@xxxxxxxxx> wrote in message
news:1170761576.493738.287440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
hi all,
I am in a process of synchronising win2k AD with Win2k3 ADAM.
adamsync /sync localhost:50010 "dc=adstestdomain,dc=com" /log -
ServerDown error is coming.
LOG for Reference:
C:\WINDOWS\ADAM>adamsync /sync localhost:50010
"DC=adstestdomain,DC=com" /log -
Adamsync.exe v1.0 (5.2.3790.2075)
Establishing connection to target server localhost:50010.
There is already an active sync session in progress.
That last message likely indicates that you have another ADAMSync running
somewhere you need to finish that off
Please allow the session to complete, or use -mai to seize the role.
Saving Configuration File on DC=adstestdomain,DC=com
Saved configuration file.
ADAMSync is querying for a writeable replica of
adstest.adstestdomain.com.
Error: DCLocator call failed with error 1355. Attempting to bind
directly to str
ing.
Establishing connection to source server adstest.adstestdomain.com:
389.
Ldap error occured. ldap_bind_s: Server Down.
Taking a network sniff will be easiest way of finding out why the bind
failed
with Server Down.
Extended Info: .
My Config File:
<security-mode>object</security-mode>
As your AD is W2K object mode security is not available you
need so in principal you need partition mode and if you are using
an account that is not a Domain Admin you will need to grant extra
rights for the account in AD for the sync. See:
http://groups.google.co.uk/group/microsoft.public.windows.server.active_directory/browse_frm/thread/3d5b60ea592ef2a0/b436b0a2edd26685
for an example.
Lee Flight
.
- References:
- Prev by Date: Local Admins on Machines
- Next by Date: Printers and AD
- Previous by thread: Problem in synchronising from WIN2K AD to win2k3 ADAM using ADAMSync
- Next by thread: Corrupt Contact
- Index(es):
Relevant Pages
|