On Saturday 06 August 2005 00:49, Art Fore wrote:
on the server, I did the nxsetup --install --setup-nomachine-key
nxserver --status results in
NX>100 NXSERVER Version 1.4.0.03 OS (GPL) NX>110 NX Server is running NX>999 Bye
I can ssh into the server from the client with no problem?
Then think about the next logical problem -- firewalls on both the server and the client. Investigate open/closed ports on your firewall(s). Are you trying to connect from a client to a server that both reside on the same LAN? Or are you trying to connect via a WAN?
What files should I have in home/afore/.ssh on the Server? On the server if have authorized_keys and Authorized_keys2. authorized_keys is the id_dsa.pub file copied from the client. Client machine has authorized_keys, I think also copied from id_dsa.pub from the client, authorized_keys.pub I don't know where from, id_dsa, id_dsa.pub from the keygen, and known_hosts when is installed when I accept certificate from server the first time I run NXClient.
People much more versed in ssh authentication will have to help you with your ssh keys. Sorry.
Knxclent always says connection could not be made, timeout.
Firewall? Also, give the free client from NoMachine a try. It includes a set-up wizard and several other packages that may help. You may have much better results with that client. -- Christopher Shanahan