From owner-freebsd-questions Sun Oct 3 15:30:11 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id DE1D214D60; Sun, 3 Oct 1999 15:30:08 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.137]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6B3F; Mon, 4 Oct 1999 00:30:07 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA60954; Mon, 4 Oct 1999 00:19:56 +0200 (CEST) (envelope-from asmodai) Date: Mon, 4 Oct 1999 00:19:56 +0200 From: Jeroen Ruigrok/Asmodai To: Chris Conrad Cc: freebsd-questions@freebsd.org, des@freebsd.org Subject: Re: Problems with NIS Message-ID: <19991004001956.J35757@daemon.ninth-circle.org> References: <19991002234621.A5817@syru205-140.syr.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991002234621.A5817@syru205-140.syr.edu> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On [19991003 08:18], Chris Conrad (chconrad@syr.edu) wrote: >Here's the situation. I've got 2 machines on a network. The gateway >machine (myrdraal) has 2 NIC's, one connected to the outside world, >and the other to my LAN. This machine is running VA Linux System's >distribution of linux (kernel version 2.2.7 with patches for the DoS >attack). ypserv (version 1.3.6.91 according to rpm -q) is running on >this machine. It is also running ypbind and it successfully binds to >itself. The second machine (caemlyn) is running FreeBSD-STABLE (I cvsup'd >everything and did a make world yesterday). Both of the names I gave >are thier names on the LAN. > >The problem is, the FreeBSD machine will not bind to the ypserv >running on myrdraal. The nisdomainname is identical on both machines. >After running ypbind on caemlyn, it returns immediately without error. ypwhich >however, gives an error saying that ypbind could not bind to the >domain. I tried running ypserv on the FreeBSD machine and having it >bind to itself and that worked. Also, the linux machine had no >problems binding to the FreeBSD ypserv. Hmm, Robert Jordan fan, cool ;) Anyways, what people unfortunately forget is that FreeBSD's NIS support is actually a NIS+ implementation. Do you have any /var/log/messages output you could paste to give a better idea of the situation as well as any config files? Also, I cc:-d Dag-Erling, since I believe he knows more about NIS in depth than I do. If this isn't DES, please cc: the person who does know. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Fame is the perfume of heroic deeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message