Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I struggled with the whole passive port range deal on IIS 7.0 tonight. I finally realized that it apparently only applies to FTP/ES or FTP/IS. When I try to do plain ftp, it assigns whatever the heck port number it wants when responding to a PORT request.

First of all, am I missing something. Secondly, if I'm not, why in the world does it work this way?

TIA.

share|improve this question

2 Answers 2

I stumbled upon this question when I had the same problem today. I set the "Data Channel Port Range" in IIS 7.5 Manager console, but the server kept picking ports outside the specified range. The issue for me wasn't a firewall rewriting the response (I was using TLS, so it couldn't, even if it tried). Actually, after you change the port range, you have to restart the "Microsoft FTP Service". Using iisreset isn't sufficient, nor is clicking "Restart" at the server level in IIS Manager; the OS-level service (ftpsvc) must be fully stopped and started.

share|improve this answer
1  
thx - that &^%#^&%@#&* finally fixed it :) –  seanb Dec 22 '11 at 5:10
1  
thank you so much. that did it! –  Philipp Aumayr Jan 16 at 16:46
up vote 0 down vote accepted

I eventually determined that the $%(*&@ firewall was REWRITING the ftp commands in an attempt to be "helpful". I determined this when I tried to install FileZilla server and had the same problem. Luckily, FileZilla server has an open monitoring window, and I was able to observe the conversation from both sides and determine that the server was, in fact, sending the proper port number.

share|improve this answer

Your Answer

 
discard

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.