I had several unpleasent experiences with Windows 2003 and Kerio Personal Firewall 2.1.5. From w2k days, I had been using this particular flavor of firewall which has very easy to use features for application level restrictions. For example, it was very easy to create rules to prevent services like svchost connect to microsoft IPs. The new version of Kerio Personal Firewall do not have application/service level configurability and hence I was stuck with version 2.1.5 from the good old days.
Now in windows 2003, everytime I install 2.1.5, OS wouldn't start from next boot.
I also happened to discover strange enmity between 2003 and KerioPF 2.1.5. I had Windows2000 running inside VMWare 4 on top of my Windows 2003. I installed KPF 2.1.5 in Win2000 inside VMWare just to discover 2003 is unstable - 2003 would lock up when VMWare fired Win2000.
I have been desperately searching for some Firewall tool that has configurability to application/service level for Windows 2003. (Built in firewall of 2003 which is included in Routing and Remote Access is more like a blind tap either you open or close certain port unconditionally).
Now in windows 2003, everytime I install 2.1.5, OS wouldn't start from next boot.
I also happened to discover strange enmity between 2003 and KerioPF 2.1.5. I had Windows2000 running inside VMWare 4 on top of my Windows 2003. I installed KPF 2.1.5 in Win2000 inside VMWare just to discover 2003 is unstable - 2003 would lock up when VMWare fired Win2000.
I have been desperately searching for some Firewall tool that has configurability to application/service level for Windows 2003. (Built in firewall of 2003 which is included in Routing and Remote Access is more like a blind tap either you open or close certain port unconditionally).