Windows Firewall inbound rules still blocks ports

07
2014-07
  • albert einstein

    I applied inbound rules for port: 1935, as well as outbound.

    When I check on canyouseeme.org, it says it (port 1935) times out.

    When I completely turn off Windows 7's firewall, it works without a problem.

    I can't always have that off or with my luck Freddy Kruger will slash my PC to bits.

    Windows Firewall logs at %systemroot%\system32\LogFiles\Firewall\pfirewall.log show this:

    2014-04-21 19:59:43 DROP TCP 107.20.89.142 10.0.0.2 52974 1935 60 S 2436636932 0 14600 - - - RECEIVE

    I see the word "drop". I'm assuming that's why it's not connecting. So what's it mean and how do I fix this mess?

    • Answers
  • Alex

    I'm not sure what you are trying to achieve but I would try Comodo firewall as it lets you be selective of what you allow to happen on your system. Remember if you do this to not have both windows firewall and comodo running at the same time.


    • Related Question

    Windows 7 Firewall Blocking FTP Server
  • xichael

    Everything else is configured. When I turn the firewall off, it connects. When I turn it on, it doesn't. I've added inbound and outbound rules, opening port 21 for all programs and services, but it's not good enough. Why??


    • Related Answers
  • John T

    FTP uses 2 channels for communication, ftp-data (20) and the ftp control channel (21). Depending on how you have it configured, active or passive, it will require a different configuration.

    Windows makes things easier due to the fact that you can allow certain executables instead of specific ports. You can choose to allow the FTP server executable, or put the server into passive mode and allow ports 20 and 21.