Microsoft Remote Desktop For Mac Connection Refused

Posted : admin On 10.04.2020

Microsoft Remote Desktop For Mac Connection Refused 5,0/5 6484 reviews

Microsoft Remote Desktop Mac Connection Refused
Microsoft Remote Desktop For Mac Connection Refused Windows 10
Remote Desktop

-->

We regularly update the Remote Desktop client for macOS, adding new features and fixing issues. Here's where you'll find the latest updates.

If you encounter any issues, you can always contact us by navigating to Help > Report an Issue.

Aug 06, 2015 Remote Desktop Connection refused (mac) Windows Server. /remote-desktop-connection-refused-mac Question 2 7/26/2015 9:38:49 AM 8/7/2015 2:25:47 AM Discussions related to the use of Microsoft Remote Desktop Clients 0 0. Question; text/html 7/26/2015 9:38:49 AM Fabinga 0. Get the Remote Desktop client. Download the Microsoft Remote Desktop client from the Mac App Store. Set up your PC to accept remote connections. (If you skip this step, you can't connect to your PC.) Add a Remote Desktop connection or a remote resource. You use a connection to connect directly to. Remote Desktop Connection from Mac to PC Does Not Connect Via Computer Name. I'm attempting to connect from my Mac to a PC on my local network via Microsoft Remote. Feb 02, 2018 1. The Windows 10 PIN feature should be disabled and a regular password used on the remote machine. Use the IPv4 address for the remote machine rather than its easy to remember name. You can get this by cmd ipconfig /all. The easy-to-remember might work on a managed network but it doesn't work on mine!

Updates for version 10.3.7

Date published: 1/6/20

In our final update of the year, we finetuned some code and fixed the following behaviors:

Copying things from the remote session to a network share or USB drive no longer creates empty files.
Specifying an empty password in a user account no longer causes a double certificate prompt.

Updates for version 10.3.6

Date published: 1/6/20

Mac Remote Desktop from a Mac to a Mac: connection refused, even as local admin. I've got a user with a Mac laptop who wants to connect to his Mac desktop. Both are 10.10.x - not sure of specific versions. The Microsoft.NET Framework 4 web installer package downloads and installs the.NET Framework components required to run on the target machine architecture and OS. Tool Remote Desktop Connection Manager 2.7. RDCMan manages multiple remote desktop connections. Tool Remote Server Administration Tools for Windows 7 with Service.

In this release, we addressed an issue that created zero-length files whenever you copied a folder from the remote session to the local machine using file copy and paste.

Updates for version 10.3.5

Date published: 1/6/20

We made this update with the help of everyone who reported issues. In this version, we've made the following changes:

Redirected folders can now be marked as read-only to prevent their contents from being changed in the remote session.
We addressed a 0x607 error that appeared when connecting using RPC over HTTPS RD Gateway scenarios.
Fixed cases where users were double-prompted for credentials.
Fixed cases where users received the certificate warning prompt twice.
Added heuristics to improve trackpad-based scrolling.
The client no longer shows the 'Saved Desktops' group if there are no user-created groups.
Updated UI for the tiles in PC view.
Fixes to address crashes sent to us via application telemetry.

Note

In this release, we now accept feedback for the Mac client only through UserVoice.

Updates for version 10.3.4

Date published: 11/18/19

We've been hard at work listening to your feedback and have put together a collection of bug fixes and feature updates.

When connecting via an RD Gateway with multifactor authentication, the gateway connection will be held open to avoid multiple MFA prompts.
All the client UI is now fully keyboard-accessible with Voiceover support.
Files copied to the clipboard in the remote session are now only transferred when pasting to the local computer.
URLs copied to the clipboard in the remote session now paste correctly to the local computer.
Scale factor remoting to support Retina displays is now available for multimonitor scenarios.
Addressed a compatibility issue with FreeRDP-based RD servers that was causing connectivity issues in redirection scenarios.
Addressed smart card redirection compatibility with future releases of Windows 10.
Addressed an issue specific to macOS 10.15 where the incorrect available space was reported for redirected folders.
Published PC connections are represented with a new icon in the Workspaces tab.
'Feeds' are now called 'Workspaces,' and 'Desktops' are now called 'PCs.'
Fixed inconsistencies and bugs in user account handling in the preferences UI.
Lots of bug fixes to make things run smoother and more reliably.

Updates for version 10.3.3

Date published: 11/18/19

We've put together a feature update and fixed bugs for the 10.3.3 release.

First, we've added user defaults to disable smart card, clipboard, microphone, camera, and folder redirection:

ClientSettings.DisableSmartcardRedirection
ClientSettings.DisableClipboardRedirection
ClientSettings.DisableMicrophoneRedirection
ClientSettings.DisableCameraRedirection
ClientSettings.DisableFolderRedirection

Next, the bug fixes:

Resolved an issue that was causing programmatic session window resizes to not be detected.
Fixed an issue where the session window contents appeared small when connecting in windowed mode (with dynamic display enabled).
Addressed initial flicker that occurred when connecting to a session in windowed mode with dynamic display enabled.
Fixed graphics mispaints that occurred when connected to Windows 7 after toggling fit-to-window with dynamic display enabled.
Fixed a bug that caused an incorrect device name to be sent to the remote session (breaking licensing in some third-party apps).
Resolved an issue where remote app windows would occupy an entire monitor when maximized.
Addressed an issue where the access permissions UI appeared underneath local windows.
Cleaned up some shutdown code to ensure the client closes more reliably.

Updates for version 10.3.2

Date published: 11/18/19

In this release, we fixed a bug that made the display low resolution while connecting to a session

Updates for version 10.3.1

Date published: 11/18/19

We've put together some fixes to address regressions that managed to sneak into the 10.3.0 release.

Addressed connectivity issues with RD Gateway servers that were using 4096-bit asymmetric keys.
Fixed a bug that caused the client to randomly stop responding when downloading feed resources.
Fixed a bug that caused the client to crash while opening.
Fixed a bug that caused the client to crash while importing connections from Remote Desktop, version 8.

Updates for version 10.3.0

Date published: 8/27/19

It's been a few weeks since we last updated, but we've been hard at work during that time. Version 10.3.0 brings some new features and lots of under-the-hood fixes.

Camera redirection is now possible when connecting to Windows 10 1809, Windows Server 2019 and later.
On Mojave and Catalina we've added a new dialog that requests your permission to use the microphone and camera for device redirection.
The feed subscription flow has been rewritten to be simpler and faster.
Clipboard redirection now includes the Rich Text Format (RTF).
When entering your password you have the option to reveal it with a 'Show password' checkbox.
Addressed scenarios where the session window was jumping between monitors.
The Connection Center displays high resolution remote app icons (when available).
Cmd+A maps to Ctrl+A when Mac clipboard shortcuts are being used.
Cmd+R now refreshes all of your subscribed feeds.
Added new secondary click options to expand or collapse all groups or feeds in the Connection Center.
Added a new secondary click option to change the icon size in the Feeds tab of the Connection Center.
A new, simplified, and clean app icon.

Updates for version 10.2.13

Date published: 5/8/2019

Fixed a hang that occurred when connecting via an RD Gateway.
Added a privacy notice to the 'Add Feed' dialog.

Updates for version 10.2.12

Date published: 4/16/2019

Resolved random disconnects (with error code 0x904) that took place when connecting via an RD Gateway.
Fixed a bug that caused the resolutions list in application preferences to be empty after installation.
Fixed a bug that caused the client to crash if certain resolutions were added to the resolutions list.
Addressed an ADAL authentication prompt loop when connecting to Windows Virtual Desktop deployments.

Updates for version 10.2.10

Date published: 3/30/2019

In this release we addressed instability caused by the recent macOS 10.14.4 update. We also fixed mispaints that appeared when decoding AVC codec data encoded by a server using NVIDIA hardware.

Updates for version 10.2.9

Date published: 3/6/2019

In this release we fixed an RD gateway connectivity issue that can occur when server redirection takes place.
We also addressed an RD gateway regression caused by the 10.2.8 update.

Updates for version 10.2.8

Date published: 3/1/2019

Microsoft Remote Desktop Mac Connection Refused

Resolved connectivity issues that surfaced when using an RD Gateway.
Fixed incorrect certificate warnings that were displayed when connecting.
Addressed some cases where the menu bar and dock would needlessly hide when launching remote apps.
Reworked the clipboard redirection code to address crashes and hangs that have been plaguing some users.
Fixed a bug that caused the Connection Center to needlessly scroll when launching a connection.

Updates for version 10.2.7

Date published: 2/6/2019

In this release we addressed graphics mispaints (caused by a server encoding bug) that appeared when using AVC444 mode.

Updates for version 10.2.6

Microsoft Remote Desktop For Mac Connection Refused Windows 10

Date published: 1/28/2019

Added support for the AVC (420 and 444) codec, available when connecting to current versions of Windows 10.
In Fit to Window mode, a window refresh now occurs immediately after a resize to ensure that content is rendered at the correct interpolation level.
Fixed a layout bug that caused feed headers to overlap for some users.
Cleaned up the Application Preferences UI.
Polished the Add/Edit Desktop UI.
Made lots of fit and finish adjustments to the Connection Center tile and list views for desktops and feeds.

Note

There is a bug in macOS 10.14.0 and 10.14.1 that can cause the '.com.microsoft.rdc.application-data_SUPPORT/_EXTERNAL_DATA' folder (nested deep inside the ~/Library folder) to consume a large amount of disk space. To resolve this issue, delete the folder content and upgrade to macOS 10.14.2. Note that a side-effect of deleting the folder contents is that snapshot images assigned to bookmarks will be deleted. These images will be regenerated when reconnecting to the remote PC.

Updates for version 10.2.4

Date published: 12/18/2018

Added dark mode support for macOS Mojave 10.14.
An option to import from Microsoft Remote Desktop 8 now appears in the Connection Center if it is empty.
Addressed folder redirection compatibility with some third-party enterprise applications.
Resolved issues where users were getting a 0x30000069 Remote Desktop Gateway error due to security protocol fallback issues.
Fixed progressive rendering issues some users were experiencing with fit to window mode.
Fixed a bug that prevented file copy and paste from copying the latest version of a file.
Improved mouse-based scrolling for small scroll deltas.

Updates for version 10.2.3

Date published: 11/06/2018

Added support for the 'remoteapplicationcmdline' RDP file setting for remote app scenarios.
The title of the session window now includes the name of the RDP file (and server name) when launched from an RDP file.
Fixed reported RD gateway performance issues.
Fixed reported RD gateway crashes.
Fixed issues where the connection would hang when connecting through an RD gateway.
Better handling of full-screen remote apps by intelligently hiding the menu bar and dock.
Fixed scenarios where remote apps remained hidden after being launched.
Addressed slow rendering updates when using 'Fit to Window' with hardware acceleration disabled.
Handled database creation errors caused by incorrect permissions when the client starts up.
Fixed an issue where the client was consistently crashing at launch and not starting for some users.
Fixed a scenario where connections were incorrectly imported as full-screen from Remote Desktop 8.

Updates for version 10.2.2

Date published: 10/09/2018

A brand new Connection Center that supports drag and drop, manual arrangement of desktops, resizable columns in list view mode, column-based sorting, and simpler group management.
The Connection Center now remembers the last active pivot (Desktops or Feeds) when closing the app.
The credential prompting UI and flows have been overhauled.
RD Gateway feedback is now part of the connecting status UI.
Settings import from the version 8 client has been improved.
RDP files pointing to RemoteApp endpoints can now be imported into the Connection Center.
Retina display optimizations for single monitor Remote Desktop scenarios.
Support for specifying the graphics interpolation level (which affects blurriness) when not using Retina optimizations.
256-color support to enable connectivity to Windows 2000.
Fixed clipping of the right and bottom edges of the screen when connecting to Windows 7, Windows Server 2008 R2 and earlier.
Copying a local file into Outlook (running in a remote session) now adds the file as an attachment.
Fixed an issue that was slowing down pasteboard-based file transfers if the files originated from a network share.
Addressed a bug that was causing to Excel (running in a remote session) to hang when saving to a file on a redirected folder.
Fixed an issue that was causing no free space to be reported for redirected folders.
Fixed a bug that caused thumbnails to consume too much disk storage on macOS 10.14.
Added support for enforcing RD Gateway device redirection policies.
Fixed an issue that prevented session windows from closing when disconnecting from a connection using RD Gateway.
If Network Level Authentication (NLA) is not enforced by the server, you will now be routed to the login screen if your password has expired.
Fixed performance issues that surfaced when lots of data was being transferred over the network.
Smart card redirection fixes.
Support for all possible values of the 'EnableCredSspSupport' and 'Authentication Level' RDP file settings if the ClientSettings.EnforceCredSSPSupport user default key (in the com.microsoft.rdc.macos domain) is set to 0.
Support for the 'Prompt for Credentials on Client' RDP file setting when NLA is not negotiated.
Support for smart card-based login via smart card redirection at the Winlogon prompt when NLA is not negotiated.
Fixed an issue that prevented downloading feed resources that have spaces in the URL.

Updates for version 10.2.1

Date published: 08/06/2018

Enabled connectivity to Azure Active Directory (AAD) joined PCs. To connect to an AAD joined PC, your username must be in one of the following formats: 'AzureADuser' or 'AzureADuser@domain'.
Addressed some bugs affecting the usage of smart cards in a remote session.

Updates for version 10.2.0

Date published: 07/24/2018

Incorporated updates for GDPR compliance.
MicrosoftAccountusername@domain is now accepted as a valid username.
Clipboard sharing has been rewritten to be faster and support more formats.
Copy and pasting text, images or files between sessions now bypasses the local machine's clipboard.
You can now connect via an RD Gateway server with an untrusted certificate (if you accept the warning prompts).
Metal hardware acceleration is now used (where supported) to speed up rendering and optimize battery usage.
When using Metal hardware acceleration we try to work some magic to make the session graphics appear sharper.
Got rid of some instances where windows would hang around after being closed.
Fixed bugs that were preventing the launch of RemoteApp programs in some scenarios.
Fixed an RD Gateway channel synchronization error that was resulting in 0x204 errors.
The mouse cursor shape now updates correctly when moving out of a session or RemoteApp window.
Fixed a folder redirection bug that was causing data loss when copy and pasting folders.
Fixed a folder redirection issue that caused incorrect reporting of folder sizes.
Fixed a regression that was preventing logging into an AAD-joined machine using a local account.
Fixed bugs that were causing the session window contents to be clipped.
Added support for RD endpoint certificates that contain elliptic-curve asymmetric keys.
Fixed a bug that was preventing the download of managed resources in some scenarios.
Addressed a clipping issue with the pinned connection center.
Fixed the checkboxes in the Display tab of the Add a Desktop window to work better together.
Aspect ratio locking is now disabled when dynamic display change is in effect.
Addressed compatibility issues with F5 infrastructure.
Updated handling of blank passwords to ensure the correct messages are shown at connect-time.
Fixed mouse scrolling compatibility issues with MapInfra Pro.
Fixed some alignment issues in the Connection Center when running on Mojave.

Updates for version 10.1.8

Date published: 05/04/2018

Added support for changing the remote resolution by resizing the session window!
Fixed scenarios where remote resource feed download would take an excessively long time.
Resolved the 0x207 error that could occur when connecting to servers not patched with the CredSSP encryption oracle remediation update (CVE-2018-0886).

Updates for version 10.1.7

Date published: 04/05/2018

Made security fixes to incorporate CredSSP encryption oracle remediation updates as described in CVE-2018-0886.
Improved RemoteApp icon and mouse cursor rendering to address reported mispaints.
Addressed issues where RemoteApp windows appeared behind the Connection Center.
Fixed a problem that occurred when you edit local resources after importing from Remote Desktop 8.
You can now start a connection by pressing ENTER on a desktop tile.
When you're in full screen view, CMD+M now correctly maps to WIN+M.
The Connection Center, Preferences, and About windows now respond to CMD+M.
You can now start discovering feeds by pressing ENTER on the Adding Remote Resources page.
Fixed an issue where a new remote resources feed showed up empty in the Connection Center until after you refreshed.

Updates for version 10.1.6

Date published: 03/26/2018

Fixed an issue where RemoteApp windows would reorder themselves.
Resolved a bug that caused some RemoteApp windows to get stuck behind their parent window.
Addressed a mouse pointer offset issue that affected some RemoteApp programs.
Fixed an issue where starting a new connection gave focus to an existing session, instead of opening a new session window.
We fixed an error with an error message - you'll see the correct message now if we can't find your gateway.
The Quit shortcut (⌘ + Q) is now consistently shown in the UI.
Improved the image quality when stretching in 'fit to window' mode.
Fixed a regression that caused multiple instances of the home folder to show up in the remote session.
Updated the default icon for desktop tiles.

-->

Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.

Check the status of the RDP protocol

Check the status of the RDP protocol on a local computer

To check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop.

Note

If the remote desktop options are not available, see Check whether a Group Policy Object is blocking RDP.

Check the status of the RDP protocol on a remote computer

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check and change the status of the RDP protocol on a remote computer, use a network registry connection:

First, go to the Start menu, then select Run. In the text box that appears, enter regedt32.
In the Registry Editor, select File, then select Connect Network Registry.
In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server.
- If the value of the fDenyTSConnections key is 0, then RDP is enabled.
- If the value of the fDenyTSConnections key is 1, then RDP is disabled.
To enable RDP, change the value of fDenyTSConnections from 1 to 0.

Check whether a Group Policy Object (GPO) is blocking RDP on a local computer

If you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings.

To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:

After this command finishes, open gpresult.html. In Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections, find the Allow users to connect remotely by using Remote Desktop Services policy.

If the setting for this policy is Enabled, Group Policy is not blocking RDP connections.
If the setting for this policy is Disabled, check Winning GPO. This is the GPO that is blocking RDP connections.

Check whether a GPO is blocking RDP on a remote computer

To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:

Remote Desktop

The file that this command produces (gpresult-<computer name>.html) uses the same information format as the local computer version (gpresult.html) uses.

Modifying a blocking GPO

You can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management.

Print this page if you want to use it as a reference when you are offline. Make sure your computer meets the minimum system requirements. Virtual pc for mac reviews.

To modify the blocking policy, use one of the following methods:

In GPE, access the appropriate level of GPO (such as local or domain), and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Allow users to connect remotely by using Remote Desktop Services.
1. Set the policy to either Enabled or Not configured.
2. On the affected computers, open a command prompt window as an administrator, and run the gpupdate /force command.
In GPM, navigate to the organizational unit (OU) in which the blocking policy is applied to the affected computers and delete the policy from the OU.

Check the status of the RDP services

On both the local (client) computer and the remote (target) computer, the following services should be running:

Remote Desktop Services (TermService)
Remote Desktop Services UserMode Port Redirector (UmRdpService)

You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).

On either computer, if one or both services are not running, start them. Microsoft autoupdate mac required data notice.

Note

If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service.

Check that the RDP listener is functioning

Important

Check the status of the RDP listener

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.

To connect to a remote computer, run the following cmdlet:
Enter qwinsta.
If the list includes rdp-tcp with a status of Listen, the RDP listener is working. Proceed to Check the RDP listener port. Otherwise, continue at step 4.
Export the RDP listener configuration from a working computer.
1. Sign in to a computer that has the same operating system version as the affected computer has, and access that computer's registry (for example, by using Registry Editor).
2. Navigate to the following registry entry:
  HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp
3. Export the entry to a .reg file. For example, in Registry Editor, right-click the entry, select Export, and then enter a filename for the exported settings.
4. Copy the exported .reg file to the affected computer.
To import the RDP listener configuration, open a PowerShell window that has administrative permissions on the affected computer (or open the PowerShell window and connect to the affected computer remotely).
1. To back up the existing registry entry, enter the following cmdlet:
2. To remove the existing registry entry, enter the following cmdlets:
3. To import the new registry entry and then restart the service, enter the following cmdlets:
  Replace <filename> with the name of the exported .reg file.
Test the configuration by trying the remote desktop connection again. If you still can't connect, restart the affected computer.
If you still can't connect, check the status of the RDP self-signed certificate.

Check the status of the RDP self-signed certificate

If you still can't connect, open the Certificates MMC snap-in. When you are prompted to select the certificate store to manage, select Computer account, and then select the affected computer.
In the Certificates folder under Remote Desktop, delete the RDP self-signed certificate.
On the affected computer, restart the Remote Desktop Services service.
Refresh the Certificates snap-in.
If the RDP self-signed certificate has not been recreated, check the permissions of the MachineKeys folder.

Check the permissions of the MachineKeys folder

On the affected computer, open Explorer, and then navigate to C:ProgramDataMicrosoftCryptoRSA.
Right-click MachineKeys, select Properties, select Security, and then select Advanced.
Make sure that the following permissions are configured:
- BuiltinAdministrators: Full control
- Everyone: Read, Write

Check the RDP listener port

On both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port.

Important

To check or change the RDP port, use the Registry Editor:

Go to the Start menu, select Run, then enter regedt32 into the text box that appears.
- To connect to a remote computer, select File, and then select Connect Network Registry.
- In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
Open the registry and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<listener>.
If PortNumber has a value other than 3389, change it to 3389.
Important
You can operate Remote Desktop services using another port. However, we don't recommend you do this. This article doesn't cover how to troubleshoot that type of configuration.
After you change the port number, restart the Remote Desktop Services service.

Check that another application isn't trying to use the same port

Open a PowerShell window. To connect to a remote computer, enter Enter-PSSession -ComputerName <computer name>.
Enter the following command:
Look for an entry for TCP port 3389 (or the assigned RDP port) with a status of Listening.
Note
The process identifier (PID) for the process or service using that port appears under the PID column.
To determine which application is using port 3389 (or the assigned RDP port), enter the following command:
Look for an entry for the PID number that is associated with the port (from the netstat output). The services or processes that are associated with that PID appear on the right column.
If an application or service other than Remote Desktop Services (TermServ.exe) is using the port, you can resolve the conflict by using one of the following methods:
- Configure the other application or service to use a different port (recommended).
- Uninstall the other application or service.
- Configure RDP to use a different port, and then restart the Remote Desktop Services service (not recommended).

Check whether a firewall is blocking the RDP port

Use the psping tool to test whether you can reach the affected computer by using port 3389.

Go to a different computer that isn't affected and download psping from https://live.sysinternals.com/psping.exe.
Open a command prompt window as an administrator, change to the directory in which you installed psping, and then enter the following command:
Check the output of the psping command for results such as the following:
- Connecting to <computer IP>: The remote computer is reachable.
- (0% loss): All attempts to connect succeeded.
- The remote computer refused the network connection: The remote computer is not reachable.
- (100% loss): All attempts to connect failed.
Run psping on multiple computers to test their ability to connect to the affected computer.
Note whether the affected computer blocks connections from all other computers, some other computers, or only one other computer.
Recommended next steps:
- Engage your network administrators to verify that the network allows RDP traffic to the affected computer.
- Investigate the configurations of any firewalls between the source computers and the affected computer (including Windows Firewall on the affected computer) to determine whether a firewall is blocking the RDP port.