Michael,
Perhaps, you might run into issue with keys overlapping on server
under the heavy load which have been fixed in 3.0.5. We didn't have to
regenerate keys on client side after upgrade, but we had to re-upload
several public keys from clients on the policy server. Also, if your
client authen
Got the verbose server output, and this seemed to be the error:
cf3 Received: [SAUTH y 256 37 c] on socket 5
cf3 Private decrypt failed = block type is not 02
cf3 Auth dialogue error
cf3 REFUSAL of request from connecting host: (SAUTH y 256 37 c)
I then regenerated the ppkeys for both the server
