From owner-freebsd-questions Mon Aug 24 08:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07519 for freebsd-questions-outgoing; Mon, 24 Aug 1998 08:09:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07509 for ; Mon, 24 Aug 1998 08:09:01 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA18005; Mon, 24 Aug 1998 08:07:36 -0700 (PDT) (envelope-from dhw) Date: Mon, 24 Aug 1998 08:07:36 -0700 (PDT) From: David Wolfskill Message-Id: <199808241507.IAA18005@pau-amma.whistle.com> To: freebsd-questions@FreeBSD.ORG, pol@leissner.se Subject: Re: Problem with NIS losing contact with master In-Reply-To: <3.0.32.19980823225116.009db598@lda> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 23 Aug 1998 22:51:19 +0200 >From: Peter Olsson >We have recently started using NIS for passwd-syncing between two of >our internal servers. They are on different subnets and this seems to >cause trouble for the client. I believe you'll want to set up "slave" servers on each subnet. If I recall correctly, NIS depends on broadcasts to a significant degree, and those generally don't get routed between subnets. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message