Tor

[Tor]

Hi.
At the moment the client doesn’t offer a way to swap Control and Command, but we’ve a feature in our roadmap which will allow to do it. I’ve documented it publicly so you can subscribe to be notified when we’ll implement it:

https://www.nomachine.com/FR03N03087

In the meanwhile you could remap modifiers by using OS X preferences (Keyboard, Modifier keys), or use a third party application like Karabiner and change modifiers mapping specifically for NoMachine client.

[Tor]

Hi Rob.
We’re not aware of such problem and we were not able to reproduce it. In order to go on with the investigation and to open a Trouble Report, could you kindly answer with information suggested by the “What to include” box (below in this page)?

I’ve also other questions:
– The freeze occurs with any kind of files and sizes?
– Can you check if drag&drop file transfer works correctly?
– Does client side OS reports the NoMachine client as not responding, or you can interact with it normally? (e.g. open the menu while the remote session is frozen)
– This may be an issue with events, so can you please confirm all screen updates are frozen? (e.g. play a video before starting the file transfer)

Thank you.

[Tor]

Hi. When you say “it immediately disappears”, you mean you see the window for a moment then it moves offscreen?
Are you using more than one monitor? What do you mean exactly when you talk about selecting your VM?
Can you please check this Trouble Report and let me know if it may describe your problem: https://www.nomachine.com/TR02N06423

Thanks.

[Tor]

Hi Niall.

You already did the best you could do to take a pixel-perfect screenshot, by raising the video quality settings. You may use a remote tool to take the screenshot and transfer it on the client with NoMachine.

We appreciate your suggestion and to track it, we’ve opened a new Feature Request:

Having a high-quality screen capture of the remote desktop independently from session configurations
https://www.nomachine.com/FR03N03062

[Tor]

Hi.

The behaviour you’ve observed is not expected, preferences should be saved in all cases. We’ve opened a Trouble Report to document the problem:

User’s settings are not saved for new connections started from the !M icon in the tray menu
https://www.nomachine.com/TR02N06543

The problem occurs only when connecting to servers discovered on your LAN. As a workaround you can connect to that server by using the NoMachine client at least once, so the tray menu will start to work correctly.

About your second question, connections to servers discovered on LAN don’t save a preferences file, all information are stored in a cache because they’re subject to change. If you want an NXS file and you know the server’s hostname or IP, you can use the connection Wizard (by pressing the button New in the NoMachine client).

[Tor]

No problem, screenshots attached. You can see that welcome panel after authenticating to the server, when the desktop becomes usable. Probably the first time you saw it you’ve selected to never show it again.

You can still configure it from the Display menu (where you see the “Resize remote screen” icon): click on “Change settings” then check the box you see in the second attached screenshot.

Attachments:

1. 

   IMG_25022016_124620-1.png
   

2. 

   IMG_25022016_124657-1.png
   

[Tor]

Hi.

When you connect to the remote desktop, the resolution changes to match the client display configuration, in order to give you the best experience when working in fullscreen mode. This is the default behaviour and it can be changed in two ways: uncheck the box “Change the server resolution to match the client when I connect” visible in a panel while the client is connecting to the desktop, or if you miss that panel or asked the client to never show it, you can uncheck the box “Match the client resolution upon connecting” in the Display settings panel.

[Tor]

Hi Steve.

You may try to switch off your X server and let NoMachine create the virtual display for you. Switch to runlevel 3 or stop lightdm, and create a connection to that desktop. Visit this link for more information about the configuration:

https://www.nomachine.com/FR10L02842

[Tor]

Hi noah.

You can do it by using the drag&drop file transfer: select multiple files on the server, drag them out of the client’s window then release the mouse button. They’ll be saved on the desktop.

[Tor]

Hi.

This may be the feature request you’re looking for:

Auto-reconnecting the session when connection is lost
https://www.nomachine.com/FR06H02356

You can enable the “notify me” option so you’ll receive an e-mail when we’ll release a version implementing this feature.

[Tor]

Hi huang.

In order to ease the configuration you’re trying to achieve, we’ve added a new Feature Request:

Offer the possibility to restore the window geometry when starting the client or connecting to a desktop
https://www.nomachine.com/FR02N03008

We’ll release it very soon, so I’d suggest to enable the notify option in the feature request page. Once you’ll use this new version you’ll just need to enable the new key you’ll find in the NXS file, and the client window will try to go to the same geometry set in the “Resolution” key.

[Tor]

Hi mkrisk,

could you please confirm you see black borders when the client window is at its minimum size, so you cannot make it smaller?

[Tor]

Hi.
Today we’ve published the new app version fixing this issue.

[Tor]

Hi huang.

All the keys you’ve mentioned are still used in NXS files. I can’t think of a reason why you didn’t find them, so I suggest to use the latest NoMachine version, create a new connection and read the corresponding NXS file created by default in ‘Documents/NoMachine’.

You may wish to read also these articles giving more information about how desktop resize works in version 5:

Resize and scaling options for NoMachine client version 4 or later
https://www.nomachine.com/AR02M00835

Changing how you view the remote host
https://www.nomachine.com/changing-how-you-view-the-remote-host

1. no matter how many sessions u have created and saved (for every single session u got a .nxs file) there is only 1 player.cfg file for all of them, if I want set 1 session as “fullscreen” and other 1 as “normal”, how does it work?

The CFG file affects all client instances. If you want to use different CFG files you may create a shortcut/link to the NoMachine client and use the ‘–config’ command line option, for example (on Mac OS X):

/Applications/NoMachine.app/Contents/MacOS/nxplayer --config /tmp/custom.cfg

You may also create a single CFG file starting the client always in fullscreen mode, and use the ‘–geometry’ command line option for those connections that should not be fullscreen, for example (on Mac OS X):

/Applications/NoMachine.app/Contents/MacOS/nxplayer --session server.nxs --geometry 1024x768

2. where can I set the concrete resolutions except the “normal”, e.g I want to create 2 sessions, 1 of them with 1024×768 and the other one with 800×600?

Use the NXS file as you did in version 3.5. More details here:

The most frequently asked options for pre-configuring the client and the session behavior
https://www.nomachine.com/DT07M00094#19

[Tor]

Hello.
Our recent release was mainly focused on mobile platforms, so some fixes didn’t go through all required testing and were delayed to the next release.
Nevertheless if you want to test our version including this fix, just contact us on forum[at]nomachine[dot]com.

[Author]

Posts