- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS problem with a Linux master server
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
Forums
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
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
тАО08-27-2001 01:41 PM
тАО08-27-2001 01:41 PM
NIS problem with a Linux master server
Any suggestions??
Many thanks..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2001 12:48 PM
тАО08-29-2001 12:48 PM
Re: NIS problem with a Linux master server
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100007 2 tcp 1028 ypbind
100007 2 udp 1029 ypbind
100007 1 tcp 1028 ypbind
100007 1 udp 1029 ypbind
100004 2 udp 718 ypserv
100004 2 tcp 719 ypserv
100004 1 udp 718 ypserv
100004 1 tcp 719 ypserv
If you get an error, there could be something wrong with RPC services. Should restart rpc (or dce). Best to bounce the box when doing this.
Tony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2001 01:11 PM
тАО08-29-2001 01:11 PM
Re: NIS problem with a Linux master server
/etc/nsswitch.conf:
passwd: compat
group: compat
Also, if you add HP-UX slaves, you will NOT be able to push maps from the master to the slaves as the NIS implementations are not compatible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2001 12:17 PM
тАО08-31-2001 12:17 PM
Re: NIS problem with a Linux master server
ypbind uses the broadcast address of the NIC to request a bind from any nis server on the lan. Check that you can ping the broadcast address from the HP and see the linux reply. If you can't one of the two has to change it's netmask. If the HP is on a different subnet you will need to use the ypset option of ypbind.
Edit /etc/rc.config.d/namesvrs and set
YPBIND_OPTIONS="-ypset"
YPSET_ADDR=
Then stop/start nis.client
/sbin/init.d/nis.client [stop | start]
If neither of these steps fix the problem
check /var/yp/secureservers. If used in your
nis domain it must have the ip address of the
servers you allow bining to.
Don't know if the linux supports securenets but check its config for that file which, if
in use, must have the ip address of the client.
For more info see ypbind(1m)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2001 05:58 AM
тАО09-01-2001 05:58 AM
Re: NIS problem with a Linux master server
Yes,check for the following..
* domainname
This should return the same domain as the Linux Server
* ps -aef | grep yp
This should return ypbind
* Even if it returns try stopping and restart the NIS Client
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
* Make sure both Linux and UR HP Client is there in the same subnet..
Basicaly ypbind broadcasts to fing ypserv and thus U need to have the Linux server in the same subnet as of the client..
If not try using ypset
Sundar