RPC Dependency

Which Firewall rules are necessary with RPC depends on how you are using RPC.

RPC/TCP

If your component is dependent on RPC/TCP functionality then you should add two rules with the following parameters to your firewall rule group:

dir="in" protocol="6" lport="RPC-EPMAP" binary="%systemroot%\system32\svchost.exe" svc="RPCSS"

dir="in" protocol="6" lport="RPC" binary="<YOUR BINARY THAT RECEIVES RPC/TCP>" svc="<YOUR SERVICE THAT IS HOSTED BY THE BINARY>"

RPC/NP (Named Pipes)

If your component is dependent on RPC/NP functionality then a single rule is necessary:

dir="in" protocol="6" lport="445" binary="System"

DCOM

If your component is dependent on DCOM functionality then a single rule is necessary:

dir="in" protocol="6" lport="RPC" binary="<YOUR BINARY THAT RECEIVES DCOM>" svc="<YOUR SERVICE THAT IS HOSTED BY THE BINARY>"

If you require DCOM Activation calls then you will need to add an additional rule:

dir="in" protocol="6" lport="135" binary="%systemroot%\system32\svchost.exe" svc="RPCSS"

 

 

Show: