Bug 81737 - etc/hosts entries prevent nfs (and telnet) from working
etc/hosts entries prevent nfs (and telnet) from working
Status: CLOSED DUPLICATE of bug 76543
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-13 11:58 EST by Robert Youngjohns
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Robert Youngjohns 2003-01-13 11:58:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.79C-CCK-MCD  [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
Entered as an NFS component error, but I suspect is more widespread.

With local HOSTS entries, NFS mounts fail with RPC portmap error using  host
name or IP address. (Similarly, Telnet fails with connection refused.) Ping
works.

Remove the HOSTS entries and NFS/Telnet works fine with IP address.  All worked
fine with redhat 7.1

I've seen comments about a bug that sounds similar and which was preventing some
sites (including redhat) migrating to 8.0, but can't find reference to this on
bugzilla.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. remove entries in etc/hosts - works
2. add entries to etc/hosts - fails
3.
    

Actual Results:  nfs mount fails with RPC portmap error. 

Expected Results:  nfs should have mounted remote filesystem

Additional info:
Comment 1 Robert Youngjohns 2003-01-16 12:32:40 EST
I think this is probably a duplicate of 76543.
Comment 2 Steve Dickson 2004-06-15 20:38:38 EDT

*** This bug has been marked as a duplicate of 76543 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:09 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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