Is there any known issues between having a 2.4 provider and a 2.2 consumer?

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)

This is the syncrepl on the consumer: ----- s n i p ----- syncrepl rid=0 provider=ldap://provider.domain.tld:3389 type=refreshOnly interval=00:00:00:30 searchbase="c=SE" filter="(objectClass=*)" attrs="*,+" scope=sub schemachecking=off updatedn="cn=Administrator,cn=auth" binddn="cn=consumer,ou=LDAP,ou=System,o=Domain,c=SE" bindmethod=sasl saslmech=gssapi realm=BAYOUR.COM authcId=consumer updateref ldap://provider.domain.tld:3389 ----- s n i p -----

And this is the provier syncprov config: ----- s n i p ----- overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100 ----- s n i p -----

On the provider machine, I also have a 2.4 consumer and that works correctly (with almost the exact config as the 2.2 consumer - without the 'updatedn' and 'authcId' - which isn't allowed - though).

I noticed that there is no 'rid' thingie on the provider any more (or in slapadd) but the 2.4 provider/consumer works any way... ?