Forum Replies Created
-
Posts
-
I advise you to update your software, we just released 4.1.29 and let us know if you are having issues still: https://www.nomachine.com/SU02L00100
We released version 4.1 which solved a number of issues. Can you install this version and let us know if the problem is fixed?
The article explains how to use version 3.5.0 and needs to be updated by the author (since we don’t make version 3.5.0 available any longer).
For headless Linux servers where you have NoMachine 4 installed, you should check the instructions here: https://www.nomachine.com/AR10K00710
The free version of NoMachine is for remote access to the physical display. It allows one connection. NX Free Edition of the earlier 3.x provided the virtual desktop functionality. This is available in the Workstation (and the other products of the Terminal Server range). The following article explains the difference between the free version and the Workstation in NoMachine 4.
Can you send us the logs? Check the instructions here: https://www.nomachine.com/AR07K00677
If they are not attachable here (because they are too big), send them to issues[at]nomachine.com. Thanks!
NoMachine doesn’t use VNC or Xvnc to share the session. It uses its own system. There is a way to create a NX session as a connection to a remote VNC server, but this is not what you are looking for.
Normally NoMachine remotes the display :0. You can change the display to your Xvnc display as explained in this article (which uses Xfvb as an example) https://www.nomachine.com/AR10K00710.
To set which display will be shared with change the node.cfg key: #DisplayDefault :0It could be the VPN blocking you. Tell your VPN administrator that you need to connect from your machine to port 4000 on the server (your Workstation).
Can you tell us what product you installed? Are you trying to start a session or start the server? When you lauch the application to start a connection, does it open? To check if the server is running, can you see the NoMachine Monitor icon (look for a !M) in the systems tray. For example, see Fig. 2 here: https://www.nomachine.com/how-to-disable-access-to-the-local-desktop.
Look at this post here: https://www.nomachine.com/forums/forums/topic/nxagent-is-listening-on-port-70017002#post-319
Hi ethanee, can you contact us via issues[at]nomachine.com? We’ve fixed this bug and have a webclient binary available for testing.
You need to open port 4000 TCP (or the port you decided to use for the NX service) on your firewall configuration. The ports are added automatically to the firewall configuration on Windows. Not so on Mac and Linux. This is going to change in the future.
Can you send us the logs? Follow the instructions here:
https://www.nomachine.com/AR07K00677
Either attach them here or submit them to issues[at]nomachine.com
@aellus download the latest 4.1. One of the fixes was specifically “Excessive X server CPU load on the client when connected to a server 3”.
The release announcement is here:https://www.nomachine.com/SU02L00100
Slackware is not supported but we will fix it. Check out the TR here: https://www.nomachine.com/TR02L04284