(ASCEND) NAT and passive ftp

["Hernan R. Silva" <hsilva@activenation.com>]

Is there a way to avoid having to use passive ftp when using NAT to connect
my private LAN to my ISP, who assigns me a single IP address dynamically?
I'm using the 6.0.10 firmware with a Pipeline 50, configured per the AOS
recommended settings for NAT. If I don't use passive ftp, the downloads
simply hang after a while (Red Hat Linux 5.2), or hang and take  CPU Usage
to 100% (Windows NT 4.0).

I had read in posts in comp.dcom.isdn that, unlike in the 3Com OCLM, NAT had
been implemented properly by Ascend in the Pipelines to avoid having to use
passive ftp, but I'm starting to wonder. Is there a workaround, or is this
fixed in another firmware level?

TIA,

Hernan R. Silva

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>