Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you start 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:. 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. To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:.
On both the local client computer and the remote target computer, the following services should be running:. 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. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong. 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.
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. Checked under device manager under show hidden devices non plug and play check if rdpdd, tdptd drivers are started or no, if not try starting them and check the behaviour.
From the Terminal Server, can you telnet the localhost with Port ? If this one is successful, please disable the firewall for test. Thanks for the reply. Any suggestions or tips that lead me to a resolution are greatly appreciated! From the terminal server, when I try to telnet I get "Connecting to localhost When I do a netstat command, it does not show that port is "listening". Here are the results of the netstat. On the server side, please run services.
If the following two services are not started, please start them:. The windows firewall is off on the server with the problem as well as the other computers I am trying to RDP from. I have tried to rdp to the problem server from several different servers as well as windows xp desktops. Windows firewall is not running on any of these. When I am on the server with the problem and I try to remote desktop to itself, I get the same error message:.
We usually assume that the server has rebooted because it kicks us off RDP but we cant see what the server is actually doing. The first thing I noticed is that PING -t continued to get responses which meant that the server was not going down at all.
It turns out that the server begins to shut down various services including the service that handles RDP connections however the server hangs before it actually stops all services - so you still get PING responses, IIS is up etc. After that everything works. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Toni Uranjek. Join our community to see this answer! Unlock 1 Answer and 10 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.
What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need.
0コメント