Talk:Network Configuration

net also attracted malicious users who are actively exploiting design flaws, bugs and the inexperience of other users. A well known software company located in Redmond certainly played a part in this"
- How typical. I'm sick of people blaming any and all security issues on Microsoft. The only reason more flaws are discovered in Windows is because it is targeted more.203.122.246.191 05:06, 15 February 2008 (CET)

"It would be FAR easier to just disable the useless Windows firewall. All problems solved."
-And again. The Windows firewall is not useless. There are better solutions out there, but stop blaming all your problems on Microsoft.203.122.246.191 05:06, 15 February 2008 (CET)

-khammond 11/13/2008

Updated the Windows Firewall section to include issues uncovered regarding the "Appliation Layer Gateway" and "Routing and Remote Access" services. We ran into these problems firsthand and disabling the "Application Layer Gateway" service resolved our problems. Unfortunately some of us need to use the Windows firewall when a hardware firewall is unavailble.

Using anything other than port 990 for implicit SSL will not work. I tried it. Filezilla server allows you to change this port but if you do you filezilla clients will fail their connect. The WIKI needs to cover this and let users know because the implication is that it is changeable, which it is not. More importantly, Filezilla clients are hard-coded for implicit port 990 and so wouldnt support setting it to anything else anyway. Mozkill 21:41, 11 May 2009 (UTC)

That's incorrect, the client supports implicit FTPS on all ports. --CodeSquid 14:08, 13 May 2009 (UTC)

I had to add the other exe without the space in it.