Forum Replies Created
-
Posts
-
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.
The logs don’t seem to contain any problem related to starting virtual sessions. Can you make sure you follow the steps here: https://www.nomachine.com/AR07K00677 in the section dedicated to Linux.
You will need to:
1) Set log level to debug as per instructions
2) Reproduce the problem.
3) Create a compressed archive of the NoMachine /var/log directory.
4) Send the archive to NoMachine Support Team by e-mail .
Don’t forget to include the client side logs as well. The userhome/.xsession-errors file will be useful to. Send everything to issues[at]nomachine.com.Hi snejok, from this post:
Under “more quality of image” I mean fonts blurring (https://www.nomachine.com/forums/forums/topic/blurry-fonts-with-latest-nomachine-viewer)
you will see that we are working on improving text rendering.
option key=”Link speed” value=”wan” is a legacy setting and only takes effect when connecting to a 3.5 server. If you are connecting to a server 4, the setting option key=”Link quality” value=”7″ is used. Changing it to 9 (this corresponds to the slider being on the far right in Display settings) will give better image quality, but will also require more bandwidth.
As Fra81 explained in his reply to the topic quoted above,
“The slider can be changed according to the quality of image that you prefer. By default it is set in the middle. Moving it to the right edge will activate lossless encoding. This should make fonts sharper….Additionally, you can also check the box ‘Disable multi pass encoding’ to avoid progressive refinement of the screen image. Disabling this refinement sends the image directly with the target quality (set in the slider).”
We haven’t been able to reproduce this error. Are you able to send us logs?
https://www.nomachine.com/AR07K00677
You attach them here, or send them to issues[at]nomachine.com making sure you include your topic title in the subject.
Did you try to change the port in the panel I have attached here?
Attachments:
