Hi there, I have a bit of an unnerving problem. I tried searching through Comodo's forums and even asked the question, but so far no answer. Here's what is happening, when setting up my bittorrent app and actually just about every P2P program, I of course set the Network Rules in Comodo. I set a specific port, then set that specific port in the application. I then make sure that the rules are above the "Block" rule in Comodo. Now, here comes the fun part. When the app tries to connect, 1 of 4 things happens and they happen randomly: 1. The app tries to connect, Comodo asks if it's ok, I allow it and it works fine. 2. The app tries to connect, Comodo says it's trying to connect to a DIFFERENT port than I have set up in the firewall and the app, I block it and the app won't work of course. 3. The app tries to connect, Comodo says it wants to connect to the CORRECT port for TCP, but an INCORRECT port for UDP. I allow the TCP and block the UDP and the program works but not the way it should, ie I can't search. 4. The app tries to connect, Comodo says both TCP and UDP are trying to connect to the CORRECT port, it works fine for a while, then Comodo pops up and the app now decides it wants to connect to the INCORRECT port, I block it, and the program goes useless. Now, the ports in question. I use very high port numbers, usually above 50000, when these problems occur, it's because the application is trying to connect to the "old P2P ports", ie the 6000 range. Now, this did NOT happen in the previous version of Comodo, only this new one. What in the world is causing this? I feel insecure for one thing, and for another it turns my apps useless. In fact, this new Comodo seems to have a LOT of OLE/Parent/Hook-type "warnings". Sometimes I have to click "Yes" 3 or 4 times just to let a browser through, most often with Firefox. I don't think my system is causing this, I don't run a router right now, and it was happening on a previous installation of Windows, and I just reinstalled Windows the other day, tightened up security and all that good stuff. There has got to be something going on with that firewall. If it can't get figured out, I'm going to have to move on to another firewall because this makes me nervous. If I do have to move on, are there any decent free firewalls left? Sygate is gone, Outpost Free is gone/outdated,LNS I know nothing about, and ZoneAlarm Free, well, it was hands down the easiest one to set up and NEVER gave any trouble letting apps through. BUT, I can't find a single soul willing to give it a half decent remark, everybody hates it, so I guess it's out.