Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО05-30-2001 01:52 AM
тАО05-30-2001 01:52 AM
i'm adding a NIS client. It's on a different subnet mask of the NIS master. To see the NIS master i have forced the client, modifying /etc/rc.config.d/namesvrs
YPBIND_OPTIONS="-ypset"
YPSET_ADDR="NIS_MASTER_SERVER_IP"
Without these options, i saw that the client doesn't work in NIS, i had a message like this:
NIS domain domain_name not bound.
Putting those options it works. My doubt is, if my nis master server is down, does the client switch to the slave or not, cause of forcing..
if it doesn't, is there any way to set somewhere subnet mask?
Solved! Go to Solution.
- Tags:
- NIS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 02:21 AM
тАО05-30-2001 02:21 AM
Re: NIS
propably your client may not binding to the NIS server domain, check whether have u specified the domain name in client.
which os does client is in?
later
ravi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 02:29 AM
тАО05-30-2001 02:29 AM
Re: NIS
/usr/bin/domainname nis_domain_name
Then i put it in the /etc/rc.config.d/namesvrs.
I think the problem regards the subnet. In fact any client under the same subnet of the nis master server works perfectly without -ypset option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 02:45 AM
тАО05-30-2001 02:45 AM
Re: NIS
if u'r NIS server is in another subnet , u have to give the -ypset option, it's better have one slave NIS slave server in every subnet , in that case there is no need of giving -ypset option.
raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 07:03 AM
тАО05-30-2001 07:03 AM
SolutionIt has nothing to do with the servers availability, but rather how the NIS client is looking for a server.
In standard NIS bindings, the client sends out a broadcast on its own broadcast address. A server has to be able to read this, and reply back for the negotiation of the connection. Since your server has a different broadcast address than the client, the broadcast for a server is not heard, so the server can not reply back.
Solutions:
1. Do as you already have and force ypbind to set to the server on the other subnet.
2. Create a larger subnet to encompass both networks, and propogate this netmask to all of your hosts.
Regards,
Shannon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 10:00 AM
тАО05-30-2001 10:00 AM