윈도우8 방화벽 문제

카테고리 없음 2013. 2. 4. 11:06

rror code 5 will be an access denied issue, most likely. To what the access denied error explicitly refers, I'm not sure at this point, however, if you've replaced the Security subkey, then that might have something do to with it.

Try using the Security Configuration and Analysis Wizard to resolve this. This is going to be a lengthy process (at least to read - it's not that long once you get into it), so get comfortable.

Part 1: Creating the policy template.
1. Open a command prompt.
2. Run mmc.exe.
3. File menu > Add/remove snap-in > Security Templates > Add button > OK button.
4. Right-click on the Security Templates > New Template Search Path > Select C:\Windows\Security\Templates as the destination.
5. Right-click the C:\Windows\Security\Templates directory > New Template > specify the name as Server 2008 Firewall > OK button.
6. Expand the Server 2008 Firewall node > click on the System Services node.
7. Right-click the Windows Firewall service > Properties.
8. Put a check in the "Define this policy" checkbox.
9. Select the Automatic radio button.
10. Select the Edit Security button.
11. Ensure the following entries are listed. If they aren't, then add them:
- SYSTEM: Full Control
- Administrators: Full Control
- INTERACTIVE: Read
12. Click OK, and OK again to close the Windows Firewall Properties dialog window.
13. Right-click on the Server 2008 Firewall node again on the left-hand side, and choose Save.

Part 2: Applying the template security.
1. In the same mmc, select the File manu > Add/remove snap-in > Security and Configuration Analysis > Add button > OK button.
2. Right-click the Security Configuration Node > Open Databse (think of this as Create Database).
3. Specify a database name > Open button.
4. In the Template window, open the C:\Windows\Security\Templates\Server 2008 Firewall.inf.
5. Right-click on the Security Configuration node > Configure Computer Now.

That's it. You've reset the security on the service to what it should be after building the OS, so try starting the service. If this does not succeed, then you'll know it's not the security on the service that is the issue.

Cheers,
Lain