Need help with NFS, can't find what I need in the man pages...
I checked all the man pages I can think of, and I can't find anything relevant in any of them: running Slack with a stock 2.4.29 kernel on a desktop and a compiled 2.6.12.3 kernel on my notebook; I'm certain I enabled NFS when I configured it, and I've started every daemon on both machines I can think of or that have been mentioned in guides (I'm on the verge of running every single script in rc.d...) -- the two comps are networked, netstat is telling me all the daemons are listening, etc.., but when I 'mount -t nfs (IP-addie):/(share) (local dir)' it says this:
mount: RPC: Program not registered lsmod says both kernels definitely have the modules loaded, and rpc.portmap is running on both as well. I totally disabled all firewalling on both machines, but I made sure that only the bare minimum scripts in rc.d get run at boot... have I turned something off that I need? I use slapt-get to keep both boxes current, if that's relevant. I'm really at a total loss here, and I just can't find anything about this issue anywhere... ... help, heh? |
is /etc/rc.d/rc.portmap executable on both machines ?
Did you try /etc/rc.d/rc.nfsd restart on both machines ? How does the /etc/exports look like on the server ? What is your output with : Code:
/usr/sbin/showmount -e <server IP> |
Is /etc/rc.d/rc.portmap executable?
Code:
chmod +x /etc/rc.d/rc.portmap Doh, too slow. :) ***/EDIT*** |
No, none of the startup scripts are executable, I was using 'sudo bash rc.nfsd start', to execute them since I have a tendency to forget what I've been playing with before I've disabled it again...
'sudo /usr/sbin/showmount -e 192.168.0.135' (the server box's IP on the LAN): mount clntudp_create: RPC: Program not registered I'm thinking it's a stupid modification I made months ago while disabling every service possible to try and maximize security, but... what I changed, or when, I have no clue. Anything related to the recurring RPC not registered business I could have mucked with unknowingly in the past 4-8 months...? |
Yeah, it's definitely running:
$ps aux bin 12103 0.0 0.1 1688 612 ? Ss 15:33 0:00 /sbin/rpc.portmap root 12651 0.0 0.1 1516 512 ? Ss 15:53 0:00 /usr/sbin/inetd root 12852 0.0 0.1 1640 748 ? Ss 16:03 0:00 rpc.statd [edit: sorry, forgot to answer -- yeah, I set up /etc/exports; manually did 'exportfs -a' after running rc.nfsd just to be sure too] |
Could you try these commands in the server :
chmod +x /etc/rc.d/rc.portmap sh /etc/rc.d/rc.nfsd restart then from your client : /usr/sbin/showmount -e 192.168.0.135 (no need to be root) |
I'm happy to try anything you can think of that might help... did precisely what you said, same exact output from showmount:
mount clntudp_create: RPC: Program not registered I tried mounting the server's share from the server... only error it gave me is that I wasn't authorized, which I'd hope it would do since that box isn't in its own /etc/exports |
Now try the same commands in your client and post back the result.
If it fails again, could you post your /etc/exports file ? |
Think I got it... but I'm not sure how... Okay, well since rpcinfo -p [server] worked fine from the server but not from the client (which said no programs registered), I emptied the server's /etc/hosts.deny file (said ALL: ALL) -- I thought you could deny all in hosts.deny, and allow individual computers access in hosts.allow without a problem? The client was definitely in hosts.allow, and once there's nothing in hosts.deny, rpcinfo -p [server] works just fine from both machines...
And yeah, mount works like a charm, just made sure. So does showmount. Am I wrong about the order of hosts.allow/deny? |
On the server machine you could add in /etc/hosts.deny :
portmap: ALL and add in /etc/hosts.allow : portmap: <client ip>/255.255.255.0 That should enable access to only your client, but if you really concerned with security, why not use scp and ssh to transfer files between machines ? |
Hmm... I'll check out the man pages and do some websearches on those; I didn't really think I was more paranoid about security than the average Linux user, but that's a different topic altogether.
Thanks so much for your speedy help, keefaz -- it's great to have this forum with friendly people when all else fails. |
Try man 5 hosts_access for documentation for /etc/hosts.allow and /etc/hosts.deny
|
Another happy customer (=
Quote:
Thank you for posting your questions on this topic. Because without these questions, there would be no answers. I found this posting really usefull and I intend to use every little bit of info that it gave me. Without you guys, its just not possible. Cheers, Dumdadum (= |
All times are GMT -5. The time now is 12:13 AM. |