Can't RDP from W10->W11

ikantspelwurdz · Jul 31, 2024

I have four computers in the house:
A: Desktop, Windows 10 Pro
B: Laptop, Windows 11 Home
C: Desktop, Windows 11 Home
D: Desktop, Windows 11 Pro

D is on wired ethernet, the rest are on wifi.

One other difference is that Desktop A has a local user account, the rest use a shared cloud MS account.

I can remote desktop from B->A, C->A, D->A, B->D, and B-D. But I can't remote desktop from A->D. When I try, I get this error:
The remote resource can't be reached. Check your connection and try again or ask your network administrator for help.

I have remoted into other computers from A before, while on a company VPN. And I can nslookup D, although a ping times out. Turning off the firewalls makes no difference to RDP (but I can ping D when its firewall is down).

Not sure what's wrong. RDP is the main reason I plunked down extra for Windows 11 Pro!

glasskuter · Jul 31, 2024

I believe your issue is related to (1)A not having the permissions to access D or (2) it is being blocked by the firewall (3) issue with listening port.

ikantspelwurdz said:
I have remoted into other computers from A before, while on a company VPN

But have you tried to remote from A-B or A-C across your network or did you attempt only A-D? I'll bet you can't.
If you can't, the problem points to A. To verify this 100%, try to make a connection from D-B and D-C. If those 2 connections are good, it definitely puts your problem strictly on A.

Corrected - Disregard this statement. It dawned on me that B and C are Home and can not be connected to. Sorry about that. I'd line through it if I knew how to.

Try the troubleshooting steps here. General Remote Desktop connection troubleshooting - Windows Server
and here How to Fix the Remote Desktop Can’t Connect to the Remote Computer Error

glasskuter · Jul 31, 2024

Notice I corrected error in my previous post.

antspants · Jul 31, 2024

Hi there, welcome to the forum

There is something you might try first?

Try logging in to the troubled computers with a password as apposed to a pin (one time process) — Log into Windows on those unreachable computers using your Microsoft Account (computer username) & Password. Then retry remote desktop agiain.
- I believe this needs to be done at leat once so that the target computer knows its own password for future connections/reference. This is a common issue.

Alternativly:

Try disabling the pin login on the target computer alltogether to see if that helps with the connection. Apparently there are people who are faceing issues when trying to Remote Desktop to a PC that uses a Pin

ikantspelwurdz · Aug 1, 2024

glasskuter:

I tried disabling the firewalls on both A&D, but it made no difference. I took a look at the troubleshooting tips - seems those are for troubleshooting the host computer rather than the client, and that most of the conditions we're checking for would prevent the host from receiving any connections at all. But they look normal as far as I could resolve.

The 'Enter-PSSession' cmdlet however does not work. Not on any of my machines, not targeting any machines, not even locally. I get this:
Enter-PSSession : Connecting to remote server A failed with the following error message : The client cannot connect
to the destination specified in the request. Verify that the service on the destination is running and is accepting
requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly
IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and
configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1

antspants:

No luck - the error message doesn't seem to suggest an authentication problem, but I tried. After removing the PIN from my main account, I noted that the PIN option on the sign-on screen doesn't completely go away, but instead becomes an option to add one. In any event, this made no difference to the behavior. B,C can remote into D using the password, A can't even find the damn thing.

I also tried adding a second administrator account to see what would happen. This one's sign-on screen doesn't even give me a PIN option. But I can't remote into D using this account from anywhere ("Your credentials did not work.")

andrew129260 · Aug 1, 2024

ikantspelwurdz said:
The remote resource can't be reached.

I am not sure why you are having this issue. That doesn't sound like an authentication issue, but a connection issue. It is quite odd.

1.) What version of windows 10 pro?

2.) Since D is wired, have you tried doing a wireless connection to see if that works?

3.) Do you use vlans?

4.) Is this the router or pc firewall? Can you ping it from other machines regardless of firewall status? On or off? Is A the only one having issues pinging?

ikantspelwurdz said:
(but I can ping D when its firewall is down)

5.) Is D set to only allow windows hello sign in? Settings-> Accounts->Sign-In Options->Additional Settings and disabling the option : For improved security, only allow Windows Hello sign-in.

_________________________________________________________________________________________________________________________________

Why bother with RDP and just use remote software instead? It works 100% of the time and never has issues imho. And you don't need to mess with firewalls.

I use google remote desktop, but there are others out there, a lot of them are free.

spapakons · Aug 1, 2024

I am not familiar with RDP, but I have seen similar weird issues that you cannot access a certain computer by network name. However if you know its IP address and try to access it by IP you can. Have you tried that? As far as I remember you connect to a computer by its network name. Try typing its IP address instead. It's probably due to a service that advertises network resources. If this service is stopped, I don't remember which it is, the computer is practically invisible on the network. It hardly shows up in the Networks window. But you still can access it by its IP address. Find that service, start it and see if it makes any difference.

hsehestedt · Aug 1, 2024

antspants said:
Try logging in to the troubled computers with a password as apposed to a pin

Maybe I can add a little bit of information regarding this issue. Remember that a PIN is accessible only on the local machine. A PIN cannot be used for any authentication from another machine.

One odd quirk of using a PIN is that the system will no longer accept the password for RDP unless you logon to the machine locally using your password at least once after the PIN is setup. As a result, simply do this:

Log off the machine that you want to connect to using RDP. Log back on by use your password rather than the PIN. That is all. You need do this only one time. You can resume using your PIN after this, but should now be able to connect using RDP (if this is the issue being encountered).

spapakons · Aug 1, 2024

But I thought the OPs problem is that it cannot connect to the target computer (network resource cannot be reached), not that he cannot login to authorise the connection. It's like calling a number and you hear this number doesn't exist. Try connecting using the target IP address rather than the network name. See my previous post.
Also, are you sure the target is configured to allow RDP incoming connections? Maybe you should enable it and set which users are allowed to access it. I don't have access to my computer right now, so I cannot guide you where to look.

hsehestedt · Aug 1, 2024

spapakons said:
But I thought the OPs problem is that it cannot connect to the target computer (network resource cannot be reached), not that he cannot login to authorise the connection.

Could well be, which is why I added the comment saying that this is if that is even the problem. I was merely responding to the post noting the issue regarding PIN usage with some additional detail. Of course, you are entirely correct - it is likely that this is not the issue being encountered.

Dru2 · Aug 1, 2024

spapakons said:
I am not familiar with RDP, but I have seen similar weird issues that you cannot access a certain computer by network name.

I connect from my Windows 10 PC to Windows 11 PCs all the time using RDP, and use computer names without issue....

ikantspelwurdz said:
I have four computers in the house:
A: Desktop, Windows 10 Pro

D: Desktop, Windows 11 Pro

One other difference is that Desktop A has a local user account, the rest use a shared cloud MS account.

I can remote desktop from B->A, C->A, D->A, B->D, and B-D. But I can't remote desktop from A->D. When I try, I get this error:
The remote resource can't be reached. Check your connection and try again or ask your network administrator for help.

Try this.... Open System Properties on PC D (Windows 11), go to the Remote tab, click Select Users and add your login username from the Windows A (Win 10) PC. Try logging in and seeing how that goes....

Also ensure all PCs have "Allow remote connections to this computer" ticked.

Let us know.

spapakons · Aug 1, 2024

I found it, go to Settings, System, Info and click Advanced System Settings. Now go to the Remote tab to check if you allow other computers to connect via RDP and configure users allowed to do so.

PS: This is how to do it in Windows 11 but I think the steps are the same for Windows 10 as well. In worst case search for Advanced System Settings.

ikantspelwurdz · Aug 1, 2024

I have a little more information. Fileshare access from A->D does work, so the computer is being found on the network, just not through RDP. But I have to use my main microsoft account credentials - using the secondary local account tells me my credentials are invalid.

ikantspelwurdz · Aug 1, 2024

andrew129260:

1: 22H2
2: Computer D does not have a wifi card.
3: No.
4: Windows firewall.
5: Yes, I disabled that.

spapakons:

RDP by IP address does not work. Same error.

hsehestedt:

I already have PIN disabled for now.

Dru2:

Remote Desktop is enabled, and I have given permission to Everyone. Weirdly, I cannot add my secondary account at all! It tells me 'An object named 'rdpuser' cannot be found." This is the name I have given my secondary account, which I can and have logged in locally with.

spapakons, continued:

I don't seem to have that exact path, but Settings->System->Remtoe Desktop is there. The 'Remote Desktop' slider option is enabled.

ikantspelwurdz · Aug 1, 2024

Solved it! Sort of.

Some settings relating to work were getting in the way. I deleted some logon settings.
Run Remote Desktop Connection
Show Options->Advanced->Connect from anywhere->Settings

This was set to use an RD Gateway server - I changed that back to automatic and delete my logon credentials. I'll probably have some work problems later on, but at least I'll know why. But remote desktop works now (but I still can't use my rdpuser account!).