Britgirl

[Britgirl]

Hi, can we see the player logs (the Windows machine you are connecting from)? Please see the instructions here:
https://kb.nomachine.com/DT07S00243, section “Fourth Step: Collect Client Side Logs”.

 

[Britgirl]

Hi, this

connects to the physical desktop, the screens turn black and then slowly begin fading between gray and black,

is because you activated screen-blanking and have the screen shading effect enabled. If you don’t want the fading affect, you can disable this. Go to server settings on the machine you are connecting to -> Server -> Security -> tick the second checkbox “Disable the screen shading effect….”.

punctuated by a split-second flash of the actual desktop. Some of the keys don’t work.

This is not normal, and we are trying to reproduce.

[Britgirl]

What I forgot to ask is for the logs, so we can verify that it is the same problem I mentioned. It would be useful to have the logs from the Ubuntu host; you can extract them using the instructions here: https://kb.nomachine.com/DT07S00243 and then submit them directly to forum[at]nomachine[dot]com.

Can you also show us the output of the following:

sudo netstat -anlp | grep egl

if the output is empty, then send the output of

sudo /usr/NX/bin/nxserver --eglcapture yes and sudo getcap /usr/bin/gnome-shell

Thanks!

[Britgirl]

A workaround that you can try is adding graphical.target to nxserver.service in After=.

nxserver.service can be in one of these paths:

/lib/systemd/system/nxserver.service
/usr/lib/systemd/system/nxserver.service

with root permissions you should add graphical.target to the following line:

After = syslog.target network.target network-online.target sshd.service http-daemon.target.service htd.service

to look like this

After = syslog.target network.target network-online.target sshd.service http-daemon.target.service htd.service graphical.target

Then, still as root

systemctl daemon-reload

and

systemctl restart nxserver.service

Does this change anything?

[Britgirl]

The logs you sent were from the Mac client you are connecting from. We would need to see the server side logs as well. In any case, it seems to be a networking/configuration problem on the server side, with the IP address possibly being dynamic (so it has changed since you last connected?) I noticed the domain you are connecting to. If you are not the administrator of the computer you are connecting to, are you able to contact the administrator of the organization’s NoMachine server? Something must have changed at the network or configuration level of the NoMachine server you are connecting to. If you are the owner of the server machine and can access it, send us the server logs as well. Please also see this article here:

How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122

[Britgirl]

Hi,

I noticed the domain you are connecting to. If you are not the administrator of the computer you are connecting to, are you able to contact the administrator of the organization’s NoMachine server? Something must have changed at the network or configuration level of the NoMachine server you are connecting to. If you are the owner of the server machine and can access it, send us the server logs via to forum[at]nomachine[dot]com? You server side logs by following the instructions in https://kb.nomachine.com/DT07S00243.

Please also see this article here:

How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122

[Britgirl]

” NoMachine will get this sorted out, too. I consider this an absolutely basic and indispensable functionality.”

So do we 🙂 you can keep tabs on the bug report using that link I posted. If you’re wondering why there is [removed] in your replies, it’s because a policy of the forum (which you agreed to when registering) is that we don’t post other products’ names unless it’s absolutely essential for understanding the problem.

NoMachine can run on Wayland, in fact we added support for Wayland quite some time ago. You can read about some of the expected behaviour in our documentation here, and possible workarounds:

Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969

Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083

[Britgirl]

Hi Mike,

thanks for your support 🙂 We have taken note of your suggestion and will be taking it into consideration.

[Britgirl]

Hi, apologies for replying so late.

Issue #1 is that if either/or of Zero and Two are in a “screen off” state (black display, no backlight) when I connect, the screen’s backlight will turn on while display stays black.

You are right. The backlight will turn on at connection and it is expected. No one has ever complained about this behaviour 🙂 but it is a valid point so we are going to add restoring dpms settings at session end.

Issue #2, only applies to Two, the Windows 10 laptop: It will do the same thing (backlight comes on, screen stays black), but I can still see the laptop’s mouse pointer moving around the screen on Two as I do my work from One.

The cursor being visible on windows with screen blanking is something we can’t fix unfortunately.

[Britgirl]

The current version is now 8.10. Please update your NoMachine client and server side software if you haven’t done so already 🙂

[Britgirl]

We have been able to reproduce the same issue and are looking at possible solutions.

[Britgirl]

Can you reproduce this problem regardless of the client OS you are connecting from? You wrote you have 4 Linux Mint systems, so I assume you are connecting between them. Is it possible for you to test from a different OS? E.g a connection from Windows to the affected system. I think you also contacted us via Report Issues, if you did, please follow the instructions you received by email 🙂

Update: problem disappeared after applying system updates.

[Britgirl]

Did you add the private key in the player as well? The last section of this article
https://kb.nomachine.com/AR02L00785

1. Launch the NoMachine User Interface from Programs menu or Applications and right click on a connection. Choose ‘Edit connection’  to access connection settings.

2. Be sure that NX is the selected protocol in the drop-down menu.

3. Go to Configuration panel and choose ‘Use key-based authentication with a key you provide’ and click on Modify.

4. Select the private key and check ‘Import the private key to connection file’ if you want to save it for that session.

5. Back to the previous panel and click on Connect

The client will prompt you for username and passphrase.

[Britgirl]

Check the IP addresses for that connection by going to ‘Edit connection’. Then select an alternative one if there are multiple ones available. A screenshot showing what I mean is and my explanation https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467

[Britgirl]

Wake On Lan works by sending so called “Magic Packets”, which are packets of the second layer (MAC). VPN emulates and works on the third layer IP. WOL on its own does not use the IP address of the destination host, it uses its MAC address. NoMachine translates the IP address to the MAC address based on the routing table. In the Magic Packet only the MAC address is used.
Magic Packet is a broadcast packet, therefore it is not possible to route it through VPN without special configuration of the VPN itself  provided that the VPN supports it, so you should check this in the VPN you are using.

[Author]

Posts