Forum Replies Created
-
Posts
-
Make sure you download the latest release 6.3.6. It contains the patch for this bug.
This is a limitation in Gnome. Please see here for more details: https://www.nomachine.com/TR10N07312
The main scope of NoMachine software is to provide access to the remote desktop (virtual or physical) and all the functionality associated with it (including attached devices, not just the apps/software running there), whether that’s your own personal computer/laptop, or a machine made available to you somewhere on the network; so you can work anywhere, access all your content from anywhere, and leave your machine and what’s on it where it is.
Having a NoMachine server for Android could be a possibility to allow customers to receive remote assistance on their device, for example, but that use case represents a very small percentage of our customers. It’s something we can possibly evaluate in the future.
Did you try to use a different resolution instead of the one of the client? To do so, disable the option “Match the client resolution upon connecting” and select a different geometry from the list available in the Display settings panel.
By enabling the “Fit to window” option it should be possible to achieve a better balance between server and client scaling, offering the desired look.
Further references:
https://www.nomachine.com/changing-how-you-view-the-remote-host
https://www.nomachine.com/DT10O00156#5What message are you seeing when you try to install?
We received the logs you included but they only include the nxdevice.log. We need to see ‘Setup Log’ from the installation which should be in C:\Users\<username>\AppData\Local\Temp\
It’ll have a name similar to ‘Setup Log 2018-01-04 #001.txt’. Send us the newest file. Attach it here or send to forum[at]nomachine[dot]com.
Right now it isn’t possible, but we have opened the following Feature Request which you can follow.
The logs didn’t attach, please follow Bro’s instructions above.
Send to forum[at]nomachine[dot]com the TAR.GZ archive.
There’s a Trouble Report open for this bug, https://www.nomachine.com/TR07P08710, and its fix will be available in the next release which is planned for this week. Keep your eyes on our news channel or sign up to receive notification of the patch with the ‘notify me’ utility you can see on the web page of the TR.
A temporary workaround we found was to download the krb5-workstation package from:
Version : 1.15.2
Release : 9.fc27to:
Version : 1.15.2
Release : 2.fc27Thanks for reporting. A Trouble Report has been opened which you can track here: https://www.nomachine.com/TR10P08910. Feel free to sign up to receiving an alert when a patch has been released with the ‘notify me’ service.
Here is the Trouble Report for this issue:
https://www.nomachine.com/TR07P08737
Please sign up to receive a notification of when the patch has been released using ‘notify me’.
Here is the Trouble Report for this issue:
https://www.nomachine.com/TR07P08737
Please sign up to receive a notification of when the patch has been released using ‘notify me’.
OK. If it happens again, try and get the information we asked for we so we can investigate thoroughly.