1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Windows Server 2008 R2 Security

Discussion in 'Web Hosting' started by bgp90, Aug 2, 2014.

  1. bgp90

    bgp90 Regular Member

    Oct 17, 2013
    Likes Received:

    I have a vps with Windows Server 2008 R2. When I scanned my vps for open ports, the ports 135 and 445 where open.
    After a lot of research I found out how to close these ports.
    I created two inbound rules which block the connection when someone wants to connect to port 135 or 445.
    After this I did another scan with the Gibson Research Corporation Shieldsup service and it gave me stealth for all the ports.

    But still I'm not sure if I did it in the right way. For instance, I choose for both blocking action TCP.
    Do I need also to create blocking actions for UDP?
    And do I need to create outbound blocking rules?

    I have searched the web a lot, but it is kind of confusing.
    Can anybody help me with this?
    Thanks in advance :)
  2. SharkServers

    SharkServers Jr. VIP Jr. VIP

    Jun 29, 2014
    Likes Received:
    Web Hosting
    DMCA? Pff! www.SuckMyBallsDM.CA
    Home Page:
    • Thanks Thanks x 1