Quoting Howard Chu hyc@symas.com:
Turbo Fredriksson wrote:
Is there any known issues between having a 2.4 provider and a 2.2 consumer?
No known issues. Of course 2.2 is Historic; there might be issues but we're not tracking them any more.
My 2.2 (using SASL) doesn't seem to be binding. I get the connect, but no bind etc (running the provider with '-d -1')... And the log on the consumer just say: do_syncrep1: ldap_sasl_interactive_bind_s failed (-2)
Then you have a problem with SASL, and not with syncrepl itself.
Yeah, I think I finaly found that out. It was the reverse... I don't have propper reverse (yet) so I had to 'fake it' (by setting up my own reverse on all my own DNS servers). However, I missed one of the servers (for some reason) and that naturaly didn't have the reverse for my server(s)...
But fixing this, I get (on the provider, running with 'parse sync none'):
----- s n i p ----- Mar 20 13:38:57 rigel slapd/provider[8932]: do_search: get_ctrls failed ----- s n i p -----
That MUST be a compability problem, right?