Tor

[Tor]

Hi CG.
We’ve confirmed there is a problem when the server has four or more monitors, it is documented here:

The client on mobile doesn’t show more than four monitors in the remote monitors list
https://www.nomachine.com/TR01N06340

In order to work around the issue you may create another connection to the same server, so all monitors will be shown by default.
We’ll release an update within a few days. Thank you for your time.

[Tor]

Hi aplocher.

Currently the mobile version optimized for small screens is one of our top priorities, we plan to have a final release in a couple of months, but an earlier beta release is not excluded. If you didn’t do it already, you may subscribe this Feature Request to be contacted as soon as we’ll release it:

Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828

Even if the current GUI is not optimized for screens smaller than 7 inches, you may wish to try the client by downloading the package from our website. The Play Store doesn’t make it available on your device, so you have to manually install the APK.

[Tor]

Hi benny.

A few days ago we’ve submitted a new app version which will offer a better support for the iPad retina resolution 2048×1536, which of course will be available also on iPad Pro. We’ve already started to work on optimizations required for the new resolution, so it should be available in one of our next updates.

[Tor]

Hi Motto!

Our engineer would like to send you some debugging libraries to retrieve more information. Can you please confirm the NoMachine version you’re using on client and server? We’ll contact you by e-mail. Thanks.

[Tor]

Hi markus! The feature FR12K02799 is not yet scheduled for implementation, so I can’t give you a release timeframe, but we’ll do our best to start it as soon as possible.

[Tor]

Hi motto.

Our engineer didn’t find relevant information in your logs, he was planning to ask your help to test a new debugging version but you solved the issue and he became sad! Now that you’ve found a new way to reproduce it, I’m sure he’ll return to the fray. 🙂

Can you please do the following when you reproduce the issue, and let me know if it is enough to work around it:

– Open the NoMachine menu and select ‘Show the connection status’
– Click the ‘On’ button to shut down the server
– In the new dialog click ‘YES’ to restart the server at the next reboot
– Authorize the server shutdown
– Open the NoMachine Client
– Click the ‘Settings’ button
– Click the ‘Connection status’ link
– Click the ‘Off’ button to start the server
– Authorize the server startup
– Click the ‘Close’ button

For the record, with the next release we’ll offer an easier way to restart the server from the GUI. It is not a common operation for a user, but it may still be useful.

[Tor]

Hi skullius.

Currently the quick connection string format “Protocol://Host:Port” can only be used in the search edit, the box you see between the Sort and New buttons, as explained in the tutorial dialog visible when the client starts.
We may extend the support to other configuration fields, but we would need to know how you’ve configured your connection in order to know what to improve.

The error you’re reporting occurs for example if you write “nx://aaa.bbb.ccc.ddd” in the Host field of the connection Edit dialog. In that case you can change Protocol and Port fields (on the right side of the dialog), so the quick connection format is ignored.
If this is your case, remove the prefix “nx://” from the address in Host, press OK and connect again.

[Tor]

Hi.

Currently the mobile version optimized for small screens is one of our top priorities, we’re working hard on it. Even so I cannot say right now when it’ll be available.
If you didn’t do it already, you may subscribe this Feature Request to be contacted as soon as we’ll release it:

Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828

[Tor]

Hi.
Can you please give us more information:

– What’s your Android version?
– Are you using a custom keyboard?

[Tor]

Those environment variables are mainly intended to be used internally, so I discourage you from defining them system-wide (which is common on Windows).
You may however create a batch file for each user which executes the ‘set’ command to change NX_CONFIG (the directory where the client will read/write all user settings), and at last starts the client.
I don’t see a real advantage though. Defining that variable may be useful when administrators don’t want to create the settings directory in the default path (%USERPROFILE%\.nx), while in your case you want to change all default paths, so you should still modify player.cfg.

[Tor]

Hi Mr.X.

The file player.cfg is the right one to modify in order to use different directories than default ones, the only condition is that those paths exist.

The command line option selecting a different CFG file is ‘–config’:

nxplayer --config <path to CFG file>

[Tor]

Hi blabj.

The connection configuration flow has gone through a lot of design changes based on feedbacks and usability tests, so what you see now is what the majority of users asked for. This doesn’t mean it is perfect, so new use cases are always helpful to evaluate how to make that flow more flexible.

First of all, how it works. The client skips configuration steps each time there is only one choice. When the connecting user has no sessions running on the server and the filter is on “My desktops”, the configuration moves on virtual desktop type selection. From this dialog you may go back and select ‘All desktops”, unless the type is stored in the configuration file or the server only offers one virtual desktop type, because in such conditions the virtual session starts right away. While this workflow is ideal for administrators wishing to make life easier for users, it might be a problem for you.

If you wish to use the same connection to do both virtual desktop and desktop sharing, then I’d suggest to not save the desktop type in the configuration (by checking the box “Save this setting in the connection file” in the type selection dialog).

[Tor]

You may try this product:

NoMachine Web Companion
https://www.nomachine.com/product&p=NoMachine%20Web%20Companion

It does exactly what you wish to do, the only difference is that it also ships a complete NoMachine Client, so users won’t need to manually install it.

Installation and Configuration Guide
https://www.nomachine.com/DT09K00053&dn=

[Tor]

Hi cyconical.
As you said, the only useful feature (so far) to achieve what you want is the ‘–exit’ option. We’re planning to improve the support for clients running in kiosk mode, but that will require configurations on client side.
If you’re sure your clients are on Linux, you may distribute a modified version of the client startup script which could append the ‘–exit’ option, so the feature would be triggered each time the user starts the session by double clicking your NXS file.

[Tor]

Hi pkats15.

Did you reboot your host after installing NoMachine? If you did it but the problem is still there, please get logs as explained in the article

https://www.nomachine.com/DT04M00076#3

and send them to forum[at]nomachine[dot]com.
Thanks!

[Author]

Posts