Cannot Access Shared Folder via Network

Quick Info:
Both Computers are running on the same network. One is Windows 10 Pro and the other is Windows 11 Pro. Both computers are fully updated via Windows Update. Both have Network and File Sharing turned on.

They previously worked, but the Windows 10 computer was packed away for a couple months and I just recently set it up again. From the Windows 11 computer I'm able to connect to the Windows 10 computer with Remote Desktop Connection. (this is the main way I like to connect so I can control the computer remotely) Occasionally there are times I need to transfer files back and forth to/from the Windows 10 computer. Just since I've set the computer up again it's not letting me access the shared folder from the Network File Explorer folder. I double click or right click open the other computer's icon and I'm getting the message "Windows cannot access". However, if I type \\computer's IP into file explorer after a minute or so the logon screen comes up where I can enter the username and password. After that I'm able to access the folder, but still cannot access from the Network File Explorer folder like I used it. I tried going in the other direction from Windows 10 computer to the Windows 11 computer and it keeps saying my credentials are wrong even though they are correct. I'm logging in with my Microsoft account and I know the username/password is right, but it's not accepting it. Pretty much both computer (that used to work and get along) are no longer working together.

I went into Credential Manager on both computers and removed all windows credentials. I don't know what else to try at this point. Suggestions?

Try this first.
Do this on all systems in network..

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:
sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation
Restart

Make sure these services are set to automatic and running

DNS-Client – Server
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPNP Device Host
Windows Defender Firewall

If you have password protected sharing on, you will need the proper credentials.

Update: So on computer B in the Windows Defender Firewall inbound the File and Printer sharing was enabled for both public and private. I disabled all the public ones and now I'm able to access computer B shared folder from computer A in the Network File Explorer folder by double clicking the icon. That is solved. However, I'm still having the issue with computer B trying to access computer A share folder. I'm getting two types of error messages.


I tried net use in command prompt and it's saying no entries.



I know the user name and password is correct, but it's not accepting it.

glasskuter said:

Try this first.
Do this on all systems in network..

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:
sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation
Restart

Make sure these services are set to automatic and running

DNS-Client – Server
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPNP Device Host
Windows Defender Firewall

If you have password protected sharing on, you will need the proper credentials.

Click to expand...

I have the same issue. I had two Windows 10 PCs that I exchanged files with regularly. I recently upgraded one of these PCs to Windows 11 after which I now get this error every time I use my new Win11 PC to access files on the Win10 PC.


I performed all the steps you have outlined here, but to no avail. I still get the error.