Tor

[Tor]

Hi. Swipe left the server item, tap the Edit icon, verify that in the Host field the selected address is the correct one. If you’re not sure, try all addresses you see in the list.

[Tor]

Hi! Old servers discovered in LAN could stay in the cache for a few hours before being completely removed, so just wait a little bit. If instead you created a connection to that server, you can right click the item in list and select “Remove connection”.

[Tor]

Hi. Can you please verify that the resolution you want to use on the remote desktop (Linux and Windows) is listed among resolutions supported in display settings?

[Tor]

Hey Finnish, welcome back. 🙂 I see you’ve the ‘Resize remote screen’ option enabled, which overwrites the size requested by custom resolution setting. Try to disable it and let me know if the resolution is correct.

[Tor]

Hi. The Ctrl + Alt + Backspace is a quite “destructive” command, so I think we could find a way to solve your problem without adding the shortcut to the UI. 😀
I’d propose to remap the standard shortcut with something different, like Ctrl + Alt + End, which can be used on client without risking to kill the wrong X server.
You would need a procedure like this:

– Create the folder where to store a new XKB map entry:

mkdir -p ~/.xkb/symbols/

– In that directory create a file called local and edit it by adding the following configuration:

default partial modifier_keys
xkb_symbols "ctrl_alt_end" {
    key <END> {
        type="CTRL+ALT",
        symbols[Group1] = [ NoSymbol, NoSymbol, NoSymbol, NoSymbol, Terminate_Server ]
    };
};

– Run the following command:

setxkbmap -print | sed -e '/xkb_symbols/s/"[[:space:]]/+local(ctrl_alt_end)&/' | xkbcomp -I${HOME}/.xkb - $DISPLAY

– Press Ctrl + Alt + End to kill your X server 🙂

You can add the setxkbmap command to a script, and execute it automatically when the session starts, for example through a .desktop file in ~/.config/autostart.

[Tor]

Hi. We could not reproduce such behaviour, could you kindly answer some questions so we can investigate it?

– What is the NoMachine version installed on server side?
– What is the Android device model?
– Are you starting the connection through a LAN discovered server item, or by using a manual connection (configured with the wizard)?
– What is the reason why the server goes offline sometimes? For example is the server switched off, or is the device changing the subnet?

Please note that for the way the LAN discovery works the client could require some time to receive the information about the server, even if it should never take more than one minute or so.

[Tor]

Hi. The servers discovered in LAN are not visible in the list of connections when they’re not available: starting that connection would fail because the host doesn’t exist or the same IP could be used by a host in a different LAN.
You can create a static connection to that server by starting the wizard with the ‘New’ button, then use the server IP (you can read it by editing the LAN discovered server item) to complete the creation.

[Tor]

Switching to VP8 would not help because, as I said, the H.264 codec is only one of the reasons why there is a limit. We’ll release shortly (couple of weeks) the version with the improvement I’ve explained.

[Tor]

Hi.
The maximum resolution is limited for a bunch of reasons (e.g. H.264 has a maximum frame size), but we’ve implemented some improvements allowing us to be more complaisant. 🙂 Thanks to this, in our testing version we’ve doubled the maximum resolution.
The change is documented here so you can subscribe to be informed when it’ll be released:

https://www.nomachine.com/FR09Q03868

If you’re connected to a virtual desktop and if your client supports a resolution width bigger than 4096 you can enable the remote resize (from Display toolbar) and increase the window size up to the resolution you need. The client will try to reach that resolution to work around the custom resolution size constraints.

[Tor]

We’ve worked on a solution like this years ago, but during our testing the experience with some games was not very friendly because the mouse pointer was released in the worst moments! 🙂 Even after some tweaking we never reached a perfect solution covering all test cases, so in the end we gave up. Since you’ve shown some interest we could eventually include this pointer release mode through a configurable option. I’ll discuss it with UI designers.
Thank you for your feedback. 🙂

[Tor]

Thank you for your feedback, I’ll make sure we track it and find a way to inform how the mouse pointer grabbing works.

[Tor]

I don’t have a timeframe for the release, but it is something we really want to include so I’m quite confident we can start working on it immediately after releasing the next big version (which is pretty close).

[Tor]

Hi.
Did you consider toggling keyboard grabbing with Ctrl + Alt + K (default) and keeping always on the pointer grabbing (Ctrl + Alt + Left click to release it)?

[Tor]

Hi. We’ve no such feature at the moment, but we plan to implement something that can help you:

https://www.nomachine.com/FR10N03220

You would place the window showing monitor <4> on monitor <2>, etc.

[Tor]

Hi. Please tap&hold the NoMachine application icon, select the ‘App info’ item (or do the same by going through Settings), select Permissions settings and verify that “Storage” permissions are granted.

[Author]

Posts