From owner-freebsd-bugs Sun Feb 14 21:20:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03481 for freebsd-bugs-outgoing; Sun, 14 Feb 1999 21: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 VAA03476 for ; Sun, 14 Feb 1999 21:20:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id VAA28568; Sun, 14 Feb 1999 21:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 14 Feb 1999 21:20:03 -0800 (PST) Message-Id: <199902150520.VAA28568@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Joseph Koshy Subject: Re: bin/8699: ypbind can't bind to server Reply-To: Joseph Koshy 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: Joseph Koshy To: yuri@xpert.com Cc: freebsd-gnats-submit@FreeBSD.org, wpaul@FreeBSD.org Subject: Re: bin/8699: ypbind can't bind to server Date: Sun, 14 Feb 1999 21:10:35 -0800 (PST) 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message