On Sep 1, 2006, at 08:00, Joseph Nastasi wrote:
FYI, I've been meaning to get this info on the FAQ, but if you are
using a Firewall this is what has to happen: (all this assumes
using PASV which is really the safest way to go any)
Client
The firewall (and router, if using one) needs to have the FTP
command port (21) enabled. Additionally, you have to enable the
range of FTP data ports that the FTP Server will give as part of
the PASV protocol. The trick here is that you may no KNOW what that
range is. In Windows, it's typically 1024-5000, but that is
dependent on the FTP Server.
FTP Server
So, if the FTP server can itself be assigned a range to use for
PASV connections, it is possible to define a range of ports that
are easy to configure in the client firewall.
But that's the key.
So, I turned off the Windows firewall and everything works
swimmingly. Obviously, running without the firewall is not option,
so I'll have to figure something out to make this work.
However, it does beg the question: Why do all the other commands,
including file transfer, work without issue and it is only the
'logoff complete' message that is blocked?
--
David Glass - Gray Matter Computing
graymattercomputing.com - corepos.com
559-303-4915
Apple Certified Help Desk Specialist
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
