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)
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)
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)
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)
Friends n Gurus
I am creating an NIS farm(Solaris only) in my office. I have successfully configured the NIS master and slave servers and a few NIS clients.
However i am not able to log into a few of my NIS clients. The commands "ypcat passwd" is displaying the NIS user. However when i try to... (5 Replies)
Hi,
I have a trouble with configure NIS Client on AIX, my NIS server is on a Linux machine.
After configure, some old NIS account could login normally. However, after I create new account from NIS server, I could not login with the new account, but could only su to that account. And I could view... (20 Replies)
Hey All!
Today I am getting an error with my NIS client
From what I understand, my server is running properly...
on my client side..
online 2:01:12 svc:/network/nis/client:default
# ps -ef |grep ypbind
root 2745 1 0 02:01:12 ? 0:00... (12 Replies)
Hi All,
In my network infra, there is a NIS master server and many more NIS slave servers. Now, I want every client to set with master server and one possible slave server so that if master goes down, client could still get info from slave server. The servers will be listed on... (0 Replies)
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
LEARN ABOUT OPENDARWIN
nisserver
nisserver(1M) System Administration Commands nisserver(1M)NAME
nisserver - set up NIS+ servers
SYNOPSIS
/usr/lib/nis/nisserver -r [-x] [-f] [-v] [-Y] [ -d NIS+_domain] [ -g NIS+_groupname] [-l network_passwd]
/usr/lib/nis/nisserver -M [-x] [-f] [-v] [-Y] -d NIS+_domain [ -g NIS+_groupname] [ -h NIS+_server_host]
/usr/lib/nis/nisserver -R [-x] [-f] [-v] [-Y] [ -d NIS+_domain] [ -h NIS+_server_host]
DESCRIPTION
The nisserver shell script can be used to set up a root master, non-root master, and replica NIS+ server with level 2 security (DES). If
other authentication mechanisms are configured with nisauthconf(1M), nisserver will set up a NIS+ server using those mechanisms. nisauth-
conf(1M) should be used before nisserver.
When setting up a new domain, this script creates the NIS+ directories (including groups_dir and org_dir) and system table objects for the
domain specified. It does not populate the tables. nispopulate(1M) must be used to populate the tables.
OPTIONS -d NIS+_domain Specifies the name for the NIS+ domain. The default is your local domain.
-f Forces the NIS+ server setup without prompting for confirmation.
-g NIS+_groupname Specifies the NIS+ group name for the new domain. This option is not valid with -R option. The default group is
admin.<domain>.
-h NIS+_server_host Specifies the hostname for the NIS+ server. It must be a valid host in the local domain. Use a fully qualified
hostname (for example, hostx.xyz.sun.com.) to specify a host outside of your local domain. This option is only
used for setting up non-root master or replica servers. The default for non-root master server setup is to use the
same list of servers as the parent domain. The default for replica server setup is the local hostname.
-l network_password Specifies the network password with which to create the credentials for the root master server. This option is
only used for master root server setup (-r option). If this option is not specified, the script prompts you for
the login password.
-M Sets up the specified host as a master server. Make sure that rpc.nisd(1M) is running on the new master server
before this command is executed.
-R Sets up the specified host as a replica server. Make sure that rpc.nisd is running on the new replica server.
-r Sets up the server as a root master server. Use the -R option to set up a root replica server.
-v Runs the script in verbose mode.
-x Turns the echo mode on. The script just prints the commands that it would have executed. Note that the commands
are not actually executed. The default is off.
-Y Sets up a NIS+ server with NIS-compatibility mode. The default is to set up the server without NIS-compatibility
mode.
USAGE
Use the first synopsis of the command (-r) to set up a root master server. To run the command, you must be logged in as super-user on the
server machine.
Use the second synopsis of the command (-M) to set up a non-root master server for the specified domain. To run the command, you must be
logged in as a NIS+ principal on a NIS+ machine and have write permission to the parent directory of the domain that you are setting up.
The new non-root master server machine must already be an NIS+ client (see nisclient(1M)) and have the rpc.nisd(1M) daemon running.
Use the third synopsis of the command (-R) to set up a replica server for both root and non-root domains. To run the command, you must be
logged in as a NIS+ principal on a NIS+ machine and have write permission to the parent directory of the domain that you are replicating.
The new non-root replica server machine must already be an NIS+ client and have the rpc.nisd daemon running.
EXAMPLES
Example 1: Setting up Servers
To set up a root master server for domain sun.com.:
root_server# /usr/lib/nis/nisserver -r -d sun.com.
For the following examples make sure that the new servers are NIS+ clients and that rpc.nisd is running on these hosts before executing
nisserver. To set up a replica server for the sun.com. domain on host sunreplica:
root_server# /usr/lib/nis/nisserver -R -d sun.com. -h sunrep
To set up a non-root master server for domain xyz.sun.com. on host sunxyz with the NIS+ groupname as admin-mgr.xyz.sun.com.:
root_server# /usr/lib/nis/nisserver -M -d xyz.sun.com. -h sunxyz
-g admin-mgr.xyz.sun.com.
To set up a non-root replica server for domain xyz.sun.com. on host sunabc:
sunxyz# /usr/lib/nis/nisserver -R -d xyz.sun.com. -h sunabc
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO nis+(1), nisgrpadm(1), nismkdir(1), nisaddcred(1M), nisauthconf(1M), nisclient(1M), nisinit(1M), nispopulate(1M), nisprefadm(1M), nis-
setup(1M), rpc.nisd(1M), attributes(5)NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 13 Dec 2001 nisserver(1M)