nfs problems mounting from FreeBSD to RH9

I'm trying to mount a nfs export from FreeBSD to RH9 but keep getting the
following message

mount: RPC: Timed out

yet the same operation runs perfectly well from a Mandrake client.

The FreeBSD exports file is this

/usr/home/pep 192.168.0.10 -mapall=pep

the RH9 fstab file is this

192.168.0.10:/usr/home/pep /home/pep/ACTUALLY-W9-HOME nfs
rw,hard,intr,user

This is the output from /etc/rc.d/init.d/nfs status

rpc.mountd (pid 18932) is running...
nfsd (pid 18924 18923 18922 18921 18920 18919 18918 18917) is running...
rpc.rquotad (pid 18912) is running...

Like I said exactly the same operation on the Mandrake client is working
with no problems.

I can ssh on to the FreeBSD server from the RH client and I have turned off
the firewall on the RH client to ensure there are no problems there.

Thanks for any help,
Pep.

Peter Walker wrote:

> I'm trying to mount a nfs export from FreeBSD to RH9 but keep getting the
> following message
>
> mount: RPC: Timed out
>
> yet the same operation runs perfectly well from a Mandrake client.
>
> The FreeBSD exports file is this
>
> /usr/home/pep 192.168.0.10 -mapall=pep
>
> the RH9 fstab file is this
>
> 192.168.0.10:/usr/home/pep /home/pep/ACTUALLY-W9-HOME nfs
> rw,hard,intr,user
>
> This is the output from /etc/rc.d/init.d/nfs status
>
> rpc.mountd (pid 18932) is running...
> nfsd (pid 18924 18923 18922 18921 18920 18919 18918 18917) is running...
> rpc.rquotad (pid 18912) is running...
>
> Like I said exactly the same operation on the Mandrake client is working
> with no problems.
>
> I can ssh on to the FreeBSD server from the RH client and I have turned
> off the firewall on the RH client to ensure there are no problems there.
>
> Thanks for any help,
> Pep.

The problem is now solved.

I tweaked the firewall rules and then restarted the firewall and it finally
works.

It does not explain to me why it did not work when the firewall was turned
off, effectively allowing all access to the workstation but what the hell,
I prefer the firewall on so that I have a secure system anyway.

Pep.

David Bolton wrote:

> Peter Walker <(E-Mail Removed)> wrote:
>>>
>>> I can ssh on to the FreeBSD server from the RH client and I have turned
>>> off the firewall on the RH client to ensure there are no problems there.
>>>
>>
>> The problem is now solved.
>>
>> I tweaked the firewall rules and then restarted the firewall and it
>> finally works.
>>
>> It does not explain to me why it did not work when the firewall was
>> turned off, effectively allowing all access to the workstation but what
>> the hell, I prefer the firewall on so that I have a secure system anyway.
>>
>
> Hello Peter, when you flushed your firewall rules, did you then ssh onto
> the
> FreeBSD, or were you already logged on when you disabled the firewall?
> I'm asking because on my FreeBSD (4.8 stable, using ipfilter v3.4.31) I
> have deny compiled as the default in the kernel (options
> IPFILTER_DEFAULT_BLOCK), yet if I ssh onto the box and flush the rules,
> the ssh session continues indefinitely despite all further login attempts
> being blocked.
>
> Best regards,
> David
> --

Sorry but I can't really help you here as the firewall I was dealing with
was on the RedHat Linux client machine.

If I understand your query, you are asking why it is that your ssh
connection to your FreeBSD server remained persistent after you flushed the
firewall in the FreeBSD server?

Presumably you had a rule that allows ssh connections to override your
default DENY rule?

If that is your query, I have to admit that I have not done much work with
the FreeBSD firewall but imagine that when you flushed the firewall it
would only affect new connection attempts not existing connections.

Pep.