One-sided Remote Desktop problem ...

Question

Noone seems to notice my Q here ... maybe because it's new forums or ... ?

It has worke so nicely till I was forced tp update from 1803/1809 ... and it seems a little odd to build a new house because water is dripping in your hair ... find the hole in the roof/ceiling instead !

So DON'T ask me to update to 2004 - 1) my problems STARTED with an update ... and 2) I HAVE tried 2004 ... it was even worse, so I downgraded again.

To simplify as much as possible:

I have 3 machines newly RE-installed ALL with Windows 10 PRO

Machine:

A) version 1903 and 2 shares, the C- and D-Hdrive

B) version 1909 and 1 share, the C-HDrive

C) version 1903 and 1 share, the C-HDrive

I'm logged on to all of them with my MS-account.

ALL machines can acces the SHARES on ALL the other machines = all combinations works well !

BUT when it comes to access via Remote Desktop, Oh, my ...

Now I've moved the A-machine to my office right beside the C-mashine - instead of the B-machine.

A and C have the SAME version/build of Windows 1903 - fully updated.

Remote Desktop only works on A = A can access C via Remote Desktop, but C CAN'T access A via remote Desktop.

Error messages is a MsgBox with these 3 proposals - translated from danish

1) Remote access is not activated ----------------------------------> it IS, I've tested severel times !

2) Remote computer is OFF -----------------------------------------> not at all !

3) Remote computer is not accessable on the network ------------> it IS because I can get access to the shares !!!!!!!

I've compared ALL Firewall rules IN- and OUT-going on A with those on C and C-rules are axactly the same settings as on A and there is the axact same number of rules on the two machines !

What's left that could be wrong ?

Best regards
KeldSor
Aarhus V, Denmark

Answer 1

Eventhough I have blocked for updates on machine A - the problematic machine - this morning it was FORCED to update to 1903 - biuld 18362.1139 !

This build was installed in machine C at 08-09-2020 and there the MESS all stated , but I was not able to update machine A at that earli time - for unknown reasons..

NOW IT WORKS NICELY WITH ACCESS BOTH WAYS BETWEEN A AND C VIA REMOTE DESKTOP !!!!!

Argh ... )=(/&=)(=)(¤#?/? - as I said befor - working with MS WINDOWS is a total VASTE of time !!!!

Answer 2

Hello @KeldSor

Updates always cause various problems :(

What do you use to access remote PC, Remote Desktop Connection (MSTSC) or Remote Desktop (MSRDC) client?

1) Have you enabled Remote desktop feature on all the PC ?

2) Please check the status of your firewall settings for Remote Desktop

3) When RDP , check RDP service are running or not On C :

4) If you are having problems using IPv6 to connect to the servers, you can force your computer to use IPv4 only

Note: Please ensure that you are connecting to the correct PC name (or IP address).

Here’s the reference airticle:
https://appuals.com/fix-remote-desktop-cant-connect-to-the-remote-computer-for-one-of-these-reasons/

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards
Karlie

Answer 3

Thx for your trime and answer, but it seems like just checking what I did check a lot of time without solving the problem.

but there seems to be a one-penny solution in the link to the reference article you gave - I'll try ALL of you proposals again AND the one-penny solution.

You mentioned "What do you use to access remote PC, Remote Desktop Connection (MSTSC) or Remote Desktop (MSRDC) client? "

... how can I see which one I in fact use - I just right-click on the icon in the network desktop icon window and choose (the 4. item in the menu) = "Opret forbindelse til fjernskrivebord" - translated form danish "Connect to Remote Desktop" - I have a danish version of Windows - is it MSTSC or MSRDC ... I really don't know.

Answer 4

@Karlie Weng

Just to ensure we're on the same page:

I have the two machines A and C set up right besides each other here in my office.

A can access C via Remote Desktop (MSTSC) but C CAN'T access A !

On C the service "Fjernskrivebord" (=Remote Desktop) is running but it's NOT running on A !

When I try to FORCE the service to run on A - it run for few seconds while I see a green moving bar and then stops again before the green bar is fully advanced and then the "bar"-dialog closes again !

I HAVE checked that the remote desktop IS turn on in the Windows dialog - the old and the new one !

According to the dialog in Windows teh service should be listening at port 3389 (default) but when I do this in the CMD:

telnet Machine_A 3389 it can NOT make connection

How can I find out why the service wont run and/or what error code it's producing ?

Answer 5

I can see a lot of people out there having that same problem with Romote Desktop Services not starting ... and all after updating too !!!!

Unfortunately I have found NONE that did solve the problem !!

I've now tried that non-sence test - it more seems like a huge vaste of time:

DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

NOTHING problematic found !

What to do here ?