Hello,
yes we checked this but the solution was in fact elsewhere ... if you jump the gun and go too fast then you don't realise that in fact it was looking for a password in the CUA and not in the correct backend system ... 
so all is solved and up and running now :-)
Thanks for your help,
Siobhan