From owner-freebsd-questions Tue Dec 14 9: 0: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43]) by hub.freebsd.org (Postfix) with ESMTP id 7EB8E150BD for ; Tue, 14 Dec 1999 08:59:57 -0800 (PST) (envelope-from mkc@benge.graphics.cornell.edu) Received: from benge.graphics.cornell.edu (mkc@localhost) by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id LAA29860; Tue, 14 Dec 1999 11:59:54 -0500 (EST) (envelope-from mkc@benge.graphics.cornell.edu) Message-Id: <199912141659.LAA29860@benge.graphics.cornell.edu> To: Blake Swensen Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NIS -- Restricted mode access list?? In-Reply-To: Message from Blake Swensen of "Tue, 14 Dec 1999 08:45:48 PST." <3.0.16.19991214084511.2ff7baf4@phil.pyramus.com> Date: Tue, 14 Dec 1999 11:59:54 -0500 From: Mitch Collinsworth Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well from the text of the error message it sounds like ypbind is not recognizing XXX.XXX.XXX.XXX (itself) as being a member of the -S list. I don't use -S myself but I would suggest first substituting the IP address for the name in your -S list. If that makes the problem go away then you know the root of the problem is in resolving the name to the address and can narrow your search to that issue. For that matter you could probably just substitute 127.0.0.1 or localhost for the slave server's hostname in your -S list and be done with it. -Mitch >Yes... I am using -S (not -s). I figured that that I needed to do this, as >the ypbind man pages states "This option is used to insure that the system >binds only to one domain and only to one of the specified servers, which is >useful for systems that are both NIS servers and NIS clients..." > >Since both master and slave are both clients and servers, I figured that >this would be the most appropriate settings... ie. > >ypbind -S domain,masterserver,slaveserver > >Do you have more information on this? > >Peace, >Blake >At 10:55 AM 12/13/99 -0500, Mitch Collinsworth wrote: >> >>>OK, This is a weird thing with NIS.... My slave server started reporting >>>the problem: >>> >>>ypbind[129]: NIS server at XXX.XXX.XXX.XXX not in restricted mode access >>>list -- rejecting. >>> >>>Where the IP address is itself (not localhost). So ypbind on the slave is >>>connecting to my master server, and ypserv on the slave is running (as is >>>rpc.ypxfrd). But if I read this correctly, the slave is rejecting its own >>>IP address as if it does not have the proper permissions? >> >>Are your using any command line options on ypbind? I'm not familiar >>with this error but is sounds like maybe you're using -s or -S. If >>so you may find your answer in ypbind(8). >> >>-Mitch >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message