Answered by:
Some group policy firewall settings not being applied

Question
-
Hello,
I am attempting to configure windows firewall settings using group policy. I have linked it to some OU's and checked the results. None of the port or program exceptions are being set. Some of the other options are. The policy is set to force and it has the highest precedence in its OU. An example of a port setting is as follows:
135:TCP:192.168.4.0/24,10.0.0.0/8,192.168.7.0/24:enabled:End Point Mapper
There are about eight such port exceptions.
An example of a program exceptions is as follows:
%windir%\pchealth\helpctr\binaries\helpsvc.exe:"*":enabled:Remote Help
There are two such exceptions.
Is the format correct? Does anyone have any ideas?
Thanks,
Enby1429Thursday, February 12, 2009 4:31 PM
Answers
-
Hi,
Thank you for your post! I would suggest posting your question in one of the Microsoft TechNet > Forums Home > Windows Server > Group Policy located here: http://social.technet.microsoft.com/Forums/en-US/winserverGP/threads/.
Have a great day!
Sudarshan shindode Tier 2 Application Support Server and Tools Online Engineering Live Services Team- Proposed as answer by sudarshans1 Friday, February 13, 2009 5:10 AM
- Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, March 27, 2012 4:04 AM
Friday, February 13, 2009 5:10 AM -
Thanks. I found the answer. Case of unnecessary characters in a field. I needed to use * instead of "*".
- Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, March 27, 2012 4:05 AM
Friday, February 20, 2009 4:18 PM
All replies
-
Hi,
Thank you for your post! I would suggest posting your question in one of the Microsoft TechNet > Forums Home > Windows Server > Group Policy located here: http://social.technet.microsoft.com/Forums/en-US/winserverGP/threads/.
Have a great day!
Sudarshan shindode Tier 2 Application Support Server and Tools Online Engineering Live Services Team- Proposed as answer by sudarshans1 Friday, February 13, 2009 5:10 AM
- Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, March 27, 2012 4:04 AM
Friday, February 13, 2009 5:10 AM -
Thanks. I found the answer. Case of unnecessary characters in a field. I needed to use * instead of "*".
- Marked as answer by Ed Price - MSFTMicrosoft employee Tuesday, March 27, 2012 4:05 AM
Friday, February 20, 2009 4:18 PM