Most FTP clients (WS_FTP, Fetch, etc), though, support persisting a user-preference to do passive transfers (single, client-initiated TCP control socket; there is no data connnection), which is reported to do okay through SSH TCP socket tunnels, though I have never tested this to Zope... Sean
-----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Wednesday, June 04, 2003 11:25 AM To: Andreas Pakulat Cc: zope@zope.org Subject: Re: [Zope] FTP access and ssh-Port-Forward
Andreas Pakulat wrote at 2003-6-4 16:40 +0200:
I've got a problem with zope on Solaris system. I can access the ftp-Port from within the LAN (being either there or using ssh to connect to a server in the LAN) but not using a port forward for it. I can however use http-Portforwarding over ssh, but ftp-Portforwarding only gives me the possibility to login, the ls command "hangs" at entering Passive Mode. If I turn off passive mode I get error 425 Cant build data connection.
Has somebody a soluting how to get ssh-forwarded ftp Access to Zope?
FTP is a very difficult protocol with respect to forwarding and FireWalls. That's because FTP uses two connections, a command connection and a data connection. The latter is created on demand. It is very difficult to forward the data connection.
Workarounds:
Transfer your data from outside into your LAN (e.g. via "scp") and then use a LAN FTP connection to Zope.
Use WebDAV to directly transfer the content into Zope.
Use "load_site.py" to import content (and something symmetrically for the reverse direction).
Dieter
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )