Al said:
Still no idea what ports, other than 21, it might need. Maybe an
email to the author? Or a "package" to Redmond, to discourage things
like Windows Firewall?
Haven't tested it yet as I have no ISP hosted FTP to check it out on,
but if works with the firewall disabled, but not enabled, I'd suggest
that it is making an active FTP connection rather than a passive one.
Quick trivia - FTP requires 2 connections, a control and a data
connection. For an normal FTP connection the FTP server connects back
to you on the data port your client sets up, passive = you make both
connections to the FTP server. Active is less hassle for an FTP server
admin, passive is less hassle for the FTP user.
More details here -
http://slacksite.com/other/ftp.html
Unfortunately, FTPpie doesn't appear to have an option to select passive
mode, so I'd hazard a guess it's using active FTP. I'd suggest punching
a hole in Windows Firewall on port 20.
"Adding the port exception
1. Click Start, click Run, type Wscui.cpl, and then click OK to open
Windows Firewall.
2. Click the Exceptions tab, and then click Add Port to display the Add
a Port dialog box.
3. Enter the port number that your program uses.
4. Select the TCP or UDP protocol, depending upon what your program uses.
5. In the Name field, type a descriptive name for the port.
6. Click Change Scope to view or to set the scope for the port
exception, and then click OK.
7. Click OK to close the Add a Port dialog box.
8. To verify that the port settings are correct for your program, test
the program."
HTH
Ben
)
?