Forum Replies Created
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.
Great! Thanks very much.
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.
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 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
[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.
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.
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.
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.