QUESTION:
I'm having trouble getting a fairly simple NIS environment up and
running. I looked through ASKQ and didn't find anything to help
so would like to describe the situation to you in hope that you will
sense the "obvious" mistake I made.
ENVIRONMENT: Two networks -- an ethernet and a token ring. Two RISCs
on ethernet only, two RISCs on token-ring only, one (the router/gateway)
on both. All systems running AIX 3.2.4.
One of the RISCs that is only on the token-ring is the Master Server.
There is no Slave Server. All other RISCs are set up as Clients.
The two other RISCs on the token-ring are able to get all of the
host and passwd information they want from the Master Server. The
ypwhich command shows that they are bound to the Master Server.
The two RISCs on the ethernet are able to ping, telnet, etc. to the
systems on the token-ring including the system which is acting as
the Master Server. I should point out that I can do this if I use
the IP address. If I use the hostname to ping or telnet, the request
hangs -- it can't resolve the host to IP address.
ypwhich on the two RISCs on the ethernet yields a message about not
being bound.
If I make the mistake of logging out before I stop the ypbind on one
of these RISCs I can't log back in -- even to root which is still
listed in the "local" /etc/passwd file. (Actually, I can log back in
as root, but I never get a prompt back after the motd. For other than
"locally" defined users -- ids defined above the NIS escape sequence
in /etc/passwd -- I can't log in at all -- get an invalid id or password
message.
So, the systems on the network which the Master Server is on work fine.
The RISC on the network which the Master Server isn't on aren't binding
to the Master Server. Got any ideas?
---------- ---------- ---------- --------- ---------- ----------
A: Before I address this question, I would like to provide some
background information on NIS.
When ypbind starts, it broadcasts for a NIS server. It will bind to
the first NIS server that responds. Unfortunately, ypbind broadcasts
do not go over subnets.
What is happening in your scenario is that the RISCs on the Ethernet
subnet are broadcasting for a NIS server, but these broadcasts are not
going over the router to the Token Ring subnet. Therefore, the RISCs
on the Ethernet cannot bind to the NIS server on the Token Ring.
The solution to this problem is to 'ypset' the NIS clients on the
Ethernet subnet.
After NIS is started and before you hang, issue the command
'ypset '.
The way to automate this is to make the following changes in the
/etc/rc.nfs file. This will issue the 'ypset' automatically everytime
you re-boot.
Your current /etc/rc.nfs file has the following lines:
if . -x /usr/etc/ypbind .; then
startsrc -s ypbind
fi
Change these lines to:
if . -x /usr/etc/ypbind .; then
startsrc -s ypbind
sleep 10
ypset
fi
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q649920 CNQRQ
Additional search words:
BIND CNQRQ COMMUNICATIO IX JAN94 MASTER NETWORK NETWORKING NETWORKS
NIS OZNEW RISCSYSTEM RISCTCP SERVER SOFTWARE SYSTEM TCPIP TP WON
WWQA: ITEM: RTA000037323 ITEM: RTA000037323
Dated: 04/1996 Category: RISCTCP
This HTML file was generated 99/06/24~12:43:14
Comments or suggestions?
Contact us