iis ftp: FTP: 500 Invalid port command -- iis ftp

You're in the

iis ftp

group:

FTP: 500 Invalid port command

HJ
10/9/2007 5:19:17 PM

iis ftp:

We have set up two FTP sites in IIS 6 on Windows Server 2003 R2 Standard
Edition, Service Pack 2.

The default site uses port 21 and points to a local directory.

The second site uses port 82 and points to a different local directory with
a LocalUser subdirectory for user isolation. If a user logs on to this FTP
site, he gets authenticated, but he does not see any files. The error says:

500 Invalid PORT Command.
Could not retrieve directory listing for "/"

The users logging on have read and write permissions on the directories and
the files.

I have read a number of newsgroup message about this error, but I cannot
find a solution.

What can I do to fix this error message and to see the files?

Thanks,

HJ

Re: 500 Invalid port command

Bernard Cheah [MVP]
10/10/2007 12:00:00 AM

Well,I saw few managed to fix by upgrading the router/nat device firmware,
etc.
and as per this kb. it is NAT related.
FTP Error: 500 Invalid PORT Command
http://support.microsoft.com/Default.aspx?id=281193

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/

[quoted text, click to view]

Re: 500 Invalid port command

HJ
10/10/2007 10:36:53 PM

Thank you for responding. We will look into this, but I think that the
article will not provide a solution. We have this problem on a new web
server that is hosted at the same internet provider as our old web server;
and on the old web server there was no problem with FTP (and on both servers
the Windows Firewall is turned off). The old web server was also Windows
Server 2003 with IIS 6.

We already tested using port number 18 (therefor lower than 21), but that
gave the same error.

So I am at a loss here. What else might be wrong?

HJ

[quoted text, click to view]

Re: 500 Invalid port command

Bernard Cheah [MVP]
10/11/2007 12:00:00 AM

Well, that's MS KB's explanation.
In your case, which is not on a typical dsl modem/router NAT setup but
rather a real ISP, and with one of the server working. then yes! not
acceptable when the other server is not working.

Are both server running side by side now ? or the new one replaced the old
one ?
what's the OS for the old one? same subnet ? same router or firewall rules
by isp ?
what is the difference between the old and new? in term of OS config,
network config, isp config?
both ftp servers also serving more than 1 site ? like you posted in the
first post?
only the non default port (21) sites give you this error ?
same error when you connecting via ftp.exe locally at the server?

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the iis ftp group.

home · blog · groups

Questions? Comments? Contact the dn