1837527 Members
3754 Online
110117 Solutions
New Discussion

Re: NIS udp error

 
SOLVED
Go to solution
Jonathan F. Van Avery
Occasional Contributor

NIS udp error

I have a N-class server running HP-UX 11.00. When I try to run "nis.client start" I get the follow error :

ypbind Failure Code 1
calling ypset with x.x.x.x (the server IP)
Sorry, I can't set up udp connection to ypbind on host severname.

Thanks for any help.
3 REPLIES 3
Uday_S_Ankolekar
Honored Contributor
Solution

Re: NIS udp error

Hi,

1.mv /var/yp/secureservers /var/yp/secureservers.save

Restart NIS client /sbin/init.d/nis.client start

2. Also check your broadcast address by
ifconfig lan0
If you find different IP address then normal change it. You can do it by SAM.

Then restart NIS cleint again



-USA..
Good Luck..
S.K. Chan
Honored Contributor

Re: NIS udp error

From Knowledge Base ..

Look on the NIS Client and check the /var/yp/secureservers file and the IP Broadcast address using these two procedures.

FIRST POSSILBE CAUSE: /var/yp/secureservers

Most often we have seen this problem occur because /var/yp/secureservers has been modified or tampered with. Although you may not think it has been modified in any way, we find the best solution is as follows:

First, move /var/yp/secureservers out of the way
# mv /var/yp/secureservers /var/yp/secureservers.save

Second, restart NIS client: /sbin/init.d/nis.client start
If the problem is resolved then the /var/yp/secureservers file was the cause.
This file provides a marginal assurance that you are binding to a valid NIS server as a security measure. However, it is often incorrectly configured and/or out of date after a network configuration change. The securenets(4) man page provides documentation of both the /var/yp/securenets (NIS Server)and /var/yp/secureserverss (NIS Client). A template copy is also available in /usr/newconfig/var/yp/secureservers .

If this first procedure did not resolve the problem, then continue on debugging with the next procedure.


SECOND POSSIBLE CAUSE: IP Broadcast address incorrect.

Less often we have seen this problem occur if the broadcast address of the Lan interface(s) isn't as expected.

First, Use the ifconfig against each of the lan interfaces to check the IP broadcast address. If it is not correct, use the following steps in this procedure to see if it resolves the problem.

Example of IP broadcast address appearing as expected:

# ifconfig lan0
lan0: flags=843 inet 145.17.184.50 netmask ffffff00 broadcast 145.17.184.255

Example of broadcast address appearing incorrectly:

# ifconfig lan0
lan0: flags=843 inet 145.17.184.50 netmask ffffff00 broadcast 145.17.184.128

Second, correct the IP address if it was incorrect. You can either use SAM ->Networking/Communications -> Network Interface Cards to change, or the ifconfig command to resolve it. For example:

# ifconfig lan0 inet 145.17.184.50 netmask 255.255.255.0

Check your change with:
# ifconfig lan0

Third, try /sbin/init.d/nis.client start to see if the problem is resolved.

Fourth, if the problem is resolved, and if you did NOT use SAM to change the broadcast address, you need to edit /etc/rc.config.d/netconf file entry for the lan card's NETMASK and BROADCAST values.