Remote Desktop Not Working

What error message you get when you try to connect?

Have you try connecting from different client or you get the error on a certain client?

Error: This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

But The Remote is Enabled.

We can able to PING, Shared folder Access and VPN also.

Same Network only

have you tried telnetting server from client on tcp 3389? is it working?
if you change rdp port in registry, r u able to telnet it?
u need to tell client to use custom port while taking rdp?

I answered a similar question recently here:

https://www.experts-exchange.com/questions/29091083/windows-10-PRO-edition-is-not-listening-on-port-3389-for-RDP-connections.html?notificationFollowed=205863683&anchorAnswerId=42513945#a42513945

It's easy to make the mistake described, and equally easy to either fix it or to eliminate such an error as the cause of your issue.

i have checked. the registry value is 3389 only there

I am not having telnet server so we cant able to check the status

But PortQryV2 Command using my result shows TCP port 3389 (ms-wbt-server service): NOT LISTENING

you just need to install telnet client on machine from where you are testing RDP and check if telnet is working?

U don't need to install telnet server on server in issue

If I am Run the telnet client on my machine

Error  Could not open connection to the host, on port 3389: Connect failed

Good Day,

would you please provide a "netstat -an" from the command line?

Thanks!

i have checked netstat -an, port 3389 not showing

now install telnet client on sever in question and run there telnet localhost 3389 and see if its working
if worked, it means some where rdp port is blocked in between, in firewall or something?
if did not worked, it means server failing to run RDP protocol, may be you can check if fdenyterminaslserver registry set to 1

Hello,
sorry you had mentioned a few of the items in your first list you posted.  It states you changed the port to 3390 or am i misreading the post.
Is this a stand alone device or is it part of a domain?
Thanks

Open Task Manager and click on the Processes tab. Then click on View in the menu bar, click on Select Columns, put a tick in the PID box, and click OK. Now click on the Services tab and locate the TermService service and make a note of its PID. Minimise Task Manager, open a command prompt, and run this command:

netstat -a -n -o

The output will list, among other things, the PIDs of the services using the listed ports. As the TermService service runs under a svchost.exe process there will be several entries having the PID you've noted; the computer I'm using to type this has five occurrences of the PID used by the TermService service, three of which I can ignore because those services are using port numbers above 49000, and the other two are using the expected RDP port number.
In your case I would look for services with the noted PID using port numbers below 20000  (at least initially) and having either the local IP of the server or the loopback address in the netstat output line, and try connecting to the server with RDP using those ports.

Sounds overly simple, but at least 20 times over the past 15 years after a reboot, especially if updates were applied, remote desktop failed.  A second reboot instantly fixed the problem with with no other changes.  For this reason all the servers I manage have an alternate way to access, I use GoToAssist, but LogMeIn, ConnectWise, or many others work well.  They allow you remote access to resolve the problem.

This Server is primary domain server.

And one more thing, we have facing this same  issue 2 days before but we resolved that issue.

We can go to regedit and local root give permission to the administrator. after thet working normally

After reboot we facing the same issue now permission also there in administrator.

fdenyterminaslserver is not available in regedit only available on fDenyTSConnections

If i am saw the Event log in our server, I have an error

Terminal Service start failed. The relevant status code was Could not read key from registry

Event ID 1048

Well, perhaps that clarifies things a bit. If the Terminal service is unable to start because it can't obtain the necessary information from the registry, that would explain its failure to be listening on any port; furthermore it wouldn't appear in the list of running services.

The failure to access the relevant registry key(s) suggests registry corruption or possibly a permissions issue on the keys, so that's where to start looking.

Then What is the Solution? How it will be resolve?

Kindly advice us.

It seems that the Terminal Server is Expired. First login as Administrator. Open Registry. Open the following folder

HKEY_LOCAL_MACHHINE\CurrentContolSet\TerminalServer

Delete GarcePeriod folder. And Restart Machine.

Hi Friends,

Thanks for your Information, But GracePeriod folder is not there in registry

i have used Windowserv server 2008 Sp2

Kindly give any other solution?

High Priority

Hi Friend,

Thanks for your response

Now i can able to take remote. After delete the permission and again given to HKLM, HKCR, HKCU and all

Full Permission given to the system and Administrator Users

After that working normally.

Excellent. I do so like happy endings!