Forum Replies Created
-
Posts
-
Hi, I assume you are using the latest version of NoMachine on the Ubuntu host. What desktop environment are you connecting to?
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.dor 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.soHi 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!
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?
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:
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 rebootOn RPi4 it’s not required anymore, but on RPi3 it is.
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?
Hi, this question has already been answered in forums 🙂 Take a look at the following:
https://forums.nomachine.com/topic/disable-ipv6-or-configure-which-interface-to-bindNamely, you can modify the server.cfg to exclude specific addresses
#
# Specify the network interface where the NX service will be bound.
# Populate the field with an IP address or a domain name.
#
#NXdListenAddress “”A brief intro about the server/node configuration files is here if you are interested:
The server.cfg and node.cfg files explained
https://kb.nomachine.com/AR02N00877Hi leprechaun,
I’ve gotten it to work just fine across my LAN and over the internet through my firewall.
Great 🙂
From what you’ve written I understand that connecting to a Raspberry device, everything is working well. But when connecting from a Raspberry device or smartphone with the NoMachine mobile app to your Windows 10, you cannot see applications windows. You see only the desktop. Right?
On my Windows 10 Machine it seems to work fine except none of the windows display remotely.
What applications are actually running there? I mean, if I was physically in front of the Windows PC , what applications would be open?
Is the Windows PC with multi-monitors? If so, take a look at this tutorial: https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session.
Hi, take a look at this article in our knowledge base 🙂
How to start the session by passing options to the client from command line
https://kb.nomachine.com/AR02P00963This means that EGL capturing isn’t enabled.
Tell us the output of
sudo /etc/NX/nxserver --egl-capture yesPlease also attach the modified scripts mentioned in the output of the command above.
Also, what is the output of
getcap /usr/bin/gnome-shell?The logs show that physical desktop sharing is disabled for user djoo.
Try running:
sudo /etc/NX/nxserver --useredit djoo --screensharing yes.Just to clarify a small detail. When you mention NoMachine session, which is on Ubuntu, knowing which desktop environment you are connecting to is useful for us. By “desktop environment” I mean KDE, Gnome or any other. OK, thanks for letting us know that the problem is solved. If it happens again, by all means open a support enquiry.
