Forum Replies Created
-
Posts
-
The logs showed that there is no FullHD in use, but 3840×1080 (so height is 1080 but the width is 1920*2) hence why SW encoding is being used given that for resolutions higher than 4K, hardware encoding is disabled. Work has already started to remove this limitation.
Hi, this is the expected behaviour. It is the new default behaviour, introduced in 9.1.24, by which scaling mode preserves the aspect ratio during resize operations when scale-to-window is enabled. What you can do is hold Ctrl while maximizing the player window to get the old behaviour (for more details, refer to: https://www.nomachine.com/AR07W01315).
We were able to reproduce this and opened a Trouble Report, here’s the link you can use to monitor its status: https://kb.nomachine.com/TR10W11586.
If you can, it would be better to enable debug, restart, reproduce (so check that the nxnode is not running) and retake the logs (if you do it from Server settings > Security , Take logs), it will make sure we receive everything we need from the server side. Thanks!
You can modify the shortcut starting the Player by adding the option
--exit-alwaysto the command line. However, when doing so, the Player can still try to reconnect to the server if there is an unexpected error. If you want to avoid it by just terminating the Player as soon as any errors occur, change the key “Automatically reconnect to the server” to false in the file %USERPROFILE%\.nx\config\player.cfg.You can modify the shortcut starting the Player by adding the option
--exit-alwaysto the command line. However, when doing so, the Player can still try to reconnect to the server if there is an unexpected error. If you want to avoid it by just terminating the Player as soon as any errors occur, change the key “Automatically reconnect to the server” to false in the file %USERPROFILE%\.nx\config\player.cfgHi. Can you please save the logs from Player Settings > Security of that computer and send them? Also, what antivirus software are you using?
A zip file is recommended for attachments. Alternatively, you can email them to us at forum[at]nomachine[at]com. Thanks.
Thanks for all your input and collaboration. We have now inserted a Trouble Report which you can monitor at the following link: https://kb.nomachine.com/TR11W11634.
“Should I update to 9.2.18 and look at the server.cfg ?” If you can, yes.
We would also needs logs from both of you before you go back to the previous version (our Info team is already handling the temporary download link). This would help us immensely because we are unable to reproduce the issue. Are you able to send us the server-side logs so we can check them, enabling debug first? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. It can be done directly from the UI in Settings > Server > Security, scrolling down, setting debug level, restarting, wait a few minutes, then Take logs.
Send them to forum[at]nomachine[dot]com or attach. Please use the title of this topic as the subject of your email. Thanks to both of you!
We always publish the latest version of the software on our public download servers, and we do this for a reason which is explained here https://kb.nomachine.com/AR08C00250.
We can of course provide you with a temporary link to the earlier version that works if you contact us through the website. First, we need to understand why both of you are encountering this issue.
Camero1579, I assume that you are also using Linux? If so, can you tell us the distro and desktop environment? Please locate the server.cfg on your server machine, and tell us what is written in the following key AvailableSessionTypes.
Pavlos, if you have a chance to do the same (so you would need to update to 9.2 again), the question also applies to you as well 🙂
Hi, NoMachine balloon notification cannot be disabled. Take a look at the following article:
Is it possible to disable NoMachine balloon notifications?
https://kb.nomachine.com/AR07W01313The error message is printed when the POSIX error is a timeout. The reason why the error is received could be wrong, but our tests on the fly didn’t reproduce a similar issue. Can you send us the logs from both client and server machines? You can extract them from the UI using the instructions here: https://kb.nomachine.com/DT08U00298
Send them to forum[at]nomachine[dot]com or attach them here. Please use the title of this topic as the subject of your email. Thanks!