Forum Replies Created
-
Posts
-
There is an issue with reporting sessions from remote node where NoMachine server did not find working ‘X server’. That’s why the virtual
session was indeed created on the remote host, but it was not reported on ‘session list’. Thus the session will not be available for reconnection. Version 4.1 will have the fix.why “out of the box server node” comes with port 22 (proto SSH?), but when I run “nxserver –nodeadd <ip>” its added with port 4000 (proto NX?)?
TR has been opened.
Hi, we will need:
1. Compressed var/log directory from server’s side (on Windows standard path should be C:\ProgramData\NoMachine\var\log
2. Confirmation of whether you have a password set (if it’s not a password-less account)
3. Did you reboot of the server machine after installing NoMachine.
4. Are there other user accounts on the server machine – can you successfully log in on them via NoMachine?For logs, see the following article: https://www.nomachine.com/AR07K00677
This is a bug. Problems with update are not related to the expired evaluation license. You should simply get a warning message and the server will refuse to work once update completed.
We have reproduced it and there is a workaround available while users wait for the fix to be released.
Hi Muttonhead, yes NoMachine is free 🙂 and you are doing everything right. What’s wrong is a bug that we’ve fixed. Can you contact us direct to get more information?
Thanks, Britgirl
And the client logs
Reproduce the problem (with player opened and connected) and send us the ‘.nx’ directory.@carsten.heidmann did you follow the instructions here? https://www.nomachine.com/AR10K00710
Or is it a normal installation running Ubuntu dekstop (LightDM/Unity)?
@simonquerrero NX Free Edition was a terminal server and supported SSH.
If you want those functionalities, you need the Workstation for Linux.
NoMachine clients have always been free as a rule. I advise you to contact our team via the website to check this and also to ask about pre-release versions of any of our upcoming products. The sales or info team will be able to provide you with more information and also advise you on the right server products.
If you connect from a PC on the same network, you have to use the internal IP which you have done correctly. When you connect from a PC on an external network, you need to use the Gateway IP instead. Your office’s external IP address should be shown in the Gateway IP field (in your case 108.xxx.xxx.xx) which you obtain by opening the GUI from the menu and clicking on the penultimate icon on the right (Server settings). It takes you to the Forwarded ports panel by default. Write down this IP address along with the port number shown next to NX:…. This information is what you need to use in the connection GUI when connecting from home. Make sure that the checkbox for NX is ticked.
If you did this, and you are still getting the connection error, then it’s either a firewall issue or a router issue. In that case you will need to configure your office router to forward a suitable port to your local IP port 4000 (NoMachine uses 4000 by default).
To connect from home, you then use your office’s external IP address and the port that you either obtained from the Forwarded ports panel or which you configured manually on the router.
Hi John, this is strange and we would need to see the logs to be able to understand what is happening. If they are not too big, you can submit them there, otherwise send to forum[at]nomachine[dot]com. You will need to follow the instructions in the article here (first reproducing the problem) on how to enable and extract them.
https://www.nomachine.com/AR10K00697The client side logs you attached are not complete. If you have problems attaching client and server side logs here, you can send them to forum[at]nomachine[dot]com.
Please consult the following article for instructions on how to get the complete client and server logs:
https://www.nomachine.com/AR10K00697
https://www.nomachine.com/AR07K00677
On the client side (on Windows 7):
– Start the session and reproduce the problem
– go to C:\Users\<YOUR_USERNAME>\.nx\
– find newest R-* directory and compress it .Make sure you set in the player settings ‘do not delete old log files on exit’ (Open the UI, click ‘Player settings’ icon, click ‘Player options’)