On Monday 03 January 2005 16:22, Örn Einar Hansen wrote a bunch of stuff about SAMBA that I'm going to study carefully, but then you said:
The difference here is, that whenever you browse to your samba share, you'll need to authendicate to the upstairs machine. While all you need for the NFS share, is to have your "/etc/passwd" identical on both linux boxes, the rest is automatic ... the rights give on the upstairs machine, will be inherited by the downstairs machine, of the same user (actually user id is what counts, not the name). No need to authendicate, as you're already authendicated on the local machine.
That's a good incentive to get NFS going. I could reserve SAMBA for just the Windoze shares, when needed/applicable, and share upstairs/downstairs via NFS most of the time. If only it would work . . . Right now, it does not work, but I don't know what is the point of failure. Upstairs (the Linux-only box) my /etc/exports file looks like this: /home/kevin/k-shared/ *(rw,root_squash,sync) /home/kevin/Documents/ *(rw,root_squash,sync) /home/kevin/downloads/ *(rw,root_squash,sync) /windows/ *(rw,root_squash,sync) /home/mywife/ *(rw,root_squash,sync) /media/ *(rw,root_squash,sync) The output of rpcinfo looks like this: upstairs:/etc # rpcinfo -p upstairs program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100227 3 udp 2049 nfs_acl 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1 udp 1085 nlockmgr 100021 3 udp 1085 nlockmgr 100021 4 udp 1085 nlockmgr 100024 1 udp 1085 status 100021 1 tcp 2560 nlockmgr 100021 3 tcp 2560 nlockmgr 100021 4 tcp 2560 nlockmgr 100024 1 tcp 2560 status 100005 1 udp 689 mountd 100005 1 tcp 692 mountd 100005 2 udp 689 mountd 100005 2 tcp 692 mountd 100005 3 udp 689 mountd 100005 3 tcp 692 mountd upstairs:/etc # Meanwhile, downstairs, on the NetVista, in Linux, I try to configure/start the NFS Client service using YaST. I am unable to browse to the upstairs machine, to fill in the fields, and if I type the values in by hand, I still get this error when NFS Client module tries to save-and-exit: NFS Client Writing NFS Configuration... ERROR Unable to mount NFS entries from /etc/fstab Downstairs, I'm logged in as my wife (it's her machine) using the same userid and password as on the upstairs machine. But even that should make no difference, because YaST is working as root and is unable to see the upstairs server. Now, granted it is very possible that I input the values incorrectly when trying to tell the Client what to do. But that should not affect the ability of the downstairs Client to browse the network and find the upstairs NFS Server. As usual, I don't know enough about this... only enough to be dangerous... :-) It appears that, upstairs, the nfs service is running, as are the portmapper, the lockmanager and mountd. What else needs to be going, upstairs, so that the YaST NFS Client downstairs should be able to see the upstairs server and browse its exported shares? Also, for bonus points, since this is approximately the simplest possible network configuration (two PCs on a single LAN subnet, joined by a simple hub/router), why is YaST not getting it right, automatically? There should be basically no options or non-default settings, so what's to screw up? POSSIBLY unrelated point. YaST seems to insert a tab character into the exports file (just before the "*" wildcards), but I read in a HowTo or a man page that the only separator should be a space. So, I edited the exports file to replace the tab characters with single spaces in those locations, but have noticed no difference after saving and restarting. Where do I go, next with NFS setup? I just want to see it working, at first. I'll worry about options and getting fancy at a later date. Now to re-re-re-read your post about how SAMBA works. Regards, Kevin (unshared at the moment)