Forum Replies Created
-
Posts
-
Can you check following command
ls -l /dev/drithere should be list of devices, one of them renderD12x will be nvidia (will be renderD129 or some other number)
then run following command
LIBVA_DRIVER_NAME=nvidia vainfo --display drm --device /dev/dri/renderD129In last command we do following:
– we say to vainfo to use nvidia driver with LIBVA_DRIVER_NAME
– we specify that nvidia device should be used by selecting it manually as renderD12x
– the most important part is that it uses DRM, instead of default X11 for display argument – we need to use it that way in our softwarePlease then show us output of the mentioned command.
Hello,
What I see here is the issue with your xorg Display configuration of the headless server, that needs to be adapted to use higher display resolutions.
NoMachine when connecting to the physical screen uses only provided resolution from the system, and as you show on your screenshots that was 1366×768.
If you want that NoMachine set up screen resolution, you could use NoMachine workstation virtual desktops, or ask NoMachine to create physical display for you. More info about mentioned feature can be found here: FR10L02842 – Giving the possibility to connect a physical session in NoMachine free version when the local X server can’t be found.Hello,
Can you tell us if you are using new M1 Mac machine?
Audio does not work on Apple M1 as a server, we have opened new Feature Request to natively support Apple M1, you can see more here: FR12R04054 – Offering NoMachine packages natively built for Apple M1 ChipHappy New Year too,
Can you tell us if you are using single or multiple display?
As well did you experienced something similar with other applications?I tried version 6.12.3, and version 7.7.4 and both work as expected and without issues on Windows 11. This looks as the installation problem happened on specific environment.
Please can you try uninstalling NoMachine and reboot host and report if here are any uninstallation errors. After reboot verify if NoMachine folder still exists “C:\Program Files (x86)\NoMachine”.
If exists rename it and then install NoMachine again. Important is to reboot Windows after installing NoMachine to correctly load needed drivers.If you still experience the problem, after new install, collect NoMachine logs ( DT11R00181 – Collect server and client logs manually ) and attach it to this post, or send to forum[at]nomachine[dot]com.
I tried on Android 11, Samsung Galaxy S10plus and right mouse click works as expected by holding the finger on the screen.
Can you tell os what is the Linux OS and Desktop environment, and as well can you try to change if there is different behavior when you change “Pointer mode”. (see screenshot)Attachments:
Please can you collect NoMachine client logs from server and client side %USERPROFILE%\.nx. You can find more information how to collect them from following article https://knowledgebase.nomachine.com/DT11R00181#2.3.
then please send logs to forum[at]nomachine[dot]com.
Problems does not looks like there is some missconfiguration or missing of some system libraries regarding the va libraries.
Strange thing is that from vainfo we have <unknown profile>.
Please can you check what is installed in relation to libva and va-api. You can do that check by executing:
dpkg -l "libva*"I am not aware about similar problem that affects file transfer.
Please can you tell us:
- What is the server, client OS
- What is the NoMachine version on server, client
- Which selection you are using for transferring files
– Download file from the server
– Upload file from the client- Additionally, can you verify if “Open menu panel” is opening menu on the client
You can do update and install NoMachine following command line process found at link here NoMachine Enterprise Desktop – Installation and Configuration Guide.
You can use SSH keys to authenticate using the NX protocol. More information you can find here: AR02L00785 – How to set up key based authentication with NX protocol.
NoMachine does the NoMachine server out-of-the-box firewall rules and assign them to the Firewall Profile “ALL”. Profile ALL is group of all Networks ( DOMAIN, PRIVATE, PUBLIC ) you can get more information from Microsoft website.
Please send us client and server logs to allow us to fully understand if problem is related to our software or something with your firewall setup.
This problem is definitely something with firewall blocking connection.
1. Can you tell me if you have some antivirus installed that has firewall features.
2. Did you tried to add new rule for port 4000 in the windows firewall?
3. As NoMachine does setup firewall rules during installation, can you remove and install NoMachine software?
4. Please if this recommendation does not help, please collect NoMachine server and client side logs and send them to forum[at]nomachine[dot]com. Please check article how to collect logs How do I collect the NoMachine log files?About documentation, NoMachine is setting firewall configuration during startup, so there is possibility that it is some different problem that I am not having good idea what to guess.
Can you please check IPs and service status on the machine you try to access as server. (selected_IPs.png)
Then go on the client machine and select correct IP that you can access from the client. (Player_edit_cconnection.pngIn anycase, please make single port accept rule for TCP/4000, and assign it to the Private network.
Attachments:
