Britgirl

[Britgirl]

It is a known issue and the workaround is to use NoMachine Enterprise Client instead of the Free Edition on the computer you want to connect from. Please uninstall FE and install the following:

https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Client

You can use this link to track the Trouble Report: https://kb.nomachine.com/TR12T10708

[Britgirl]

Hi,

can you submit the server side logs (Windows) as per the instructions here?

We’ll also need the player side logs from the Ubuntu machine.

https://kb.nomachine.com/DT07S00243

 

Please send everything to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thanks!

[Britgirl]

Please see https://forum.nomachine.com/topic/sound-shuts-off-on-host#post-44604.

Does this help?

[Britgirl]

The attachment was too big and didn’t attach.

Please send directly to forum[at]nomachine[dot]com. Thanks.

[Britgirl]

It’s not currently possible to disable the confirmation panel.

[Britgirl]

Hi, I assume you are connecting to a Linux server, if so is Wayland or Xorg the display server?
What distro and version is on the server side?
What OS and version is on the Player side?
What NoMachine product and version did you install?
What type of NoMachine session are you starting?
What desktop environment are you connecting to?

What are the steps to reproduce the problem?

[Britgirl]

Please tell us 1) the desktop environment running there and 2) whether the display server is Wayland or X.org.

[Britgirl]

As I mentioned, we have reproduced the same behaviour and opened a Trouble Report which you can track using the following link:
https://kb.nomachine.com/TR06U10880.

As a workaround, focus on the window of another application before switching to another NoMachine client window.

[Britgirl]

You installed the package, so presumably you are an administrator of your machine. If it is so and you are a sudo user, please insert your password and verify that the authentication succeeds. If it does not, from a terminal on the server, making sure you are opening the terminal as the same user that wants to connect from remote, run sudo -l -U <username> /bin/pwd and give us the output of this command.

[Britgirl]

Following on from the logs that you submitted from our last debug library, can you send us the output of ls -l /dev/dri?

[Britgirl]

The NoMachine directory you see is the application sandbox directory that the app makes available to you, in case you want to access the created files or if you want to use new private keys or upload files from your device. As you rightly guessed, your connection files are also stored there 😉

 

[Britgirl]

Hi, we are not aware of similar issues with disappearing connections (connection files) from the Machines panel.

Can you tell us what iOS version it is and on what device you’ve installed the NoMachine app? Can you also take a screenshot of the Machines panel and submit it?

The next time the connections disappear, you could connect the device to your Mac or use iTunes on a PC  to check what is in the NoMachine directory.

[Britgirl]

Hi, logs indicate a possible network or even firewall issue and not a problem with the NoMachine software. The connection drops because there is no network. Please check your network and firewall configurations.

[Britgirl]

Hi,

welcome to the forums 🙂

To answer your questions:

1) To connect with NoMachine you need one of the NoMachine servers installed on each machine you want to access. So, let’s take the Free Edition as an example. Download and install NoMachine FE for Windows on your Windows computer. Then download and install the Free Edition on your Ubuntu machine. The operating system can be physical or virtual, it doesn’t matter, but there must be a desktop environment installed there.

Then, on the device you are connecting from, you can install either the Free Edition or Enterprise Client. All NoMachine server packages contain both the Player and the Server components. The Player is what you need to be able to start a connection. The Enterprise Client package contains only the Player.

NoMachine’s model is “number of connections per server” and they are counted on the server, not on the device you are connecting from. See the following articles for more information:

https://kb.nomachine.com/AR07L00808
https://kb.nomachine.com/AR10K00716

2) To access any VM, a NoMachine server must be installed on each of them.

Take a look at the following article: https://kb.nomachine.com/AR11E00489

[Britgirl]

Hi

If I understand what you have written, you would like to be able to create multiple virtual monitors on a headless machine. We do this already, it’s available in the Terminal Server family (virtual desktops on Linux).

As far as I understand, if the server was not headless, but rather had 2 monitors, I was able to connect to each of them remotely while configuring the client (thus, connecting to the same server in parallel from 2 nx clients), while choosing on each of them different “monitor” of the multiple monitors I have on the server .

This will be possible in the future. For a later version, we are going to implement the possibility to have multi-monitors on the server side which can be managed as separate windows on multi-monitors client side. In each of these separate windows users will be able to apply all the usual settings, like applying a different scaling factor, resizing the window to any size, sending the window to fullscreen and placing the window in any desired location.

Unfortunately, we cannot give a definitive ETA. Development priorities are currently on NoMachine Network (www.nomachine.com/network) and v9. Work on the feature you are interested in may start after that.

Right now, what’s possible is to have multiple monitors on the server and you can cycle through the monitors on your client-side monitor (see https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session).

Additionally, if you have a Terminal Server (Linux) product installed, such as the Workstation, you can have multi-monitors on the client as separate monitors in NoMachine sessions. Doing so lets you maximize the session window, for example, in one monitor only, instead of going full-screen across all the client-side monitors available.

To enable it:
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’

You briefly mention using a dummy display dongle for your headless machine, this is an option. Take a look at our tips for headless machines: https://kb.nomachine.com/AR03P00973.

[Author]

Posts