Forum Replies Created
-
Posts
-
Hi, can you try disabling hardware decoding on the client machine that you are connecting from? See the article for further instructions making sure to set the appropriate key to “disabled”.
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Can you send us the client side logs (the device that you are connecting from)? Please take a look at step 4 in the instructions here, https://kb.nomachine.com/DT07S00243. We don’t need server side logs for the moment.
Hi,
We have planned to add an option to capture the screen of the server at native pixel resolution on High-DPI displays as well as make the NoMachine User Interface “DPI Aware”.
You don’t mention what OS you are using butif you are using Windows, a possible workaround is to
– Right-click the NoMachine app shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”Hi, changing a label in your Machines panel, changes the name for you, not other users. With MDNS connections, NoMachine broadcasts the presence of the machine and uses the name set on the system. This type of connection (MDNS) works differently to a traditional connection which has its own connection file. If you want others to see the new name, you could change the hostname in the machine’s system configuration. Alternatively, you could create a connection file and distribute that to all your users and they will then also know the new name.
Hi, can you try disabling hardware decoding on the client machine that you are connecting from? See the article for further instructions making sure to set the appropriate key to “disabled”.
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Documentation is current but we will certainly check again to make sure everything is up-to-date. About the limitation, I believe I already pointed you to a Trouble Report which explains that there is bug preventing web sessions from using 4096-bit keys for authentication. Here is the link again: https://kb.nomachine.com/TR08Q09394. Developers are currently working on a possible fix.
Can you send us the first and last 1000 lines of the big files?
On Windows you can use Powershell e.g
Get-Content -Path <path to big file> -TotalCount 1000 | Set-Content -Path head.txt Get-Content -Path <path to big file> -Tail 1000 | Set-Content -Path tail.txtbut you may have your own graphical tools to do that. Send everthing to forum[at]nomachine[dot]com. Thanks.
what’s the output of
uname -mon your Red Hat host?You are installing a 32-bit package. Is your architecture 32-bit or 64-bit? Whilst it’s possible to install 32-bit on a 64-bit host, you must have the appropriate 32-bit libs installed as well. If you don’t, you need to use the 64-bit packages.
Hi, NoMachine is designed to work out of the box with all Mac configurations. It’s not necessary to configure the Mac in any particular way.
Ok thanks for letting us know. We’ll keep this topic open in case you have more questions about your NoMachine and your DUO configuration.
Thanks for the update. Let us know here if you encounter the issue again. This topic will be kept open for a few weeks.
Thanks for the screenshots and additional info. We’ll come back to you once we have some news about our investigation.
This page for “NoMachine 8” (2022-12-28)
How To Use Different Keys Or Certificates With NoMachine
https://kb.nomachine.com/DT07S00229Indeed you should be referring to version 8 software documentation and not version 7. The link has been removed from the v7 document since, as you noticed, the NoMachine development roadmap is no longer in the public domain.
As for the feature request, work has already started.