Remote desktop can't connect to the remote computer for one of the reasons

Panzera 6

Hello all!
Hope you are well.

In my client's network, we have 3 windows 10 pro PCs. He used to connect to his PC in his office room from either of the other 2 in the building via remote desktop. That was until yesterday where the pc installed the kb5005565 update.

After the update, he went along with his day and tried to connect to the office PC but it returned the following message:

The strange thing is that he can control the other 2 PCs from his and the other 2 can connect fine with each other!

I tried and read everything (turn off the firewall, change the port for RDC, change the port to decimal, check services, policies, check hosts, check ping, check if it was allowed through the firewall, and more...) recommended as solution to no avail. I even unistalled the update but the problem persists.

I am literally one step from going crazy here. i can't find what is wrong all the sudden and i do not know what else to try so i can help him.

There is no file server or any server on the network. Roughly the network is composed by the isp router where 3 switches are connected (1 in each pc room), only having a PC and printer connected on them.

I would appreciate any assistance.

Thanks in advance.

Andy Reed 1 Reputation point

2021-09-22T10:15:45.003+00:00

I have the same problem since this update. However removing the update does not solve the problem.
Erik D. Snowden 1 Reputation point

2021-09-24T18:27:17.38+00:00

I also have this problem after kb5005565. It is not affecting all of our users just some. Uninstalling the update did not solve the problem. Sometimes you can log in via RDP but then you can't click on anything or it disconnects. Is there a fix?

3 answers

Dave Patrick 426.1K Reputation points MVP

2021-09-19T12:28:21.913+00:00

Try PowerShell from source and target. (use target address in both cases) post results

Test-NetConnection -ComputerName "192.168.49.142" -CommonTCPPort "RDP" -InformationLevel "Detailed"
Please sign in to rate this answer.
Dave Patrick 426.1K Reputation points MVP

2021-09-20T12:49:40.997+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--

Panzera 6 Reputation points

2021-09-20T15:39:37.753+00:00

Hello @Dave Patrick and thanks for the answer.

We run it to all pcs and the results are as follows:

WARNING: TCP connect to host:port failed.

RemotePort: 3389
IsAdmin: False
PingSucceeded: True
PingReplyDetails (RTT): 0 ms
TcpTestSucceeded: False

On every pc is the same. Would you like to post the photos as well?

Thanks once more.

Dave Patrick 426.1K Reputation points MVP

2021-09-20T17:31:41.197+00:00

Yes, post the complete result from source and target. (using target address in both cases)

Panzera 6 Reputation points

2021-09-21T11:11:10.273+00:00

Dave Patrick 426.1K Reputation points MVP

2021-09-21T12:57:22.053+00:00

Looks like services are not running on target or using a different port. Try netstat -aon and lookup in Task Manager\Processes

--please don't forget to upvote and Accept as answer if the reply is helpful--

Panzera 6 Reputation points

2021-09-21T14:06:53.587+00:00

And yes even though i check everything before running netscan, no services.... how is this even possible? i am gonna go insane...

Dave Patrick 426.1K Reputation points MVP

2021-09-21T14:11:45.18+00:00

Sounds like it isn't running.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Panzera 6 Reputation points

2021-09-21T14:15:11.567+00:00

ok.... that's new error. yesterday was running on services.

Dave Patrick 426.1K Reputation points MVP

2021-09-21T14:19:18.323+00:00

Ok, well that is the root of the problem. The operating system is broken for some reason. Try rebooting, or possibly a repair install, but time may be better spent clean installing it.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Panzera 6 Reputation points

2021-09-21T14:21:40.457+00:00

i was terrified of that answer.

i can not clean install. the pc is currently under 24 hrs operations and can not be interupted.

My question is what caused that out of the blue? Until last Thursday was working great. What could have caused and is there a way to fix it?

Thanks for you immediates responses, higly appreciated.

Dave Patrick 426.1K Reputation points MVP

2021-09-21T14:51:07.847+00:00

is there a way to fix it?

You can try a repair install
https://support.microsoft.com/en-us/windows/how-to-refresh-reset-or-restore-your-pc-51391d9a-eb0a-84a7-69e4-c2c1fbceb8dd

but time may be better spent standing up a new one for replacement.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Panzera 6 Reputation points

2021-09-21T15:03:02.083+00:00

i see.... Thanks once more Patrick.

Just one more thing i just found out. While searching for the error i came accross to some posts from 2009 that said about corrupted .dll's

That got me thinking and asked my client to backtrack everything that was made to the PC couple days before the error appears.

And to my suprise i found out that they had a blackout during a Remote Session and the client pc asked for repair check when power was back on. And then he said me that he does not remember if the repair was skipped or made. Could this be the isssue and cause of them all?

Dave Patrick 426.1K Reputation points MVP

2021-09-21T15:04:51.493+00:00

Anything is possible. Try the repair and if no joy I'd stand up a new one for replacement.

J--please don't forget to upvote and Accept as answer if the reply is helpful--

Dave Patrick 426.1K Reputation points MVP

2021-09-23T13:35:32.61+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
Sign in to comment
Limitless Technology 39,351 Reputation points

2021-09-20T10:22:50.097+00:00
Hello,

Thank you for your question.

I would like to suggest you to check below Troubleshooting steps.

If you think its due to KB5005565 then uninstall it to see if you are able to get back to RDP.

Please try to run port query tool from Microsoft if the if you are able get thru RDP port
https://www.microsoft.com/en-in/download/details.aspx?id=24009

Please check if all three PCs are in same network and same subnet or try to give same IP range for all of them to narrow down the issue.

Please cleanup C:\Windows\Temp and C:\WinNT\Temp

If the reply was helpful, please don’t forget to upvote or accept as answer.
Please sign in to rate this answer.
Panzera 6 Reputation points

2021-09-21T14:47:31.803+00:00

Hello and thanks for the prosped solution. i checked everything and did everything but stll dont work.

I tried to manually start the service (as recommended by DSPatrick above) and got return the below error:

Is it fixable in anyway?
Sign in to comment
cthivierge 4,056 Reputation points

2021-09-21T15:14:48.593+00:00

Can you validate on the destination computer that the value fDenyTsConnections is set to "0"

reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections
Please sign in to rate this answer.
Panzera 6 Reputation points

2021-09-21T15:28:38.38+00:00

Hello.

Yes it is set to "0"
Sign in to comment