NIS setup/RPC:program not registered

[Norman Dignard]

HPUX 11i NIS master, 11.00 client - both on same subnet. Client not resolving UIDs/GIDs. Excuting nis_client start comes up find whic ypbind & keyserv processes, rpcbind already started, binds to NIS server.

/etc/nsswitch file has
passwd: compat
group: compat
hosts: nis [NOTFOUND=return] files
the rest of the sevices just say files.

Executing /var/yp/ypxfr_1perhour
ypxfr: can't mv /var/tmp/AAAa04069.pag to /var/yp/engdev/passwd.byname.pag
ypxfr: rename error: couldn't mv /var/tmp/AAAa04069 to /var/yp/engdev/passwd.byname
ypxfr: can't mv /var/tmp/AAAa04070.pag to /var/yp/engdev/passwd.byuid.pag
ypxfr: rename error: couldn't mv /var/tmp/AAAa04070 to /var/yp/engdev/passwd.byuid
root@dms_dev:/var/yp # mkdir engdev
root@dms_dev:/var/yp # ./ypxfr_1perhour
ypxfr: bind_to_server clntudp_create error: RPC: Program not registered

Manually creating the dir /var/yp/engdev gets rid of the mv errors but I still get the ypxfr msg.

Doing a manual ypxfr on the map gives me the same ypxfr message.

Whats wrong with my NIS setup?

[sven verhaegen]

hi

the important question here is : what is your patchlevel , this might be important because there is a known problem with hp-ux 11.x and NIS Slave serber binding on YPXFR being :

execute a ypxfr from a slave server with a hostname greater than 8 characters gets the following error message:

"ypxfr: bind_to_server clntudp_create error: RPC unknown host"

this looks a lot like your problem , the fix for this is installing the latest ONC NFS/NIS megapatch

This problem seems to have been addressed in relation to autofs in JAGab68200. The above fix was not working with the patch PHNE_16470. It's working fine with PHNE_22642 or later , so make sure you have at least that patch or later installed , make sure all dependency patches are installed as standard ONC NFS/NIS PATCHING HAS ABOUT 13 TO 15 DEPENDENCY PATCHES

[Norman Dignard]

I'm at PHNE_22625 patchlevel.

[Steve Labar]

Are you setting up an NIS client or an NIS slave server. NIS client does not require ypxfr commands. With "compat" in your nsswitch file, you need to define which NIS users/groups are allowed to login to the client. For users add lines to the end of your /etc/passwd file as follows:

+user1
+user2
...

Do the same thing for your /etc/group file:
+group1
+group2
...

If you are setting up an NIS slave server, you need to do a ypinit -m and follow the prompts to set up the domain slave.

[S.K. Chan]

The ypxfr is run to "synchronize" maps between 2 NIS servers, you don't run this on a NIS client because the map directory /var/yp/ is not suppose to exist in a NIS client machine at the first place.