On Wed, 24 Oct 2007, Rudie, Tony wrote:
Are you running ypbind -broadcast? If so, you have to have ypserv running on the same subnet. The alternative is to add IP addresses to the (I think) /var/yp/binding/<domainname>/ypservers file, and then ypbind will not run in broadcast mode. We hate doing this because it's another item to maintain locally on every client.
I manually configured /etc/yp.conf with domain MY_NIS_DOMAIN server my_nis_server
I'll try the IP address scheme you show, and see what that does.
The other thing we are often able to do is get the network guys to add "helper" statements to the routers so that ypbind DOES get routed to specific (ypserver) hosts. I'm considerably fuzzy about how they do that, but I can get details if you're interested.
Both the test and production setups are on simple lans - server and clients are connected to an unmanaged switch, each with /etc/hosts acting as local dns.
Scott
- Tony Rudié -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ehrlich Sent: Wednesday, October 24, 2007 10:03 AM To: [email protected] Subject: [BBLISA] ypbind and ICMP host unreachable? Brief refresher again - RedHat Enterprise 5 server, CentOS 5 clients. Test setup, everything works fine. Production environment, clients cannot bind to yp on server. In trying to track down the ypbind problem I'm having, I discovered tcpdump produces ICMP host <yp server> unreachable only when ypbind is run. I'm doing some googling now to try and find an answer. I'd be happy to entertain any feedback this list has, too. Thanks. Scott _______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
_______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
