Win Server 2008 Standard BROKEN FIREWALL . . . .

Cannot create shares on a Windows Server 2008 (std) because of a Windows Firewall problem.

The end of this post contains a "fix" / "work-a-round".

Any downsides of this?

Yes: I know that reinstalling the OS would be the cleanest, but I really can't do that now.

Anyway, here it goes:

1.      When I tried to create the \UsersTest share on D, it failed with message “An error occurred while trying to share UsersTest.  There are no more endpoints available from the endpoint mapper.”
2.      I tried to create any new “share” on either D or E, but both failed likewise. If we can’t create a new share anywhere on PNFS1, we certainly can’t move \Users from one volume to another.
3.      Research cites several different causes for that error message; a common one is failure of the Windows Firewall Service.  If the Windows Firewall is not running, you cannot create a share.
4.      Indeed, I found that I was unable to open the Windows Firewall snap-in.
5.      In “Services”, Windows Firewall may not even be there, or if it is, it will not turn on, with message “Error 1075: The dependency service does not exist of has been marked for deletion”. What dependency service is missing?
6.      I reviewed the “netsh” command line utility “netsh firewall” to verify that the service was not only disabled, but not even listed as present.
7.      As comparison, I successfully created “shares” on PNFS2 and PNFS3 without incident and, in both cases, Windows Firewall was running properly.
8.      Research (newsgroups/blogs) reveals that the absence or malfunction of Windows Firewall may be due to viral or malware infection that caused corruption in the Registry resulting in missing keys or entire hives.
9.      Further evidence that Windows Firewall (WFW) is malfunctioning:
•      Cannot open the Control Panel WFW snap-in.
•      Cannot start the WFW service (The dependency service does not exist…).
•      On the Service > Dependencies tab, “Base Filtering Engine” appears, but “Windows Firewall Authorization Driver” does not.
•      In C:\Windows\System32\Drivers, mpsdrv.sys exists, but in regedit, hive HKLM\System\CurrentControlSet\Services\MpsDrv\ is completely missing.
•      Registry hives HKLM\System\CurrentControlSet\Services\MpsSvc\ and HKLM\System\CurrentControlSet\Services\SharedAccess\ exist, but several keys are missing, when compared to similar servers where WFW is functional.  
•      In Device Manager > Show Hidden Devices > Non-Plug and Play Drivers > “Windows Firewall Authorization Driver” is missing.

1.      I found considerable evidence on the web that this problem is pretty common.
2.      But, sadly, I found no posts of a solution that worked with confidence.  I tried them all.
3.      Mostly, I read the only fix is to reinstall Windows to get WFW to work again.  
4.      While a reinstall certainly makes WFW works, I would like to avoid that, except as a last resort.  
5.      However, thru lots of additional research and trial and error, I have been able to duplicate the problem “on demand”, and thus, reverse-engineer a “work-around” solution that seems to work.
6.      If we can assume that there are no other underlying problems besides the WFW malfunction (which I cannot guarantee, but no other problems are evident), here is my reverse-engineered work-around…

a.      Go to a similar server (same OS, SP level), export these three hives as separate reg files:
HKLM\System\CurrentControlSet\Services\MpsDrv\    (mpsdrv.reg)
HKLM\System\CurrentControlSet\Services\MpsSvc\    (mpssvc.reg)
HKLM\System\CurrentControlSet\Services\SharedAccess\    (sharedaccess.reg)
b.      Copy each reg file to C:\temp of the ailing server.
c.      Execute each reg file.
d.      Reboot server.
e.      That’s it!  Check functionality of Windows Firewall (see Step 9 above).  
f.      The snap-in opens, the service starts, the dependency Windows Firewall Authorization Driver exists, etc.  And, you can now create a “share”.

I can only say that initial tests do not show any evidence of other problems after this “fix”, but I am hopeful that executing these three reg’s from a “good” server will correct the damage that was done, and it will not be necessary to reinstall Windows.

Who is Participating?
Darius GhassemConnect With a Mentor Commented:
No downsides.

Have you run sfc /scannow to see if this fixes system files?

I have done the same on a Vista machine
mike2401Author Commented:
Yes, we did do the sfc.

Glad to hear no major downsides.

mike2401Author Commented:
Please cancel the delete (sorry), I lost track of this thread.

I would like to award points.

I'm going to paste a link to this in the community support forum.

mike2401Author Commented:
Thank you, sorry for the delay.

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.