Windows 10: Solved: Can't see other computers in Workgroup on Windows 10

Awesome Bill! Cheers on the Coors! ... ... ...

 

All

Not sure if my problem is 100% the same but I discovered my lack of access between win 7 and win 10 pc's that was introduced recently, was down to firewall settings on the win 10 PC. (These were all working fine until the recent update) I haven't discovered which setting is causing the issue but turning the firewall off for Private networks solves the issue for me. (Not something I want to continue with! *Huh)

Regards

 

Something else I discovered. My wife has a Surface Pro (8.1). Neither one of the 10 boxes could see it but somewhere I read part(all?) of the problem had something to do with the adapter IPV4 settings, specifically 'Wins".

I opened the adapter settings, IPv4, Advanced, Wins then ticked 'disable Netbios over TCP. I left the LMhosts enabled which allowed the W10 boxes to see the Pro. I when ahead and turned off the Win Bios in them. This morning they're all on a friendly speaking basis.

Did I fix something? Heck I dunno. I'm a old beat up Digital RSX-VMS Fortran-Visual Basic programmer from the last century. I haven't a clue what I doing with this stuff!

 

How can you do that?
Can you post an example?

Thanks.

 

Would one of the moderators please get the posts on this thread arranged by date. I've been on quite a few forums over the years and never had to search for responses to my posts

 

Hi elPuSHeR,

You have to edit the Hosts file in Notepad et al as an Administrator.

On my machine(s) the Host file resides in C:\Windows\System32\drivers\etc

I added the IP Addresses and names of the computers that have shared files / folders to the end of the file
192.168.1.108 ASUS-6870
192.168.1.103 NetVista
192.168.1.102 Inspiron

HTH -Kevin N

 

I have gone through this thread and applied some of the suggestions. I have four PCs on a home network (DBNET). They are:
1) NB, winver 1511 Build 10586.29, Windows 10 Pro 64 bit, cabled to router.
2) B, winver 6.1 Build 7601, Windows 7 32bit, wireless connection
3) BG, winver 1511 build 10568.36, Windows 10 64 bit, wireless connection.
4) DP, winver 6.1 Build 7601, Windows 7 32bit, wireless connection.

The NB PC cannot see itself on the Network dialog; hence, none of the other three cannot see it either. The other three can see each other and can share files and folders without any problems. Therefore my perceived issue is with PC NB. By the way it did work at one time after updating NB from Windows 7 Ultimate to Windows 10 Pro. I do not recall when this issue started.
In command mode, NET SHARE reports all shared objects. Pinging ip addresses is no problem between all connections. Pinging NB (192.168.1.11 which is outside DHCP range) response as well as 127.0.0.1. PC NB has no problems with the Internet or the ISP mail servers. It is just missing from the DBNET Home network. I am tending to agree with some of the contributors to this thread that this is an issue with Windows 10 Pro or there is some clandestine setting that we have not yet found. Services such as "Function Discovery Resource Publications" and "Function Discovery Provider Host" are running. Network discovery settings are correct on all PCs and incoming data is not blocked for home network. If there is a setting that I have missed I would appreciate a hint. https://www.tenforums.com/images/smilies/089.gif

 

I have two notebooks with Windows 10 (1511) with this same problem. I have one notebook with Windows 10 (10240) that is working perfectly well. I use pin in this notebook (10240). It's a bug. Microsoft should fix it.

 

Yeh just to add me also....lost visibility to Nas and other machines. Checked all the usual file print sharing etc. All looks as it is supposed to be. Will keep on checking stuff out. Had win 10 for a couple weeks now but this is a first time.

I will keep on eye out for a resolution on this thread.

 

Please try what I wrote in post #59. It worked for me and KRL. It's a single setting that corrected the problem after updating to 1511. It's possible there are different issues out there but if you lost visibility on your network after the 1511 update, try this.
**************************************************************************************************** **********************
Figured it out (at least for me)
It's the advanced sharing settings under "All networks". Apparently "public folder sharing" under "All Networks" gets set to 'off'. Turn it back on for all the PCs that have been upgraded.

Go to "Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings" then expand the "All Networks" section and select "Turn on sharing so anyone with network access can read and write files in the public folders"

Let me know if it works for you.

Update: Here's a screen shot.

 

After fooling around where I shouldn't have, I managed to not be able to see my desktop PC from my wireless laptop in the Network window, where I did before in Windows 10. Then I happened on Settings > Network and Internet > Wi-Fi > Manage Wi-Fi Settings > Manage known networks, and saw that my Wi-Fi was not set to "Shared". After changing it to Shared, I can now see my desktop PC in the Network window, however, I still cannot see it in a "homegroup". (Not sure I need to, as I can get to my desktop under Network). Hope this helps.

False alarm. Next day my desktop went back to a no-show. (frustrated).

 

After spending a couple hours online with Microsoft tech, we finally came to the solution (at least for me).

I am running W10 1511 (Build 10586.36) on each device.

What did the trick for me was going into system properties (where you can change the workgroup and computer name) then running the wizard to join a workgroup by clicking the Network ID button. From there I used the same workgroup name and set it up as a business computer. Reboot.

All seems to be working smoothly now!