Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have Windows Server 2008 R2 installed and using XLight FTP Server. I need to use 2221 port as FTP. I've created rules in FireWall, also run commands:

netsh advfirewall firewall add rule name="FTP (non-SSL)" action=allow protocol=TCP dir=in localport=2221

netsh advfirewall set global StatefulFtp enable

FTP clients connect, but hangs on getting list of files and directories.

How to resolve that problem. Thank you!

share|improve this question
Force a passive data channel instead? – Steve-o Feb 1 '13 at 14:34

By default active FTP uses port 21 for control messages and 20 for data transfer and passive uses 21 for control and > 1023 for data transfer. The easiest way to resolve this in Windows is to use a program or service based rule instead of a port-based one.

share|improve this answer
Thanks a lot, will try – ihorko Feb 1 '13 at 13:57
I added this program to rule, it doesn't help, same problem, ftp client can't get list of files and folders – ihorko Feb 1 '13 at 14:07
Have you restarted the FTP server service since adding the rule? Also, is the FTP client that you're using aware of your alternate port scheme? – MDMarra Feb 1 '13 at 14:33
Yes, I restarted FTP service of XLight FTP server and set up port 2221 in the XLight FTP server. I connect, but it hangs on on getting list of files and folders – ihorko Feb 1 '13 at 14:43
I would try with another FTP server software see if it's related to a problem with "XLight FTP Server" – ToastMan Feb 1 '13 at 18:46

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.