[quoted text, click to view] > From: ewruff <ewruff.18hc8z@mail.webservertalk.com>
> An error occured opening that folder on the ftp server. make sure you
have permission to access that folder
> details:
> 200 type set to A
> 500 Invalid PORT command
> 500 'LPRT 6,16,0,0,0,0,0,0,0,0,67,0,0,0,0,0,133,96,2,8,98': command not
understood
The "LPRT" command is pretty close to bogus and can be ignored.
The "invalid PORT command" indicates that this is not a problem with the
server, but that the server has detected that your PORT command asks it to
connect to an address that is unacceptable. It would be helpful to see
what PORT command was attempted, but we can make a few guesses. The first
guess is that the last few parameters of the LPRT command are probably the
same, or close to the same, as those used for the PORT command. This rules
out my first thought, that a NAT was not translating the PORT command's use
of an internal IP address. There are a couple of other possibilities:
1. You've already asked it to connect to that port, and you closed that
connection less than four minutes ago. This is somewhat unlikely, unless
this is the result of trying to transfer several small files.
2. That isn't the same IP address as the incoming control connection came
in on. I can't quite imagine how you'd manage that, so for the moment,
we'll dismiss that.
3. Something else is bound to port 20, preventing the server from binding
to port 20 (if the server is running on port 21) before connecting out.
One thing you can try is to use the command-line ftp client, with the debug
parameter - open a command prompt window, and type "ftp -d your-ip-here"
(where "your-ip-here" gets replaced with the IP address of the server
you're connecting to).
Alun.
~~~~