Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Feb 2001 20:15:36 +0100 (CET)
From:      "O. Hartmann" <ohartman@ipamzlx.physik.uni-mainz.de>
To:        <freebsd-questions@freebsd.org>
Cc:        <freebsd-stable@freebsd.org>
Subject:   NIS/YP massiv problems ...
Message-ID:  <Pine.BSF.4.33.0102191957370.642-100000@klima.physik.uni-mainz.de>

next in thread | raw e-mail | index | archive | help
Hello.
I'm sorry bothering you again.
As I posted priorly here, NIS/YP does a lot of nasty things to me.
The last weekend our whole server systems were down.

The problem:
OS: FreeBSD 4.2-STABLE as cvsupdated today the last time

In my defined domain, I can not contact neither the local ypserver
nor a remote ypserver. I set up the master server without being
NIS client. /var/yp/securenets reflect localhost's address and the LAN's
address and mask. I set up /var/yp/securenets on all NIS servers (master
and slaves). portmap is running. ypserv is running on each machine.
I used 'ypbind -s -S_DOMAINNAME_,local_yp_slave,remote_master,remote_slave'
as described in the manpage to bind ypbind on a slave server to the
local server. But that is not working! The ypbind daemon can not
communicate with its server on the same machine. ypcat does not work.
Login procedures take a lot of time.Against other opinions here it seems
that NIS/YP is dependends on tcpwrapper, but I witched off tcpwrapper
or set first line to ALL:ALL:allow. I switched off IPFW due suspecting the
IP filter filtering UDP packets from portmapper. Nothing of that helped.

On a considered slave server I can not run DHCP/TFTP with ypserv and ypbind,
after this machine offerd IPs to its clients successfully, it drops by
TFTP timeouts. This is not when NIS/YP is not running.

I feel a little bit helpless this moment. Not the smallest, little
configuration will work! Why is ypbind unable to contact a ypserv
daemon on the same machine? I checked three times whether domainname
is set up correctly, checked for the proper setup of /etc/passwd,
group etc ... No chance to get it running.

Another very suspicious behaviour revealed keyserv. I want to set up
SecureRPC (but it was disabled when I tried to test how I could get
YP running and working).
On the master server, keyserv is running (keyserv -d -v). Additionaly,
rpc.ypupdated is also running, ypserv (ypserv -n) runs, too.
I tried to set up a hostkey for the local host, gave newkey -h master-server.
name, enterd passowrd ...
Then I wanted to create the /etc/.rootkey by keyserv -n, but after typing again the
password I gave prior, I received an error. keyserv was unable to decrypt the
given password ...

Please help ...

--
MfG
O. Hartmann

ohartman@mail.physik.uni-mainz.de
----------------------------------------------------------------
IT-Administration des Institut fuer Physik der Atmosphaere (IPA)
----------------------------------------------------------------
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz

Tel: +496131/3924662 (Maschinensaal)
Tel: +496131/3924144
FAX: +496131/3923532



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0102191957370.642-100000>