I can not find the solution, but I do recall reading a solution on the web
stating having to reset the password on the server node side and then the
client password to match, even though they already match.

This worked for the 4.1.30 client we were seeing this error on.

Sorry I can not find the original solution, I do not want to take credit for
this fix, just passing on the info.

Hope it helps,
Mark B.