CFW 4 (64 bit) running under Win XP x64 Pro SP2 makes the computer it is installed on invisible to requests for remote desktop connections from other computers in my LAN. I found instructions for a workaround in this archived thread for v3:
https://forums.comodo.com/help-for-v3/comodo-fw-blocking-ms-remote-desktop-on-host-computer-t23595.0.html
However, I don’t understand why this should be necessary. I told CFW on installation to allow all LAN traffic. As a result, it automatically created 2 rules, one allowing all inbound traffic from the LAN, and one allowing all outbound traffic to the LAN. Neither of these rules specify a port or protocol. Therefore I would expect CFW to allow Windows Remote Desktop along with all of the other traffic in the LAN without the need for an additional rule. What logic might explain this counter-intuitive behaviour?
Also, why is the generic permission for the local network configured as 2 separate rules, instead of a single rule allowing in/out?
P.S. Adding the rule suggested in the v3 post mentioned above still didn’t fix the problem, or maybe I didn’t interpret it correctly. I added a rule allowing In/Out on the RDP for all addresses in the LAN zone. Perhaps “invisible” is the wrong expression for what is happening. When I try to connect with Remote Desktop, I get a timeout error. It’s not clear from the error message whether or not RD “sees” the host computer.
This is a K.O. criterion for me. If I can’t get RD to work, I’ll have to find another firewall.
P.P.S In further research, I came across two threads, which suggest that this is a problem with performance rather than a problem with rule definition:
https://forums.comodo.com/firewall-help-cis/comodo-firewall-causing-very-high-pings-in-windows-7-64bit-t61798.0.html
and
https://forums.comodo.com/firewall-help-cis/massive-ping-spikespacket-drops-t61995.0.html
Two incidental bits of information, which may be relevant:
- Before I installed CFW, I was using Windows Firewall, with which Remote Desktop connections worked fine.
- During the CFW installation, at the point where the kernel drivers are installed, Windows warned me that CFW (64 bit) didn’t fulfill the “Windows Logo” certification criteria.
P.P.P.S.
BTW, the original title was erroneous. I was trying CFW 5, not 4.
Reinstalling didn’t help, adding a rule for RD port 3389 didn’t help. Since RD is a service, not an application, I wouldn’t know how to add an application rule for it, as suggested in some threads.
IAC, since no one bothers to answer here, and since the last similar thread I found (https://forums.comodo.com/empty-t57302.0.html) doesn’t report any resolution of the problem, I have given up, deinstalled CFW5 and am now using Outpost 7.0 free. It is not as sophisticated as CFW, but it is free, supports XP x64 and seems to be adequate for my needs.