[Curley_Boy]

Hi all, just been visiting grc.com, which advises me to monitor and block external access to port 135 (which aparently is used by the RPC service, svchost.exe)

Im currently running Tiny Personal Firewall 2, and have set the parameters up as follows:

Description: RPC
Protocol: TCP and UDP
Direction: Incoming

---Local Endpoint---
Port Type: Single Port
Port Number: 135
Only Application selected below: c:\winnt\system32\svchost.exe

---Remote Endpoint---
Address Type: Any Address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Windows always needs this port open to access the net. So I can't close it (and grc will therefore still report it as 'open') are the settings above correct to block access to this port externally?

[Jerry Atrik]

naw doesnt need 135 to access the net
but it does use it as a loopback.
close both directions and allow tcp/udp coms from local ip to 127.0.0.1 (local loopback address)