Britgirl

[Britgirl]

Please everyone update their installations to the latest version. If you continue to have problems, open a new topic. Thanks!

[Britgirl]

This topic is now closed. Please contact us via the website (https://www.nomachine.com/contact-request) if you have feedback about the test package, would like to submit logs or provide other info that is useful for the investigation. Thanks!

[Britgirl]

Hi,

NoMachine for Linux includes a nxagent virtual X server that you can run, just to make one X server that the system can “see”, one that can run your desktop software and one you can connect to. When the Linux machine is headless, NoMachine detects that there is no X server running and prints the message:

Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?

to which you should click “Yes”. Did this appear the first time you connected? What happened? What happened the second time?

When you connected previously, and it was working, is it possible that a monitor was attached and on?  After connecting the first time, and then disconnecting the session, did the monitor turn off or maybe it’s a laptop and you closed the lid? It could be that the graphics card installed there did not correctly detect one or the other events (so it’s not NoMachine at fault here).

Take a look at this article and follow the tips there:

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

Also, if Wayland is the display server running there, please check the article here:

https://kb.nomachine.com/AR02P00969

[Britgirl]

HI, with the release of v7 all details from the folder were moved to redis database to increase performance of the NoMachine server. I can confirm that to be able to identify session name with display and username included you can use the command --history --verbose.

[Britgirl]

Eshama, what desktop environment (DE) is running on your Linux SLED ie. is it Gnome, KDE, LXDE, something else? Is it the NoMachine Free Edition running there? Were you able to connect before?

We are not aware of similar problems with Suse or Ubuntu.

[Britgirl]

What Ubuntu desktop environment is installed in that VM? NoMachine can install in any VM, what’s important is that there is a desktop environment running there.

You can check with grep ^Exec /usr/share/xsessions/*

Take a look at:

How to run a virtual desktop environment on Linux different from the default one with NoMachine
https://kb.nomachine.com/AR04K00667

to know how to set the right desktop.

[Britgirl]

I’ll as the same question that I asked in your other topic (https://forums.nomachine.com/topic/the-session-negotiation-failed-error-node-was-not-retrieved):

I assume you are using the latest version on the SLED host. What desktop environment are you connecting to?

[Britgirl]

Hi, I assume you are using the latest version of NoMachine on the Ubuntu host. What desktop environment are you connecting to?

[Britgirl]

System users authentication doesn’t work on systems with pam.d placed in a different location than /etc/pam.d.

It looks like you have the same issue which was reported a while back by another user. The problem is not in NoMachine, but the fact that you have pam.d iconfig files in two places in your OS. (https://kb.nomachine.com/TR02R09538)

As a workaround, link pam.d to /etc/ directory before installing NoMachine:

sudo ln -s /usr/share/defaults/etc/pam.d /etc/pam.d

or add manually nx and nxlimits files to pam.d directory (/usr/share/defaults/etc/pam.d):

cat /usr/share/defaults/etc/pam.d/nx
auth       include       su
account    include       su
password   include       su
session    include       su

cat /usr/share/defaults/etc/pam.d/nxlimits
session   optional pam_limits.so

[Britgirl]

Hi tomku

…I immediately realized, this is the reason. Many thanks!

Good. So the problem was that IPv6 is not enabled by default by the Windows XP OS. Good. Soo problem solved 😉

Good luck with your move!

[Britgirl]

I can’t imagine NX to ignore IPv6

In fact it doesn’t. IPv6 is fully supported, fully tested and fully working. We test IPv6 regularly, among our standard test procedures, before any new release.

1) Can you tell us the IP address you are using?
2) Where did you put it?

Even an description of the error number would be appreciated

In fact, there is the description: “Error 102: protocol doesn’t support address family”
Where exactly was it shown? Where was it reported? Can you show us a screenshot?

if I use the IPv6 address…….Nothing worked using SSH or HTTPS.

3) What’s the IP address that you used.
4) How are you using it with SSH or HTTPS?
5) What are you connecting to?

In other words, please provide all the information we need to reproduce the problem.

Also, have you tried using the same IPv6 address with another application and it worked well?

[Britgirl]

When a NoMachine server runs on a machine, it makes a list of network interfaces, and it collects all the information (hostname, list of IPs, ports on which it is listening) and sends it on the LAN where NoMachine clients (on the same LAN) receive this info. This info is used to create an mDNS item in the list. The server cannot know in advance if those IPs are the right ones to use or not. So, if the first of the IPs is “wrong”, the client will fail to connect. What you can do is go in to the Player’s Configuration panel of the connection and check if there are multiple entries in the Host field. An example of what you could see is attached:

Select another item from the list for the connection and then connect.

Attachments:

1. 

   nomachine-IP-address-edit-connection.png
   

[Britgirl]

Hi, I assume your Raspberry is headless. Did you follow the instructions in our tutorial?

https://www.nomachine.com/tips-on-how-to-set-up-your-raspberry-pi-for-remote-access-via-nomachine

See Tip 2: Connecting to a headless Raspberry.

sudo vim /boot/config.txt
hdmi_force_hotplug=1
sudo reboot

On RPi4 it’s not required anymore, but on RPi3 it is.

[Britgirl]

Hi, let me understand better:

1) you’ve been using Xorg (not Wayland) connecting with NoMachine and had no problems up until recently?

2) all of a sudden you’re getting small fonts in the NoMachine player? What have you changed on the host, in the time it was working and when the font problem started? Did you only update NoMachine to 7.10?

2) have you followed your own tips from your original post in https://forums.nomachine.com/topic/no-text-showing-in-client-sceen-under-xorg-kde? e.g reboot?

3) what is the ‘zoom level’ that you mention?

We’ll try and reproduce it here. I’ll write what I wrote last time:

Do the following, open a terminal on the affected host execute ‘xdpyinfo’ and ‘xrdb -query -all’ . What’s the output?

If you change the font in the NoMachine Player settings, does the problem go away?

 

[Britgirl]

Glad to hear that. Happy nomachining 🙂

[Author]

Posts