is this the only client that you have tried on this particular server ? (i.e.
do you know, for a fact that the server is set up correctly ?)
generally:
on server
- set NISDOMAIN in /etc/sysconfig/network
- in /etc/yp.conf set a line like this:
domain <the NISDOMAIN name> server <the server hostname>
put <the server hostname> in all /etc/hosts files, clients included
or they will not be able to find the server (of course you can
broadcast, but I prefer the more direct approach).
- run ypinit (i.e. /usr/lib/yp/ypinit -m)
enter your hostname.
- make sure thatt he following services are started in your runlevel
portmapper
ypbind
yppasswdd
ypserv
(order of starting these is important, but most run level config
utilities have sane defaults)
- reboot (this actually is a requirement, given the RH setup, though
if you REALLY know what you are doing, you can avoid the reboot). The
problem is that the NISDOMAIN is only read in /etc/rc.sysinit, and
not as part of an /etc/rc.d/init.d start-stop file.
on client
- set NISDOMAIN in /etc/sysconfig/network
- in /etc/yp.conf set a line like this:
domain <the NISDOMAIN name> server <the server hostname>
put <the server hostname> in all /etc/hosts files, clients included
or they will not be able to find the server (of course you can
broadcast, but I prefer the more direct approach).
- make sure thatt he following services are started in your runlevel
portmapper
ypbind
(order of starting these is important, but most run level config
utilities have sane defaults)
- either reboot, or start portmapper, stop (if runing) then start
ypbind.
- a "ypwhich" will tell you which host it finds as your ypserver.
Note: the value that you chose for NISDOMAIN is arbitrary, and I do not believe
that there is an 8 character limitation. I do think that it is case-sensitive
though. i.e. the value assigend in sysconfig/network script must match the value
in yp.conf
hope that the above helps.
-Greg
On 09-Mar-2002 Nicholas Reese wrote:
>
> Hi all,
>
> using Redhat 7.1
>
> Standard disclaimer: have read all howtos, looked through the archives, read
> all available books, worked on system for three days
>
>
> I have the NIS server up and running OK - passes all the tests and seems to
> have no problems. I have set the client on install to use NIS, and have also
> checked out the setup on the clients manually after install.I can ping and
> use NFS on the NIS server.
>
> On boot up I get the following:
>
> Binding to the NIS domain [OK]
> Listening for an NIS domain server [failed]
>
> I just can't seem to get the client to see the NIS server. Would anyone have
> any suggestions?
>
> Regards,
>
> Nick Reese
>
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://lists.slug.org.au/listinfo/slug
+---------------------------------------------------------------------+
You can release software that's good, software that's inexpensive, or
software that's available on time. You can usually release software
that has 2 of these 3 attributes -- but not all 3.
| Greg Hosler [EMAIL PROTECTED] |
+---------------------------------------------------------------------+
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
