• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

Windows Firewall cannot start service Specific error code 14

This is a Domain environment. Firewall policy is set by group policy to leave the firewall service running but turn the windows firewall itself off. This is happening on windows 7 x64 machines and Server 2008 R2 machines. When you add them to the domain and reboot the windows firewall service will not start. When you try to start you you get an error "Windows Firewall Service cannot start. Specific Error code 14" If you remove it from the domain and reboot you can start the firewall service. You can then add it back to the domain and reboot and it will continue to work at the next reboot. Once you reboot the second time the service turns off and you cannot restart it until you remove it from the domain again. Google is surprisingly blank on this issue,
0
BFCorp
Asked:
BFCorp
  • 4
1 Solution
 
QlemoC++ DeveloperCommented:
No details in eventlog?
0
 
BFCorpAuthor Commented:
No it is not logging anything in the eventlog. I just double checked
0
 
WiReDWolfCommented:
Please post exactly what you put in your GPO regarding the firewall.  I suspect you have this set up backwards - you have disabled the service and left the firewall active.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
BFCorpAuthor Commented:
I have attached a screen shot of the settings. It is not all machines doing this. Its about 20% of them
Firewall.bmp
0
 
BFCorpAuthor Commented:
The solution was to readd the local accounts for Localservice and networkservice.
0
 
BFCorpAuthor Commented:
It fixed it
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now