Home / server / Questions / 327120
In Process
Chris
Asked: 2011-11-03 09:02:31 +0800 CST

Passive FTP Server Port Configuration Troubles Win2003

  • 772

Win2003

Ports 20 & 21 are open

IIS6 - Direct Metabase Edit enabled

Configured FTP service passive range to 5500-5550

5500-5550 added to windows firewall

iisreset and double checked by restarting ftp service

nothing has changed, when I connect and enter passive, it still hangs when ever I try to LIST or transfer files. Active is just as useless.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\user>ftp
ftp> open x.x.x.x
Connected to x.x.x.x.
220-Microsoft FTP Service
    xxxxxxxxxxxxxxxxxx
220 xxxxxxxxxxxxxxxxxx
User (x.x.x.x:(none)): user
331 Password required for user.
Password:
230-YOUR ACTIVITY IS BEING RECORDED TO THE FULLEST EXTENT
230 User user logged in.
ftp> QUOTE PASV
227 Entering Passive Mode (82,19,25,134,21,124)
ftp> ls
200 PORT command successful.
150 Opening ASCII mode data connection for file list.

and it hangs..

Now I can see from microsooft documentation that on newer windows releases, additional steps such as these are suggested, but they dont work on 2003...

netsh advfirewall firewall add rule name=”FTP Service” action=allow service=ftpsvc protocol=TCP dir=in
netsh advfirewall set global StatefulFTP disable

is there anything I am missing, what is this StatefulFTP malarkey at the end

EDIT

I can connect and transfer binary files using WinSCP client - Therefore the problem must be with my ftp commands no? Can anyone see anything wrong with my windows ftp client example? why would it hang on ls, i tried QUOTE LIST as well, and that just hangs, and the windows ftp client doesnt work in active, it hangs if I try to go "binary" then put - This worked before I added 5500-5550 on the router. I have since added this range to the router but no difference to the windows ftp client.

ftp windows-server-2003 iis-6

2 Answers

  1. Maybe it is the firewall that block...

    To correct this issue and allow FTP state tracking on Windows Firewall, run this command from a command prompt :

    netsh advfirewall set global StatefulFtp enable

    or put inetsrv.exe in the trusted program of the firewall .

    EDIT

    Script to configure firewall on windows server 2003 :

    C:\Inetpub\AdminScripts\adsutil.vbs set /MSFTPSVC/PassivePortRange “ 5500-5550″
FOR /L %I IN (5500,1,5550) DO netsh firewall add portopening TCP %I “Passive FTP Port “%I
    • 1

  2. Turns out windows ftp client needed adding to the firewall LOL

    • 0