I am running Windows 2003 Advanced Server with all of the current updates.  
My problem is accessing the FTP site from outside of my LAN.  I am hosting m
y own WWW site using a free URL from DynDNS.org the website's URL is linked 
to a service that updates my local IP address, the site works fine externall
y.  I want to use the same url except ftp instead of http as the protocol.  
I can connect to the FTP site using the private ip address from another comp
uter on my LAN, and my router firewall is set up correctly to forward ports 
20-21 to the private ip of the server.  I also tryed setting up a new ftp si
te and forwarding to port 2020-2021 to make sure my ISP is not blocking port
 20-21.  I even placed the server ip address in the DMZ to make sure it is n
ot a router issue.  I have my DNS server pointed to the DNS server for the D
ynDNS.org service as they require.  NSLOOKUP resolves both my public and pri
vate ip address and the URL.  Here is the error I get when trying to log in.

An error occured opening that folder on the ftp server. make sure you have p
ermission 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 unde
rstood

[ Post a follow-up to this message ]

a) first test everything locally. try ftp.exe at local machine.
make sure everything working before you proceed b)

b) use ftp.exe can connect remotely.. outside your LAN.
ftp youpublicip

do you see login prompt ?
can you login ?
can you do dir listing ?

Ftp operation mode and ports requirement, read
Information About the IIS File Transmission Protocol (FTP) Service
http://support.microsoft.com/?id=283679

to be clear.
inbound 21
outbound 20

passive port range.. you can customize it.
How To Configure PassivePortRange In IIS
http://support.microsoft.com/?id=555022


--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"ewruff" <ewruff.18hc8z@mail.webservertalk.com> wrote in message
news:ewruff.18hc8z@mail.webservertalk.com...
>
> I am running Windows 2003 Advanced Server with all of the current
> updates.  My problem is accessing the FTP site from outside of my LAN.
> I am hosting my own WWW site using a free URL from DynDNS.org the
> website's URL is linked to a service that updates my local IP address,
> the site works fine externally.  I want to use the same url except ftp
> instead of http as the protocol.  I can connect to the FTP site using
> the private ip address from another computer on my LAN, and my router
> firewall is set up correctly to forward ports 20-21 to the private ip
> of the server.  I also tryed setting up a new ftp site and forwarding
> to port 2020-2021 to make sure my ISP is not blocking port 20-21.  I
> even placed the server ip address in the DMZ to make sure it is not a
> router issue.  I have my DNS server pointed to the DNS server for the
> DynDNS.org service as they require.  NSLOOKUP resolves both my public
> and private ip address and the URL.  Here is the error I get when
> trying to log in.
>
> 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
>
>
>
> --
> ewruff
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message283764.html
>

[ Post a follow-up to this message ]

> 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.
~~~~

[ Post a follow-up to this message ]

I have not tryed using the DOS ftp utility, I used internet explorer and als
o tried ws_ftp, both of which worked locally.  I will try again offsite and 
include ftp.exe. I ran a port scanner from grc.com and it listed 21 as open 
20 as closed, maybe my ISP blocks 20.  I configuring 2120-2121 in my router 
and reconfigired IIS to 2121, but still no luck.  When this was done the por
t scanner showed 2121 as open 2120 closed. I tried various other port number
s and the same results.  I will read the articles you posted. Thanks for you
r help.

quote:
Originally posted by Bernard 
a) first test everything locally. try ftp.exe at local machine.
make sure everything working before you proceed b)

b) use ftp.exe can connect remotely.. outside your LAN.
ftp youpublicip

do you see login prompt ?
can you login ?
can you do dir listing ?

Ftp operation mode and ports requirement, read
Information About the IIS File Transmission Protocol (FTP) Service
http://support.microsoft.com/?id=283679

to be clear.
inbound 21
outbound 20

passive port range.. you can customize it.
How To Configure PassivePortRange In IIS
http://support.microsoft.com/?id=555022


--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



"ewruff" <ewruff.18hc8z@mail.webservertalk.com> wrote in message
news:ewruff.18hc8z@mail.webservertalk.com...
>
> I am running Windows 2003 Advanced Server with all of the current
> updates.  My problem is accessing the FTP site from outside of my LAN.
> I am hosting my own WWW site using a free URL from DynDNS.org the
> website's URL is linked to a service that updates my local IP address,
> the site works fine externally.  I want to use the same url except ftp
> instead of http as the protocol.  I can connect to the FTP site using
> the private ip address from another computer on my LAN, and my router
> firewall is set up correctly to forward ports 20-21 to the private ip
> of the server.  I also tryed setting up a new ftp site and forwarding
> to port 2020-2021 to make sure my ISP is not blocking port 20-21.  I
> even placed the server ip address in the DMZ to make sure it is not a
> router issue.  I have my DNS server pointed to the DNS server for the
> DynDNS.org service as they require.  NSLOOKUP resolves both my public
> and private ip address and the URL.  Here is the error I get when
> trying to log in.
>
> 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
>
>
>
> --
> ewruff
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message283764.html
> 

[ Post a follow-up to this message ]

Alun,

Thank-you for you contributions, I will try the debug mode along with the pr
evios post.  I am truly baffled at this problem, I appreciate everyones help
.  I did previously have a ftp server running on an xp machine, which worked
 fine with this configuration, that machine is now formatted as this 2003 ad
vanced server.  The new server is the only machine that has an ftp server ru
nning on my network.

quote:
Originally posted by Alun Jones [MSFT] 
> 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.
~~~~ 

[ Post a follow-up to this message ]

> From: ewruff <ewruff.18mw92@mail.webservertalk.com>
>
> Thank-you for you contributions, I will try the debug mode along with
the previos post.  I am truly baffled at this problem, I appreciate
everyones help.  I did previously have a ftp server running on an xp
machine, which worked fine with this configuration, that machine is now
formatted as this 2003 advanced server.  The new server is the only
machine that has an ftp server running on my network.

Has anything new occurred on this problem?  Did "ftp -d" tell you anything
new?

Alun.
~~~~

[ Post a follow-up to this message ]

ISA Server 2000 Hotfix for FTP Client Invalid PORT Command

http://www.microsoft.com/downloads/...2D797EA3-3958-4
CBB-872E-A34455D96E6C&displaylang=en


I hope that this helps

*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

[ Post a follow-up to this message ]