From owner-freebsd-bugs Mon Feb 15 02:20:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13769 for freebsd-bugs-outgoing; Mon, 15 Feb 1999 02:20:06 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13763 for ; Mon, 15 Feb 1999 02:20:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id CAA32050; Mon, 15 Feb 1999 02:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Mon, 15 Feb 1999 02:20:02 -0800 (PST) Message-Id: <199902151020.CAA32050@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Yuri Gindin Subject: Re: bin/8699: ypbind can't bind to server Reply-To: Yuri Gindin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/8699; it has been noted by GNATS. From: Yuri Gindin To: Joseph Koshy Cc: freebsd-gnats-submit@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: bin/8699: ypbind can't bind to server Date: Mon, 15 Feb 1999 12:13:27 +0200 (IST) On Sun, 14 Feb 1999, Joseph Koshy wrote: > > > Hi, > > Are you still facing the 'ypbind' problem? Did you try the -m option? > > Are you by any chance trying to connect to a YP server via an interface > that doesn't support broadcast? > > In the case of the second respondent to this PR, the problem turned out to > be a netmask misconfiguration problem which was subsequently rectified. > > Koshy Hello, Yes, the netmask was the problem. Thanks. --Yuri Gindin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message