SUMMARY: NIS slave on different subnet

From: Patrick L. Nolan (
Date: Wed Apr 03 1996 - 13:10:14 CST


I was having trouble establishing an NIS slave server on a different
subnet from its master. There were obscure errors in ypbind and ypset.
The original posting is attached below.

A number of people pointed out the necessity of having the domainname
set properly. Some warned me to check the netmask, IP address, default
router, and securenets. Also ypinit -m needs to be run on the master to
declare the slave. The /var/yp directory must exist on the slave and the
master's IP address must be listed in the slave's /etc/hosts. These were
all OK.

There was no explanation for the problem, but there was a solution.
Some people pointed out that what I really want to accomplish is to
copy the contents of /var/spool/<domain>. Any means that works is
OK. So I quit messing around with the NIS programs and used ftp
to copy over the directory. Then I could just run ypserv and ypbind.

Here's the list of those who replied:

The original posting:
> A computer was moved to a different building with a new subnet. It needs
> to become an NIS slave server to function there. I've done this a
> couple of times before, but this time I'm stumped. I tried to follow
> this procedure:
> 1. /usr/etc/ypbind -ypsetme
> 2. /usr/etc/yp/ypset <IP address of master>
> 3. /usr/etc/yp/ypinit -s <master>
> Step 1 seems to work, but there's a delay of about 3 minutes before it
> returns. That's ominous.
> Step 2 sits for a couple of minutes and says this:
> ypbind: can't register tcp service
> ypset: Sorry, I can't set up upd connection to ypbind on host <slave>
> ypbind: going down on signal 6
> This is all mysterious to me. By the way, both <slave> and <master>
> are running SunOS 4.1.x. What's happening?

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:56 CDT