Forum Replies Created
-
Posts
-
Results of tests show that it would not be powerful enough to run as a NoMachine server. As a client device it could be possible, just, but it’s not a device we would recommend, I’m afraid.
@russellaugust, if you are able to reproduce this issue using the latest 6.11 version, you should provide the output that fra81 requested in his reply. Otherwise, full logs from both sides of client and server would be useful.
There is a Trouble Report for this issue:
Termination of virtual session causes GDM crash
https://www.nomachine.com/TR06R09761Please sign up to receive a notification of when a fix has been released.
Logs received July 7th. Environment details both client (Ubuntu 18.06) and server (Ubuntu 16.04).
But didn’t show enough information. Debug should be enabled on both client and server sides, please see instructions on how to do this. Send them to forum[at]nomachine[dot]com like last time.
The logs didn’t show anything useful. For now please look at this article here:
Troubleshooting the error message ‘Connection refused’
https://www.nomachine.com/AR09O00937and follow the tips outlined there.
There’s also this article if you’re connecting to the server when it’s behind a NAT.
https://www.nomachine.com/AR11L00827There is a bug with user switch on Ubuntu 20-04. It could be this. Please use this link to monitor its status and sign up to receive notification of a fix.
Problems with fast user switch on Ubuntu 20.04
https://www.nomachine.com/TR04R09661Is Windows the operating system on the client you are connecting from? Or is Windows the OS on the machine you are connecting to? Either way, please confirm what the OS is on the device that you didn’t mention. Are you connecting to the physical desktop via the native client, or are using the browser (i.e did you install Enterprise Desktop on the remote computer or the free version?). Confirm also that you are using the latest version of the NoMachine software (both sides).
@rsperson, we got the logs, thank you, but they were no actual error logs. Nevermind. Let’s assume it’s this known problem:
https://www.nomachine.com/TR06R09772
Please try the following known workarounds: either disable hardware decoding on the client (see image here: https://forums.nomachine.com/wp-content/uploads/2019/09/NoMachine-display-menu-panel.png) or try the one in the Trouble Report (server-side).
You mention a “CAD guy”, I assume that’s the administrator in control of the NoMachine server, so I assume that you are not in control of the remote server. If that’s the case and if that Linux server is running a subscription from NoMachine, it’s better if the administrator opens a ticket with the NoMachine support team. He would then be able to follow our instructions.
Have you enabled port-forwarding on the router? See this article for tips:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827This is the same topic as here: https://forums.nomachine.com/topic/error-60-operation-timed-out-2
This is a known issue:
Sessions cannot be started because of error ‘descriptor out of range’
https://www.nomachine.com/TR04R09620Please sign up to receive a notification of the fix when its released.
Please update both client and server to the latest 6.11.2 and let us know if you continue to get the same problem.
It is the display server that uses the GPU. It depends on the configuration of machine and display server. NoMachine does not decide the GPU they use.
Indeed, there is a workaround in the Trouble Report which mentions this:
No sound is coming through NoMachine Audio Adapter, when playing audio inside the NoMachine session. This problem has been reproduced on macOS 10.13, 10.14 and 10.15. This issue is triggered by the fact that NoMachine Audio Adapter is muted. This is not always visible in system sound settings.
Sometimes in the Audio MIDI Setup, volume stream is set to 0 and it’s enough to raise it.
In other cases, volume stream in Audio MIDI Setup seems to be already enabled. As a workaround, go through all volume sliders for Input and Output side and lower volume value to 0.0. Then set it again to 1.0.”
