From owner-freebsd-questions Mon Jul 14 14:44:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15992 for questions-outgoing; Mon, 14 Jul 1997 14:44:27 -0700 (PDT) Received: from loos.ummu.umich.edu (loos.ummu.umich.edu [141.213.35.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15985 for ; Mon, 14 Jul 1997 14:44:20 -0700 (PDT) Received: from localhost (azuresky@localhost) by loos.ummu.umich.edu (8.8.5/8.8.3) with ESMTP id RAA02739 for ; Mon, 14 Jul 1997 17:43:43 -0400 (EDT) Message-Id: <199707142143.RAA02739@loos.ummu.umich.edu> X-Mailer: exmh version 1.6.7 5/3/96 X-URL: http://www.umich.edu/~azuresky/etc To: freebsd-questions@FreeBSD.org Subject: NIS woes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 17:43:41 -0400 From: Andrew Westrate Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I am trying to get NIS running on a small lan made up of just two machines (but soon to be a few more). I have set up the first machine as the server, and it starts ypserv when rebooted and creates all of the neccessary maps. I then set up the other machine as a client, and I think I have it running properly, because it starts ypbind, creates a file in /var/yp/bindings named after the proper domainname, and it complains that it can't reach the nis server when that machine is rebooted, BUT: in order to test nis, I added a new user to master.passwd on the server, rebooted both machines, and then tried to log in as that user on the client machine, and wasn't able to log in. So basically I don't know if I have it working in general, but only the passwd file isn't set up right, or if I have either the client or server or both set up improperly. Does anyone have any ideas about how to fix this, or at least about how to test it another way to see what works and what doesn't? Also, I would like to set up the server to also be a client, but the first time I did this, the machine wasn't able to boot because it was looking for the server at startup, but there was no server running yet. Does anyone know how to fix this too? Thanks, Andy Westrate