HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NIS udp error
Operating System - HP-UX
1837527
Members
3754
Online
110117
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2002 01:48 PM
01-09-2002 01:48 PM
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.
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.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2002 01:58 PM
01-09-2002 01:58 PM
Solution
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..
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..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2002 02:01 PM
01-09-2002 02:01 PM
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2002 02:06 PM
01-09-2002 02:06 PM
Re: NIS udp error
Hi Jonathan,
Try these links from hp docs site,
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1031-90048/B1031-90048_top.html&con=/hpux/onlinedocs/B1031-90048/00/00/24-con.html&toc=/hpux/onlinedocs/B1031-90048/00/00/24-toc.html&searchterms=nis.client&queryid=20020109-140958
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1031-90048/B1031-90048_top.html&con=/hpux/onlinedocs/B1031-90048/00/00/43-con.html&toc=/hpux/onlinedocs/B1031-90048/00/00/43-toc.html&searchterms=nis.client&queryid=20020109-140958
Hope this helps.
Regds
Try these links from hp docs site,
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1031-90048/B1031-90048_top.html&con=/hpux/onlinedocs/B1031-90048/00/00/24-con.html&toc=/hpux/onlinedocs/B1031-90048/00/00/24-toc.html&searchterms=nis.client&queryid=20020109-140958
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1031-90048/B1031-90048_top.html&con=/hpux/onlinedocs/B1031-90048/00/00/43-con.html&toc=/hpux/onlinedocs/B1031-90048/00/00/43-toc.html&searchterms=nis.client&queryid=20020109-140958
Hope this helps.
Regds
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP