«

On or somewhere about Wednesday 02 February 2005 08:17 pm, Wil Schultz might
have said:

<snip>
>> I haven't tried to do that, but I recently worked on something sort
>> of related.
<snip>

Hey Walter, I haven't tried this yet but I found a good doc that looks like
it has the answer to both of our problems. I don't know that I like it, but
looks like it has the answer.

http://www.cisco.com/en/US/products/....html#xtocid48

--
Wil
my 3¢

"When everything seems to be going well, you have obviously overlooked
something."

<snip>

Looks like you hit this one right on the head Andrey. Thanks! I'll report
back later with the results...

Very disturbing is the fact that Cisco PIX Doc's from 5.x and up do not have
this information. They go through the RPC (111) and NFS (2049) ports but
blatently leave out the higher dynamic ports that portmapper requires.

--
Wil
my 3¢

"When everything seems to be going well, you have obviously overlooked
something."

As a suggestion, don't use conduits in your configuration; they're being
phased out.

I did a google of 'NFS fixup' and voila!
http://www.cisco.com/univercd/cc/td/...62/config/fixu
p.htm#xtocid28



On 02/03/2005 09:03 AM, in article , "Wil
Schultz" <> wrote:

> <snip>
>
> Looks like you hit this one right on the head Andrey. Thanks! I'll report
> back later with the results...
>
> Very disturbing is the fact that Cisco PIX Doc's from 5.x and up do not have
> this information. They go through the RPC (111) and NFS (2049) ports but
> blatently leave out the higher dynamic ports that portmapper requires.