Increasing complexities of remote work, cloud adoption and system migration demands simple, efficient and cost-effective remote access for IT professionals and teams. Used by over 200,000 IT professionals across the world, ASG-Remote Desktop simplifies remote access and administration of desktops, servers and systems.
Hi, For how to Secure Remote Desktop Connection with TLS 1.2 ,you can refer to the method in the following link: -US/ff98d296-42cb-4f4d-a69f-c8dea82453ad/how-windows-server-2012-r2-use-tls-12-for-remote-desktop-connection?forum=winserver8gen
-Thanks George for the support - Yes, this is happening to multiple workstations that are on Windows 11 version 22H2. All workstation are on workgroup. wksprt.exe process does not exist on any of the workstations. Also, cleared any saved entry in rds and credential manager. Tried connecting by manually typing in the gateway, server, username and password with same result. Password and credentials are correct. I did test the same configuration using the microsoft remote desktop app from the microsoft store. The remote desktop app does work. Just having issue with mstsc. It seems weird that by uninstalling Windows 11 22H2 update I was able to start using mstsc for rdp again.
I have a very simple desktop to desktop RDP connection over a VPN. Both computers are 22H2. Though my setup is much simpler than what is described above, I too experienced a black screen when trying to connect followed by a time-out. Occasionally I would get a PIN screen which would not recognize my PIN, then time-out. If I rebooted the remote Host machine, I could then log in and work but subsequent sessions would time out. I will admit I have a bad habit of closing an RDP session by closing with the Close "X" at the top of the screen. However, considering that my problems making the connection were somehow related to a current open session, I started Logging Out instead of X'ing out of the session. I haven't experienced a problem since. 48h, multiple connections. For what it's worth. I made no registry changes. I did not copy the 21H2 mstsc.exe and the .dll to the 22H2 install remote host. I just Log Out and subsequent sessions seem to open correctly.
There are many remote desktop connection problems that administrators may encounter, including network failure, Secure Sockets Layer certificate issues, authentication troubles and capacity limitations.
It's easy to dismiss the notion that a firewall could contribute to a remote desktop not working, but it's quite common. To avoid firewall problems, ensure that the port your remote desktop software uses is open on any firewalls residing between client computers and the server they connect to. Remote Desktop Protocol (RDP)-based tools use RDP port 3389 by default.
Security certificates can also cause remote desktop connection problems. Many VDI products use Secure Sockets Layer (SSL) encryption for users that access VDI sessions outside the network perimeter. But SSL encryption requires the use of certificates, which creates two problems that can cause a remote desktop to not work.
First, if remote desktops are going to connect properly, client computers must trust the certificate authority that issued the certificate. This isn't usually a problem for organizations that purchase certificates from large, well-known authorities, but clients won't always trust the certificates an organization generates in-house. Use a reliable certificate authority to ensure that clients establish remote desktop connectivity.
Many remote desktop connectivity problems can be traced to DNS issues. If an admin changed a host's IP address, then clients might not be able to connect to the host until the client's DNS resolver cache expires. To expire a DNS resolver cache, follow these steps:
You could also experience remote desktop connectivity issues if you exceed infrastructure capacity. In an organization with virtual desktops or VDI, for example, clients may be unable to connect if the available licenses have been depleted. Some VDI implementations also refuse client connections if the server is too busy or if launching another virtual desktop session would weaken the performance of existing sessions.
The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at or in the accompanying "license" file. This code is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either expressed or implied. See the License for specific language governing permissions and limitations. 2b1af7f3a8