Cannot start Base Filtering Engine on 2008 server joined to 2003 domain

After initial boot of the server (factory install) the server was joined to
the 2003 AD domain. Prior to rebooting I noticed that I was unable to make
any configuration changes to the Firewall i.e. add exceptions.
Upon rebooting the firewall service was not running and when I tried to
restart it, received a message saying that one of it's dependant services
(BFE) was not started.

Starting the BFE resulted in an error 5: Access is denied. This occurred in
both local and domain admin accounts.

Moving the server to a seperate OU that denies all GPOs resulted in the same
issues as did a gpupdate/reboot.

Setting BFE to run as the domain admin resulted in error 1297.

No domain policies are set to enforce.

Can anyone assist as this seems to be a common issue but the fixes above did
not resolve it?

Thanks

Paul

Meinolf
Fri Sep 05 04:28:10 PDT 2008

Hello Paul,

See your other posting in microsoft.public.windows.server.setup

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> After initial boot of the server (factory install) the server was
> joined to
> the 2003 AD domain. Prior to rebooting I noticed that I was unable to
> make
> any configuration changes to the Firewall i.e. add exceptions.
> Upon rebooting the firewall service was not running and when I tried
> to
> restart it, received a message saying that one of it's dependant
> services
> (BFE) was not started.
> Starting the BFE resulted in an error 5: Access is denied. This
> occurred in both local and domain admin accounts.
>
> Moving the server to a seperate OU that denies all GPOs resulted in
> the same issues as did a gpupdate/reboot.
>
> Setting BFE to run as the domain admin resulted in error 1297.
>
> No domain policies are set to enforce.
>
> Can anyone assist as this seems to be a common issue but the fixes
> above did not resolve it?
>
> Thanks
>
> Paul
>