Close Port 135? Safely Disable RPC?

Discussion in 'other security issues & news' started by Thelps, Jul 16, 2018.

  1. Thelps

    Thelps Registered Member

    Joined:
    Apr 1, 2012
    Posts:
    46
    This thread has been asked many times before. Just hoping there have been new developments...

    I'm trying to close Port 135 and (if possible) disable Remote Procedure Call.

    I'm aware accepted wisdom is that RPC is essential and Windows won't run without it.

    I found This Article:

    https://social.technet.microsoft.co...w-can-i-close-rpc-ports?forum=w7itprosecurity

    (Read the 2nd post in the thread).

    The solution didn't entirely work for me (ended up with BSODs). Wondering if anyone else has better luck with it or if they know other ways to close this port and possibly this service...?
     
  2. reasonablePrivacy

    reasonablePrivacy Registered Member

    Joined:
    Oct 7, 2017
    Posts:
    2,010
    Location:
    Member state of European Union
    I quote post 3rd and 4th:
    Really, using firewall is enough... Even built-in Windows Firewall, when used properly, is enough...
     
  3. TairikuOkami

    TairikuOkami Registered Member

    Joined:
    Oct 10, 2005
    Posts:
    3,440
    Location:
    Slovakia
    Disabling port 135 disabled Task Scheduler service (Windows updates, updating certificates, SMART, etc). I used this on 10, when it was released, never tried it again though.
    Code:
    http://www.softpedia.com/get/Security/Firewall/Windows-Worms-Doors-Cleaner.shtml
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.