10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear all,
I am using solaris 10 OS.
I configured NIS server and i also configured NIS client server but when i use the command ypinit -s sunserv1 in NIS client it is showing me the below error.
Enumerates maps from sunserv1. please check that it is running. (2 Replies)
Discussion started by: bhargav90
2 Replies
2. UNIX for Advanced & Expert Users
Please do reply if anyone has done NIS server setup on redhat
Please let me know steps to do NIS server configuration on redhat & NIS client configuration on suse (2 Replies)
Discussion started by: timus1980
2 Replies
3. Solaris
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
4. Solaris
HI Unix Gurus
i am new to Solaris OS, i want to configure NIS CLient for Solaris 7 x86 Machine. i need what are the step and how to configure it in that machine.. please let me know
Thanks in Advance
Regards
..kiruba.. (2 Replies)
Discussion started by: nkkirubakaran
2 Replies
5. Solaris
Hi....,
I'm having two intel system.both the system i installed sun sol 10.now i wan't to configure NIS .Pls tell me step by step configuration for server and client.pls Help me any body......... :mad:
Rgds,
Jay (4 Replies)
Discussion started by: rjay.com
4 Replies
6. UNIX for Advanced & Expert Users
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies
7. Red Hat
I would like to know how to configure a Redhat 9.0 as NIS+ client. I have seen the post of larry, but it is not enough information for me to do the configuration. Could anyone tell me how to do it? Please help!
Thank you! (3 Replies)
Discussion started by: alexhon
3 Replies
8. UNIX for Dummies Questions & Answers
Hello all,
I wanted to know if any one had successfully install nis+ utils and use nis+ client on a linux (redhat) and have a Solaris nis+ server. I am able to install the client software on the linux and am able to see the nis+ tables. The passwd tables' works file but the auto_master and... (10 Replies)
Discussion started by: larry
10 Replies
9. UNIX for Dummies Questions & Answers
Hello all,
I am wondering if anyone had success with installing a redhat linux (PC box) on a Solaris NIS+ network. I have gotten information on how to do this but have been unsuccessful. The information that I have gotten is a little out dated and is not 100%. ... (0 Replies)
Discussion started by: larry
0 Replies
10. UNIX for Advanced & Expert Users
Hello all,
I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Discussion started by: larry
2 Replies
nisauthconf(1M) System Administration Commands nisauthconf(1M)
NAME
nisauthconf - configure NIS+ security
SYNOPSIS
nisauthconf [-v] [mechanism,...]
DESCRIPTION
nisauthconf controls which authentication flavors NIS+ should use when communicating with other NIS+ clients and servers. If the command
is not executed, then NIS+ will default to the AUTH_DES authentication flavor when running security level 2. See rpc.nisd(1M).
nisauthconf takes a list of authentication mechanism's in order of preference. An authentication mechanism may use one or more authentica-
tion flavors listed below. If des is the only specified mechanism, then NIS+ only use AUTH_DES with other NIS+ clients and servers. If
des is the first mechanism, then other authentication mechanism's after des will be ignored by NIS+, except for nisaddcred(1M). After
changing the mechanism configuration, the keyserv(1M) daemon must be restarted. Note that doing so will remove encryption keys stored by
the running keyserv process. This means that a reboot usually is the safest option when the mechanism configuration has been changed.
The following mechanisms are available:
+-----------------------------+-----------------------------+
| Authentication mechanism | Authentication Flavor |
+-----------------------------+-----------------------------+
|des |AUTH_DES |
+-----------------------------+-----------------------------+
|dh640-0 |RPCSEC_GSS using 640-bit |
| |Diffie-Hellman keys |
+-----------------------------+-----------------------------+
|dh1024-0 |RPCSEC_GSS using 1024-bit |
| |Diffie-Hellman keys |
+-----------------------------+-----------------------------+
If no mechanisms are specified, then a list of currently configured mechanisms is printed.
OPTIONS
-v Displays a verbose table listing the currently configured authentication mechanisms.
EXAMPLES
Example 1: Configuring a System with only RPCSEC_GSS Authentication Flavor
To configure a system to use only the RPCSEC_GSS authentication flavor with 640-bit Diffie-Hellman keys, execute the following as root:
example# /usr/lib/nis/nisauthconf dh640-0
Example 2: Configuring a System with both RPCSEC_GSS and AUTH_DES Authentication Flavors
To configure a system to use both RPCSEC_GSS (with 640-bit Diffie-Hellman keys) and AUTH_DES authentication flavors:
example# /usr/lib/nis/nisauthconf dh640-0 des
Example 3: Transitioning to Other Authentication Flavors
The following example can be used while adding credentials for a new mechanism before NIS+ is authenticating with the new mechanism:
example# /usr/lib/nis/nisauthconf des dh640-0
Note that except for nisaddcred(1M), NIS+ will not use mechanisms that follow 'des.'
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/etc/rpcsec/nisplussec.conf
NIS+ authentication configuration file. This file may change or be removed in future versions of Solaris.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO
nis+(1), keyserv(1M), nisaddcred(1M), rpc.nisd(1M), attributes(5)
NOTES
A NIS+ client of a server that is configured for either dh640-0 or dh1024-0 must run Solaris 7 or later, even if the server is also config-
ured with des.
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 12 Dec 2001 nisauthconf(1M)