From owner-freebsd-questions Fri Mar 5 10:44:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fisicc-ufm.edu (unknown [209.198.197.200]) by hub.freebsd.org (Postfix) with ESMTP id 8720A151BB for ; Fri, 5 Mar 1999 10:44:09 -0800 (PST) (envelope-from solca@fisicc-ufm.edu) Received: from fisicc-ufm.edu (samsara.fisicc-ufm.edu [209.198.197.197]) by fisicc-ufm.edu (8.8.7/8.8.7) with ESMTP id MAA14979; Fri, 5 Mar 1999 12:49:34 -0600 (CST) (envelope-from solca@fisicc-ufm.edu) Message-ID: <36E0241E.828CDBB0@fisicc-ufm.edu> Date: Fri, 05 Mar 1999 12:36:14 -0600 From: "Otto E. Solares" Organization: FISICC-UFM X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.2 i686) X-Accept-Language: en MIME-Version: 1.0 To: John Kenagy , freebsd-questions@freebsd.org Subject: Re: NFS & NIS Problems References: <36DF4ADE.8A231CF5@fisicc-ufm.edu> <199903050433.WAA29491@bga.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Kenagy wrote: > Please let us know how your NIS is set up. Master server, any slave > servers? Has it ever worked? Check > > I would guess it is NIS trying to figure out who is logging in. Try to > give us as much detail as possible on how it is configured. > > Did you get NFS to work without NIS? Or, was it the other way around? > Probably, you should solve one at a time. We have only a master server "zeus.adm.fisicc-ufm.edu", no slaves, one NIS domain "olympia.fisicc" and all clients are in time synch with zeus. The clients used to be in the same network with the server (192.168.1.0) but that was when we was setting up the clients 1 by 1 so we have no chance to see if has the same problems, now each lab contains like 40 clients, we have 4 labs (lab1: 192.168.2.0 lab2: 192.168.3.0 lab3:192.168.4.0 and lab4: 192.168.5.0) The clients are almost 95% the day in windows and a few days we have like 60 in FreeBSD (student projects), very tipically it hangs in X with the user logged in and display a message like RPC time out. The server's link is @ 100Mb/s and the clients @ 10Mb/s. Each LAN is connected to 3Com switches and each switch is connected to a big 3Com switch (CoreBuilder) and are organized with VLANS. Each VLAN has a default router which is this CoreBuilder which do routing too. The server's NIC is 3Com 3c59x II Boomerang and client's NIC is Intel EtherExpress Pro 10/100B. When the client starts ypset, this say: ypset: sorry, cannot ypset for domain olympia.fisicc on host So after that we perform an ypset -setme and works with this problems. The server 's rc.conf says: # Network Information Services (NIS) options: ### nis_client_enable="YES" # We're an NIS client (or NO). nis_client_flags="" # Flags to ypbind (if enabled). nis_ypset_enable="NO" # Run ypset at boot time (or NO). nis_ypset_flags="" # Flags to ypset (if enabled). nis_server_enable="YES" # We're an NIS server (or NO). nis_server_flags="" # Flags to ypserv (if enabled). nis_ypxfrd_enable="NO" # Run rpc.ypxfrd at boot time (or NO). nis_ypxfrd_flags="" # Flags to rpc.ypxfrd (if enabled). nis_yppasswdd_enable="YES" # Run rpc.yppasswdd at boot time (or NO). nis_yppasswdd_flags="-t /var/yp/master.passwd" # Flags to rpc.yppasswdd (if enabled). And the client's rc.conf says: nisdomainname="olympia.fisicc" # Set to NIS domain if using NIS (or NO) # Network Information Services (NIS) options: ### nis_client_enable="YES" # We're an NIS client (or NO). nis_client_flags="-ypsetme" # Flags to ypbind (if enabled). nis_ypset_enable="YES" # Run ypset at boot time (or NO). nis_ypset_flags="zeus" # Flags to ypset (if enabled). nis_server_enable="NO" # We're an NIS server (or NO). nis_server_flags="" # Flags to ypserv (if enabled). nis_ypxfrd_enable="NO" # Run rpc.ypxfrd at boot time (or NO). nis_ypxfrd_flags="" # Flags to rpc.ypxfrd (if enabled). nis_yppasswdd_enable="NO" # Run rpc.yppasswdd at boot time (or NO). nis_yppasswdd_flags="" # Flags to rpc.yppasswdd (if enabled). Thank you in advance. Otto E. Solares To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message