D
dowNNshift
Guest
After much of testing and troubleshooting of Plesk 8.2 prior to our latest server deployment, we finally discovered a solution to a persistent Windows Server 2003 Web Edition SP2 FTP Port 21 firewall issue.
The problem; Whenever the main firewall was activated within the Plesk control panel (thus activating the full Windows Firewall SP2), all attempts to connect via FTP port 21 were dropped and unable to connect. With the firewall off, connections via FTP port 21 work fine -- verifying that it was a Windows Firewall blocking conflict. Notably all other opened ports (DNS, HTTP, HTTPS, SMTP, POP, etc) worked correctly with Windows Firewall on or off.
We verified that a rule allowing port 21 connections was allowed in both Windows Firewall and in the Plesk Control Panel >> Server >> IP Addresses >> Firewall >> Local Area Connection.
Our solution; We discovered that the installer had created a Windows Firewall conflict by adding a FTP exception rule in the Windows Firewall >> Local Area Connection >> Advanced Tab. We unchecked all FTP rules where found, and then created a simple exception in the Windows Firewall >> Exceptions Tab.
We added a new exception titled, Plesk FTP (Port 21), and then the TCP port 21.
Now we can connect via Active FTP through the Windows Firewall.
Will the SWSoft software engineers please look into correcting this Windows Firewall conflict in future revisions, and/or issue a knowledge base bulletin.
The problem; Whenever the main firewall was activated within the Plesk control panel (thus activating the full Windows Firewall SP2), all attempts to connect via FTP port 21 were dropped and unable to connect. With the firewall off, connections via FTP port 21 work fine -- verifying that it was a Windows Firewall blocking conflict. Notably all other opened ports (DNS, HTTP, HTTPS, SMTP, POP, etc) worked correctly with Windows Firewall on or off.
We verified that a rule allowing port 21 connections was allowed in both Windows Firewall and in the Plesk Control Panel >> Server >> IP Addresses >> Firewall >> Local Area Connection.
Our solution; We discovered that the installer had created a Windows Firewall conflict by adding a FTP exception rule in the Windows Firewall >> Local Area Connection >> Advanced Tab. We unchecked all FTP rules where found, and then created a simple exception in the Windows Firewall >> Exceptions Tab.
We added a new exception titled, Plesk FTP (Port 21), and then the TCP port 21.
Now we can connect via Active FTP through the Windows Firewall.
Will the SWSoft software engineers please look into correcting this Windows Firewall conflict in future revisions, and/or issue a knowledge base bulletin.