FTP site on alternate port

[Giuseppe Pellegrino]

Hello,
I have a problem with a FTP site I'm configuring.

There are two FTP sites on this server (IIS 5.0 on Windows 2000 ADV SP4): a
default FTP site is configured on default port 21 and it works with no
hassles, connections are successful from both internal and external clients.

Another FTP site has been configured to respond through port 65001 and
here's the deal: internal clients connect immediately to this other site but
external clients go timeout right after authentication negotiation.
Apparently there is no problem with FTP publishing service for it responds
and authenticates as expected on port 65001, instead it hangs when it says
"receiving content folders" (or sort of) and only from external clients
after they authenticate.

One would say there's some kind of firewall filter for incoming connections
on port 65001 from the outside but this can't be for the following reasons:
- No firewall is present on this network (yet)
- No IIS lockdown Tool or Urlscan is installed/configured (yet)
- FTP is reachable and responds with required authentication as I said
before.
- Plain Windows98 and Windows 2000 clients with no firewall were used for
testing connections from the outside.

I have tried moving the site to some other ports such as 8080, 8081, 3333
and so on and it is always the same. Thought the ports might have been busy,
but as I configure test WWW sites (not FTP) on those same ports they all go
fine wherever the connection comes from.

For those who would like to experience the problem I'm having, they can
access the FTP sites with these addresses, they both contain one text
document..

FTP Site #1 (working) redirects to C:\Inetpub\ftproot
ftp://213.199.5.252:21

FTP Site #2 (not working) redirects to C:\Inetpub\ftproot2
ftp://213.199.5.252:65001

For testing purposes I set NTFS permission to grant full control to the
Everyone group and FTP authentication granted to the following user:

username: test
password: test

Can someone please help me figure this out?
Any help would be appreciated, thanks in advance.

Giuseppe Pellegrino

 

[Dave]

I get an error about 'invalid port command' when i try the 65001 site using
ie6. you might want to ask on the microsoft.public.inetserver.iis.ftp group
for a group that is dedicated to this type of stuff. this sounds similar to
the active/passive problem when port 20 is blocked by 21 is ok, you get the
login but can't transfer any data. maybe there is some problem with
conflicts on ports, i'm not sure what the ftp server would do when you set
the port to 65001, would it still want to use 20 and conflict with the other
server or would it try some other port... in the ftp group someone probably
knows.

Hello,
I have a problem with a FTP site I'm configuring.

There are two FTP sites on this server (IIS 5.0 on Windows 2000 ADV SP4): a
default FTP site is configured on default port 21 and it works with no
hassles, connections are successful from both internal and external clients.

Another FTP site has been configured to respond through port 65001 and
here's the deal: internal clients connect immediately to this other site but
external clients go timeout right after authentication negotiation.
Apparently there is no problem with FTP publishing service for it responds
and authenticates as expected on port 65001, instead it hangs when it says
"receiving content folders" (or sort of) and only from external clients
after they authenticate.

One would say there's some kind of firewall filter for incoming connections