Forum Replies Created
-
Posts
-
Hi, when you uninstalled NoMachine (free version), did you also remove the directory /usr/NX before installing the Workstation? It looks like the previous license is interfering with the Workstation installation.
Can you tell us what Linux distribution and version you are using on the server side. What OS on the client side? Steps to reproduce.
Hi treevine,
For us to provide you with some guidance, can you provide more information? Check the list “What to include” just below 😉
Hi, version 4.1 will provide a check box “Don’t show this message again” or similar. That way, you will be able to hide it.
Can you send us the server logs from the Window host, too? These client logs are reporting a problem on the server, so we would need to see those. Enable logs on the server side, reproduce the problem and then send them on as you did before.
I am just updating this so the thread is not lost. We received the logs, but it would be useful to look at the .nx directory from the user’s home on the server side.
That’s correct. The Workstation and all the Terminal Server versions work as terminal servers, by creating sessions running in the background. These are terminal servers, intended for the enterprise market. The free 3 worked as a terminal server limited to 2 users. This functionality (virtual desktop) is no longer available in the free version. SSH support which was previously available in the free 3 is now available in the enterprise market-oriented products. If you want to replace NX Free Edition with version 4, the Workstation is what you need.
The logs show there was a problem with display driver initialization. You could try disabling the driver:
– Run devmgmt from Windows command prompt
– Find the device “NoMachine Display Adapter” and disable it.I can’t connect to my Mac using my PC, the message was connection timed out.
This is very likely a firewall problem. Try disabling the firewall or check that the firewall is not blocking port 4000 (this is the default port used by NoMachine).
Every time I connect to the PC, “The connection with the server was lost. Error is 54: connection reset by peer” pops up.
Logs would be useful for the problem connecting from Mac to Windows. We would need sets from both sides, so client logs from the Mac machine and server logs from the Windows PC. You can submit them here or send them to issues using the title of your topic.
Instructions on how to gather logs are available here: https://www.nomachine.com/AR10K00697.
Thanks for bringing it to the forums 😉 As well as the forums, you can search for known bugs here: https://www.nomachine.com/troublereports. From there you can also look for other topics within the knowledge base.
Britgirl
Check this article here: What does “The NoMachine service is not available” mean in version 4?
Hi! If you want to transfer a file from the local machine to the remote machine, go to the monitor (black and white !M icon) and click ‘Upload a file to the server’. If you want to do it the other way round, go the monitor on the remote desktop and select ‘Send a file to a client’.
Let us know if you continue to have issues.
Hi,
When creating a new virtual desktop on the server host, the NoMachine server starts the default desktop as set on the system.
If you want to run a different window manager/DE, you can choose to run a custom session (click the link ‘New virtual desktop or custom session’) and specifying the WM to run in ‘Run the following command’ in the successive panel.
Alternatively, you can set it on the server by editing the configuration files. The following articles provide more information about this:
Desktops environments supported by NoMachine 4 – http://www.nomachine.com/AR10K00725
How to run a desktop environment on Linux different from the default one with NoMachine 4 – https://www.nomachine.com/AR04K00667
Hi, we will need some more information from you:
1) Distribution and version of the Linux system that you are using and whether it’s 32 or 64-bit.
2) Enable debug logs in /usr/NX/etc/node.cfg, restart the server, start the session and reproduce the issue, then send us /usr/NX/var/log/nxserver.log
3) After reproducing the problem (and while having session running) run the command:
‘ls -al /usr/NX/var/log/nxnode/C-(…)/audio’ where C-(…) is the current session’s log folder and tell us the output.