It remains to be seen whether this is a bug or by design. (I am assuming you already know what you are doing and I will not cover how to do this or the dangers of doing so in this guide) Now, let's say you prefer the old insecure way of Windows shares and you have turned password protected sharing off. The can be whatever you please, it can be the PC Name, it can be WORKGROUP, it can be a period, it can even be Neowin if you want.Įxample: Your User name is Bob, and your password is 12345. To do this, simply add \ to the login user name. By making Windows believe the share is part of a domain it will ignore homegroup authentication and use the legacy login system not tied to homegroups or Microsoft accounts.
In order to bypass this, we must "trick" Windows into thinking the network share is part of a domain. This causes incompatibility (both with Windows 10 and previous versions of Windows) if a homegroup is not used on the network. In Windows 10, when a domain is not set and a Microsoft account is linked, it makes homegroup (tied to your Microsoft account) the default (and only) setting to use as authentication. To see what is actually going on, let's look into the issue deeper. This problem occurs when you have linked a Microsoft account to your login but have not setup (or you are not using) a homegroup. Or maybe you have disabled password protected sharing but it is still asking for a password. You are 100% sure the login and password are correct but Windows is insisting your password is incorrect.
You may have noticed after upgrading to Windows 10, you can no longer access network shares.
0 kommentar(er)
