Group: Forum Members
Posts: 21,
Visits: 112
|
Our problem is more generic - I am having trouble getting the public keys to work using network drives. I do not want to use the Registry because the servers are load balanced.
What I have managed to deduce is the following:
We have two test users: UserA and UserB We have two servers: Server1 and Server2
Bother users have their public key stored in an appropriate location on a shared drive.
UserA has a PAD entry in the Registry on Server1, but not on Server2 UserB has a PAD entry in the Registry on Server2, but not on Server1
Bother servers are now configured to not store the key in the registry.
UserA can successfully connect using his key to Server1, but not Server2 UserB can successfully connect using his key to Server2, but not Server1
So they users can only connect to the server which have an appropriate PAD entry for them in the registry. Even though the servers are configured to use the network share for the key authentication. this leads me to believe that authentication is still involving the registry in some way.
I will have a think about the other users issue you mentioned. I have also noticed that if the directory doesn't exist in advance it doesn't seem to work - but then this is possibly to be expected. it's not a problem for us to create these directories in advance.
Thanks, Robin
|