Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

workgroup networking after 1511

Feb 22, 2016 6:09PM PST

Network computers could be seen in file explorer>network on my win 10 laptop with ver. 10240, but after ver. 1511 network computers cannot be seen in file explorer>network.
NOTE: I can type the PC name as a share into the file explorer address bar and it will appear but closing file explorer means a repeat of the process of typing it in.
Here is my network setup so maybe it will shed some light:
There are 4 computers on my workgroup network, 3 of which have assigned IP's and the Win 10 is Obtain IP auto, all but one ( which as a shared folder ) having my named administrator account and the same password on all.
Computer 1= workstation 2, Win 7 Pro 64 bit ( which doesn't show up on the Win 10 in network list ).
Computer 2= workstation, an older Win 7 Pro 32 bit which I seldom have on. I just happened to have it on yesterday and it showed up on the Win 10 in file explorer>network listing.
Computer 3= XXXX-PC which is my girlfriends computer, Win 7 Pro 64 bit with a "Shared folder" that I can access because I have an account setup on it. But it no longer shows up on the Win 10 computer in the network listing.
Computer 4= workstation 5, HP ProBook 450 G2 i7, Started as Win 7 Pro 64 bit upgraded to Win 10 ver. 10240 which showed all of networked computers, upgraded to ver. 1511 which now only shows itself and the 32 bit Win 7 computer in file explorer>network.
Conclusion so far, for some unknown reason the 32 bit old computer shows up but the newer 64 bit computers do not show up. Evidently when opening file explorer, it search's for other computers on the network but it is only finding the 32 bit. I'm assuming that there is a setting somewhere that must change when ver. 1511 is applied.
Any help to shed light on the problem would be appreciated, thanks.

Discussion is locked

Lumpy95 has chosen the best answer to their question. View answer

Best Answer

- Collapse -
Solved
Mar 2, 2016 1:57PM PST

Today ( 3/2/16 ) I got 2- W10 updates, KB3140743, and KB 3139907 which brought it up to build 10586.122 and the W10 computer now sees the other network computers in
file explorer>network
.
Thanks R. Proffitt for at least trying to help when no one else did on here.

- Collapse -
Answer
More info
Feb 23, 2016 10:43AM PST
- Collapse -
Just so you know
Feb 23, 2016 10:53AM PST

I haven't seen this issue but for years I've had to remove a share, make it anew, add users and check all the ACLs and more. I can't tell if you did that. You may want to try that.

- Collapse -
Nope
Feb 24, 2016 7:23AM PST

Thanks for the response.
No, I haven't redone the shares as I was hoping to not have to go through all that since ver. 10240 worked fine with recognizing my network as-is. Something changed in ver. 1511 as to not allowing my 64 bit computers to be listed in file explorer>network although it recognizes them when I type the computer name into the address bar.
To save from having to type them in constantly, I made shortcuts to place on the desktop for accessing the other computers 1 at a time but that is a PITA when the computers "should" be listed just like on the previous version. Win 7 see's all computers as before, it's just the Win 10 ver. 1511 that changed.

- Collapse -
Microsoft has a habit of changing things like that.
Feb 24, 2016 10:28AM PST

Not only do they update the file but they may "correct" registry entries that can break someone's fine work. I think it was some old LAN that the NTLM authentication entry would reset on updates. https://www.google.com/#q=allow%20ntlm%20authentication but I can't tell you this. All I know is my method to deal with it.

- Collapse -
Hmmm
Feb 24, 2016 2:11PM PST

I followed your link and I am wondering if windows authentication may not be turned on ( not close to the Win 10 computer to check right now ). I'll have to work up some courage to start redoing shares as I am no whiz.
Thanks for your input R. Proffitt.

- Collapse -
I can't know if my link applies.
Feb 24, 2016 2:30PM PST

I used it as an example where we had been turning that on for some legacy PCs (over a decade old) and updates appeared to turn it off. Sorry if I mislead you to write that was it.

- Collapse -
Re
Feb 24, 2016 5:57PM PST

No apology needed. I just looked at the link and thought that maybe it might lead to something. At this point, I am grasping at straws anyway.
At this point I am thinking of assigning an IP to the win 10 computer instead of obtain IP auto and editing the host file so it can look for the other machines. Not sure if that will change anything but all the other computers are assigned IP's and I edited the host file on all of them a long time ago. What have I got to lose, other than the time it takes to do it, LOL.