Windows 10: Home network - not all computers can see each other

Hello,

Here's my problem. We have three PCs (one a laptop) connected to our router. Mine, is W10 Pro x64, hardwires into the router; my wife has a W10 Home x64 laptop, connected by an ethernet power plug, and downstairs we have a W7 Pro x64 working as a media server.

All are set up to use the same Workgroup.
All have the same advanced private sharing options.
All have been rebooted multiple times, as has been the router.
Nothing changes

On PC1, I can sometimes see PC2, but not at the moment. The PC itself is not listed in "Network"
On PC2, all 3 PCs can be seen
On PC3, it can only see itself

PC1 has Homegroup activate - it always fails however when I try to activate it on either of the other 2 PCs.

This is very frustrating, as we all need to share each others machines. Ho won earth can I diagnose and fix this, as it is driving me mad!

Thanks in advance

Jeremy Poynton

:)

 

Windows 10 PC can't see other PCs on network

Dell4's solution worked for me.

I had to do a "Network Reset" for each of the three computers on my home network. Now each computer can see the other networked computers and browse their folders.

 

Home Networking

Have recently tried networking my home computers , which all run Windows 10. As well I have install nas4free on an older computer to use for backups. Cannot see any shares or other computers on any of the windows machines.

My Mac on the other hand can see all computers on the network including nas4free. **** Microsoft? I have tried for hours to get the Windows computers to recognize each other but to no avail. How do I fix this?

Thanks

 

I had a similar problem. This is what fixed mine. Settings> Network at the bottom click on Network Reset. It takes 5 minuets for it to reboot. When it does, there will be a box asking "Do you want this PC to be Discovered". Click yes.

 

Neat. I will try that. Many thanks. Does the reset clear anything else - DNS settings, for example?

 

Here's a pretty good explanation of the network reset in Windows 10 from Walter Glenn at Howtogeek.com: How to Reset Your Entire Network in Windows 10 and Start From Scratch . Looks like it pretty much resets everything.
HTH,
--Ed--

 

Hi Jeremy

Try this on the two Pro PC’s

Run gpedit.msc
Computer Configuration>Administrative Templates>Network>Lanman Workstation
Enable insecure guest logon = enabled

Let us know if it fixes the problem

Roger

 

Thanks. That fixed my issue too.

 

Network reset worked perfectly, and one of the PCs had a default DNS server which I changed to use OpenDns as on the other two PCs. All can now see each other. Many thanks, and thanks also to Ed for the link, that's very useful. I shall note down all suggestions in case needed down the line.

Jeremy

 

Nice while it lasted. I switch the downstairs W7 PC off every night. The next day, it could not see my upstairs PC. The folder I had mapped as a network drive **from** mpPC is still visible and accessible - but not my PC. Its very tiresome that after all these years Windows STILL cannot maintain a super simple home network. And as noted, Homegroup is a shamble.

Any more suggestions? I want all three PCs to be able to see each other all the time. Not that much to ask of Windows is it?

 

Check that SMB1 is installed and active. Mine had been partially disabled.

 

Thanks for the tip Kado897

 

Just an FYI ...
You may want to uncheck SMB 1.0/CIFS Automatic Removal or at least go to Task Scheduler Libray > Microsoft > Windows > SMB and disable the task it adds for SMBv1 removal.

• If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.
  
• Automatic removal of SMB1 after 15 days is a one-time operation. If an administrator re-installs SMB1, no further attempts will be made to uninstall it.

From this link ... https://support.microsoft.com/en-us/...r-version-1709

 

I shall try that. God knows what people with no tech skills at all do when hitting such a problem.! Thanks, will report back.

 

Thanks for that. It's last run time was about when I started having issues. I've disabled them now just in case.