I also disabled the "Accounts: Limit local account use ... " on both my devices as suggested by gijoetech1 (Thanks for the response) without that affecting the access from either machine to the other. Enabling it again didn't seem to have any effect on my problem, either. Not for the way my devices were setup, anyway. Then I noticed, in Networking and Sharing Centre, that one of my devices was showing that the network was a "Public" network, and the other, that the network was "Private." Further digging revealed that one device was set as "Discoverable," and the other, not.
This tutorial helped me to change the device that wasn't discoverable, to discoverable.
Network Location - Set to Private or Public in Windows 10 - Windows 10 Forums
My devices are now showing the network as private, and each now see, and can access, the shared drives/folders on the other machine. And this function has remained effective after two full shutdowns of both devices. So, fingers crossed that it will remain so. I'll have to remember to check this after the next "Insider" update
I don't have that problem, both machines are set to discoverable, issue remains UN-resolved.
After both devices were shut down overnight, then started this morning, Surface could see and access files on Desktop, but Desktop could not access folders/files on Surface. It saw Surface, but couldn't access it. Changed the Network ID ... on Surface to : ... Home ... rebooted Surface, now Desktop can access files on Surface.
Both machines are running W10Pro x64, "Insider" build 14342 on Desktop, Version 1511 10586.318 on Surface. Both connected by Ethernet, Desktop via the on-board network circuit, Surface through a Surface 4 Dock. Neither have problems accessing the Internet.
Settings/Network & Internet/Ethernet label the icon "Network, Connected" on Desktop, on Surface the label is my ISP's identifier name.
Hmmm. Looking at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles I saw that Surface had 3 entries, whereas Desktop only had one. I deleted the 2 on Surface that were the result of other connections, rebooted, and Desktop can now access files on Surface. Now the question, will they still be both able to access files on the other machine after an overnight shutdown. We'll see what happens tomorrow.
Last edited by lmod; 21 May 2016 at 17:44.
I wonder if I have solved my problem, after an overnight shutdown both devices can access files on the other device. But not claiming success yet, will wait and see if this ability to access the other machine continues in the days ahead.
I created an account just to share this, which might help... hopefully.
So at my work, we were experiencing networking problems with the new windows 10 computers. We couldn't get them to connect to our work server where we keep the majority of our work files and data. When logging in with the correct username and password it would say the credentials were invalid. However adding a registry key fixed the issue!
In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ right click and add a new DWORD value, name it " LMCompatibilityLevel ", and change the value to 1 (screenshot below of what it should look like). I hope this helps you!
[Link for reference to issue: NTLMv2 Secure Authentication method]
So my Win10 computer has been accessing drives on my Win XP computer for more than a year with no problems, but today I cannot get onto that computer. I get the user name or password incorrect error.
I've quadruple checked my logins and passwords. I tried entering the computer name in the login path. I tried creating a new user on the host computer to log in to. I've cold re-booted everything.
None of the above has made any difference.
What the heck is going on with Win10 now?
When you said make that registry entry above do you mean on the computer hosting the shared folders, or the client computer?
The registry change should fix your problem immediately, however, I suggest you reboot to make sure it has indeed stuck and not reverted back for some odd reason.
-Please let us know either way what happens
I tried another Win10 computer connecting to the same shared folders and had the same problem saying my specified password is not correct. This one also used to work, and hasn't had any Win10 updates for a while. I can still operate the WIn XP computer from the Win 10 computer (I use Synergy) so the network connection is alive.