NFS problem: "RPC: Port mapper failure"

From: Rob (nospam_at_users.sourceforge.net)
Date: 12/28/03

  • Next message: Igor Pokrovsky: "Re: NFS problem: "RPC: Port mapper failure""
    Date: Sun, 28 Dec 2003 21:20:41 +0900
    To: freebsd-stable@freebsd.org
    
    

    Hi,

    I am running two FreeBSD-Stable PCs.

    One is an NFS server and the other NFS client. Everything used to
    work fine until recently. I suspect that either the new kernel is the
    problem (although there are no complaints on the stable mailing list)
    or the network administration has changed some things.

    The server is on 147.46.44.183 with following /etc/exports:
            /usr/ports -maproot=root 147.47.254.184
            /home/entertainment -ro 147.47.254.184

    The server boots with rc.conf:
            nfs_reserved_port_only="YES"
            portmap_enable="YES"
            nfs_server_enable="YES"
            mountd_flags="-r"

    The client boots with rc.conf:
            nfs_reserved_port_only="YES"
            nfs_client_enable="YES"

    On the client (147.47.254.184) I do not get the proper response on:
            $ showmount -e 147.46.44.183
            RPC: Port mapper failure
            showmount: can't do exports rpc

    Doing a mount_nfs on the client, gives the same port mapper failure.

    Portmap is running on the server; it is not on the client, but
    that should be OK here, right?

    I am at a total loss, since I have no idea how to investigate further
    what is actually going wrong. What could be a reason for the RPC Port
    mapper failure? How else can I test the port mapper's functunality?

    Thanks,
    Rob.

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: Igor Pokrovsky: "Re: NFS problem: "RPC: Port mapper failure""

    Relevant Pages

    • Re: Unable to print to networked printer - get access denied messa
      ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
      (microsoft.public.windowsxp.print_fax)
    • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
      ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
      (Debian-User)
    • Re: Remote Connection Issue
      ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
      (microsoft.public.windows.server.sbs)
    • Re: RealVNC
      ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
      (microsoft.public.windows.server.sbs)
    • Re: Redirecting data sent to a local printer to another host and port on the network
      ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
      (comp.unix.sco.misc)