Britgirl

[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.

[Britgirl]

sk.bsd, take a look at this Trouble Report which we opened for a similar issue to the one you are describing

https://kb.nomachine.com/TR07U10921

As a temporary workaround, disable Wayland.

embee999, your issue is also known https://kb.nomachine.com/TR10U11031. There is a workaround in the TR.

[Britgirl]

Take a look at the third option in this https://kb.nomachine.com/AR03P00973. Use the proper command to stop the X server according to your display manager and then restart the server.

https://kb.nomachine.com/AR03P00973

If the tips don’t help, tell us the desktop environment and send us the logs.
https://kb.nomachine.com/DT07S00243.

[Britgirl]

Can we assume you are the latest version which is 8.10? We are not aware of white screen issues as you describe when connecting to Windows or other OSes (you wrote Linux client under XFCE to Windows 10 server). Any white screen issues similar to yours that we encountered in earlier versions have been fixed (you can take a look in the Trouble Reports section of the knowledge base to search them). We are aware of ONE issue connecting to Linux which temporarily shows a white screen and then disconnects with an error, but this does not appear to be your case (it appears when connecting to KDE/Plasma desktop, as well as disconnects with an error). You can find it here:

White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921

We’re happy to investigate your issue, but to do that we need to know:

– the Linux distribution/version you’re connecting from
– the graphics card installed on the both sides
– logs from the affected machine (https://kb.nomachine.com/DT07S00243) You can submit them to forum[at]nomachine[dot]com.

[Britgirl]

Improvements to support for HiDPI displays is still of course planned. We’ve not dedicated the necessary resources simply because of other development priorities related to version 9 and NoMachine Network. Once v9 is out, can start on adding an option to make the session “DPI Aware”

[Author]

Posts