Operating System - HP-UX
1822505 Members
2377 Online
109642 Solutions
New Discussion юеВ

NIS problem with a Linux master server

 
John Henrikson
Regular Advisor

NIS problem with a Linux master server

I'm trying to set up as a Master NIS server a Linux machine that does not run the ypxfrd daemon.. this machine works fine as a master server for other Linux machines but I can't get my HP machine to bind to it..
Any suggestions??
Many thanks..

4 REPLIES 4
Anthony deRito
Respected Contributor

Re: NIS problem with a Linux master server

ypbind uses RPC services at the session layer. Use rpcinfo -p [hostname_of_linux_box] from your HP box. If RPC services are working on both sides, you should get a response something like this depending on what programs are registered with the portmapper:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100007 2 tcp 1028 ypbind
100007 2 udp 1029 ypbind
100007 1 tcp 1028 ypbind
100007 1 udp 1029 ypbind
100004 2 udp 718 ypserv
100004 2 tcp 719 ypserv
100004 1 udp 718 ypserv
100004 1 tcp 719 ypserv

If you get an error, there could be something wrong with RPC services. Should restart rpc (or dce). Best to bounce the box when doing this.

Tony
Charles Slivkoff
Respected Contributor

Re: NIS problem with a Linux master server

I've got a Linux NIS master here myself and have several HP-UX clients, running 10.01 through 11.11. All clients need to have the "+" entry in passwd & group. In addition, the 11.x systems need to have passwd and group services configured in "compatibility" mode.



/etc/nsswitch.conf:



passwd: compat

group: compat



Also, if you add HP-UX slaves, you will NOT be able to push maps from the master to the slaves as the NIS implementations are not compatible.

Peter Van Sant
Advisor

Re: NIS problem with a Linux master server

John,

ypbind uses the broadcast address of the NIC to request a bind from any nis server on the lan. Check that you can ping the broadcast address from the HP and see the linux reply. If you can't one of the two has to change it's netmask. If the HP is on a different subnet you will need to use the ypset option of ypbind.

Edit /etc/rc.config.d/namesvrs and set

YPBIND_OPTIONS="-ypset"
YPSET_ADDR=

Then stop/start nis.client

/sbin/init.d/nis.client [stop | start]

If neither of these steps fix the problem
check /var/yp/secureservers. If used in your
nis domain it must have the ip address of the
servers you allow bining to.

Don't know if the linux supports securenets but check its config for that file which, if
in use, must have the ip address of the client.

For more info see ypbind(1m)
Sundar_7
Honored Contributor

Re: NIS problem with a Linux master server


Yes,check for the following..

* domainname

This should return the same domain as the Linux Server

* ps -aef | grep yp

This should return ypbind

* Even if it returns try stopping and restart the NIS Client

/sbin/init.d/nis.client stop

/sbin/init.d/nis.client start

* Make sure both Linux and UR HP Client is there in the same subnet..

Basicaly ypbind broadcasts to fing ypserv and thus U need to have the Linux server in the same subnet as of the client..

If not try using ypset

Sundar
Learn What to do ,How to do and more importantly When to do ?