jkissane

[jkissane]

Thank you very much! Adding that single line to sssd.conf got everything working.

ad_gpo_map_network = +nx

 

 

[jkissane]

Thank you, let me know if you require any further logs etc.

[jkissane]

I checked this morning & this is working on Fedora 33 now using version 7.7.4.

Thanks for the fix.

[jkissane]

Thank you very much for the update.

[jkissane]

An update on this, we’re moving from NIS to LDAP authentication on Linux PC’s & I’ve found on a Fedora 34 system that has been joined to our Windows domain, NoMachine also is unable to authenticate.

It’s a different error message this time:

nxserver.log

3266 3266 2021-07-14 10:07:43 981.246 NXSERVER ERROR! Authentication with ‘NX-password’ from host ‘10.1.81.115’ failed. Error is ‘Wrong password or login’.

3384 3384 2021-07-14 10:07:53 377.881 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –auth’ with pid ‘3415/3415’ finished with exit code 1 after 0,351 seconds.

nxerror.log

3415 3415 10:07:53 361 RetrieveKerberosTicket: ERROR! Failed to readkerberos principal.

3415 3415 10:07:53 361 RetrieveKerberosTicket: ERROR! Kerberos error is -1765328189.

3415 3415 10:07:53 366 nxexecPAMCheckCredentials: ERROR! Account validation failed with error 6.

Info: Connection from 10.1.81.115 port 51515 closed on Wed Jul 14 10:07:53 2021.

I can log in successfully on this PC either graphically on the console or via ssh.

[jkissane]

Yes RHEL/Centos 7 works fine as does older version of Fedora. I know it doesn’t work with Fedora 33 & does work with Fedora 25 but that’s as far as I gone.

[jkissane]

Great! Thanks very much.

[jkissane]

I sent that file a few days ago as requested.

I’ve since tested NoMachine with the latest version of RHEL 7 (Red Hat Enterprise Linux Server release 7.9 (Maipo)) & can confirm it works ok there. Looks like the problem is with RHEL 8 & newer versions of Fedora.

[jkissane]

Sure no problem but given I log into the machine & authenticate via NIS, I’d suggest it’s working ok! The attached file is from a RHEL 8 box as the original PC has been re-installed with Fedora 25 which works fine with NoMachine.

Thanks!

 

[jkissane]

Thanks for the update, as I mentioned I installed Fedora 25 instead & all works fine with NIS configuration as before. When you say “configuration problem on your server” what exactly does that mean?

This combination works:
[root]# rpm -q NoMachine
NoMachine-7.1.3-1.x86_64
[root]# cat /etc/redhat-release
Fedora release 25 (Twenty Five)

Also doesn’t work under RHEL 8.3 so I suspect if the group who own those servers chose to purchase NoMachine licenses then I’ll be opening a support ticket at that stage.

[jkissane]

I reinstalled the PC with Fedora 25 as more important to the user is to be able to access it remotely than to have the latest & greatest. NoMachine (7.1.3) is working fine on that version. I don’t have the time to see where NoMachine stops working on the various Fedora versions between 26 & 33.

[jkissane]

I just tried this on a new server running the latest version of RedHat (Red Hat Enterprise Linux release 8.3) & the same issue appears. An older version of NoMachine is working normally on some older versions of RedHat with the same setup.

Not working – NoMachine-7.4.1-1.x86_64 on RHEL 8.3

Working – NoMachine-5.0.47-1.x86_64 on RHEL 6.9

Both using the same NIS domain/server.

[jkissane]

Thanks for the suggestion.

“getent passwd” produces the entry in the yppasswd file, “getent group” produces nothing but then there is no group called john.kissane.

As mentioned I can either ssh onto this box or login via window manager on the local screen without any errors.

[Author]

Posts