On Monday 22 May 2006 21:34, hackhound wrote: > I don't think it matters as long as the client knows where to find the key, > but I moved it anyway. I got the same error message. I tried connecting > with no key and the error message in the details window changes to: > > NX> 208 Using auth method: publickey > NX> 210 Enter passphrase for key 'L:\NX73F8~1/temp/2160/keylog':
>From this message, it would appear that NX in Windows IS actually finding the key you are using, however, it would also appear that you have encoded the key with a passphrase. Is it possible that NX in Windows does not have a passphrase dialog capability, the ability to prompt you for your password prior to connecting. When I needed to work with SSH via Windows, I almost always used Putty as the SSH client. Putty includes an agent that allows you to pre-load your keys, entering the passphrase at that time and then when you connect with a key, it doesn't need to prompt you again for the passphrase. You might consider using Putty to create a local tunnel for NX and then connect the NX client through the tunnel. Or, as an alternative, try creating a separate key that has no passphrase, install that and see if it works. If so, then that confirms that the problem is with NX prompting you for a passphrase. ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
