fra81

[fra81]

We did not reproduce this issue in our labs on Ubuntu 12.04 with MATE. Can you tell us your exact Ubuntu version?

Please also send us the output of the ‘xinput’ command run on the server machine.

[fra81]

Hi TeutonJon,

we reproduced this issue in our lab and opened a Trouble Report: https://www.nomachine.com/TR10M06072.

Thank you for reporting!

[fra81]

Hi Lantizia,

thank you for this report, we are going to check it in the same environment. The expected behaviour is that user input is blocked. This is certainly a bug, since the tens of Linux distributions we tested it on don’t have this problem.

[fra81]

Hi Hoijima,

your problem is known and will be fixed in the next update. Here is the related Trouble Report: https://www.nomachine.com/TR08M05893. Please check the suggested workaround.

[fra81]

Please provide more info on your environment:

– NoMachine product and version on local and remote machine (free version, Workstation, etc).

– Whether the problem arises connecting to a physical or a virtual display, or to a custom session.

– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).

[fra81]

Hi iceback,

don’t forget that what you have in upload also matters. I would check the real bandwidth on both directions. Most important is the direction where graphical output flows.

[fra81]

Scaling the display to fit your window is already possible in version 4. Please open the menu panel and find the ‘Fit to window’ icon in the Display settings. That is also available in the quick action icons at the bottom of the menu panel.

[fra81]

Hi tangbotu,

you can select “Resize remote screen” in the Display settings to make the remote display automatically resize to the resolution that fits better in your player window. Please note that the only available resolutions in physical desktop sessions are the ones supported by the remote configuration (i.e. the ones that you can select from the system settings of the remote desktop environment).

[fra81]

Can you send us the server side logs after enabling the debug level, as explained in https://www.nomachine.com/DT04M00076? You can send them to forum[at]nomachine[dot]com.

Additionally, please try to edit the connection in order to connect with SSH protocol (instead of default NX) and “System login” (Advanced tab).

[fra81]

Hi Mule52,

supported resolutions don’t depend on the NoMachine software, but on what is supported on the remote system. In other words, the 2560×1440 screen resolution will be available in your NoMachine session only if such resolution is selectable in the system settings of your remote Mac.

If that resolution is among the available ones on your Mac, then you may simply need to click on the “Resize remote screen” button (the one on the right of “Fit to window”). That will make the remote screen automatically resize to the resolution that will fit better in your local screen.

[fra81]

Hi ilker,

you may need to run a virtual session on your linux laptop, so that the physical desktop will not be affected by what you run remotely. Virtual sessions are supported by the NoMachine Workstation product. You can find the evaluation version here: https://www.nomachine.com/download-enterprise.

Alternatively, you can try the instructions of this article: https://www.nomachine.com/AR10K00710. There is explained how to manually setup a virtual X server.

[fra81]

Regarding the HTTP proxy, the typical usage in on the client side. For example, direct connections to the internet are not allowed at your workplace, so you need to configure a HTTP proxy for connecting from workplace to home.

More in this article:

https://www.nomachine.com/AR04E00457

[fra81]

Hi yaris,

I still think you are facing the same bug of the other post. This crash occurs when the UDP negotiation fails, whatever the reason that makes it fail. The correct behaviour would be to fallback to TCP silently.

A fix to that TR will be released very soon in the next update.

[fra81]

Hi cameron,

here are two possible issues. The first one is about the failure in establishing a connection and it seems the same issue tracked here: https://www.nomachine.com/TR08M05855. The normal behaviour would be that the connection falls back to using TCP seamlessly.

The second possible issue is about UDP being not functional with the firewall enabled, regardless the exception rule. We will do more tests in our labs with the same environment. Thanks for reporting!

[fra81]

Hi smartin,

the problem was known and a fix will be released with the next update.

Here you can track the issue:

https://www.nomachine.com/TR08M05883

[Author]

Posts