How to set up NFS?

[Tem]

Seems I can't figure this out. What am I doing wrong trying to get NFS to work..?

1) Made a /NFS/tst dir

2) Setup NFS Server through YaST Control Center as:
- NFS Server: Start
- Firewall: Open Port in Firewall
- Added directory /NFS/tst
- Added host 192.168.7.191 with rw,no_root_squash

3) Verified that the changes appear in /etc/exports

4) Verified that NFS is running with 'rpcinfo -p' and that I have the nfs-utils with 'rpm -q nfs-utils'

5) Added 'ALL: 192.168.7.191' into /etc/hosts.allow

6) Disabled firewall, not being 100% sure if that blocks something
(these are just networked together, not in internet)

7) Tried other NFS options, like host * and *.*.*.* with different options

I already have tftp working, so the network itself should be fine. 192.168.7.191 is the ip of system which is trying to connect to NFS on Suse10 with ip 192.168.7.148

I suppose I'm missing something obvious here, any ideas?

[DThor]

OK, but you don't finish your story. You attempted to mount it on the second system and....?

Just in case you don't know, you set up an NFS share on the server, you need to have nfs running on the client, and you need to attempt to mount the server share at a specific mount point on the client end. You can use Yast on the client system to add from server systems.

Btw, as a rule you should keep your nfs configuration as simple as possible to start with, especially if you're behind a firewall and don't need to concern yourself about security. Start over, delete old shares, create new ones that let anyone mount it, lose all the restrictions you mention apart from the default system settings - it should just work.

DT

[Tem]

OK, but you don't finish your story. You attempted to mount it on the second system and....?

...and it kept saying it can't find NFS service.

The 2nd system is a Freescale LITE5200B board, not Suse, that's why I didn't mention much of it here. I just wasn't sure if I had the NFS Server running on the PC, but seems I had. My issue was that apparently the boot args didn't get passed to kernel from the boot like the instructions said. The system started to work when I forced the boot args in kernel compilation.