Britgirl

[Britgirl]

Thanks for reporting. We are currently investigating.

[Britgirl]

Yes. Install the Enterprise Client for Linux in order to connect.

[Britgirl]

We got the logs thank you, and we’ll come back to you soon about those. Do you confirm you are always getting black screen regardless of the client OS you are connecting from?

[Britgirl]

Did you try the workaround in the other topic? I.e did you disable eglcapture with /usr/NX/bin/nxserver --eglcapture no on the Kubuntu host?

[Britgirl]

It seems you disabled debug on the server this time, possibly you executed only--collect without the --debug. We got only the debug agent logs (from the special package). You wrote that the black screen problem only shows when connecting from iOS but when you tried the special package we sent you, you are now getting black screen no matter what client you are connecting from? Is that correct?

1) Enable debug level on the problematic server/node machine:
nxserver --debug --enable all
2) Connect to the NoMachine server and reproduce the problem
3) Create the log archive on the server/node machine:
nxserver --debug --collect

Thanks very much for your collaboration.

[Britgirl]

When you mention NoMachine’s interoperability with other hypervisors, can you confirm whether you are just referring to the fact that products like NoMachine Desktop can be installed onto VM’s managed by those hypervisors?

That’s right.

I am currently thinking I might be able to use NoMachine Terminal Server paired with a custom session to accomplish what I am trying to do.

Take a look at the article here: https://kb.nomachine.com/AR10K00720. NoMachine supports VNC sessions. You need to enable VNC on the TS/ETS host first and then you will be able to run a VNC session to the VM. In the ‘VNC remote desktop’ panel, provide the IP or hostname of the VNC server and port to continue. In the next panel you will be requested to provide username and password to login to the VNC server.

[Britgirl]

Hi, take a look at this article here: https://kb.nomachine.com/AR05T01160. You can use the --configsave command.

[Britgirl]

Hi, that scenario is not supported, I’m afraid. We had planned to develop our own Virtualization Server, but with so many options on the market at the time, we decided to invest efforts in developing our current product suite (for example, Cloud Server which besides functioning as the gateway to your infrastructure is also a powerful remote access management tool). We also invested efforts in improving NoMachine’s interoperability with the multitude of hypervisors already available (not just physical workstations) as well cloud-based platforms. Indeed all NoMachine products integrate seamlessly with VMware, Virtualbox, Proxmox and other hypervisor solutions, as well as cloud providers such as AWS EC2, Amazon WorkSpaces Core, Azure, and Google Cloud Platform for example.

[Britgirl]

Hi, at the moment there is no setting to force the windows to stay minimized. The NoMachine window pops up to report a connection status change which could be useful for the user, and to apply some window configuration requests when needed. Your request is certainly a reasonable one though, so we’ll see how we can improve this aspect 🙂

[Britgirl]

So we need the logs from the server-side host and with debug enabled, they will help us to understand why the server seems to be unable to detect the physical display. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.

[Britgirl]

We’re not aware of similar issues of not being able to open the app after waking the machine from sleep mode. Are you able to send us the .nx folder in the user’s home of the affected system? The steps are:

1) Reproduce the problem

2) Compress and send us the .nx folder from the user’s home. On Windows the .nx folder is hidden, so to find it write the following in the address bar or the file browser: %USERPROFILE%\.nx

3) Check the list of processes in the task manager and check how many Player processes are running, even if the UI is not visible. If there are multiple processes, can you take a screenshot and send us it together with the logs?

Send everything to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, so you need to tell NoMachine to create its own display service (without the TV interfering), so what you could try is setting a different display in the node.cfg file of the NoMachine server host.  You can do it by editing the appropriate key, PhysicalDisplays.

In the node.cfg file (/usr/NX/etc/node.cfg) you can find:

For physical desktops, specify the physical display or range of X server displays which are made available to NoMachine connections. It is possible to specify a # single display by display number, e.g. :0, or by port, e.g. 6000.
The range of displays can be specified as a dash-separated list,  e.g. :0-:7 or, by port number, 6200-6204. By default all displays detected as running will be made available for users.

PhysicalDisplays :0

We suggest you set it to PhysicalDisplays :2.

Does that help?

[Britgirl]

Now it’s clear 🙂 I forgot to mention this article that have about headless hosts. You might find some useful information there as well: https://kb.nomachine.com/AR03P00973.

[Britgirl]

Hi, are you connecting to a Terminal Server product? We have reproduced in a custom rootless session (supported only in terminal server products)? We have not reproduced it connecting to the physical display. Please tell us what NoMachine product is running on the server side.

[Britgirl]

Hi

On my side (server? – the machine I’m sitting at to remotely connect to the other computers – so clients?) there is no “Switch Monitor” icon. Both the NoMachine and real computers have two displays I can select from but they are not the same between the two.

First some clarification about server and client in the NoMachine model. The “server” is considered the computer that receives incoming connections, i.e the computer you are connecting to. Clients are the devices you are connecting from.

Is the server computer you are connecting to headless? In that case, NoMachine detects no physical display and so it starts a virtual desktop (which would be the correct behaviour). If the server is not headless, then NoMachine should not be starting a virtual display. In that case we need logs and with debug enabled, they will help us to understand why the server seems to be unable to detect the physical display. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com or attach here. If you send them by email, please use the title of this topic as the subject. Thanks!

[Author]

Posts