Bug 7749 - Client will not bind to NIS server if server's hosts.deny has any rule
Client will not bind to NIS server if server's hosts.deny has any rule
Product: Red Hat Linux
Classification: Retired
Component: ypbind (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-12-11 01:56 EST by Lan Barnes
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-27 14:13:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lan Barnes 1999-12-11 01:56:02 EST
I have a NIS master server (no slaves) with hosts.allow:

ALL:	LOCAL, .mydomainname.com

and hosts.deny:


In this configuration, no clients will bind (reason, permission denied).
However, when I comment out the "ALL: ALL" in the master server's
hosts.deny, everything works.

Others in my LUG have had the same problem, but only after upgrading from
5.2 to 6.0 or higher.
Comment 1 chris 2000-01-17 23:18:59 EST
THe ypserv that comes with redhat 6.1 (and I presume 6.0 also) is compiled to
use securenets rather than tcp_wrappers (do a /usr/sbin/ypserv --version to
prove this for yourself).

do a `man ypserv` to learn how the /var/yp/securenets file is set up.

If you must use tcp_wrappers, then you'll need to recompile with the appropriate
Comment 2 Cristian Gafton 2000-01-27 14:13:59 EST
not a real bug, the network configuration needs to be updated.

Note You need to log in before you can comment on or make changes to this bug.