This is really strange. I have a nfs server with 2 exports, every one can mount them fine, except for this one linux box, who can mount only one of the exports but get permission denied on the other. The 2 exports have the exact same options, there is nothing in the /etc/hosts.deny or /etc/hosts.allow. The permssions for the 2 dirs exported are exactly the same. Is there some setting that could allow a machine to mount one export and not the other besides /etc/exports (other than exportfs). "exportfs -v" shows the exact same options for both exports. Any help would be greatly appreciated. Thanks in advance.

I appear to be getting a similar problem as you using 2 thin clients. my first workstation sucessfully mounts. however as soon as i attach my second workstation via a hub it reports errors whilst attempting to mount.

It is really perplexing me as despite checking the config of server (including DHCP, DNS & NFS), of which all appears to be fine I'm getting errors!

Sorry that this isn't a useful post to your plight, however if I find the answer I'll try 2 remember to let you know

cheers

Hi knaries2000, hi naesyllek!

I had exactly the same problem. The interresting thing in my case is: It was already working before.

We had to switch our whole network to another ipaddress range. After that we realized, that our backup wasn't working correct because the connection via nfs couldn't be established.
I checked everything (hosts.allow, hosts.deny, possibly set firewall rules, ...) without any success.
At last I had a look at the hosts file of both of the servers and there was the problem. We just forgot to modify those two machines.

On the client: Try to ping the server using the full qualified domain name (myclient.network.company.com) not the IPaddress
and
On the server: ping the client the same way.

They must know and reach each other.
In my case they don't, till I corrected my hosts-file.

In your case, check your dns configuration as well.

Hope it helps

Peter


PS: Sorry about my awful english

hi pedali,

thnx for the post, i did manage to sort the problem out. it was as you have suggested the DNS config. Everything worked a treat after that

sean

I tried what had been suggested with no luck - ended up bouncing the nfs service on the clients and that clear the issue- not sure why wold the nfs service would get confused ...