One week ago i updated my ZoneAlarm Pro 7.0.362.000en to ZoneAlarm Pro 7.0.408.000en
with a 'Clean Installation'. I dont change the recommended default settings.
My Windows XP Prof. PC are updated with SP2 and the latest Windows/office online updates.
Yesterday I have found out to my astonishment that with a Portscan http:// www.heise.de/security/dienste/portscan/
the port 135 is indicated as open, although in ZoneAlarm Pro 7.0.408.000en port 135 is registered as blocked.
(This are the default settings of ZoneAlarm Pro 7.0.408.000en)
(Firewall-> Internet zone Security = High, "block incoming tcp port 135, etc . ..." )
(Firewall-> Trusted zone Security = Medium)
There I knew from earlier Portscans that with previous ZoneAlarm Pro versions the port 135 was also blocked,
i have carried out the following tests.
I have played in a backup of the C-Partition on which still ZoneAlarm Pro 7.0.362.000en was installed.
Also with ZoneAlarm Pro 7.0.362.000en the port 135 is indicated with a Portscan as open.
I have played in a backup of the C-Partition on which still ZoneAlarm Pro 7.0.337.000en was installed.
Now with a Portscan the port 135 was also indicated as blocked.
Then I updated the ZoneAlarm Pro 7.0.337.000en version to ZoneAlarm Pro 7.0.408.000en.
With a Portscan the port 135 was indicated now again as open.
Then I deinstalliert ZoneAlarm Pro 7.0.408.000en and installed again ZoneAlarm Pro 7.0.337.000en.
With a Portscan the port 135 was indicated now again as blocked.
Can it be that ZoneAlarm Pro leaves the port 135 open starting from version 7.0.362.000en,
although the port 135 is registered in ZoneAlarm Pro 7.0.408.000en as blocked?
Windows XP Pro
Message Edited by hxllo on 09-28-2007 06:34 AM