RDC

Greetings,

I have RDC on about 6 Windows Pro computers all hard wired on my home network.

All running various 25H2 builds.

I have recently clean installed my main pc (JWMAIN) and enabled all necessary RDC toggles.

I have also purchased a new laptop (MSI Prestige 16 Flip AI+) and installed all necessary RDC controls.

Before the clean install of JWMAIN, all RDC connectins worked almost flawlessly.

Now I cannot connect to any of the devices.

All devices show uo in the network, I have tried by pc name and ip to get connected to any of the pc's.

I also have tailscale on all devices and tried using that as well with no avail.

Enter Gemini AI, worthless at best.

Windows keeps telling me my credentials are wrong to sign into RDC (had these issues before the clean install as well).

I have been going at this for about 8 hours and I am really perpe[lexed. I have even done a clean install for the 3rd time on JWMAIn and the new laptop.

User guides for RDC have been unreliable to get this running.

Can any of the experts here tell me if htere is any easier way to be able to remote into a home network pc without all the dredential stuff?

Everything was wipe in credential manager and reset.

All pc's have the same Microsoft account to log in, a pin is used for the log in. I have used the password forthe Microsoft account and it says it is wrong.

I am extremely frustrated and looking for some assistance.

Thank you in advance.

Jeff

jwent333 said:

All pc's have the same Microsoft account to log in, a pin is used for the log in. I have used the password forthe Microsoft account and it says it is wrong.

Click to expand...

Try using the the PIN, as opposed to the password.

Scott said:

Try using the the PIN, as opposed to the password.

Click to expand...

No go.

I actually just restored from Hasleo and all is back up and running.

RDC has always been a huge issue within my network for some reason.

It is probably me not knowing what I am doing.

There should be an RDC for dummies manual.

Thank you for your reply.

Scott said:

Try using the the PIN, as opposed to the password.

Click to expand...

You can't use the PIN to login to a remote machine using RDC, you have to use the password.

Depending on when that Haselo image was made, it is possible your RDC may break again once windows updates. The April 2026 update made changes to RDC, then the July 2026 made more changes.

If it breaks again, you can manage RDP using group policy or through credential manager. Take a look at this article regarding RDC group policy settings. Scroll down to section marked "Permissive Environments"

When it comes to anything involving credentials, I found it much easier to create a credential on each machine for each of the others.
You do this even if the same user name and password is being used on all of them, whether local or MS account..

To create a credential:
Go to Control Panel>Credentials> Windows Credentials>add a windows credential

In the "Internet or network address" box, type the name of the computer on the network that you want to access.
In the User name and Password boxes, type the user name and password that you use for that computer, and then click OK. (EVEN IF ALL COMPUTERS USE SAME USERNAME/PASSWORD)
Note: It must be a password, not a pin. While you can still use a pin to logon to any device , you must restart the device and log into it using a password
at least once for this to work.
In other words, you would create a credendial on each computer for the other five. Restart each computer and log on at least once using its password.

glasskuter said:

Depending on when that Haselo image was made, it is possible your RDC may break again once windows updates. The April 2026 update made changes to RDC, then the July 2026 made more changes.

If it breaks again, you can manage RDP using group policy or through credential manager. Take a look at this article regarding RDC group policy settings. Scroll down to section marked "Permissive Environments"

RDP file security in Group Policy on Windows and Windows Server

Learn how to configure Group Policy settings that control how Remote Desktop Connection handles signed, unsigned, and trusted-publisher RDP files.

learn.microsoft.com

When it comes to anything involving credentials, I found it much easier to create a credential on each machine for each of the others.
You do this even if the same user name and password is being used on all of them, whether local or MS account..

To create a credential:
Go to Control Panel>Credentials> Windows Credentials>add a windows credential

In the "Internet or network address" box, type the name of the computer on the network that you want to access.
In the User name and Password boxes, type the user name and password that you use for that computer, and then click OK. (EVEN IF ALL COMPUTERS USE SAME USERNAME/PASSWORD)
Note: It must be a password, not a pin. While you can still use a pin to logon to any device , you must restart the device and log into it using a password
at least once for this to work.
In other words, you would create a credendial on each computer for the other five. Restart each computer and log on at least once using its password.

Click to expand...

Actually the image was created yesterday before I did the clean install on the main pc.

I will be checking out the article that you linked as well.

Gemini was trying to do a group policy, but well, it is Gemini. If you ever worked with that model you might understand, However it is the free one so I am certain it is "dumbed" down.

I will copy your instructions on creating a credential and go from there.

I have been using RDC for around 5 years or so and I am still ignorant to it.

Thank you for the reply.

There is also this option in the Remote Desktop Connection window. It might bring you some joy and happiness.

Here's mine to give you an idea how it looks after credentials are created. I use remote desktop (and file sharing) between 4 devices. Both RC and file sharing use the same set of credentials. The device I am currently using is a Dell-7080. You can see the credentials I created for the other 3 devices.