Find network access credentials windows 10 or 11

11 pages of similar networking problem's that microsoft doesn't seem to be able to correct , I have posted and/or been watching the frustration's of user's like me over this issue...I actually have given up and now use a different method of moving files/folders from P.C. to p.c. , not as easy as having a working private network but works well . V.P.N's offer these type's of work-arounds .

How about providing an example of such a workaround? (Or a link to further information about workarounds?)

I can only speak about what I have tried and am not an i.t. guy to any depth . I have multiple P.C's running Win 7 and Win 10 , there was a time after spending countless hours of fiddling with them and tweaking settings that it all actually worked , not so anymore and i refuse to waste any more time on something that the next update could trash .

Microsoft may never get proper networking fixed , in fact it seems to have become worse instead of better .

So , since i pay for a VPN anyway's , starts with a "N" I have been using the inclusive file and folder sharing abilities that have been built in for at least 6 months now . No...not nearly as good as proper networking would and should work . Also requires that you have access to the P.C's that you are sharing folder's/files from . If one is at a another location or in a locked room then you must wait til you are seated at it to send or recieve . Otherwise...works fine .

Just adding to this answer, which does indeed still work (using 7 digits of account phone number as user name).

Tested and found that this is necessary when connecting from Win 11 PRO licensed computer to a Win 11 HOME licensed computer, or from a HOME licensed computer to another HOME licensed computer, when using the microsoft account as the primary login, and not using local accounts.

When connecting between two WIN 11 PRO licensed computers, or from HOME to a PRO computer, the email and password of the host PC microsoft account is required and works.

In short:

PRO -> PRO: microsoft account user/pass authentication

HOME -> PRO: microsoft account user/pass authentication

PRO -> HOME: local account user/pass, or account phone number as username if using microsoft account or windows hello

HOME -> HOME: local account user/pass, or account phone number as username if using microsoft account or windows hello

Why does the phone number only work for HOME, and why does Microsoft not acknowledge it? I believe only PRO licenses have the ability to validate the Microsoft account over the internet when a client computer tries to browse the local share. This is probably linked to the remote desktop feature which was moved to a pro license with Windows 11. Hence when accessing a Windows 11 HOME shared drive, the microsoft username and account will fail. (Windows security sees this as MicrosoftAccount domain, i.e. MicrosoftAccount[email]. It FEELS like they retrofitted this msft account authentication for share drives and remote desktop to Active Directory in Win11, to meet business objectives, without thinking about every situation that the various SKUs they sell will encounter, since HOME cannot join a domain like this).

Since this feature change was breaking home networks after they upgrade to Win11, along with the push to change users to Windows Hello authentication from local user accounts, I believe they added the phone number username as a hidden function that maintains backwards compatibility with functions broken by the changes in Win11. Since local password accounts no longer exist on Win11 by default, and they stubbornly moved the replacement for this (online account verification) to the PRO license tier. Microsoft probably prefers users to either upgrade to PRO, or create local accounts if they stick with HOME edition, which is probably part of the script their techs must repeat. But the phone number must be some sort of intentional workaround, since any random string of seven numbers does not work. But one Microsoft would rather not publicize, since it highlights the awkward transition period they put themselves in, where they have to compromise security so they can move an intrinsic part of Windows functionality to higher license tiers.

I have had this problem and fixed it by adding a windows credentials for the new computer on the server. After I added the new computer credentials, the server recognized the new computer and I was able to access the files on the server.