Forum Replies Created
-
Posts
-
We were not able to reproduce this problem. Could you enable logs on the affected servers, reproduce the problem and then send to us the whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted). We’ll also need the client logs.
Instructions about debug and collecting logs you can find here: https://www.nomachine.com/DT04M00076.See the tutorial here: https://www.nomachine.com/creating-new-virtual-desktop-sessions.
Choose ‘Create a new custom session’ (fig. 6). Also check that you have the right package installed (https://www.nomachine.com/AR10K00724).
It’s a bug. We’ve opened a Trouble Report which you can find here: https://www.nomachine.com/TR05N06873
There’s also a workaround.
Hi, I haven’t forgotten 🙂 It’s actually been fixed and we’ll be sending you all a link to download the package.
Do you mean that before updating the NoMachine software on your client you could see the other computers on your LAN, and now you can’t? In theory, updating the client side shouldn’t affect autodetect of NoMachine servers running in the same LAN.
Have you accidentally changed something in the Player privacy settings? See this: https://www.nomachine.com/DT11M00106#2.5. If the ‘Don’t show other computers on the network’ is checked, you won’t see any available machines. Similarly, if other machines where NoMachine is installed have not checked ‘Advertize on the network’ box (https://www.nomachine.com/DT11M00106#3.1.), you won’t see them when you are on the LAN.
If you are not on your company’s LAN, your Player won’t be able to find the machines that are available. Is it possible that you have moved off the company’s network?
We’re not able to reproduce this. Can you send us those logs (forum[at]nomachine[dot]com)? We tried on 1 core with 1 GB RAM and everything was ok. This is the lowest parameters that can be set for this image, I think. What did you use? Also tell us the steps you executed to install Gnome.
We’ve not been able to reproduce this problem. We’ll keep trying to see if we can trigger it. In the meantime, can you send us the logs once you’ve reproduced the problem? Check the following article and send to forum[at]nomachine[dot]com, https://www.nomachine.com/DT04M00076.
Resolutions greater than 1929×1080 were disabled because on some cards we observed graphical artifacts. On the client side you are using Windows, so what you can do is install the FFMPEG libraries. The relevant article for how to set up the client with H.264 decoding libraries is here: https://www.nomachine.com/AR10K00696. Let us know how you get on.
This issue seems to be the same as one already reported: https://www.nomachine.com/forums/topic/clean-install-service-doesnt-start-win-10
Newly created nxserver processes can’t load all necessary dependencies. This can be verified using Process Monitor.
Follow these instructions:
1. Download and install Process Monitor from this site:
https://technet.microsoft.com/pl-pl/sysinternals/processmonitor2. Shut down or kill all NoMachine processes.
3. Run Process Monitor as Administrator.
4. In Process Monitor Filter window:
– Expand ‘Column’ drop down list (default value is ‘Architecture’), change the value to ‘Command Line’.
– Expand ‘Relation’ drop down list (default value ‘is’), change the value to ‘contains’.
– Type ‘daemon’ in the ‘Value’ field.
– Set ‘Action’ field to ‘Include’.
This should create rule: ‘Command Line contains daemon than Include’.– Click on ‘Add’, ‘Apply’ and ‘Ok’.
5. In top bar of Process Monitor check ‘Show Registry Activity’, ‘Show File System Activity’, ‘Show Network Activity’,
‘Show Process and Thread Activity’ and ‘Show Profiling Events’ icons.6. Run ‘nxserver –startup’ from command line.
7. After 30 seconds click on ‘Save’ icon in Process Monitor top bar.
Save file using ‘Native Process Monitor Format’. Send us produced event file (to forum[at]nomachine[dot]comThis was the TR in association to this topic. A patch was released in 5.1.22. https://www.nomachine.com/TR04N06711