SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Im currently trying to do an install from nfs server and im getting a connection refused error from the client.
On the server I have loaded the nfsd module and started the pormapper, also added an entry to the exports file, but i still dont seem to be able to connect to the server from the client.
entry in exports file is
/home/share (rw)
i think the nfsd module is required and the portmapper has to be started I also read something about mountd but I cant load or find that module ????
It seems i am onto the correct things here the problem is that I cannot connect to the server to do a network install. Seems like I have left a user or permission thing out.
thanx hope this gets to someone that has used nfs before.
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
Hi,
I'm not an nfs expert either, but I think what's missing is the list of clients that are allowed to connect!
Quote:
I can tell you, if you leave out that pisky little * it will not work.
The '*' should match any client that is trying to connect to your nfs server, or you could put in a specific IP address e.g. 192.168.1.2 or what ever your machine happens to have as an IP. It also accepts address ranges such as 192.168.1.* - this should match any client on the 192.168.1 network.
If you read the man pages though, it's all there....
You might want to try http://www.tldp.org/ . There are a couple of really useful how-tos for NFS that outline all this stuff. I've currently got a working NFS setup, so if you want I'll post the following files (could be long):
That's why there are more than one of us here. I actually use webmin to set mine up. It always leaves out that * though. Wonder why it do that??? I have to put it in manually every time.
When it leaves out that *, I get the same error he was getting, permission denied. Took me a bit. I'm getting slow in my old age.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.