Microsoft Remote Desktop Not Connecting



Check Firewall Settings Next, check if Remote Desktop is enabled in the Windows Defender Firewall. To do so, type firewall in the Start menu. Now, select the Windows Defender Firewall option. Dec 09, 2014 Make sure the PC is turned on and connected to the network, and that remote access is enabled. If this keeps happening, ask your admin or tech support for help.' Everything is normal except the Remote Desktop app cannot connect. I have no connectivity problems with either device.

Microsoft remote desktop download

Nslookup rdweb.wvd.microsoft.com Try connecting with another client, like Remote Desktop client for Windows 7 or Windows 10, and check to see if you can open the web client. Can't open other websites while connected to the web client. If you can't open other websites while you're connected to the web client, there might be network connection. Go to “Start” “Administrative Tools” “Remote Desktop Services” “Remote Desktop Session Host Configuration“. Select “Connections“, right-click the name of the connection “Properties” “Client Settings” “Redirection“. Ensure that “Windows Printer” is not checked. Microsoft offers a service pack that includes the missing TLS support for the Remote Desktop Server on Window 2008 but it might also allow the Remote Desktop Client to make more secure connections. If not, you should look into updating the RDC on your 2008 server or use an alternative.

Windows Remote Assistance lets someone you trust take over your PC and fix a problem from wherever they are.

Before you can use it, you'll need to enable access. In the search box on the taskbar, type remote assistance, and then select Allow Remote Assistance invitations to be sent from this computer from the list of results. Then, on the Remote tab, select the Allow Remote Assistance connections to this computer check box, and then select OK.

Microsoft Remote Desktop Not Connecting

Microsoft Remote Desktop For Mac

To get help:

  1. In the search box on the taskbar, type remote assistance again and select Invite someone to connect to your PC and help you, or offer to help someone else.

  2. Select Invite someone you trust to help you.

  3. Do one of the following: If you've never used Easy Connect, select Use Easy Connect. If you've used Easy Connect before, select your helper’s contact name. To invite someone who isn't on your contact list, select Invite someone to help you.

  4. Follow the instructions.

To give help if someone has requested it:

  1. Go to the search box and enter remote assistance, then select Invite someone to connect to your PC and help you, or offer to help someone else.

  2. Select Help someone who has invited you.

  3. Do one of the following: If you’re using Easy Connect for the first time, select Use Easy Connect. Or, if you’ve used Easy Connect before, select the contact name of the person you want to help. To help someone not on the list, tap or click Help someone new.

  4. Follow the instructions.

You can also use Quick Assist to give and receive remote assistance.

-->

This article describes common issues with the Remote Desktop client and how to fix them.

Remote Desktop client for Windows 7 or Windows 10 stops responding or cannot be opened

Starting with version 1.2.790, you can reset the user data from the About page or using a command.

Use the following command to remove your user data, restore default settings and unsubscribe from all Workspaces.

Connecting

If you're using an earlier version of the Remote Desktop client, we recommend you uninstall and reinstall the client.

Web client won't open

First, test your internet connection by opening another website in your browser; for example, www.bing.com.

Use nslookup to confirm DNS can resolve the FQDN:

Try connecting with another client, like Remote Desktop client for Windows 7 or Windows 10, and check to see if you can open the web client.

Can't open other websites while connected to the web client

If you can't open other websites while you're connected to the web client, there might be network connection problems or a network outage. We recommend you contact network support.

Nslookup can't resolve the name

If nslookup can't resolve the name, then there might be network connection problems or a network outage. We recommend you contact network support.

Your client can't connect but other clients on your network can connect

If your browser starts acting up or stops working while you're using the web client, follow these instructions to troubleshoot it:

  1. Restart the browser.
  2. Clear browser cookies. See How to delete cookie files in Internet Explorer.
  3. Clear browser cache. See clear browser cache for your browser.
  4. Open browser in Private mode.

Client doesn't show my resources

First, check the Azure Active Directory account you're using. If you've already signed in with a different Azure Active Directory account than the one you want to use for Windows Virtual Desktop, you should either sign out or use a private browser window.

If you're using Windows Virtual Desktop (classic), use the web client link in this article to connect to your resources.

If that doesn't work, make sure your app group is associated with a workspace.

Web client stops responding or disconnects

Try connecting using another browser or client.

Other browsers and clients also malfunction or fail to open

If issues continue even after you've switched browsers, the problem may not be with your browser, but with your network. We recommend you contact network support.

Web client keeps prompting for credentials

If the Web client keeps prompting for credentials, follow these instructions:

  1. Confirm the web client URL is correct.
  2. Confirm that the credentials you're using are for the Windows Virtual Desktop environment tied to the URL.
  3. Clear browser cookies. For more information, see How to delete cookie files in Internet Explorer.
  4. Clear browser cache. For more information, see Clear browser cache for your browser.
  5. Open your browser in Private mode.

Windows client blocks Windows Virtual Desktop (classic) feed

If the Windows client feed won't show Windows Virtual Desktop (classic) apps, follow these instructions:

Remote Desktop Connection Issue

  1. Check if the Conditional Access policy includes the app IDs associated with Windows Virtual Desktop (classic).
  2. Check if the Conditional Access policy blocks all access except Windows Virtual Desktop (classic) app IDs. If so, you'll need to add the app ID 9cdead84-a844-4324-93f2-b2e6bb768d07 to the policy to allow the client to discover the feeds.

If you can't find the app ID 9cdead84-a844-4324-93f2-b2e6bb768d07 in the list, you'll need to register the Windows Virtual Desktop resource provider. To register the resource provider:

Microsoft Remote Desktop Not Working

  1. Sign in to the Azure portal.
  2. Go to Subscription, then select your subscription.
  3. In the menu on the left side of the page, select Resource provider.
  4. Find and select Microsoft.DesktopVirtualization, then select Re-register.

Next steps

  • For an overview on troubleshooting Windows Virtual Desktop and the escalation tracks, see Troubleshooting overview, feedback, and support.
  • To troubleshoot issues while creating a Windows Virtual Desktop environment and host pool in a Windows Virtual Desktop environment, see Environment and host pool creation.
  • To troubleshoot issues while configuring a virtual machine (VM) in Windows Virtual Desktop, see Session host virtual machine configuration.
  • To troubleshoot issues related to the Windows Virtual Desktop agent or session connectivity, see Troubleshoot common Windows Virtual Desktop Agent issues.
  • To troubleshoot issues when using PowerShell with Windows Virtual Desktop, see Windows Virtual Desktop PowerShell.
  • To go through a troubleshoot tutorial, see Tutorial: Troubleshoot Resource Manager template deployments.