How do I allow remote desktop connection remotely?

26 Replies

· · ·

Mace

OP

Denis Kelley

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 22, 2011 at 11:58 UTC

Try this. I have had to do this sometimes.

//thebackroomtech.com/2007/05/18/how-to-enable-remote-desktop-on-a-windows-xp-machine-remotely/

0

· · ·

Mace

OP

Sosipater

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 22, 2011 at 12:01 UTC

If there is a user at the remote computer you can get connected using join.me and then enable it yourself.

0

· · ·

Serrano

OP

JPo1215 Apr 22, 2011 at 12:01 UTC

Use this script. Works wonders

//community.spiceworks.com/scripts/show/302-enable-or-disable-rdp-remote-desktop-on-remote-system-vbs

0

· · ·

Mace

OP

Alex3031

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 22, 2011 at 12:24 UTC

I think you have all ready been pointed the right way, there are script that will enable RDP on a system as long as you have remote registry access. It looks like a couple of people have pointed you to scripts all ready.

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 12:30 UTC

trying the script but it says "make sure you type the right machine name" i have and doesn't work..tried IP, name and nothing

0

· · ·

Chipotle

OP

Kendall

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 22, 2011 at 12:31 UTC

did you run the script from your PC at home or the server that you are RDPed into?

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 12:54 UTC

Yea from remote location.

0

· · ·

Serrano

OP

Best Answer

Don7478 Apr 22, 2011 at 13:08 UTC

From the onsite computer run Regedit.

In Regedit:
File-->Connect Network Registry

In the 'Select Computer' dialogue make sure that the 'Look In' location is correct(should be your domain if applicable)type in the computer name or IP that you want to connect to then click Ok.

Now expand:
<computername>HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

Once you've opened that key look for fDenyTSConnection

Set it to a value of 0 <--a zero

The computer will have to restart for the change to take effect.

1

· · ·

Serrano

OP

JPo1215 Apr 22, 2011 at 13:41 UTC

is it possible the computer is off or in sleep mode? Can you ping it?

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 14:50 UTC

yep it pings.

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 14:55 UTC

seems as there's no way i can get to this.

0

· · ·

Serrano

OP

Don7478 Apr 22, 2011 at 15:05 UTC

The registry edit didn't work? What were the results when you tried?
Were you able to get to it's registry?

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 15:17 UTC

I was able to type the IP and it took me to the enter username and password. I inserted the right username and password and nothing.

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 15:25 UTC

I was able to use the script just fine to my window servers by simply inserting the IP and it gave me the option to enable and disable, but the problem is i am trying to get to a desktop in the office it just doesn't work. I was able to get a ping from the adress.

0

· · ·

Serrano

OP

JPo1215 Apr 22, 2011 at 15:47 UTC

so the script works on the servers, you can ping the desktop which proves connectivity, you can run regedit on the desktop but cant authenticate...

do you have admin rights to the desktop?

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 15:51 UTC

I just found out the desktop is not on the domaincontroller, but can still ping..would that have something to do with it?

0

· · ·

Serrano

OP

Don7478 Apr 22, 2011 at 15:53 UTC

Most definitely wold change the permissions required.

0

· · ·

Datil

OP

Cazi Apr 22, 2011 at 16:27 UTC

If the desktop is not on the domain you would need to enter local admin credentials when connecting to the remote registry.

0

· · ·

Serrano

OP

JPo1215 Apr 22, 2011 at 16:34 UTC

ciprian3798 wrote:

I just found out the desktop is not on the domaincontroller, but can still ping..would that have something to do with it?

yes it does.

in that case:

Cazi wrote:

If the desktop is not on the domain you would need to enter local admin credentials when connecting to the remote registry.

+1

0

· · ·

Jalapeno

OP

chip379811 Apr 22, 2011 at 17:17 UTC

i tried and some reason username/password doesn't work.

0

· · ·

Mace

OP

Alex3031

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 22, 2011 at 19:49 UTC

ciprian3798 wrote:

i tried and some reason username/password doesn't work.

Might need tobe in the format of PCName\LocalUsername & Password.

0

· · ·

Serrano

OP

RjD Apr 23, 2011 at 14:48 UTC

I have also seen where strangely there were no users in the remote desktop group(including local and domain admins), never was too sure the how or why that one occured i just added them into the group and it worked fine afterwards. another thing is the firewalls may be causing blockages check those settings remotely as well for both port and program access

0

· · ·

Habanero

OP

CE Harden

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Apr 25, 2011 at 07:29 UTC

I created this a long time age:

//community.spiceworks.com/scripts/show/616-enable-remote-desktop-remotelyand you may like:

//www.lazynetworkadmin.com/knowledgebase-mainmenu-6/2-windows/68-remote-assistance-take-control-without-permission

I make that one a few years back with help from another admin.

0

· · ·

Chipotle

OP

lt.son Apr 25, 2011 at 08:39 UTC

I use Remote Enabler.

It's quick and easy.

//download.cnet.com/Remote-Desktop-Enabler/3000-2094_4-10572855.html

0

  • prev
  • 1
  • 2
  • next

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Remote Desktop - Allow access to your PC

Is this page helpful?

Yes No

Any additional feedback?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Submit

Thank you.

In this article

Applies to: Windows Server 2022, Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2

You can use Remote Desktop to connect to and control your PC from a remote device by using a Microsoft Remote Desktop client (available for Windows, iOS, macOS and Android). When you allow remote connections to your PC, you can use another device to connect to your PC and have access to all of your apps, files, and network resources as if you were sitting at your desk.

Note

You can use Remote Desktop to connect to Windows 10 Pro and Enterprise, Windows 8.1 and 8 Enterprise and Pro, Windows 7 Professional, Enterprise, and Ultimate, and Windows Server versions newer than Windows Server 2008. You can't connect to computers running a Home edition (like Windows 10 Home).

To connect to a remote PC, that computer must be turned on, it must have a network connection, Remote Desktop must be enabled, you must have network access to the remote computer (this could be through the Internet), and you must have permission to connect. For permission to connect, you must be on the list of users. Before you start a connection, it's a good idea to look up the name of the computer you're connecting to and to make sure Remote Desktop connections are allowed through its firewall.

Remotely Enable Remote Desktop on Windows 10

/ / Information Technology

We’ve all been there – we’ve finished at a customer’s site, and need to quickly remote in later on to finish/fix something. Trouble is, Windows doesn’t enable Remote Desktop Protocol by default.

There are four steps needed toremotelyenable RDP connections in Windows 10.

  1. Open ports in the Windows firewall
  2. Edit the registry
  3. Start the Remote Desktop service
  4. Connect

This guide relies on you being on the same LAN as the remote PC you wish to access – you may already have RDP’ed into another server on that LAN. You must also have Windows administrativeprivilegesfor the remote computer. These instructions work well in a domain environment.

Note: If you have access to the computer, you can follow the standard procedure for enabling Remote Desktop.

How to allow remote connections on Windows 10

The Remote Desktop app is easy to use to connect to other devices. However, the configuration you need will depend on whether you're trying to connect in the local network or through the internet.

Enable remote connections on Windows 10

When trying to start a remote connection from within the local area network (LAN), you only need to make sure the computer you're trying to access has the option to allow remote desktop connections enabled.

Control Panel

To enable remote connections on Windows 10, use these steps:

  1. Open Control Panel.
  2. Click on System and Security.
  3. Under the "System" section, click the Allow remote access option..

    Source: Windows Central

  4. Click the Remote tab.
  5. Under the "Remote Desktop" section, check the Allow remote connections to this computer option.

    Source: Windows Central

  6. Check the Allow connections only from computers running Remote Desktop with Network Level Authentication option.
  7. Click the OK button.
  8. Click the Apply button.
  9. Click the OK button.

Once you complete the steps, remote desktop connections will be allowed on the device. Windows 10 will even add the necessary rules in the built-in Microsoft Defender Firewall, but you may need to configure the rules manually if you have a third-party firewall.

Settings app

You can also enable the Remote Desktop feature using the Settings app with these steps:

  1. Open Settings.
  2. Click on System.
  3. Click on Remote Desktop.
  4. Turn on the Enable Remote Desktop toggle switch.

    Source: Windows Central

  5. Click the Confirm button.

If you're setting up a remote desktop using an internet connection, continue with the steps below. If you're trying to connect to another device within the local network, you can skip to the steps below, and continue with the start a remote desktop connection instructions.

Enable remote connections on router

If you have to access the computer over the internet, you will also have to configure the router (modem) to allow the remote connection. A process that also requires knowing the public address to contact the remote computer.

Configure static IP address on Windows 10

Computers usually get assigned dynamic IP addresses from the DHCP server (router), which means they can always change. If you plan to use remote desktop often, you may want to configure a static IP address to avoid reconfiguring port forwarding on the router when the computer gets a new address.

Control Panel

To set a permanent IP address configuration, use these steps:

  1. Open Control Panel.
  2. Click on Network and Internet.
  3. Click on Network and Sharing Center.

    Source: Windows Central

  4. Click the Change adapter settings option from the left navigation pane.

    Source: Windows Central

  5. Right-click the active adapter and select the Properties option.

    Source: Windows Central

  6. Select the Internet Protocol Version 4 (TCP/IPv4) option.
  7. Click the Properties button.

    Source: Windows Central

  8. Click the General tab.
  9. Select the Use the following IP address option.
  10. Specify a valid local IP address outside the local DHCP scope to prevent address conflicts. For example, 10.1.4.201.

    Source: Windows Central

    Quick tip: Typically, you'll find this information on the router inside the DHCP settings section. The routers' interface is always different per manufacturer, which means that you may need to consult your manufacturer support website for more specific details. If you're unsure of the configuration you have to use, you can use your current TCP/IP configuration as a reference, which you can find running the ipconfig /all command in Command Prompt.

  11. Specify a subnet mask for the network (for example, 255.255.255.0), but the system usually fills this infomration for you based on the "IP address" you entered earlier.
  12. Specify the default gateway address, which is the router's address—for example, 10.1.4.1.
  13. Under the "Use the following DNS server addresses" section, in the "Preferred DNS server" field, specify the IP address of your DNS server, which in most cases is also the address of the router —for example, 10.1.4.1.

    Quick tip: If you can't connect to the internet, you may also want to try using one of the Google Public DNS addresses (such as 8.8.8.8) for the "Alternate DNS server" option.

  14. Click the OK button.
  15. Click the Close button.

After you complete the steps, the new network configuration will apply, and the IP settings will never change.

Some routers include a feature to make the current TCP/IP configuration static. If you want to use this option instead, you can consult your manufacturer support website for specific steps on how to complete this task.

Determine network public IP address

You'll also need the remote network's public IP address to contact the device over the internet.

To find the IP address assigned by the Internet Service Provider (ISP), use these steps:

  1. Open web browser.
  2. Visit Bing.com or Google.com.
  3. Search for "What's my IP."
  4. Confirm your public IP address in the first result.

    Source: Windows Central

Usually, for residential customers, internet providers also offer dynamic public IP addresses, which means that your public IP address may change from time to time.

If you need a more reliable solution, there are "Dynamic Domain Name System" (DDNS) services (such as DynDNS, OpenDNS, No-IP, Asus.com (for Asus routers)), which can track the public IP changes. Alternatively, you can also contact your ISP to request a static IP address, but it might costs you additional since this is typically a feature reserved for business.

Forward port on router

You must also forward the TCP port 3389 on the router to allow a remote connection over the internet to the computer in the local network.

Quick note: The interface to change the router settings are different per manufacturer, and sometimes even per model. However, you can use the following instructions as a reference to configure your router. You can always check the manufacturer support website for more specific details.

To forward a port on your router, use these steps:

  1. Open Start.
  2. Search for Command Prompt and click the top result to open the console.
  3. Type the following command to view the current TCP/IP configuration and press Enter:

    ipconfig

  4. Under the "IPv4 Address" field, confirm the device address. For example, 10.1.4.100.
  5. Under the "Default Gateway" field, confirm the device gateway address (the router address)—for example, 10.1.4.1.

    Source: Windows Central

  6. Open web browser.
  7. Type the IP address of the router (Default Gateway) in the address bar and press Enter.
  8. Sign in to the router using the correct username and password.

    Quick tip: If you have never done this, and you are using the router provided by the ISP, you can find the information on a sticker attached to the device.

  9. Browse to the Port Forwarding settings page.
  10. Confirm that the Port Forwarding service is enabled (if applicable).
  11. Under the port forwarding list, click (in this case) the Add profile button.

    Source: Windows Central

  12. Create a new port forward with the required information. For example:

    • Service name: Specify the reference name for the service. For instance, OfficePC Remote (optional).
    • Protocol: TCP.
    • External Port: 3389.
    • Internal Port: 3389.
    • Internal IP Address: Specify the IP address of the computer you're trying to connect. For instance, 10.1.4.100

    Source: Windows Central

  13. Click the OK button.

Once you complete the steps, the port will open on the router, allowing remote desktop connections through the internet to that specific computer.

Allow Remote Desktop via Group Policy ^

The easiest way certainly is to enable RDP access via Group Policy:Allow users to connect remotely using Remote Desktop Services

You can find the policy here:

Computer Configuration > Administrative Templates > Windows Components >Remote Desktop Services > Remote Desktop Session Host > Connections.

Allow users to connect remotely by using Remote Desktop Services

You will also have to allow RDP in the Windows Firewall on the remote Windows 10 computer:

Computer Configuration > Policies > Administrative Templates > Network > Network Connections > Windows Firewall > Domain Profile

Allow inbound Remote Desktop connections via Group Policy

The only problem is that Group Policy is sluggish, and if you want to log in quickly to a remote machine, it is often not an option. By contrast, on a PowerShell console, you can essentially get the job done with a single command.

Enable Remote Desktop via PowerShell ^

However, there is a catch—actually, two. Windows Firewall might get in your way, and if PowerShell remoting is not enabled on the machine, things can get a bit tricky. I know of two methods to enable Remote Desktop remotely via PowerShell. Which method you use mostly depends on your Windows Firewall configuration.

Let's assume first that PowerShell remoting is enabled on the remote machine. If so, you can simply enable Remote Desktop by modifying a registry key on the remote machine:

Invoke-Command -Computername <computer name> -ScriptBlock {Set-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name "fDenyTSConnections" –Value 0 }

We are using Invoke-Command to execute the Set-ItemProperty remotely, which changes the value fDenyTSConnections to 0.

Most likely, Windows Firewall blocks RDP on the remote machine. To open the Remote Desktop port, you can use this PowerShell command:

Invoke-Command -Computername <computer name> -ScriptBlock {Enable-NetFirewallRule -DisplayGroup "Remote Desktop"}

We are using PowerShell remoting again to execute Enable-NetFirewallRule remotely.

Video liên quan

Chủ đề