tag:blogger.com,1999:blog-1585105787473796476.post3833807726893409799..comments2024-03-29T10:50:44.713+00:00Comments on keyliner.blogspot.com: Configuring Windows Firewalltraywolfhttp://www.blogger.com/profile/06205565591880314520noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-1585105787473796476.post-40956903073649443282010-09-29T22:32:47.059+01:002010-09-29T22:32:47.059+01:00DUH...Found problem to not updating MSE and Window...DUH...Found problem to not updating MSE and Windows Defender. I changed the "local" ports instead of the "remote" port. After fixing my mistake, all is working. I stand corrected! Very helpful article.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1585105787473796476.post-43952060013244074132010-09-29T17:57:36.189+01:002010-09-29T17:57:36.189+01:00Follow these steps to grant an Exception in the Fi...Follow these steps to grant an Exception in the Firewall.<br /><br />1. As before, create a new Outbound Rule, selecting this program:<br />C:\Windows\System32\svchost.exe<br /><br />Name the rule "A-Svchost" so it sorts with the others.<br /><br />When selecting "svchost," Windows will display a warning. Ignore the warning and allow it to create the rule, but because this is an operating-system file, additional steps should be taken and these are detailed next.<br /><br />2. Edit the new rule's properties by double-clicking the name ("A-svchost").<br /><br />3. Illustrated below, select the [Programs and Services] tab<br />Click the "Settings" button.<br /><br />4. Choose the radio-button "Apply to this service"<br /><br />In the list, choose "Windows Update";<br />Click OK<br /><br />5. In the "Protocols and Ports" tab<br /><br />Change the Protocol Type from Any to "TCP"<br />Change the Remote Port from All Ports to "Specific Ports"; type ports "80, 443"<br /><br />Save the changes and close the entire control panel. Windows Update and Windows Defender should now work properly.<br /><br />Windows Defender and MSC did not update for me when I followed your instructions above. I changed the Protocols and Ports settings back to "Any" and they now update. Is there something that has changed since your posted instructions?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1585105787473796476.post-11233416578702948062009-06-13T03:54:33.768+01:002009-06-13T03:54:33.768+01:00D.Parsons asked: What firewall for XP? The author...D.Parsons asked: What firewall for XP? The author replies: I am partial to ZoneAlarm and recommend their free version.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1585105787473796476.post-27984936239450977612009-06-08T18:20:08.876+01:002009-06-08T18:20:08.876+01:00You talk about Vista but do you have a good system...You talk about Vista but do you have a good system for XP Pro?Doug Parsonshttp://thegreatserver.comnoreply@blogger.comtag:blogger.com,1999:blog-1585105787473796476.post-17871783799733056112009-05-30T19:03:03.694+01:002009-05-30T19:03:03.694+01:00You are correct. If configured as I recommended, p...You are correct. If configured as I recommended, ping only works inside the firewall (within the Default Gateway) but not beyond. I'll have to ponder this, as I am not a Router-god.traywolfhttps://www.blogger.com/profile/06205565591880314520noreply@blogger.comtag:blogger.com,1999:blog-1585105787473796476.post-51206078673373901412009-05-30T10:38:07.615+01:002009-05-30T10:38:07.615+01:00Nice article. I use Windows Firewall on Vista to b...Nice article. I use Windows Firewall on Vista to block outbound connections too however I'm facing some sort of strange bug with ping. Even if I allow outgoing rule for ping.exe I can not use ping it returns General Failure. I have to allow ICMP protocol type request globally without application specification to make it work but this is possible security hole. Other rules for applications work just fine. Does someone know where is the problem?Anonymousnoreply@blogger.com