Forum Replies Created
-
Posts
-
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.Hi chengas123, looks like this problem here: https://www.nomachine.com/TR12K04107.
You can sign up to receive notification when the fix has been officially released.
We can post it here 😉 this time, but don’t be afraid to open a new thread for a new topic. Looks like a bug and we’ll look into it. Thanks for reporting.
Hello BitCoin,
The colors selected at the moment in the GUI are the fruit of a lot of tinkering and I don’t think our designers would accept a similar change lightheartedly 🙁 We actually have a plan to make the GUI customizable. The colors chosen are just RGB values and reading them from a file is trivial. Unfortunately there is no code yet. I created a Feature Request for this so you can track its status (receive notifications for any FR we implement by submitting a valid email address).
https://www.nomachine.com/FR01L02802
And for any other questions or nice things to say, you’re in the right place 😉
Brice, if you are using a client 4 to connect to your new server 4 you need to make sure that connect using the ‘NX’ protocol. It appears that you are trying to connect via SSH and the free NoMachine for Linux does not support SSH connections. Steps on how to do this are here: https://www.nomachine.com/AR12K00759.
I suspect that on your Linux client machine you are using a configuration file (nxplayer.cfg) created on Windows. Could that be possible? If this is the case, the nxplayer.cfg file on your Linux host will have the SSH Client key set to nxssh.exe:
You can check whether this is the case by:
$ cat nxplayer.cfg | grep nxssh
If you get:
<option key=”SSH Client” value=”nxssh.exe” />change it to:
<option key=”SSH Client” value=”nxssh” />The free NoMachine for Linux does not include the virtual desktop functionality. With the free version you connect to the physical desktop of the remote host. If you want to connect to multiple desktops on the Linux host, you will need any of the terminal server products from the Enterprise range.
You can find related posts here:Can you tell us what ARM variation you are using? It might be that it’s among the popular ones that we build for testing.
Hi Ricardo,
Firstly, you should check the following article: https://www.nomachine.com/AR11K00751 which explains why this message “The NoMachine service is not available on host…” appears and what you can do. Seeing that you are using an old version of NX, you could try this article here:
http://https://www.nomachine.com/AR04J00627
Secondly, it would be better if you used official packages from NoMachine on your server 🙂 To run a virtual desktop you could install the Workstation product. Unfortunately, we aren’t responsible for the FreeNX packages you are using.
Hi,
there are two options for users of the earlier NX 3.5.0 client package. You can install the free NoMachine package (which functions as both a server and a client) or you can use the Enterprise Client as you did 🙂 This is also free.
The reason you are getting a “an evaluation expired” message is probably due to a previous package (e.g. the Workstation perhaps?) that you had installed on your remote machine. I suggest uninstalling the nomachine-4.0.369-1.x86_64 package from your server host, removing the directory and reinstalling.