Major Solaris NIS Problems

We have a bunch of Solaris 2.5.1 servers that
are experiencing major NIS problems.  We have installed
NSKIT 1.2 (with appropriate patches).  We have all OS patches installed.  We are having problems in these areas:
- Autmount is not working properly (same subnet, fast machines) - it timesout mounting a share
- Logging in takes a long time to authenticate (Pc and UNIX side) and sometime authenticates correct passwords incorrectly.
- PC users cannot use NIS to do hostname resolution using a winsock application.
- Ypbind loses its binding to the domain often.
Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I have a very similar config as you (a NIS master, running 2.5.1 and having the NISKIT installed). I do not have your problems. Let me know more details about your config, the above is too common.

Only answer now: for hostname resolution you usually use a DNS service. You can do it within your NIS domain also, but I have not herad that there is NIS for PC's...

Peter (

saintjoesAuthor Commented:
We have NIS setup to DNS forwarding.  The client PC's are
using NIS as thier host name resolution.  The only odd thing in our setup is a SunOS master (these 2.5.1 machines are actually slaves, but are being used as NIS servers).
We have duplicated this on *3* Solaris 2.5.1 machines!

Again, there is no obvious problem. We also had here a SunOS
NIS master running successfully for quite a while. Now I have one master + one slave under Solaris 2.5(.1) + mixed (Solaris + SunOS) clients.

Hmm, it is difficult do help you, things have to be verified step by step. I hope I am not bothering you with trivialities, but just to make shure: did you activate the right /etc/nsswitch.conf file? I.e. did you copy nsswitch.nis to nsswitch.conf an all systems?

So some more questions: do you have automatic or static NIS server recognition? I.e. does ypbind run with -broadcast options? How did you install the clients? Did you run ypinit -c and did you then specify all master and slaves? I found that methode more stable then running dynamic binding (ypbind -broadcast).

Then you have to find for a given client (a slave might be regarded as a client) which is his master, use the ypwhich command on that machine. Try to isolate the problem, e.g. shut down all slaves and run with one master only.

To the slaves: did you add the crontab entries? Here an example from mine:

# run the ypxfr's to syncronize aldebaran (slave) with orion (master)
0 * * * * /usr/lib/netsvc/yp/ypxfr_1perhour
0 1 * * * /usr/lib/netsvc/yp/ypxfr_1perday
0 2,14 * * * /usr/lib/netsvc/yp/ypxfr_2perday

You might have to edit the ypxfr scripts to support the tables you need.

Then your automount problem: if you enter "ypcat" do you get the correct listing? I had to add en entry to /var/yp/Makefile for the support of the file. Also check in /etc/nsswitch.conf for the line "automount:  nis files" to be present.

Then the name resolution prob: look into /var/yp/Makefile (of your master) and make shure the the line "B=-b" is active. Does the name resolution work at all, i.e. does nslookup <address> work?

Last not least are the right daemons running? On the master (Solaris):
/usr/lib/netsvc/yp/ypserv -d
/usr/lib/netsvc/yp/rpc.yppasswdd -D

on the slave(s):
/usr/lib/netsvc/yp/ypserv -d

and on the clients:

Hope you get any idea from that,

Peter (


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I am confused...
you wrote in the comment to my answer:

"Another note: Clients wore fine if they use the SunOS machine as their nis master." and "But all clients are using the solaris machine as their master."

I conclude that you switched between master and slave server and found out that only the slave server give problems.

Question: does NIS work properly on the slave(s) itselve? Is there a difference between those slave(s)?

Again: I am not nervous about your master being a SunOS system. I had this situation here too for several years (also with previous Solaris versions).

What did you precisly do to "We have duplicated this on *3* Solaris 2.5.1 machines!"? "this" meaning the slave service.

How does your /etc/auto_master look like?

Peter (

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.