Base Filtering Engine (and Firewall) fails after upgrade to Server 2008 from 2003

After an upgrade of Server 2003 to server 2008 R2, the server can not accept connections, (but can connect outbound to other servers and the internet) because the Firewall is blocking inbound connections.

I've traced this down to the Base Filtering Engine failing due to "access denied".

There is a thread here in EE  ID:26191452 about permissions to start the BFE service being inadequate after an upgrade from 2003 to 2008.  Quite complex, but I've made the registry changes that were recommended.
BFE and Windows Firewall still won't start.

Any super experts who know how to debug this?

Who is Participating?
dakota5Connect With a Mentor Author Commented:
Quite Complex.  Microsoft has been working on this for days.  Base filtering engine won't start because of permission issues.  This forces the Firewall to enter a locked-down mode, rejecting all incoming traffic.

A temporary work-around is to disable the  Windows Firewall.  This prevents it from partially starting and going into a lock-down mode. (Might also need to disable  IPSec Policy Agent, and the Base Filtering agent.)

Technet blog describes fixing the Discretionary Access Control List (DACL).  Base Filtering agent fails because it does not have DACL controlled access to query the configuration of one or more services that are running.  This, in turn, prevents the firewall from starting correctly.  

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.