LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris
User Name
Password
Solaris / OpenSolaris This forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.

Notices


Reply
  Search this Thread
Old 04-01-2011, 06:57 PM   #1
brownwrap
Member
 
Registered: Jan 2010
Posts: 121

Rep: Reputation: 16
Trying to get NIS up


OK, I am trying to get NIS installed on Solaris 10. I've set up a machine as a master, and one other as a client. On the client side, in order to get ypwhich to work, I had to start up ypbind with "-broadcast", and both machine are on the same subnet. Otherwise, the client can't find the master. So for the minute, I have put that aside, and am now try to get some of the other commands to work, like ypcat. When I try a "ypcat hosts", I get rpc failures. The error on the client side says:

RPC failure on yp operation

In the log file on the client side I see:

yp_all - transport level create failure for domain ims / map group.byname: RPC: Rpcbind failure - RPC: Authentication error


And on the server side, I see:


Did not receive identification string from ... ip address.

And I see refused connect from ... .


So its something that is misconfigured, or being blocked, but I can't figure out what it is. Anyone seen this? Thanks.
 
Old 04-19-2011, 11:18 PM   #2
fsainsbu
LQ Newbie
 
Registered: Aug 2010
Posts: 5

Rep: Reputation: 1
What does nisdomainame return?
There were solaris help sites out there. I have done this before, but a few years ago,
 
Old 09-13-2018, 09:36 PM   #3
shgarg
LQ Newbie
 
Registered: Sep 2018
Posts: 1

Rep: Reputation: Disabled
Smile yp_all - transport level create failure for domain ims / map group.byname

Hi brownwrap,

Please find below explanation for the RPC transport failure issue.

Cause

At random times, a slave NIS server has a problem that causes ypbind(1M) to
report ypserver not responding, and the machine must be rebooted.

The syslog file contains the following:

Dec 14 07:11:03 rahab syslog: yp_all -
RPC clnt_call (transport level) failure:
RPC: Unable to receive; An event requires attention

Permanent Fix is : Reboot the server.

WORK Around ( Temperory Fix)

As a workaround, increase the file descriptor limit in the yp startup script,
/etc/rc2.d/S71rpc. Add this command to the script before ypserv is started:

ulimit -n 256


FIX for 2nd error :- RPC: Authentication error
--------------------


Cause
This is a Federated Naming Service message. The operation could not be completed
because the principal making the request could not be authenticated with the name
service involved.

Action
Run the nisdefaults(1) command to verify that you are identified as the correct
NIS+ principal. Also check that the system has specified the correct public key source

FIX for 3rd error :- RPC: Rpcbind failure

The remote file system needs to be shared on the remote host. Take a look at /etc/dfs/dfstab on the remote host. If the file system is shared look at the entry for -o entries. These are normally read/write restrictions that may be given to individual workstations or it can be groups as listed in /etc/netgroup.

If this doesn't resolves your issue, then check if the server is in dmz.
 
Old 09-25-2018, 03:47 PM   #4
MadeInGermany
Member
 
Registered: Dec 2011
Location: Simplicity
Posts: 903

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
For not broadcast binding, you need to create /var/yp/binding/`domainname`/ypservers with the name(s) of the NIS server(s), resolvable to IP addresses via /etc/inet/hosts.

Your NIS server might be protected. Then a
"ypwhich -m" still works but "ypmatch" or "ypcat" are prohibited.
Create /var/yp/securenets that allows your NIS client or your NIS client's network.
Code:
man securenets
Debugging
Code:
rpcinfo -p nisserver
must list "ypserv", and
Code:
rpcinfo -p nisclient
must list "ypbind".

On the NIS server have the following order in /etc/nsswitch.conf
Code:
hosts: files nis
ipnodes: files
services: files nis
networks: files nis
netmasks: files nis
protocols: files nis
rpc: files nis
The order "nis files" can cause a pontential race condition at service startup.
--
Regarding the previous post:
not helpful here - the solution is for Solaris 7 and older.

Last edited by MadeInGermany; 09-25-2018 at 04:06 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
NIS failed for one user on one NIS client - strange problem resolved catbird Linux - Networking 1 10-05-2009 11:00 AM
solaris nis server and linux nis client configuration soumalya Solaris / OpenSolaris 1 04-08-2008 11:25 PM
NIS: NIS running but users not able to log in with NIS credentials outerspace Linux - Server 3 10-17-2007 08:51 AM
How to setup a Solaris NIS client while with a Linux NIS server? ntcm Solaris / OpenSolaris 1 03-31-2004 06:10 AM
How to setup a Solaris NIS client while with a Linux NIS server? ntcm Linux - General 1 03-31-2004 06:10 AM

LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris

All times are GMT -5. The time now is 03:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration