Forum Replies Created
-
Posts
-
Logs received.
What desktop environment are you connecting to by the way?
There’s not enough information in the logs to know what is going wrong. You would need to enable debug on the server side, reproduce and resubmit the logs. Make sure the player logs are included from the client side.
What version do you have installed, the latest one? What steps did you follow to disable and switch off the nxserver? Did you try with
nxserver --shutdownrun from a CMD console?Complete instructions on how to switch of NoMachine server and services are available on our website. Did you follow these instructions?
How to shutdown NoMachine and disable the automatic startup at boot time
https://www.nomachine.com/AR11P01005or perhaps these here?
Disabling the automatic start-up of NoMachine at boot time
https://www.nomachine.com/AR04L00800We tested on the fly just to be extra sure that there was no weird behaviour. Everything works correctly.
Can you send us the logs from both the connecting Windows client and remote Linux server? So there will be two separate sets.
Please see here for instructions on how to extract logs (once you’ve reproduced the problem) and send them to forum[at]nomachine[dot]com.Have I understood correctly that you connected from a Linux laptop as well and connected successfully?
Is the tablet on the same network as the Linux laptop and Linux server?
If you have full logs from the affected Windows host, you can attach them here or send them directly to forum[at]nomachine[dot]com making sure to include the title of your topic in the subject. Thanks!
We actually updated that Feature Request recently to fit in with our current development roadmap because we recently changed the priority on it. It’s definitely in our plans to do 😉
Hi, thanks for reporting. We checked the Win10_2004 update just to make sure. Everything was working correctly. If you can reproduce the problem again, next time, send us the logs from the affected machine 🙂
Have you tried disabling hardware decoding altogether on the Windows client?
See here where to do it: https://forums.nomachine.com/wp-content/uploads/2019/09/NoMachine-display-menu-panel.png
If that doesn’t help, please send us the logs of the affected Windows computer. You can attach them here or send them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in your email.
How to collect NoMachine logs – https://www.nomachine.com/AR10K00697
Logs show the following:
Cannot get information for group id '23636965' Warning: Could not open for writing settings file '/Users/davidn/.nx/config/player.cfg'.– What is group 23636965?
– Check your access rights to server side folder .nx/config and file player.cfgIf you’re sure it’s not a case of wrong username and password, then we need to see the .nx folder of computer you are trying to change preferences of. You can find it in the user’s home (under /User/username) . Attach it here or send it to forum[at]nomachine[dot]com making sure you include the title of your topic in the subject.
We checked on the fly if there were issues with Tumbleweed and weren’t able to reproduce your issue.
Are you clicking ‘yes’ or ‘no’ when being prompted to create a new display? Did you change anything in the server.cfg?
Take a look at the tips here: https://forums.nomachine.com/topic/unable-to-make-the-local-display-available-or-access-to-the-local-display-is-disabled.
– What distro is on the server?
– What NoMachine version and official products did you download from our website? If this is the free version – are you sure that X server is started there?
– What is the desktop environment installed there? You can check by executing in a terminal:sudo grep DefaultDesktopCommand /usr/NX/etc/node.cfgThe port we use by default is 4000. Who could have changed it to 3389? Where is the host that you are connecting to? Is it under your control?
The problematic part at this point is between the Intel driver and libva – which we can’t do much about it, because it’s not a part of NoMachine. We can only provide instructions on how to make it work. Even wth NoMachine OUT of the picture, it’s a struggle in general to make Quicksync work on Linux.
1. Installed intel media driver as mentioned in https://www.nomachine.com/AR09O00938 ( except kernel changes )
Kernel changes are fundamental to make it work. The steps we’ve got in article are from Intel itself, so there’s a reason they included changes to the kernel to make it work.
When connecting to the laptop, you are attaching to its physical display, so on the client you can only see the monitors that are physically available on the server.
