Forum Replies Created
-
Posts
-
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/AR09L00809Hi, this would appear to be a problem with Firefox profiles. More information about that is on their website. You mentioned a “virtual display”. Firefox will use the same profile for both the original OS and the virtual one that’s running. I think this could well be the issue.
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Have you tried with another browser, for example Safari?
Did NoMachine give any error messages at all?
The related Trouble Report for this topic is https://www.nomachine.com/TR03P08450.
Please sign up to receive a notification of the patch when it becomes available. Thanks!
From the logs we can see it was a network issue.
When the NoMachine (server) computer is behind a NAT router or a firewall, NoMachine tries to use the UPnP or NAT-PMP protocol (depending on what is supported by the router) to:
– Retrieve the public or external IP of the host machine where it’s installed.
– Configure the router to allow a NoMachine client to connect from outside of the private network.
Further reading:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827So, we’ll need the logs 🙂 because we’re unable to reproduce this behaviour. Server-side logs can be extracted using the instructions here: https://www.nomachine.com/DT10O001630.
For client-side logs it’s enough to tick the box “Don’t delete log files on exit”. Send what you have to forum[at]nomachine[dot]com making sure to reference your topic.
Statistics would be very useful: https://www.nomachine.com/DT10O00157&dn=menu%20panel#9. Run the session, open the menu, click Connection and click “Take the statistics”.
Thanks 🙂