Britgirl

[Britgirl]

Hi, thanks for letting us know know. If you also tried ‘Scale to window’ mode instead of ‘viewport’ and that didn’t help, it could be related to the GPU on your Linux host that makes available only one resolution when the monitor is not present. A dongle “tricks” the system into thinking the monitor is attached.

It’s one of the workarounds for connecting to headless hosts. See our article in the KB for reference:
https://kb.nomachine.com/AR03P00973

[Britgirl]

Hi, can you send us the server side logs of that Intel machine? We just acquired one of those Intel machines and are also testing it, so we can advise better. It would be good to compare.

These are the instructions for the logs, send them to forum[at]nomachine[dot]com with the title of this topic as the subject of your email 🙂 https://kb.nomachine.com/DT07S00243

[Britgirl]

Default settings are to not terminate, kill or remove any session that a user initiates. Please check what you have for the following server keys.

#
# Allow NX Server to terminate oldest disconnected sessions:
#
# 1: Enabled. Enable the automatic kill of the disconnected
# sessions.
#
# 0: Disabled. Disconnected sessions are never terminated.
#
# When this option is set and the maximum number of concurrent sessions
# has been reached, the server will kill the oldest disconnected sessions to
# make room for the new session.
#
#EnableAutokillSessions 0

and this:

#
# Set for how long the server has to keep alive virtual desktops in
# status disconnected. When the time is expired, the server will
# terminate virtual desktops if no user are connected there.
#
# 0: Virtual desktops in status disconnected are never terminated.
# This is the default.
#
# >0: Keep Disconnected session alive for this number
# of seconds.
#
#DisconnectedSessionExpiry 0

If they are both set to zero, tell us what NoMachine product and version you are using.

[Britgirl]

Hi, can you contact us directly at forum[at]nomachine.com and we will send you an apk package to sideload 🙂

[Britgirl]

We tested on the fly and can’t reproduce. With activegrab enabled, the Windows+3 keys are intercepted and show us the 3rd application running on the remote desktop. In our case, it’s the file explorer.

Can you start the player from a terminal instead like this?
/usr/NX/bin/nxplayer --activegrab

Attachments:

1. 

   image.png
   

[Britgirl]

Not sure what the file was that you tried to attach 🙂 If it was some kind of log, send it to forum[at]nomachine.com.

Let’s also try collecting client side logs_
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.
– Send the compressed logs archive to us using the email address above.

[Britgirl]

Try one of the Cloud Server products. Cloud Server can be used as a gateway to broker connections to desktops/machines that are behind the cloud server (desktops can be physical or virtual machines), on the corporate network. You can find more here: https://www.nomachine.com/cloud-server-family. It’s not just a gateway for your users, it also provides admins with a configuration and management interface accessible also from remote, including a web browser. You can add as many nodes as you want to any of the Cloud Server products through its admin interface. You can also use what we call “inverse add method”. This means that if a desktop node “moves” or is in DMZ, the node can be added to the Cloud Server from the node, of doing it from the cloud server, by going to Settings -> Server -> Clouds panel on the desktop node.

If you are using the free edition of NoMachine, switch to Enterprise Desktop or Workstation. Enterprise family products can be added as nodes to a Cloud Server.

See this guide which explains everything you need to know (I chose the Enterprise Cloud Server guide) https://kb.nomachine.com/DT08T00263. The full list of guides is available here: https://www.nomachine.com/support/documents.

Further resources: https://www.nomachine.com/adding-nodes-to-nomachine-cloud-server-via-the-nomachine-user-interface#inverse

[Britgirl]

We’re not aware of off-set problems, but we will investigate. Are you using the current NoMachine version, 8.11? Can you tell us the desktop environment you are running?

[Britgirl]

Hi, the zip of logs you sent us is empty. Try gathering again and resubmit.

[Britgirl]

Hi, is it possible for you to update to the latest version on the MacBook? What macOS is it? Is the NoMachine Linux server side also the latest? What Linux distro is it?

Diagnostic Reports from the macOS side would be useful:

Finder, bring up Go to Folder (Shift + Command + G) and paste ~/Library/Logs/DiagnosticReports. Submit what you have there. You can attach here or send to forum[at]nomachine[dot]com.

[Britgirl]

Thanks for letting us know gippy73!

[Britgirl]

Ok thanks for letting us know.

[Britgirl]

Thanks for the information. We’re currently investigating.

[Britgirl]

What you should do is update your NoMachine software both sides. If you can’t, then earlier versions to the what’s in production (currently version 8) can be managed in your customer area if you have a subscription.

If you are using the latest 8.11 on both client and server sides and still see the problem, we will need logs. Also, as in the other topic which was closed for lack of feedback, we need full details of the set-up including language settings on both sides, and Linux desktop environment. Is it a physical desktop session or are a virtual desktop session? Is the display server Wayland or X.org?

 

[Britgirl]

We are moving away from the original question which was how to connect if I have two NoMachine computers on different subnets. I assumed that you had already taken a look at the options of port forwarding/portmapping, setting up a VPN, and enabling UPnP. My mistake. Searching for Fritzbox on the net, it says the guest network is isolated, which complicates things a little. In your case a VPN might help to bring them together.

The following articles about portforwarding and portmapping in any case can be useful for you:

https://kb.nomachine.com/AR10T01175
https://kb.nomachine.com/AR04S01122

To sum up the commercial and technical differences between version 8 and the upcoming version 9, if you want to control (I previously used the term “connect to”, maybe this is what was not clear enough) another computer you have the following options:

– with NoMachine 8

• 1) start a connection to any NoMachine server using the IP address if on LAN or configuring port-forwarding/port-mapping/router changes if on different networks.

with NoMachine 9

• 1) start a connection to any NoMachine server using the IP address if on LAN or configuring port-forwarding/port-mapping if on different networks.
• 2) log in to Network and start a connection to any NoMachine server using the Machine Id. This will require a Network Subscription. If there is no Network Subscription associated to your NoMachine account, revert back to option 1.

[Author]

Posts