Solved Can't access shares on a Windows 11 system from a Windows 10 system

Win 10 Pro 21H1 19043.1586
ASUSTeK M4A785TD-V EVO
AMD Phenom II X4 925 Processor, 2800 Mhz, 4 Core(s), 4 Logical Processor(s)
RAM 8GB HDD 250GB
EDUP 600MBPS Dual Band USB WiFi Dongle

4 other Desktop and Laptop computers access the Windows 11 shares with no problem, just this particular system won't do it. All are setup the same way so I don't know what the cause of the problem is. When I try to access a share I get this error:



The same username and password works okay on the other systems accessing the Windows 11 computer. I use my own set of instructions to setup sharing and until now it's always worked:

2022-04-28-13_02_49-window-zip is a Word document with the instructions I use.

This is my ipconfig info:

I can ping the Windows 11 computer from this Windows 10 computer:

Windows 11 is very temperamental on shares. There appears to be something a bit screwy with credentials, eapecially if using MS accounts. I found if you run the credential manager on both pcs, and manually add the pc name, account and passwords, it sorts it. Also, it tends to fall over of no password with local account.

Networking always since its inception way back with Windows for workgroups 3.11 has always had touches of "Gandalf the Wizard" about it. Usually though it eventually works. First on the windows system ensure that connectivity to the appropriate device or system works via simple ping -- if the computer name isn't picked up try the ip address.

Then ensure that the remote computer allows inbound (and if required) outbound connections. I'd assume that you've already enabled that on the local machine !!! and of course ensure Network discovery is turned on and the network is a "Private" one.

Ensure users have correct access rights on the target system(s).

Ensure devices have correct permissions to allow access.

On Local Networks ensure no machines or mobile phones etc have "grabbed" an IP address that another device wants -- I've found that switching entire system off plus routers etc often works and then restart computers individually - don't switch ANY phones etc on until all the Windows machines are up and running.

Don't start any NON Windows devices until all your Windows machines are up and running (i.e also don't start TV's, Amazon fire sticks, Sky Q boxes etc ).

(I really have 100% no idea why this sometimes works -- it seems to "just do it for me" -- I haven't got the time and skill to analyse that problem -- I just want the Network up and running properly !!!! as quick as possible).I leave the "Monday Morning Quarterbacking" to others who are experienced in this!!!.). As an "Old School Engineer" I want to get kit up and running again as quickly as possible providing it can be done safely. Once it's working then is the time to try and find out what went wrong -- no point in having systems idle for maybe days when people need them to be online again as quickly as possible.

(You might need also to enable SMB1 depending on the equipment that needs to be accessed).

Don't forget any Windows firewall rules and / or hardware rules you might have in your routers.

Programs like filezilla (free) and work on Windows as well are brilliant also for checking shared file / drive access.
In some cases depending of the direction of File transfer you might need to install and enable the OPENSSH-Server -- install from Windows add an optional feature).

I sympathsize with ANYBODY having problems with Windows Networking -- it really seems to be far more complex than it needs to be. (Perhaps that's why these guys who understand this stuff get paid really good money !!!!!!).

I'd finally suggest testing using LOCAL accounts on all windows machines -- there could be some problem in how "Logon info" is propagated to / from a remote Windows machine using an Ms account. If you can get local accounts working but not Ms account logins then you know where the problem lies. Solving it is another matter though !!!!.

Cheers
jimbo

I opened Credential Manager, clicked on Windows Credentials then added a new credential.

In Internet or Network address I put name of the Windows 11 system. I added the username and password then clicked OK.
(this was the same username and password I used in Windows Credentials in my first post)

Now I can browse all shares on the Windows 11 system.

Rich,

What an imaginative experiment. I'm so pleased to hear that it worked.

I have no problems sharing with any of computers but I checked my Credential manager & I have an entry for only one of my network computers there.
- I have never manually added that entry.

Perhaps your method will help others, I do hope so,
All the best,
Denis

I'm trying to figure out exactly what to put in the windows credential manager when I add new.

what would the network address be ? And then I would create a local account using the ten forums tutorial to create a " local " account.
I am pretty sure its going to be the local account login name the name that is used for the local user accounts desktop. So like I create a user account and it makes a folder called dons1070 under users and Im pretty sure that dons1070 will show up under network then. IM pretty sure that is how it works?? In the past however I have also seen the FULL COMPUTER NAME being used as a share name under network. Its all very confusing at times. When a person has a Microsoft account and then they start a local account will the make a new desktop ? And can a person access shares when logged into the Microsoft account. ? I do not think they can not reliably anyway.