Forum Replies Created
-
Posts
-
The nxservice.log is missing from the received logs, I’m not sure why.
From the logs you submitted we can see there are some issues with access rights issue related to log dir like:
Cannot change access rights: C:\NoMachine\logs\nxserver.log to Read-Write. Error is 2, No such file or directory.Could it be that you changed the NoMachine log path some time and therefore you don’t have the correct permissions in place?
– Remove old installation of NoMachine
– Reboot Windows
– Install NoMachine again with default install and log location
– Reboot machine@Zhiliang, if you’ve kept your NoMachine software up-to-date using automatic updates or manual installation, you should also be on 5.3.25 on the server. Or, are you referring to the update of your system OS?
Hi, very strange. Let’s start by seeing only the Player logs from the connecting client. Maybe that will shed some light.
NoMachine shortcuts are handled in the Player GUI.
By default it’s set to Ctrl-Alt-T.
You can change this if you prefer a different combination.
See Fig 3 in the document here: https://www.nomachine.com/DT10O00154#2.1 for more details.
hi sledjunk, I’m going to send you a private email with further instructions. The logs you submitted didn’t help us. We would need you to install a debug package and extract the logs again (after you’ve reproduced the problem).
Of course shoe54 🙂 You need to contact our sales team https://www.nomachine.com/contact-request and put in a request for an extension.
Hi, so everything is working fine when connecting from Windows, but not from Mac. From what you copied from the logs it’s not possible to say what the cause is of not being able to reconnect.
Did you follow the instructions for setting up Docker first?
https://www.nomachine.com/DT10O00161If you’re using a subscription of Workstation, have you considered opening a support enquiry in your customer area from where you downloaded the software? They’d also need to see logs.
Are you sure WebRTC is enabled? Without WebRTC there will be no video encoding.
Can you submit here a screenshot of your Display settings? (Connection menu->Display->Display settings)
Hi, the files that you wanted to attach didn’t attach. Are you able to send them to us directly? (to forum[at]nomachine[dot]com)
Did you follow the instructions here: https://www.nomachine.com/accessing-your-remote-linux-desktop-on-amazon-elastic-compute-cloud-via-NoMachine ?
Unfortunately, the log file you sent was empty. Additionally, we need server-side logs (see document I mentioned earlier). The document also explains the steps for getting the client-side logs.
Send directly to forum[at]nomachine[dot]com.
Thanks!
Hi, section 2.3 refers to software encoding which is used when the H.264 software encoder is present on the server. The H.264 codec is not shipped in the evaluation.
Hardware encoding is possible regardless of the NoMachine server you have – the free version, an evaluation even – provided there are the right GPU capabilities in place. From the article:
1. NoMachine and H.264 hardware acceleration
NoMachine supports H.264 hardware acceleration for these types of sessions:
(i) Connections to the remote physical desktop.
(ii) Linux virtual desktops without activating X11 vector graphics mode.1.1. On server side
NoMachine supports H.264 hardware encoding provided by graphics cards with Nvidia Kepler microarchitecture and later.
1.2. On client side
NoMachine software on the user’s computer (i.e. NoMachine used as a client or Enterprise Client) supports the H.264 hardware decoding on Windows and Mac hosts with hardware accelerated video cards (GPUs). No further action is required.
and from https://www.nomachine.com/AR10K00706
In the case of web sessions, H.264 codec is supported from v. 6 provided all the following requirements are met:
(i) H.264 hardware or software encoding is available on the remote host where NoMachine sessions are run.
(ii) The browser supports WebRTC/HTML5 and H.264.
(iii) support for WebRTC is enabled on the NoMachine Server.@marty39, apologies for replying just now. We’re still unable to identify the cause of the issue despite the logs you sent and our several attempts to reproduce. Check your inbox for emails from us.
Hi, we are still unable to reproduce the problem, and the logs you submitted didn’t reveal the reason behind the issue. So, we have to ask you to submit some further information if you’re able to:
– Using Valgrind to detect possible memory leaks in the nxnode program
https://www.nomachine.com/AR09L00809