Forum Replies Created
-
Posts
-
We do not have this particular model in our labs. Please update to 8.8 on both client and server so that we can investigate further. It would be helpful if you send us the logs from an affected session. Please take a look at the following document for instructions on how to gather logs for Player and Server sides. Then submit them via email to forum[at]nomachine[dot]com.
We didn’t receive the logs. Please update to the latest version (both sides) and let us know if you can reproduce the same issue by opening a new topic and providing steps to reproduce, along with logs.
Hi Tomas,
Update to the latest 8.8 and tell us if there is any improvement because some fixes have been applied to keyboard in general. Is the result the same as before?
Hardening nxhtd should follow same rules of hardening Apache. The NoMachine web server, nxhtd, is a minimal version of Apache web server currently based on httpd-2.4.56 (NoMachine v8.5 or later). The nxhtd web server has some built-in modules already preconfigured necessary for the functioning of the Web Player application. Most common configurations suitable for Apache should work also with nxhtd.
Can you print from Windows outside NoMachine sessions? If not, you probably turned off the print spooler service.
If you can print outside the NoMachine session, please submit the Player logs (see the following document on how to extract them: https://kb.nomachine.com/DT07S00243 (section Fourth Step: Collect Client Side Logs) Attach here in the topic or submit directly to forum[at]nomachine[dot]com.
Also, please state the version of NoMachine you are using on the Windows client.
What you can look for in the logs is this indicator:
ERROR! Bitrate is equal or below 0.
VCE: WARNING! Failed to set parameters.instead of these:
VCE: WARNING! Failed to init device.
VCE: WARNING! Failed to create encoder.Just a note about VP8 decoding/encoding.
Prior to the more recent update (8.7.1 for Android/iOS) the NoMachine app for iOS and Android used VP8 as the default decoding method. With 8.7.1 it is now H.264 on mobile as well(see here for more details https://kb.nomachine.com/SU07U00248).
As for the HW encoding on the Ubuntu side, there is a bit of a mess with the drivers you have installed. Is it possible for you to revert back to the drivers version you had around June 23, because logs indicate that was the time when the encoder went through initial stages of initialization (so drivers were not actually failing). Then, on the server side, in the node.cfg file set the EncoderMode key to ‘bitrate’. Then try connecting.
We’ve now opened a Trouble Report for this issue. You can monitor its status here: https://kb.nomachine.com/TR08U10980
Hi, you can try disabling UDP as a workaround:
– go the Player -> Machines panel
– enter ‘edit’ of the connection
– go to the Configuration panel
– Uncheck option ‘Use UDP communication for multimedia data’Does this help?
This is fixed in version 8.8, https://kb.nomachine.com/SU07U00247.
TR07U10939 – Sudden termination of Xorg after certain events sequence
Link to TR: https://kb.nomachine.com/TR07U10939
We’re working on supporting Wayland, natively without XWayland, but it’s not a priority at the moment, so don’t expect this very soon. By the way, the client runs on top of X, and as such it needs the compositor to support the keyboard grabbing on top of XWayland in order to work correctly. If this is not the case, then our keyboard grabbing can’t work.
NoMachine is designed to work out-of-the-box on Linux headless machines. It can detect when the X server is not running and so runs its own virtual display.
This is duplicate of https://forum.nomachine.com/topic/windows-10-client-to-linux-nx-server-no-printers-2.
If I understand correctly, what you need to do is set the “lock the physical screen on disconnect”. This is useful in conjunction with screen-blanking.
When the screen blanking feature is activated, the remote screen is blanked, and the remote keyboard and mouse are locked whilst the user is connected by NoMachine. I.e. operations made on the physical screen by the NoMachine user are not shown and the local user cannot interact with the desktop until the NoMachine user logs-out.
As soon as the session is disconnected, the remote screen is unblanked, mouse and keyboard are released. To avoid this, it’s possible to activate the automatic lock of the screen, even if the user didn’t lock the screen before disconnecting by NoMachine.
See here more details:
https://www.nomachine.com/protecting-the-host-screen-during-a-remote-control-session
and
How to enable screen blanking and the automatic lock of the screen
https://kb.nomachine.com/AR07M00851