Sponsored Content
Full Discussion: NIS Client issues
Operating Systems Solaris NIS Client issues Post 302301741 by Keepcase on Friday 27th of March 2009 10:08:06 PM
Old 03-27-2009
This is my master server

# hostname
master

#domainname
domain.com

# cat /etc/hosts

#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
192.168.2.55 master loghost
192.168.2.60 client

# ping client
client is alive
# ping 192.168.2.60
192.168.2.60 is alive

# svcs -a | grep nis
disabled 21:45:18 svc:/network/rpc/nisplus:default
disabled 21:45:19 svc:/system/patch-finish:delete
online 21:45:53 svc:/network/nis/update:default
online 21:45:56 svc:/network/nis/server:default
online 21:45:56 svc:/network/nis/xfr:default
online 21:45:56 svc:/network/nis/passwd:default
online 21:46:00 svc:/network/nis/client:default

# rpcinfo -p localhost
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100028 1 tcp 32771 ypupdated
100028 1 udp 32772 ypupdated
100069 1 udp 32773
100069 1 tcp 32774
100004 2 udp 1023 ypserv
100004 1 udp 1023 ypserv
100004 1 tcp 1017 ypserv
100004 2 tcp 32775 ypserv
1073741824 2 udp 32774
100009 1 udp 1022 yppasswdd
100007 3 udp 32781 ypbind
100007 2 udp 32781 ypbind
100007 1 udp 32781 ypbind
100007 3 tcp 32776 ypbind
100007 2 tcp 32776 ypbind
100007 1 tcp 32776 ypbind

# cat /etc/nsswitch.conf
#
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# ident "@(#)nsswitch.files 1.14 06/05/03 SMI"

#
# /etc/nsswitch.files:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any naming service.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.

passwd: files
group: files
hosts: files dns
ipnodes: files
networks: files
protocols: files
rpc: files
ethers: files
netmasks: files
bootparams: files
publickey: files
# At present there isn't a 'files' backend for netgroup; the system will
# figure it out pretty quickly, and won't use netgroups at all.
netgroup: files
automount: files
aliases: files
services: files
printers: user files

auth_attr: files
prof_attr: files
project: files

tnrhtp: files
tnrhdb: files

Last edited by Keepcase; 03-27-2009 at 11:15 PM..
 

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. Solaris

NIS - Client Not loggin in

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)
Discussion started by: Renjesh
5 Replies

6. AIX

AIX NIS Client to Linux

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)
Discussion started by: aloneattack
20 Replies

7. Solaris

Solaris 10 NIS Client

Hi all, Recently i have implemented NIS functionality in solaris 10 and i have created server and client with user in server side by giving useradd -d /export/home/user1 -m -s /bin/sh user1 after that I went to /var/yp dir and give /usr/ccs/bin/make so that it will refelect to client... (2 Replies)
Discussion started by: esungoe
2 Replies

8. Solaris

Problem with NIS client

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)
Discussion started by: naw_deepak
0 Replies

9. 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

10. HP-UX

NIS Master and Client problem

I have a NIS Master server and NIS Clients. But when I started the service all the process and files that should be owne by root apper by the owner 0 This is an example 0 1709 1708 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1710 1709 0 10:06:10 ? 0:00 /usr/sbin/nfsd 4 0 1708 1 0 10:06:10 ? 0:00... (2 Replies)
Discussion started by: GCSG
2 Replies
RPCINFO(8)						    BSD System Manager's Manual 						RPCINFO(8)

NAME
rpcinfo -- report RPC information SYNOPSIS
rpcinfo [-m | -s] [host] rpcinfo -p [host] rpcinfo -T transport host prognum [versnum] rpcinfo -l [-T transport] host prognum [versnum] rpcinfo [-n portnum] -u host prognum [versnum] rpcinfo [-n portnum] [-t] host prognum [versnum] rpcinfo -a serv_address -T transport prognum [versnum] rpcinfo -b [-T transport] prognum versnum rpcinfo -d [-T transport] prognum versnum DESCRIPTION
rpcinfo makes an RPC call to an RPC server and reports what it finds. In the first synopsis, rpcinfo lists all the registered RPC services with rpcbind on host. If host is not specified, the local host is the default. If -s is used, the information is displayed in a concise format. In the second synopsis, rpcinfo lists all the RPC services registered with rpcbind, version 2. Also note that the format of the information is different in the first and the second synopsis. This is because the second synopsis is an older protocol used to collect the information displayed (version 2 of the rpcbind protocol). The third synopsis makes an RPC call to procedure 0 of prognum and versnum on the specified host and reports whether a response was received. transport is the transport which has to be used for contacting the given service. The remote address of the service is obtained by making a call to the remote rpcbind. The prognum argument is a number that represents an RPC program number. If a versnum is specified, rpcinfo attempts to call that version of the specified prognum. Otherwise, rpcinfo attempts to find all the registered version numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version. Note: the version number is required for -b and -d options. OPTIONS
-T transport Specify the transport on which the service is required. If this option is not specified, rpcinfo uses the transport specified in the NETPATH environment variable, or if that is unset or null, the transport in the netconfig(5) database is used. This is a generic option, and can be used in conjunction with other options as shown in the SYNOPSIS. -a serv_address Use serv_address as the (universal) address for the service on transport to ping procedure 0 of the specified prognum and report whether a response was received. The -T option is required with the -a option. If versnum is not specified, rpcinfo tries to ping all available version numbers for that program number. This option avoids calls to remote rpcbind to find the address of the service. The serv_address is specified in universal address format of the given trans- port. -b Make an RPC broadcast to procedure 0 of the specified prognum and versnum and report all hosts that respond. If transport is speci- fied, it broadcasts its request only on the specified transport. If broadcasting is not supported by any transport, an error message is printed. Use of broadcasting should be limited because of the potential for adverse effect on other systems. -d Delete registration for the RPC service of the specified prognum and versnum. If transport is specified, unregister the service on only that transport, otherwise unregister the service on all the transports on which it was registered. Only the owner of a service can delete a registration, except the super-user who can delete any service. -l Display a list of entries with a given prognum and versnum on the specified host. Entries are returned for all transports in the same protocol family as that used to contact the remote rpcbind. -m Display a table of statistics of rpcbind operations on the given host. The table shows statistics for each version of rpcbind (ver- sions 2, 3 and 4), giving the number of times each procedure was requested and successfully serviced, the number and type of remote call requests that were made, and information about RPC address lookups that were handled. This is useful for monitoring RPC activi- ties on host. -n portnum Use portnum as the port number for the -t and -u options instead of the port number given by rpcbind. Use of this option avoids a call to the remote rpcbind to find out the address of the service. This option is made obsolete by the -a option. -p Probe rpcbind on host using version 2 of the rpcbind protocol, and display a list of all registered RPC programs. If host is not specified, it defaults to the local host. Note: Version 2 of the rpcbind protocol was previously known as the portmapper protocol. -s Display a concise list of all registered RPC programs on host. If host is not specified, it defaults to the local host. -t Make an RPC call to procedure 0 of prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. -u Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. EXAMPLES
To show all of the RPC services registered on the local machine use: example% rpcinfo To show all of the RPC services registered with rpcbind on the machine named klaxon use: example% rpcinfo klaxon The information displayed by the above commands can be quite lengthy. Use the -s option to display a more concise list: example$ rpcinfo -s klaxon program version(s) netid(s) service owner 100000 2,3,4 local,tcp,udp,tcp6,udp6 rpcbind super-user 100008 1 udp,tcp,udp6,tcp6 walld super-user 100002 2,1 udp,udp6 rusersd super-user 100001 2,3,4 udp,udp6 rstatd super-user 100012 1 udp,tcp sprayd super-user 100007 3 udp,tcp ypbind super-user To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use: example% rpcinfo -T tcp klaxon prognum versnum To show all RPC services registered with version 2 of the rpcbind protocol on the local machine use: example% rpcinfo -p To delete the registration for version 1 of the walld (program number 100008 ) service for all transports use: example# rpcinfo -d 100008 1 or example# rpcinfo -d walld 1 SEE ALSO
rpc(3), netconfig(5), rpc(5), rpcbind(8) August 18, 1992
All times are GMT -4. The time now is 08:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy