From owner-freebsd-questions Wed Apr 22 16:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06647 for freebsd-questions-outgoing; Wed, 22 Apr 1998 16:57:33 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06622 for ; Wed, 22 Apr 1998 23:57:22 GMT (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id QAA25882; Wed, 22 Apr 1998 16:57:21 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 22 Apr 1998 16:57:20 -0700 (PDT) From: Doug White Reply-To: Doug White To: Sean Shilton cc: questions@FreeBSD.ORG Subject: Re: ypbind w subnets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Apr 1998, Sean Shilton wrote: > I am running a solaris/sparc 2.5.1 ypserver on one subnet, i have three > freebsd 2.2.6 NIS clients on the same subnet, and i have no problem with > thoose machines. I have on another subnet (100bt routed) three more > freebsd NIS clients. When they were running 2.2.5-Release, i had the nis > set up as: > ypbind -ypset > ypset master.nis.server > This ran without a problem, except that when the master.nis.server was > rebooted, the freebsd clients on the other subnet (not the subnet of > master.nis.server) would hang and login prompt (either on console, or > telnet) would hang after asking for the user name. I upgraded thoose > boxes to 2.2.6-Release and now when it boots with the > ypbind -ypset > ypset master.nis.server > it returns the error of cannset set for domain nis.server on > master.nis.server, the nis clients do work after that error message > however. And when the master.nis.server is reboot the 2.2.6 clients still > hang. Try running ypbind -S yourdomainname,master.nis.server I can understand if the FreeBSD boxes hang while the NIS server is rebooting -- it has to wait for it to come back up. If you want a few minutes the FreeBSD box should either start complaining about how the NIS server went SOL or start working again. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message