I've used commandline FTP and other clients. PASV mode is for transfer, when
all external clients, while locally I can login without problem.
Reinstalling SP2 did fix the problem. Only disabling Windows Firewall can
"Deniz" <deniz.turkmen@gmail.com> wrote in message
news:1185229505.928213.105790@e16g2000pri.googlegroups.com...
> On Jul 23, 3:29 am, "Viktor Jevdokimov" <vik...@baltsoft.lt> wrote:
>> Have added inetinfo.exe to the Firewall - no changes.
>> Probably I need to try to reinstall SP2, since FTP service was added
>> after
>> SP2 was installed.
>> BTW, locally with Firewall enabled, FTP works fine, while from external
>> IP's
>> connection is dropped right after I entered user name.
>>
>> "Bernard Cheah [MVP]" <qbern...@hotmail.com.discuss> wrote in
>> messagenews:u2IPxxPzHHA.3768@TK2MSFTNGP06.phx.gbl...
>>
>> > ya. it checked for access ip before prompt for login.
>>
>> > do you have inetinfo.exe defined in the firewall exception list?
>>
>> > if you try ftp.exe command line to connect remotely, will it drop again
>> > after you entered the user name or ?
>>
>> > --
>> > Regards,
>> > Bernard Cheah
>> >
http://www.iis.net/ >> >
http://msmvps.com/blogs/bernard/ >>
>> > "Viktor Jevdokimov" <vik...@baltsoft.lt> wrote in message
>> >news:u$9GjMhyHHA.3564@TK2MSFTNGP04.phx.gbl...
>> >> No IP restrictions. BTW, if IP is rejected, why it is starting an FTP
>> >> connection and asking for a user name? If IP is restricted, connection
>> >> should be dropped before FTP welcome line and user name prompt.
>>
>> >> ".._.." <.....@yourmom.mil> wrote in message
>> >>news:q5Kni.36677$G23.20324@newsreading01.news.tds.net...
>> >>> There is an IP address-based ACL in the "Security" tab that allows
>> >>> the
>> >>> server to accept, or reject traffic from individual or blocks of IP
>> >>> addresses.
>>
>> >>> Your description is consistent with it being that the originating IP
>> >>> is
>> >>> on that list. So it's worth a check in there.
>>
>> >>> "Viktor Jevdokimov" <vik...@baltsoft.lt> wrote in message
>> >>>news:%23W9xCufyHHA.2224@TK2MSFTNGP02.phx.gbl...
>> >>>> Hi all,
>>
>> >>>> Environment:
>> >>>> - Windws Server 2003 R2 Standard Edition Service Pack 2
>> >>>> - IIS with FTP service
>> >>>> - Windows Firewall enabled, TCP ports 21 and 20 are enabled both on
>> >>>> exceptions list and on connection.
>>
>> >>>> Problem: "Connection closed by remote host." right after user name
>> >>>> is
>> >>>> entered when connecting from outside.
>>
>> >>>> When testing locally on the server or when Windows Firewall is
>> >>>> disabled -
>> >>>> everything is fine, no problems. When Firewall is enabled,
>> >>>> connection
>> >>>> from
>> >>>> outside just drops right after user name is entered.
>>
>> >>>> IIS log file shows 421 FTP status and 121 win32 status.
>>
>> >>>> How to configure Windows Firewall properly for FTP service to work
>> >>>> from
>> >>>> outside?
>>
>> >>>> Thanks in advance,
>> >>>> Viktor
>
> Hi,
>
> Does your FTP client use passive mode? I was having similar problem,
> and disabling the passive mode solved the case. IIS 6 FTP service does
> not work properly in passive mode (high ports) while Windows Firewall
> is enabled. Or you can try what Bernard says, use ftp command line
> utility to see if you can connect, which doesn't send any PASV
> commands to the server.
>
> In my case, directory listing hangs at certain point when I use
> passive mode. I tried whatever was suggested (defining passive mode
> port range in Meta Base explorer and adding those ports to the Windows
> Firewall) but nothing helped but using active mode. I hope this helps.
>
> Deniz
>
>
> Deniz
>