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

Thanks UK Media, will try this. *Smile

 

I have the same issue, and have had for the last 3 insider builds. On a domain (I am the admin) with several Win10 boxes that are release product and several with current rev insider builds. ALL of the insider builds are unable to see other domain computers (release product can, and ALL pcs can see network devices), yet I am able to access them by name and IP. It's a pain in the ass since I use explorer daily to access other pcs. I've searched through firewall rules, services, and anything else I can find, even pulling the nics and replacing with a different manufacturer (thankfully I have several of these and didn't buy any). Nothing has worked, nor can I find any differences between the insider builds and the release product.
This tells me that someone either changed something in the network stack...well...actually that's all I can think of. I've posted to the feedback section and noticed many others have this problem. All of my systems were clean loads, not upgrades, so there are no leftovers from previous os's.
Posting this mainly in the hopes that a genius comes along with a fix *Smile

 

Anyone found a solution to this issue? My began happening after the Threshold update this week. I can see SOME of the computers on my network, but can't see others, including the one I especially need to see. . Totally flumoxed!

Any suggestions appreciated. Thanks.

 

Update/clarification to previous post:
All insider build boxes (3 virtual, 3 daily use, all on domain), and 1 win10 release product box can see each other, but not other domain pc's. Other domain pc's (4 win7, 5 server 2008r2) can see ALL pc's.
ALL pc's can see all network attached devices.
Brought an older build (about 4 builds back, forget the number) in a VM back up and it could see everything. Installed the current insider build over it, which again, removed all other pc's from explorer. This problem was definitely introduced within the last 3 builds.

 

Hi all
I have the same issue, and have 3 laptop connected in my network on same domain (workgroup - I am the admin) since last 1511 w10 update I lost my network map drives (2 other laptop) and I can NOT see them in my network and I can NOT use it.
I reset the winsock network but nothing happens.
MS Shame on you !
Please help !

 

Out of curiosity, have you attempted L: \\ComputerName\drive$ to access? After that have you remapped your mapped drives? I had my mappings disappear as well, but after recreating them, they have stayed.
I am not saying that I can see the network PC's in explorer, just that a mapped drive will stick.

 

Hi
I tried \\ComputerName\drive$ and I still have no access to them
what do you mean by After that have you remapped your mapped drives ?
How did you remapped your drives ?

 

Prior to update I could see other domain computers under Network, but after the update they disappeared.

I can ping map the drives and all that so access is not a problem. Its just a major pain is all. I agree with previous post that indicates this was working and then stopped.

If there are any other suggestions please post.

Thx.

 

Glad, I found this forum or thread. I thought I am the only one going crazy of losing my NAS and other PC in the Network folder. Everything disappeared after I reboot my router or reset. I can still access directly by typing "\\MYDRIVE"" but such inconvenience that it no longer discover other networked device / nas drive / computer anymore.

Yes, I am running Windows 10 Pro 64bit build 10586 (just updated yesterday)

 

Let me take a step back. When this problem first occurred on one of my systems, I also lost my mapped drives (which are shares on other servers on my lan) (all of them are members of my domain, and this would be the same if you were using a workgroup). This was very problematic because I have several business apps using the mapped drives.
I remapped in the standard fashion, right click, then "map network drive", select the drive letter I want to use and such, but it seemed to have some big delays when accessing.
I then went back to the mapped drive and selected "disconnect", rebooted to be sure there would be no oddities, then went back to my network share, right clicked, and selected "map network drive" again.

If you absolutely cannot access your network drives in any fashion, I would suggest first checking to be sure whatever network type you are on has file and printer sharing enabled. If you r system comes back up as public network it will be disabled (however, it should pop up a yellow band at the top of explorer telling you that it isn't enabled if it indeed is not), then I would suggest checking out your firewall; turn it off if you have to just as a test, turn back on once you narrow down the problem.
In my earlier comment I should have said "re-map the drives you want mapped".

As I was typing this response, something popped in my mind, so I checked it out, and it appears to have resolved this issue for me. I will need to do some further checking because it doesn't make total sense, but...

If you want to check it out, open SERVICES on EACH PC or server on your workgroup or domain, scroll to "Function Discovery Resource Publication", and start it. Then check to see if all your pc's show up in explorer. There is also a "Function discovery Provider Host" that may play into it. There are a few other settings that may play into other device discovery that I'll have to look into. All my devices actually show up though.
If this works for you, change the start up for the service to automatic and it should stay on. I don't know the ramifications of changing this setting so Ill be monitoring to see if there are any obvious ones.

My guess is that some change that was implemented in the latest insider builds has affected network discovery. I know that my servers all had this ("Function Discovery Resource Publication") turned off for as long as they've been in service, which is a matter of years, and it always worked, so it isn't the other pc's, it's the Win10 boxes.

 

That's interesting. I disabled those two services and it did not stop any of my shares showing as they should. This comp could see and be seen.

My workgroup network uses Lanman for sharing.

 

Hello all,

I did check that function discovery service as suggested, but it is running on my machine without intervention from me.

Please continue to post any suggestions. One of them might work.

Its a strange one. Everything works just fine mapping, backup to network, etc. You just cant see the machine in the network neighborhood window (if that's the right name for it).

Interestingly if I create a shortcut and put the path \\hda\ then press the browse button it will display the available shares ok, and the machine shows up in the left pane tree under network (but only until operation is finished).

Don't know if that's a clue.

Also turned off firewall and all that but no change to the issue.

Thanks,

 

I've check what other had suggested, no luck here.

 

I noticed, I cannot even see my own computer in the Network folder but I can see my Sufrace Pro 2 only. That's all. Not my NAS or my router NAS drive.

 

I came into my office this morning and found there were some updates that required a reboot. I rebooted and lo and behold, I can now see my network computers and am able to set up mapping that drive as I normally do. I have no idea what happened, but it;s now working for me. Hopefully everyone else gets this.