Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to set up an old laptop to access my main desktop's NFS shares. I believe the host is working correctly, but the client (running Slackware 8.1) is returning an error when attempting to mount the directories:
> mount -t nfs [ip address]:/exported/dir /local/mnt/dir
mount: RPC: Port mapper failure - RPC: Unable to receive
> rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 tcp 111 portmapper
to add instances of nfs, nlockmgr, and mountd to the above rpcinfo command, but still receive the same error. NFS doesn't seem to be starting even though /etc/rc.d/rc.nfsd is present and executable, and /etc/rc.d/rc.inet2 has the appropriate lines uncommented. The nfs-utils and portmap package are both installed. Can anyone help me solve this problem?
If you can post your exports file? Also you said you added your own NFS startup scripts, can you post those or are you using the existing startup scripts that Slack will usually have already in /etc/rc.d ?
I was speaking about the server when I said I added NFS to the startup. The server is a Red Hat 9.0 machine and I added NFS to the startup services using their GUI tool. When the machine reboots I can see NFS starting up.
As for the Slackware client startup (using existing scripts), rc.inet2 and rc.nfsd are both executable and I made no changes. After a reboot a rpcinfo -p command only shows portmapper running.
That didn't do it. I'm almost positive that the client machine isn't starting all the necessary daemons/services and that is why it is unable to receive. What services MUST be shown when running an rpcinfo -p command? How can I start/restart all the necessary daemons/services? I have nfs-utils and portmap packages installed, am I missing any?
If the client is running Slackware, look in your /etc/rc.d directory. There you will find your startup scripts. Make sure you have the NFS client specific uncommented in your rc.nfsd, rc.inet2 and then whatever runlevel you boot into.. say for instance rc.M if you boot into runlevel 3, etc.
After taking a closer look at the Slackware startup scripts I noticed that NFS would not load at startup without an entry in the /etc/exports file. I added an entry and now NFS comes up completely at startup.
rpcinfo -p command now shows running instances of portmapper, rquotad, nfs, nlockmgr, mountd, and status
Unfortunately, I am still receiving the same "Unable to receive error" when I try:
mount -t nfs [serverip]:/remote/dir /local/dir
I am able to ping both machines on the network, but not connect via NFS. I still think the problem is the client, but I can't figure out what is missing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.