Issues with opening allowed program DLLHOST in Firewall?

[MarkDunn]

I'm having problems seeing a LOT of machines on my network due to the RPC server not responding. One of the fixes mentioned is to run this on the machines in a .cmd file:

call netsh firewall set service RemoteAdmin enable
call netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
call netsh firewall add allowedprogram program=%windir%\system32\wbem\unsecapp.exe name=WMI
call netsh firewall add allowedprogram program=%windir%\system32\dllhost.exe name=Dllhost

My main concern with this is allowing dllhost as a program in the firewall. Isn't this process used by many virus writers to exploit dll files?

Any thoughts would be appreciated.

[MarkDunn]

I'm assuming this will suffice?

http://www.lansweeper.com/kb/firewall.aspx

[Hemoco]

MarkDunn wrote:
I'm assuming this will suffice?

http://www.lansweeper.com/kb/firewall.aspx

Yes, in a domain this is the easiest way.

[Hemoco]

All windows files can be potentially exploited if you don't install the latest Microsoft patches.

Easiest solution is to set up a group policy for the windows firewall