Hey I’m trying to set up a NFS on one of my systems, I followed the some what guide in NFS - openSUSE along with using the YaST tool for both the server and client. As far as I can tell the server is running correctly but when trying to set up the client I get an error about problem in fstab, this is what I have in my fstab entry
192.168.2.*/24 is not a legal subnet specification. What you want is 192.168.2.0/24.
Here’s a rough and ready method when you aren’t sure which log file a message goes to. Provoke the error and then see what was the latest update in /var/log:
ls -lrt /var/log
The latest files changed will be at the bottom. Assumptions: It was actually written to some log file. The log is in /var/log and not a major subdirectory like samba or apache2. Buffering has had time to flush the message. The server isn’t so busy that plenty of log files get updated.
If you really want to be sure, check the documentation for the category of NFS server messages and then look at /etc/syslog-ng/syslog-ng.conf to see where they are directed.
Well changing the host ip in /etc/exports and restarting the NFS server I still can’t get on and ls -lrt /var/log didn’t help because /var/log/messages was the last one and that is just showing me people are trying to break into my FTP server.
Also have you tried a mount from the server itself? It should work the same way.
mount -t nfs 192.168.2.16:/home/music /somewhere
And since you are attempting to mount nfs4, I think there are other things you need like authentication. You’d have to do a search, I’m still using nfs version 3 (it’s only a thin client).
>
> Do you have these services running:
>
>
> Code:
> --------------------
> nfsd
> nfsd4
> rpc.mountd
> portmap
> rpc.statd
> rpc.idmapd
> --------------------
>
>
> Also have you tried a mount from the server itself? It should work the
> same way.
>
>
> Code:
> --------------------
> mount -t nfs 192.168.2.16:/home/music /somewhere
> --------------------
>
>
> And since you are attempting to mount nfs4, I think there are other
> things you need like authentication. You’d have to do a search, I’m
> still using nfs version 3 (it’s only a thin client).
>
>
nfsd, nfsd4 and rpc.mounted are not on my system, portmap, nfsserver, rpc.statd, rpc.idmapd are running. I am able to mount it locally and now remotely I don’t know if it just decided to work, or the fact that this time I added -t nfs even though when I was calling mount with out that it could tell I was mounting a NFS and used mount.nfs for it.
The way it looks from the YaST module, both server and client, the only thing that you need to do for nfs4 is a domain name on the server. Of course there could be more this is the only thing special for nfs4 I had to specify.
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
>
> Ah, I see you don’t know how to use the CLI ps to check for running
> processes, you were using YaST. nfsserver starts nfsd* and rpc.mountd
> IIRC.
>
>
Well I can mount the drives now, but my permissions are not carried over to the remote client, I want to clients to have read and write permissions but for some reason the client machine only has read. Is there something I need to do to the permissions?
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
Did you export it rw and also mount it rw at the client end? Also remember that root gets mapped to nobody (that’s what root_squash means). Also possibly because your uids don’t match up? If you do ls -l at the client and the owner of the files is not what you expect, you have uid mismatch. The accounts on both machines (at least the ones that matter to you) must match.
Just as a side remark: Did you open the firewall port? If not, go to yast2 -> Security and Users -> Firewall -> Allowed Services and add the nfs server.