Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Windows RDP

2»

Comments

  • MoopahMoopah Member

    @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    You can also set up VPN and restrict firewall rules to allow access to the internal VPN IP

  • dev_vpsdev_vps Member
    edited July 2024

    @Moopah said:

    @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    You can also set up VPN and restrict firewall rules to allow access to the internal VPN IP

    These are the steps to restrict Windows RDP only from selected ip addresses

    1. Open Windows Defender Firewall with Advanced Security

    1. Access Firewall Settings:
      • Open the Control Panel.
      • Navigate to System and Security > Windows Defender Firewall.
      • Click on Advanced settings in the left-hand menu.

    2. Create or Modify an Inbound Rule for RDP

    Option A: Modify Existing RDP Rule

    1. Locate RDP Rule:

      • In the left pane, click on Inbound Rules.
      • Scroll down to find the rule named Remote Desktop - User Mode (TCP-In) or similar.
    2. Edit the Rule:

      • Right-click on the rule and select Properties.
      • Go to the Scope tab.

    Option B: Create a New RDP Rule

    1. Create New Rule:

      • In the left pane, click on Inbound Rules.
      • In the right pane, click on New Rule.
    2. Rule Type:

      • Select Port and click Next.
    3. Select Ports:

      • Select TCP and specify port 3389 (default port for RDP).
      • Click Next.
    4. Allow the Connection:

      • Select Allow the connection and click Next.
    5. Specify Profile:

      • Choose when the rule applies (Domain, Private, Public). Typically, you would select all three for RDP.
      • Click Next.
    6. Name the Rule:

      • Give the rule a name (e.g., Restricted RDP Access).
      • Click Finish.

    3. Specify IP Addresses

    1. Scope Tab:

      • In the rule properties, go to the Scope tab.
    2. Remote IP Address:

      • In the Remote IP address section, select These IP addresses.
      • Click Add.
    3. Add IP Addresses:

      • Enter the IP addresses or ranges you want to allow. You can add individual IP addresses (e.g., 203.0.113.1) or a range of IP addresses (e.g., 203.0.113.0/24).
    4. Apply and Save:

      • Click OK to save the settings.

    4. Ensure Security of the RDP Port

    1. Change the Default RDP Port (Optional):

      • For additional security, consider changing the default RDP port from 3389 to another port. This requires editing the registry and firewall settings accordingly.
    2. Regularly Update Firewall Rules:

      • Periodically review and update the list of allowed IP addresses to ensure it remains current.
    Thanked by 1imcool
  • @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    Just use a VPN in allow 1 IP in firewall you're fine

    Thanked by 1Frobsy
  • Windows RDP on a low-end machine
    Running Windows Server 2019 OS on 2 vCore / 2GB / 50 GB VPS

  • @WhiteRoseG said:

    @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    Just use a VPN in allow 1 IP in firewall you're fine

    Simple and effective. I never thought of that before
    thanks for sharing!

  • @dev_vps said:
    Windows RDP on a low-end machine
    Running Windows Server 2019 OS on 2 vCore / 2GB / 50 GB VPS

    Where do you get licenses from if you dont mind?

  • @Frobsy said:

    @WhiteRoseG said:

    @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    Just use a VPN in allow 1 IP in firewall you're fine

    Simple and effective. I never thought of that before
    thanks for sharing!

    How will you access the RDP if for some reason vpn is down or not accessible?

    Thanked by 1Frobsy
  • @dev_vps said:

    @Frobsy said:

    @WhiteRoseG said:

    @dev_vps said:
    Simple rules for keeping Windows RDP more secured

    • Administrator account must be disabled
    • Use non standard port for connecting with RDP

    Just use a VPN in allow 1 IP in firewall you're fine

    Simple and effective. I never thought of that before
    thanks for sharing!

    How will you access the RDP if for some reason vpn is down or not accessible?

    I won't be able to ahaha. I see your point!

  • @Frobsy said:

    @dev_vps said:
    Windows RDP on a low-end machine
    Running Windows Server 2019 OS on 2 vCore / 2GB / 50 GB VPS

    Where do you get licenses from if you dont mind?

    That is 2019 trial edition valid for 180 days.

    I have MSDN professional membership, so I have enough valid keys

Sign In or Register to comment.