Sponsored Content
Full Discussion: AIX NIS Client to Linux
Operating Systems AIX AIX NIS Client to Linux Post 302291247 by otheus on Wednesday 25th of February 2009 04:48:10 AM
Old 02-25-2009
I still think the problem is having no shadow file in /var/yp/domain_directory. There's an option in the RedHat startup scripts for the NIS server that, depending on a configuration variable in /etc/sysconfig/ypserv (or something), it will either merge the passwd and shadow files, or serve them separately. Try setting up a second Linux server with this option to merge the files and see if then your AIX client can handle it.
 

10 More Discussions You Might Find Interesting

1. Solaris

Unregietred a nis+ client

Hi, How can I unregistered a nis+ client. I want it works without nis+. Bests regards (2 Replies)
Discussion started by: omainfroy
2 Replies

2. AIX

Use AIX as NIS client

Hi everyone. Has anyone here used AIX as a NIS client to a Linux server? If have configured this setup and cant get it to work. I have verifyed that the NIS server is working since other machines are able to connect to it and users to log in on other clients. On the AIX machine the users are... (0 Replies)
Discussion started by: sprellari
0 Replies

3. AIX

AIX NIS client

All, I have just started using AIX (Solaris admin here) and I need to setup my new AIX box as an NIS client. Where would I do this? Thanks for the help! -Kevin (2 Replies)
Discussion started by: kjbaumann
2 Replies

4. Solaris

How to configure a NIS client bound to the NIS server in another subnet?

Hi, all. I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client, 1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01 2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies

5. UNIX for Advanced & Expert Users

Linux NIS sever not binding with Solaris client

I am installing a NIS master server with a linux SLES 10 SP1. And it was pretty straight forward. (Simple since it GUI ) The server can bind to itself when issue with ypwhich command. But on solaris 10 box, I set up the defaultdomain (/etc/defaultdomain) and also issue ypinit -c to startup the... (3 Replies)
Discussion started by: ibroxy
3 Replies

6. AIX

Aix 5.3 NIS Client from a Suse10 sever

Hello Guys, Unfortunately after look for it on entire www I did not find anyone that have made a tutorial how to make it works. I'm using an AIX 5.3 as a nis client from a SUSE 1.0 server. I can see the maps - ypcat passwd (so I can Bind server) and I can su NIS users. BUT I CAN... (0 Replies)
Discussion started by: michelan
0 Replies

7. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

8. UNIX for Dummies Questions & Answers

Help with NIS client

Hi All, I have a new server on the network, I did configure the NIS. ypwhich is working and ypcat all are working. But when I log in as me, home directory is not coming up. I looked at other servers we have at work to see what's under /etc/fstab. I don't see anything for home directory. ... (3 Replies)
Discussion started by: samnyc
3 Replies

9. AIX

AIX LDAP client authenticate against Linux Openldap server over TLS/SSL

Hi folks, How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL? It works like a charm without TLS/SSL. i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
Discussion started by: paco699
6 Replies

10. Solaris

User authentication failed while log in Solaris 8 client on Linux NIS server.

Based on the NIS migration tests I did and another question I posted earlier on. https://www.unix.com/solaris/272021-solaris-8-md5-encryption-support.html I tried to downgrade NIS linux encryption to DES to support solaris connection. So I modified /etc/pam.d/system-auth as below, password... (0 Replies)
Discussion started by: bestard
0 Replies
rpc.yppasswdd(1M)					  System Administration Commands					 rpc.yppasswdd(1M)

NAME
rpc.yppasswdd, yppasswdd - server for modifying NIS password file SYNOPSIS
/usr/lib/netsvc/yp/rpc.yppasswdd [-D directory] [-nogecos] [-noshell] [-nopw] [-m argument1 argument2...] /usr/lib/netsvc/yp/rpc.yppasswdd [passwordfile [adjunctfile]] [-nogecos] [-noshell] [-nopw] [-m argument1 argument2...] DESCRIPTION
rpc.yppasswdd is a server that handles password change requests from yppasswd(1). It changes a password entry in the passwd, shadow, and security/passwd.adjunct files. The passwd and shadow files provide the basis for the passwd.byname and passwd.byuid maps. The passwd.adjunct file provides the basis for the passwd.adjunct.byname and passwd.adjunct.byuid maps. Entries in the passwd, shadow or passwd.adjunct files are changed only if the password presented by yppasswd(1) matches the encrypted password of the entry. All password files are located in the PWDIR directory. If the -D option is given, the passwd, shadow, or passwd.adjunct files are placed under the directory path that is the argument to -D. If the -noshell, -nogecos or -nopw options are given, these fields cannot be changed remotely using chfn, chsh, or passwd(1). If the -m option is given, a make(1S) is performed in /var/yp after any of the passwd, shadow, or passwd.adjunct files are modified. All arguments following the flag are passed to make. The second of the listed syntaxes is provided only for backward compatibility. If the second syntax is used, the passwordfile is the full pathname of the password file and adjunctfile is the full pathname of the optional passwd.adjunct file. If a shadow file is found in the same directory as passwordfile, the shadowfile is used as described above. Use of this syntax and the discovery of a shadowfile file gener- ates diagnostic output. The daemon, however, starts normally. The first and second syntaxes are mutually exclusive. You cannot specify the full pathname of the passwd, passwd.adjunct files and use the -D option at the same time. The daemon is started automatically on the master server of the passwd map by ypstart(1M), which is invoked at boot time by the svcs:/net- work/nis/server:default service. The server does not insist on the presence of a shadow file unless there is no -D option present or the directory named with the -D option is /etc. In addition, a passwd.adjunct file is not necessary. If the -D option is given, the server attempts to find a passwd.adjunct file in the security subdirectory of the named directory. For example, in the presence of -D /var/yp the server checks for a /var/yp/secu- rity/passwd.adjunct file. If only a passwd file exists, then the encrypted password is expected in the second field. If both a passwd and a passwd.adjunct file exist, the encrypted password is expected in the second field of the adjunct file with ##username in the second field of the passwd file. If all three files are in use, the encrypted password is expected in the shadow file. Any deviation causes a password update to fail. If you remove or add a shadow or passwd.adjunct file after rpc.yppasswdd has started, you must stop and restart the daemon to enable it to recognize the change. See ypstart(1m) for information on restarting the daemon. The rpc.yppasswdd daemon considers a shell that has a name that begins with 'r' to be a restricted shell. By default, the daemon does not check whether a shell begins with an 'r'. However, you can tell it to do so by uncommenting the check_restricted_shell_name=1 line in /etc/default/yppasswdd. The result will be to restrict a user's ability to change from his default shell. See yppasswdd(4). On start up, yppasswdd checks for the existence of a NIS to LDAP (N2L) configuration file, /var/yp/NISLDAPmapping. If the configuration file is present, the daemon runs in N2L mode. If the file is not present, yppasswdd runs in traditional, non-N2L mode. In N2L mode, changes are written directly to the Directory Information Tree (DIT). If the changes are written successfully, the NIS map is updated. The NIS source files, passwd, shadow, and passwd.adjunct, for example, are not updated. Thus, in N2L mode, the -D option is mean- ingless. In N2L mode, yppasswdd propagates changes by calling yppush(1M) instead of ypmake(1M). The -m option is thus unused. During an NIS-to-LDAP transition, the yppasswdd daemon uses the N2L-specific map, ageing.byname, to read and write password aging infor- mation to the DIT. If you are not using password aging, then the ageing.byname mapping is ignored. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWypu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), make(1S), passwd(1), yppasswd(1), inetd(1M), svcadm(1M), ypmake(1M), yppush(1M), ypstart(1M), NISLDAPmapping(4), passwd(4), shadow(4), ypfiles(4), yppasswdd(4), ypserv(4), attributes(5), smf(5) NOTES
If make has not been installed and the -m option is given, the daemon outputs a warning and proceeds, effectively ignoring the -m flag. When using the -D option, you should make sure that the PWDIR of the /var/yp/Makefile is set accordingly. The second listed syntax is supplied only for backward compatibility and might be removed in a future release of this daemon. The Network Information Service (NIS) was formerly known as Sun Yellow Pages (YP). The functionality of the two remains the same; only the name has changed. The name Yellow Pages is a registered trademark in the United Kingdom of British Telecommunications PLC, and cannot be used without permission. The NIS server service is managed by the service management facility, smf(5), under the service identifier: svcs:/network/nis/server:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.11 24 Aug 2004 rpc.yppasswdd(1M)
All times are GMT -4. The time now is 01:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy