SunOS 4.1.X NIS+ binary problems

SunOS 4.1.X NIS+ binary problems

Post by Brian Stempi » Sun, 17 Jul 1994 09:20:11


I have a mixed network of a few Solaris 2.3 machines and a bunch of SunOS
4.1.3 machines. I have a Solaris 2.3 root server and I want to use a few
SunOS machines as Replicas and Subnet masters.

My first question is: Can this be done? Or am I wasting my time?

Right now I get the binaries installed and follow the directions to make it
an NIS+ client. At the stage where it tells you to do a keylogin -r I run
into the first problem. The program can't find the secret key. I can't make
one either since we do not have NIS running. I have the machine's
credentials loaded in the Root server, so I assume the SunOS machine can't
find them.

So, I tried running with security off, and I still can't get anywhere.
After I set up the root replica on the root side, and start rpc.nisd on the
replica I try doing an nisping. This fails and the logs on the client
machine are dated in December of 1969! This obviously sets the Time to live
field to 0. So I assume something is wrong with the communication between
the two machine types. I have installed the 2.3 recommended patches (even
the messed up 101318-50) and patch 100075-14 for the SunOS 4.1.3 side.

Can anyone help? Has anyone tried this particular configuration? The
compatibility mode seems to work ok, but with out Replicas etc we can't go
forward. Thanks in advance!

                                                         Brian Stempien
                                            Western Michigan University

                                           Voice:  (616)-387-5848


1. NIS,NIS+ on SunOS 4.1.x and Solaris 2.x

         1         2         3         4         5         6         7         8

Hello, all.

I have a Sparc 4/20 running SunOS 4.1.4, an Auspex enterprise file server
running its own modified SunOS 4.1.3x, a Sun 690 with Solaris 2.5, and
an UltraSparc 2 and a handful of Intel boxen running Solaris 2.6.

Currently, my 4/20 is the main RADIUS/user server.  We are currently
running no form of NIS.  The 4/20 is pretty overloaded, as the former
"sysadmin" believed in minimal effort, was scared of the Auspex, and
didn't know how to do things the right way.  He piled a bunch of services
onto this thing, and consequently, it's not very stable.

I'm trying to bring some of these other boxen in to take over services
currently being performed by the 4/20, which will allow me to eventually
take it offline long enough to nuke it and stick Solaris 2.6 on it.
However, I'm obviously going to need to do some sort of centalized
management such as NIS/NIS+, which I've not used before.

I've been downloading whitepapers left and right, and have persuaded my
boss to order some of the 2.6 documentation for me (I have the 4.1.4
books already), and have the O'Reilly _Managing NFS and NIS_ book, so
I've got plenty of reading, but I don't have anything currently that
really goes into detail about NIS+.

What is my best option here?  I'd prefer to go with NIS+, if I have to
do this at all, in order to keep things as secure as possible, but from
what I know, since I have the two 4.1.x boxen I can't do that.

How hard is it going to be to transfer the current password files off
of the 4.1.4 box into an NIS master?  Is there any reading material out
there that can help me gain some insight into this godawful mess I'm
about to plow into?

Thanks in advance; if you email me your responses, I'll compile the results
and post them here.


Chief Systems Administrator
Premier1 Internet Services

2. Reading is much more interesting than TV (1155/1708)

3. SunOS 4.1.3C NIS/DNS problems

4. Binary compatibility between Sco xenix and Sco unix

5. Problem with NIS group map on Sunos 4.1.x

6. NFS Installation

7. SunOS 4.1.x crypt binary needed.

8. Glibc 2.2.2 Make Check Errors (Repost)

9. sunos 4.1 binaries

10. Password aging with NIS under SunOS 4.1.x

11. Need help setting NIS+ replica on SunOS 4.1.x

12. SunOS 4.1 as NIS client

13. SunOS 4.1 / 4.1.1 / 4.1.1U_1 /usr/etc/rpc.yppasswdd doesn't work.