Connecting Win10 PC's on LAN works for some, and not for others

I have several laptops connected to a local LAN (192.168.0.XX) and to the same HomeGroup.
They all run the same version of Windows 10 Pro (21H1). All of them can be logged on to using either a local account or an MS account.
All are admin accounts.

If I open Network (Neighborhood) on any PC and try to connect to another, I'm always asked to provide target PC credentials the first time. Attempting this between two PC's that both are logged on with a local account, works well.
But trying to log on from a PC logged in with a local account to a target PC which is logged on using an MS account, fails, whether I try using the local account credentials or the MS account credentials.
However, If I log off the MS account on the target PC and instead log on using the local account, then connecting to it using its local account credentials, works.

As always, credentials are stored once successful logon is achieved. And here comes the strange thing; If I now re-log on to the target PC using the MS account again, the connecting to it using its local account credentials suddenly works!
So, once a connection has been made, it continues to work independently of how the target PC is logged into.

Even attempting connection between two PC's which both are logged into an MS account, fails if the target machine's local account credentials is used. And trying to use the MS account credential always fails. Maybe because the MS account username is an email address?

I completely fail to understand how MS intended this to work.

VikingOy said:

I have several laptops connected to a local LAN (192.168.0.XX) and to the same HomeGroup.
They all run the same version of Windows 10 Pro (21H1). All of them can be logged on to using either a local account or an MS account.
All are admin accounts.

If I open Network (Neighborhood) on any PC and try to connect to another, I'm always asked to provide target PC credentials the first time. Attempting this between two PC's that both are logged on with a local account, works well.
But trying to log on from a PC logged in with a local account to a target PC which is logged on using an MS account, fails, whether I try using the local account credentials or the MS account credentials.
However, If I log off the MS account on the target PC and instead log on using the local account, then connecting to it using its local account credentials, works.

As always, credentials are stored once successful logon is achieved. And here comes the strange thing; If I now re-log on to the target PC using the MS account again, the connecting to it using its local account credentials suddenly works!
So, once a connection has been made, it continues to work independently of how the target PC is logged into.

Even attempting connection between two PC's which both are logged into an MS account, fails if the target machine's local account credentials is used. And trying to use the MS account credential always fails. Maybe because the MS account username is an email address?

I completely fail to understand how MS intended this to work.

Hi there
I HATE Windows networking --Gandalf the Wizard in Lord of the Rings would have more success in making it work every time

However what I've found is probably the easiest and seems to work.

1) For any non Windows devices or Windows prior to Win 10 -- enable SMB1.
2) Ensure that any computer has "enable remote connections to this computer" set - and allow the "earlier versions of RDP etc to be used".
3) ensure Network discovery on all machines is turned on.
4) create a new workgroup -- you can choose anything you like in advance computer rename.
5) rename all computers -- joining them to the new workgroupname.
6) enable sharing on all relevant Disks on all machines.

Also an obvious one - on the same LAN don't have computers with identical host names.

If you must use a Ms account check that the user name is really what it seems to be -- I'd 100% skip the Ms account for Local LAN connectivity -- local accounts cause far less hassle anytime.

I'm sure there will be zillions of Windows gurus saying this is B/S -- go into local policies, fiddle around with reg entries etc etc --that's what those people are paid for -- but I've found however unlikely this solution might appear it always seems to work.

Cheers
jimbo

Hi!
I assume your problem is cos you try to connect from two different work group.
One is logged on with a local account the other is logged on with an MS account.