Forum Replies Created
-
Posts
-
hello,
Terminal Server Node can only be accessed via an Enterprise Server or Cloud Server. If you want to access nodes directly, as well as via a central login point, you could install the Workstation or Terminal Server.
See here for more details:
hello,
if it is possible, can you send to us the previous pair of keys? We would like to investigate further in order to prevent a similar situation arising in the future.
Hello, we suspect that problem is related to authorization on the remote node with the public key
Can you please check if the issue persists also when you generate a new pair of keys?
Rename the original keys to preserve them:
/usr/NX/etc/keys/node.localhost.id_dsa
/usr/NX/etc/keys/node.localhost.id_dsa.pub
and generate a new key-pair by running on the server host:
# export LD_LIBRARY_PATH=/usr/NX/lib
# /usr/NX/bin/nxkeygen -k /usr/NX/etc/keys/node.localhost.id_dsa -p /usr/NX/etc/keys/node.localhost.id_dsa.pub -t dsaEnsure that the new keys have proper permissions and ownership
and update the node:
# /usr/NX/bin/nxserver –nodeupdate <node>Instructions are available also here:
https://www.nomachine.com/DT04L00069#4Hello, thank you for reporting this issue.
We have just inserted a new Trouble Report
To investigate it further we will require the full set of logs:
https://www.nomachine.com/AR07K00677
from both servers: main and remote node.
From what you have written, we can see that a connection to the remote node with protocol NX is created, but it is then lost. The host certificate on the client side cannot be read, and the server cannot see the client version.
Please check your firewall setting if connection on 4000 port is somehow being filtered or blocked.