- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- NIS Problems on RHEL WS4
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 02:35 AM
тАО07-19-2006 02:35 AM
NIS Problems on RHEL WS4
We have a server running RHEL_WS4 that is configured as a NIS Slave. The problem on this server is that if ypbind is running, but the NIS master isn't reachable (for example when I get down the network interface on the slave), root can't login.
If ypbind is down the problem doesn't appear and root is free to login.
the order in the nsswitch.conf is
passwd: files nis
shadow: files nis
group: files nis
Moreover I've seen that if I put an incorrect password for root, it gives "incorrect login", while when we put the right password, we have a "timeout".
I think it's a pam problem...
Thanks for any help,
Filippo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 04:30 AM
тАО07-19-2006 04:30 AM
Re: NIS Problems on RHEL WS4
Seems like a NIS configuration files. Check the conf files and try setting yppasswd on a user on the NIS slave.
Check the results of ypmake on the server.
Make sure basic ping and NIS_DOMAIN connectivity exists.
Check for local users in /etc/passwd that conflict with the NIS master.
You do not need to make pam.d changes to make NIS work.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 04:44 AM
тАО07-19-2006 04:44 AM
Re: NIS Problems on RHEL WS4
if in /etc/nsswitch.conf I delete the "nis" entry for "group" and "hosts", id est:
passwd: files nis
shadow: files nis
group: files
hosts: files dns
root can login even if the NIS MASTER is unreachable.
I'm not understanding...
Filippo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2006 03:00 PM
тАО07-19-2006 03:00 PM
Re: NIS Problems on RHEL WS4
With ypbind running, the login for root times out. Where is the meta escape character in the /etc/passwd file? It should be at the end, after all the local users. It sounds like the +:0:0:... entry is at the beginning of the /etc/passwd file, causing the NIS maps to be checked first. Make sure that the escape is after the root user.
Your further test of removing the nis reference for group also points to basic configuration problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2006 06:50 AM
тАО07-21-2006 06:50 AM
Re: NIS Problems on RHEL WS4
I have seen issues with nscd and NIS. You might try stopping the nscd and see if the problem goes away.
- Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2006 09:11 PM
тАО07-23-2006 09:11 PM
Re: NIS Problems on RHEL WS4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2006 09:11 AM
тАО07-24-2006 09:11 AM
Re: NIS Problems on RHEL WS4
1. instead of edit the files manually, you may run system-config-authentication to config the authentication to use NIS
2. SELinux thing. You may disable SELinux to see it blocks the YP connection
3. IPTABLES, TC wrapper
4. In Pam, system-auth is notoriously causing problems.
5. Make sure yp database excludes root (uid 0). Default ypserv configuration should be good (>500)