For years, I've had file-sharing set up so that my laptop can access files on my desktop PC. I did that by creating matching (local) user accounts on both PCs. That worked fine for years, even when I had Windows 7 on my desktop PC, but it spontaneously stopped working a few months ago (several months after I upgraded my desktop PC to Windows 10).
I can still access the shared folders by IP address, but not by host name. In other words, \\192.168.1.9\ works, but \\DesktopName\ doesn't. Unfortunately, my router won't let me assign the desktop PC a static IP address, so I can't use that as a convenient workaround.
The only thing that fixes it – temporarily – is to use the "Network Reset" in Windows settings. However, it stops working almost immediately. After that, any attempt to access the shared folders by host name prompts me to "enter network credentials," but my credentials aren't accepted.
The problem is only with this laptop accessing this desktop PC. I can still access shared files from other computers in my household, including another Windows 10 laptop. I can also access other computers by host name from this laptop.
Other notes:
• I use the Private Internet Access VPN, but I don't think it's responsible, because I have the issue with or without it turned on.
• I prefer not to sign into my personal computer with a Microsoft account, so I haven't tried that.
• I've tried the Windows Credential Manager — both adding and removing my credentials.
• I've tried turning on Windows Services recommended on various help pages.
• I've double-checked the "advanced sharing settings" in the Network & Sharing Center.
• My TCP/IPv4 settings are configured to obtain an IP address and DNS server automatically.
I'm stumped here. I know there are similar questions already on this forum, and others... but I feel like I've tried all of that advice already. I must be missing something.
ping
the remote machine with the share on it my it's name from the machine with share connection issues? If not, you might need to add thec:\Windows\System32\Drivers\etc\hosts
on the remote machine and ensure it's IPV4 address is statically assigned rather than DHCP assigned. I assume you've already triednet use /delete *
and then tried remapping the drive. Windows has been hardening defaults for NTLM as I see mentioned in other answers, so if you need to use NTLM, you might investigate how to ensure it's enabled on the remote machine.