Ok, so we were already working on your problem. I've been out
of the office for a few days, hence the lack of progress. We already
know that you haven't made a simple configuration error. There's
some problem with interaction between winsync on the FDS side
and your particular Win2003's AD.
The next thing I was going to ask you if you have the capability
to take ethereal or tcpdump traces of the LDAP traffic between
FDS and AD under the conditions we tried earlier (restart the
server then initiate a re-sync)? Those traces would be useful
in figuring out which side (AD or FDS) has caused the transmission
of entries to halt.
OK, I'm happy to do that. I've used both ethereal and tcpdump. Is there a
filter I should add to capture just the ldap traffic?
BTW, did you see my post on irc vis-a-vis the ldapsearch results?
Dimitri