How to sucessfully block port 135?

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 -Loca ...

Windows Networking 2246 This topic was started by ,


data/avatar/default/avatar14.webp

302 Posts
Location -
Joined 2001-12-18
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?

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar12.webp

694 Posts
Location -
Joined 2002-06-10
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)