Proceed to Check the RDP listener port. Otherwise, continue at step 4. 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. 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.
On both the local client computer and the remote target computer, the RDP listener should be listening on port No other applications should be using this port. 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. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.
Open a PowerShell window. To determine which application is using port 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.
Use the psping tool to test whether you can reach the affected computer by using port Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Most common reasons for Remote Desktop not responding?
Ask Question. Asked 12 years, 6 months ago. Active 8 years, 10 months ago. Viewed 33k times. Improve this question. Kjensen Kjensen 1, 9 9 gold badges 27 27 silver badges 39 39 bronze badges. I have an odd one that, once I get a writeup done, I'm going post as my first question on Server Fault. I have several boxes at different Customer sites, Win bit and bit, that on roughly 3 out of 10 boots don't listen for RDP. I haven't been able to sort out what's causing it.
Potentially you might be seeing the same strangeness I am, too. Add a comment. Active Oldest Votes. Connections being blocked by the local Windows firewall Connections being blocked by some other firewall device between your client and the server The server being behind a NAT arrangement that is not forwarding a port to the RDC port on the server The relevant service has stopped manually or due to error Remote Desktop not actually enabled or was and has since been disabled If RDC was previously working then any of the above could still be the case due to reconfiguration.
Improve this answer. David Spillett David Spillett Also Windows Firewall picking a different profile, such as Public instead of Domain.
Anywhere that teh machine requires credentials to be typed is freezing. Thanks for the reply, but this issue is not with UAC. This is a problem when accessing something like a network shared folder that my local user does not have permission to access directly, therefore it prompts for a users details that does have access Domain admin e.
As Below. As soon as i press "use another account" it freezes the screen there was also an option to insert a smart card that froze it as soon as it appeared, but dissabling that service let me get this far. To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks.
Hi All, I have a strange one.
0コメント