The Windows Filtering Platform has blocked a packet.

We setup 4 new DC's in our AD domain after we updated our schema to 2008 R2. The 4 new DC's are standard builds with all the latest updates applied and now changes to the default firewall settings. In our security logs we are getting thousands of 5152 audit failures.

The Windows Filtering Platform has blocked a packet.

Application Information:
      Process ID:            0
      Application Name:      -

Network Information:
      Direction:            Inbound
      Source Address:            xx.xx.xx.xx
      Source Port:            7474
      Destination Address:      xx.xx.xx.xx
      Destination Port:            32775
      Protocol:            17

Filter Information:
      Filter Run-Time ID:      68188
      Layer Name:            Transport
      Layer Run-Time ID:      13

They are announcement broadcasts that are being dropped.
According to this article I should be able to disable these so my event logs stop filling up.

http://blogs.technet.com/instan/archive/2009/01/08/the-windows-filtering-platform-has-blocked-a-bind-to-a-local-port.aspx

However, the logs start filling up again after a few hours or right away after a reboot. Looking for any suggestions out there. This article seems to be similar to what I have but it does not list R2 as one of the systems it is supposed to fix.

http://support.microsoft.com/kb/969257
 Looking for someone who may have some experience with this.
LVL 2
DKAdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

wantabe2Commented:
This will lead you in the right direction. It looks like the enable feature it audited by default.

http://blogs.technet.com/instan/archive/2009/01/08/the-windows-filtering-platform-has-blocked-a-bind-to-a-local-port.aspx
0
DKAdminAuthor Commented:
Sorry but I already listed that link in my original question but it does not solve the problem permanently as my question explains.
0
DKAdminAuthor Commented:
I found the issue to be a buried gpo setting under the Default Domain Policy. Computer Configuration, Policies, Windows Settings, Security Settings, windows firewall with Advanced Settings, domain profile, logging. Click Customize and set log dropped packets and log successful connections to No.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.