- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS domain AAA not bound
Operating System - HP-UX
1753725
Members
4492
Online
108799
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
05-01-2000 11:54 PM
05-01-2000 11:54 PM
NIS domain AAA not bound
Hi Everybody,
We have an NIS domain here. The network guy change one of the client's IP to
another network segment. ( change from 55.219.x.x to 55.9.y.y ) But the NIS
master, slave and other clients' IP remain the same. On this particular
client, after I did a ypbind, I checked ypwhich . It gives me the error
message: NIS domain AAA not bound.
I have changed all the related hosts information of both this client and the
master.
Does anybody know how to fix it? Thanks in advance!
We have an NIS domain here. The network guy change one of the client's IP to
another network segment. ( change from 55.219.x.x to 55.9.y.y ) But the NIS
master, slave and other clients' IP remain the same. On this particular
client, after I did a ypbind, I checked ypwhich . It gives me the error
message: NIS domain AAA not bound.
I have changed all the related hosts information of both this client and the
master.
Does anybody know how to fix it? Thanks in advance!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2000 12:27 AM
05-02-2000 12:27 AM
Re: NIS domain AAA not bound
An NIS client gets its configuration information from an NIS master server or
an NIS slave server. When an NIS client is started, it sends out a broadcast
message requesting a server. Any server on the client's network that holds the
NIS maps for the client's domain may respond to the message. The NIS client
"binds" to the first server to respond to its broadcast message, and that
server answers all the client's queries for information.
Check to see if the nis client is in the same subnet as the master.
NIS works based on broadcast response. If the master is in a different
subnet then you will need to define that information in the file:
/etc/rc.config.d/namesvrs
modify:
YPBIND_OPTIONS="-ypset"
YPSET_ADDR=ip_address_of_the_master_server
stop / start the nis client:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
Berlene
an NIS slave server. When an NIS client is started, it sends out a broadcast
message requesting a server. Any server on the client's network that holds the
NIS maps for the client's domain may respond to the message. The NIS client
"binds" to the first server to respond to its broadcast message, and that
server answers all the client's queries for information.
Check to see if the nis client is in the same subnet as the master.
NIS works based on broadcast response. If the master is in a different
subnet then you will need to define that information in the file:
/etc/rc.config.d/namesvrs
modify:
YPBIND_OPTIONS="-ypset"
YPSET_ADDR=ip_address_of_the_master_server
stop / start the nis client:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
Berlene
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP