NIS client on HPux 10.20 - HP712/100WS

[Moujahid]

I do not get a HPux WS bound to a Linux NIS server (Suse8).
NIS server IP: 192.168.200.2/24
NIS Client IP: 192.168.203.110/24

ping is working from both directions.

the clinet config:
/etc/rc.config.d/namesvrs
============================
NIS_MASTER_SERVER=0
NIS_SLAVE_SERVER=0
NIS_CLIENT="1"
NIS_DOMAIN="fi-umts-lab"
WAIT_FOR_NIS_SERVER=FALSE
MAX_NISCHECKS=3
YPSERV_OPTIONS=""
YPBIND_OPTIONS="-ypset"
YPPASSWDD_OPTIONS="/etc/passwd -m passwd PWFILE=/etc/passwd"
KEYSERV_OPTIONS=""
YPUPDATED_OPTIONS=""
YPXFRD_OPTIONS=""
YPSET_ADDR="192.168.200.2"
============= ENDE ==========

Domainname set to fi-umts-lab

but when I issue the:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start

I get the folowing error:
==============================
bash-2.05# ./nis.client stop
bash: ./nis.client: No such file or directory
bash-2.05# cd /sbin/init.d/
bash-2.05# ./nis.client stop
stopping ypbind
stopping keyserv
bash-2.05# ./nis.client start
starting NIS CLIENT networking
starting up the portmapper
\tportmap already started, using pid: 638
\tdomainname fi-umts-lab
starting up the Network Information Service
\tstarting up the ypbind daemon
FAILURE CODE: 1
\tcalling ypset with 192.168.200.2
Sorry, I can't set up a udp connection to ypbind on host ws3.de.lu.
Checking NIS binding.
Bound to NIS server using domain fi-umts-lab.
\tstarting up the keyserv daemon
\t/usr/sbin/keyserv
==============================
I do not know what to change on the UDP stack and the NIS server(Ethereal running) doesn't get any packets from the client.

Can some body may be tell me what I'm doing wrong.

by the way to set up the HP NIS client I used first the SAM then later on the procedure descripted on the:
"http://docs.hp.com/servlets/iknow/iKtypeB?INFO_TYPE=how&Action=configuring&Item=NIS&INFO_TYPE_CHANGED=false&Topic_Area=Networking&Sub_Topic=Network+Information+Services+%28NIS+and+NIS%2B%29&MODE_A=NOMASTER&MODE_I=NOMASTER"

but allways the same outcome.

Please help????

CU and tanx in advance
Moulay

[jean-yves poch]

ping 192.168.200.2

maybe a problem with the nemask or the default router.

[IT Response]

Are other boxes binding to this NIS server, also try on the HP workstation #rpcinfo -u ypbind. This will tell you if ypbind is available.

[Moujahid]

Yes, other boxes are binded to the NIS server (linux and solaris boxes).
Only HP WS won't bind.
bash-2.05# rpcinfo -u nissvr1.de.lucent.com ypbind
program 100007 version 1 ready and waiting
program 100007 version 2 ready and waiting
bash-2.05# rpcinfo -u 192.168.200.2 ypbind
program 100007 version 1 ready and waiting
program 100007 version 2 ready and waiting

[Darrick Schuch]

How about when you run a ps -ef |grep ypbind, does it show it set with the -ypset option on it? Also can you run a ypset manually once the box is up and have it bind? Is there a route to the NIS server? Try traceroute from both sides.

[CSSI]

Hi

I have the same problems

look at your /var/yp/secureservers
subnetmask is certainly wrong
comment line and re-run nis.client start