Cannot see other pc on home network

I do pretty much the same as MisterEd except I just have the shortcuts on the Desktop, I don't even bother with the network folder, I just use the shortcuts, works 100%.

dalchina said:

Ok, so you had 2 where networking sometimes worked, and you're hoping to add a 3rd.
I will assume all are running Win 10.

See:
Share Files and Folders Over a Network in Windows 10
Option 1
and methodically work through all the settings. First time I did it I had to check twice. It's frustratingly inconvenient.

Note that with Win 10 you don't need SMB1 enabled. It's a disadvantage to do so. Check this is disabled on all PCs.

I had networking working quite well with build 1903 on both PCs. Then I upgraded 1 to 20H2 and had to do something to get that seeing the 1903 PC again. After upgrading the same one to 21H1 - networking only works from the 1903 PC.

I'm trying to work up enough enthusiasm to try again!

Yes, same here, My issue started with upgrading to 20H2, broke my P2P that had been running great for many years. with the Smb 1 thing being a quickly fix issue.
My P2P 3 desktops and 2 Notebooks all worked fine until 20H2. All the other computer except this one which i take chances on with new stuff I was able to rolled back to 2004 and the issues resolved. This Office desktop I have used the .cab file to upgrade to 20H2 So I was not able to roll it back. Its is now upgraded to 21H1and a it still doesn't see itself nor can any of the other units see it in Network places or File explore.
However it actually is available to connect to my network, It just doesn't show up.
So back then, we came up with a work around. Create a Folder Called Network on my desktop. Inside this folder create a short cut the computer that can't be seen. that short cut work just like Network places or file explore.
I came here today to see if this issue has been resolved or a better work around had been found.
This is very inconvenient way to access my network, and is preventing me from upgrading from 2004

Basics windows doesnt look for pcs on the network it asks the master browser it can take 20+ mins for it to find new pcs and if you tuen the pc off it drops from the list. The MB uses netbios to resolve the name but in the mean time you can access via IP. It access via IP you need to use the share name ie 192.168.1.24\share name from a cmd prompt try
net use s: \\192.168.1.24\share /user:HTG password
Change ip to yours change htg to a user on the pc your connecting to and their password. You can change s: to the drive letter you want.

When you get it working you can save the txt as a cmd file ir connect.cmd so you can double click to connect newxt tiem

NOTE windows doesnt like - names ie pc1-win10 remove -


Try this util on all pcs does ot see the other pc and which is master browser NetBScanner - NetBIOS scanner

windows doesnt look for pcs on the network it asks the master browser it can take 20+ mins for it to find new pcs and if you tuen the pc off it drops from the list

- only if SMB1 is enabled, which is only needed if you have devices with Win 7 or earlier or certain NAS's.
Otherwise SMB1 should not be enabled.

Samuria said:

Basics windows doesnt look for pcs on the network it asks the master browser it can take 20+ mins for it to find new pcs and if you tuen the pc off it drops from the list. The MB uses netbios to resolve the name but in the mean time you can access via IP. It access via IP you need to use the share name ie 192.168.1.24\share name from a cmd prompt try
net use s: \\192.168.1.24\share /user:HTG password
Change ip to yours change htg to a user on the pc your connecting to and their password. You can change s: to the drive letter you want.

When you get it working you can save the txt as a cmd file ir connect.cmd so you can double click to connect newxt tiem

NOTE windows doesnt like - names ie pc1-win10 remove -


Try this util on all pcs does ot see the other pc and which is master browser NetBScanner - NetBIOS scanner

Well all my desktops are on 24/7 all on 2004 have no issues on this one, that the issue started with the 20H2 update has the issue. updating to21H1 did not help either.
All my units had the issue while running 20 H2, and stopped having the issue when rolled back to 2004, I didn't roll this one back since i have updated with a .cab file rather than WU So it can't be rolled back. And I didn't find it important enough to restore a Image file. Since it had been several days as I thought surly MS would fix this issue or the group would find a work around. So looks like that is not the case.

If it get a major update it is no longer the same pc its a new pc as far as the network is conserned