Step: On click "Add Roles" will bring up some begin Add Roles wizard and lots of stuffs to read if you want, once done click next Step: Open Server manager and right click on Roles and select "Add Roles"
#Windows ftp server 2008 install
Here is the step-by-step guide to Install IIS Web Server and add FTP server roles in Windows Server 2008 R2 Install Web Server (IIS) in Windows Server 2008 R2 or Windows Server 2012 (Which is very easy to figure out).Ĭreate your first or I say "Hello World FTP" site. To configuration FTP server in IIS following steps should be followed: Most of the process to configure FTP server in IIS 7.5 and Windows Server 2008 (or R2) and configure FTP server in IIS 8 and Windows Server 2012 are same. Close FireFTP/client and retry and this time within any luck you'll be in.Windows server provides out-of-the-box FTP server feature in IIS. Be sure to restart the Microsoft FTP service service to pick up the new port range. I then thought the problem would be solved, but not quite. Now, in your firewall open up that range of TCP ports as "FTP passive port range".
In Data Channel Port Range, specify x amount of ports, in my case 10000-10125. Each FTP site you use will use these port ranges, individual FTP sites will have this option greyed out as it's inherited from this section. To fix, I loaded IIS (using version 8.0, believe it's the same in 7.5), at the server level of the tree (that is the top node) single click it and select "FTP Firewall support".
Also locally on the server - no problems. I knew it was a firewall issue as with the firewall off the FTP connects fine. Turns out it then picks some other dynamic ports. I had to open port 21 in the firewall which got me a stage further but it'd hang at Opening ASCII mode data connection. When setting up an FTP in IIS the default port will be 21. I was using FireFTP which by default connects via passive mode. I had this problem and it was resolved by doing the following. If you can't get a smarter firewall, then you'll have to stick to the "open a bunch of ports" option (or switch to a protocol that doesn't need to open a bunch of random ports like ssh's sftp).
#Windows ftp server 2008 how to
You'll probably still want to force passive mode since some people don't know how to configure their FTP client properly and nearly everyone is behind a broadband router/firewall these days. This can often fix NAT addresses as well (when the firewall is also handling the NAT). The firewall will read the traffic on port 21 and open whatever port your server wants open. If you're not using SSL, the best answer is to see if you can get your firewall to do protocol inspection for FTP. If your server is using NAT you'll also need to set up the proper IP address for the server to advertise to clients, most obey whatever the server provides as the passive mode connection string and if the server thinks it's 10.1.1.1, that's what it's going to tell the clients. If you're using SSL, the only answer is to open a range of ports (say, 10000-11000) on the firewall and configure your FTP server to force Passive mode and use that port range.
I have ports 20, 21 open on my Windows firewall. This leads me to believe its a Firewall issue, (or even an IIS7 issue?) but I am unsure what ports I need to open? If I specify the "localhost" URL, I do not get the error.
#Windows ftp server 2008 full
If I specify my full FTP URL, I get the hanging error. Here is what bothers me.if I use DOS FTP commands, I can login and use the "DIR" command only if I use "localhost" as my address. I can remote desktop on to the server and through DOS commands I can login rather easily.īut if I issue a command like "DIR", it hangs with:Įverything I have researched and read points to Firewall ports and/or Passive/Active mode settings. I am setting up an FTP server on my Windows 2008 server (R2).Įverything appears to be installed correctly but I am having trouble using an FTP Client to login to my FTP server.
0 kommentar(er)
