07-13-2021, 01:40 AM
(This post was last modified: 07-13-2021, 01:44 AM by Gribouille.)
(07-12-2021, 06:06 PM)KC9UDX Wrote: I checked the domainname and they all agree.Hello,
I tried 'su - test' on the client which *worked* to my surprise.
I edited /etc/resolv.conf and changed test.net to the correct domain; NetworkManager apparently put this in there and probably will again; I'll have to investigate NetworkManager.
But since changing that, I restarted nis and rpcbind and now /var/log/auth.log gives more information:
Jul 12 19:15:44 client login[14820]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/pts/1 ruser= rhost=localhost user=test
Jul 12 19:15:47 client login[14820]: FAILED LOGIN (1) on '/dev/pts/1' from 'localhost' FOR 'test', Authentication failure
You have to use an other account than 'root' to make 'su - test', because the password is not asked.
An other test, use an other local account, as 'root' and make 'su - <the other account>', and after 'su - test'. If you haven't restricted the root's rights, this a good way to check the password.
The network domain name and the network NIS domain name are two different things without link. We can suppose that if your hosts are in different network domains, depending of their configuration, it could be more tricky to access to the hosts.
As you can access by 'SSH' to the host and with the extract of your logs, the NetworkManger seems innocent for me.
A classic trap : the fonts ! Have you check that when your are physically on the host and when you type the password, in place of the login per example, the display is good ? It could be good in a graphical session but not in console mode. The console mode is the mode used when you make a 'SSH'.
I always add the following packages :
- console-data
- console-common
- unicode-data