![]() ![]() Tick all the scopes and click next once more enter a name for the rule like (e.g.) "FTP server (control)" and a description and click "finish" to complete the rule creation Now, click "new rule" in the rightmost "actions" panel select the "port" option and click "next", select "TCP" and "specific local port" and enter 21 as the port number click "next" and select "allow the connection", then click next again Once the FTP server will be running and port 21/tcp will be shown as "LISTENING", you may go on creating the appropriate firewall rule, to do so, open the "server manager" expand the "configuration" node, then the "firewall" node and select "inbound rules" Then, check the contents of the file "ports.txt" and ensure that port 21/TCP is in the list, if that isn't the case then your FTP service isn't running or either it isn't listening on port 21 so you'll need to re-check your FTP server config Then, start by ensuring that your FTP service is running and listening to do so, fire up a command prompt (as admin) on the server console and enter the following commands netstat -aon|find "LISTEN" >ports.txt The "FTP connection issue" solved, please, try running anįrom another machine and ensure that the FTP will still allow the connection and the logonįirst of all DO NOT DISABLE THE FIREWALL ! Yes, it's possible, although such a thing is outside the purpose of this forum which is dedicated to the windows server security to proceed with further setup for your IIS FTP, please start a new discussion on the IIS forum at any rate, before considering I have question though, can i also use the server IP or the web app So, it sounds like the issue was caused by some misconfiguration of the FTP siteĪs I wrote, one step at a time. I recreated the FTP site using the link you provided.ģ31 Anonymous access allowed, send identity (e-mail name) as password. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |