DonnieDraco
2006-08-31, 01:07 PM CDT
I starte using FreeNX on FC5 a few months ago and after the initial installation and configuration I had everything working, albeit with a few hiccups here and there. That is until I reformatted my XP Pro machine.
With everything the same on the server, my windows machine is now incapable of connecting to the server via the NoMachine client (2.0.0-98).
Following the directions from Rick Stouts setup page (copying the /etc/nxserver/client.id_dsa.key to the client and saving it in the configuration) my connection sequence goes :
1) Setting up the environment
2) (Prompt) The authenticity of host 192.168.1.103 can't be established. RSA fingerprint blah blah blah blah. Do you want to continue?
3) Click yes and then it just hangs on "Connecting to 192.168.1.103" until timeout
Here's the weird part. I can connect to the server through SSH (using passwords) just fine from my windows box so the server is reachable. I can also issue the "ssh -i /etc/nxserver/client.id_dsa.key nx@localhost" from the server to connect as the nx user so the server is configured properly. The same command from a windows box "ssh2.exe -i c:\client.id_dsa.key nx@192.168.1.103" does not work however and it prompts me for nx's password.
There are no entries in messages, secure, or nxserver.log that are of any help either.
Not quite sure what to do but I feel there is some issue using key authentication on the windows box although I'm not sure how to fix it.
Any help would be greatly appreciated and I apologize for another FreeNX question.
With everything the same on the server, my windows machine is now incapable of connecting to the server via the NoMachine client (2.0.0-98).
Following the directions from Rick Stouts setup page (copying the /etc/nxserver/client.id_dsa.key to the client and saving it in the configuration) my connection sequence goes :
1) Setting up the environment
2) (Prompt) The authenticity of host 192.168.1.103 can't be established. RSA fingerprint blah blah blah blah. Do you want to continue?
3) Click yes and then it just hangs on "Connecting to 192.168.1.103" until timeout
Here's the weird part. I can connect to the server through SSH (using passwords) just fine from my windows box so the server is reachable. I can also issue the "ssh -i /etc/nxserver/client.id_dsa.key nx@localhost" from the server to connect as the nx user so the server is configured properly. The same command from a windows box "ssh2.exe -i c:\client.id_dsa.key nx@192.168.1.103" does not work however and it prompts me for nx's password.
There are no entries in messages, secure, or nxserver.log that are of any help either.
Not quite sure what to do but I feel there is some issue using key authentication on the windows box although I'm not sure how to fix it.
Any help would be greatly appreciated and I apologize for another FreeNX question.