Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 23, 2018 3:01 PM
Hello!
This article says
Explorer Network Browsing
The Computer Browser service relies on the SMBv1 protocol to populate the Windows Explorer Network node (also known as "Network Neighborhood"). This legacy protocol is long deprecated, doesn't route, and has limited security. Because the service cannot function without SMBv1, it is removed at the same time.
However, if you still have to use the Explorer Network in home and small business workgroup environments to locate Windows-based computers, you can follow these steps on your Windows-based computers that no longer use SMBv1:
Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start). When you open Explorer Network, enable network discovery when you are prompted.
All Windows devices within that subnet that have these settings will now appear in Network for browsing. This uses the WS-DISCOVERY protocol.
After starting these two services (along with UPnP Device Host, SSDP Discovery and DNS Client) my newly installed Windows 10 1803 still does not see any computers in the Network Neighborhood (but it does see all network printers!).
Network Discovery is turned on.
Is there a way to make Windows 10 see all computers (including Windows 7 !) in Network Neighborhood?
Thank you in advance,
Michael
All replies (5)
Thursday, August 23, 2018 11:27 PM
Windows 10 does not have "Network Neighborhood". Neither does Windows 7. Nor do they need SMB1 or the computer browser service. That was for XP or earlier. The first two paragraphs of article you quote do not refer to your situation.
All Windows systems from Vista onwards use the newer network discovery method (as described in the third paragraph of the article). You will plenty of posts in this forum on this issue.
Bill
Friday, August 24, 2018 7:18 AM
"Windows 10 does not have "Network Neighborhood". Neither does Windows 7" - in this case what does the second paragraph describes?
"However, if you still have to use the Explorer Network "(also known as "Network Neighborhood")" in home and small business workgroup environments to locate Windows-based computers, you can follow these steps on your Windows-based computers that no longer use SMBv1:"
"All Windows systems from Vista onwards use the newer network discovery method (as described in the third paragraph of the article)" - and I know quite well HOW do they use this new protocol: without enabling the old-fashioned Computer Browser service only ~60-70% of computers can be seen in Network Neighborhood (that does not exist in Win7 according to your reply) in Windows 7/2008R2.
"You will plenty of posts in this forum on this issue." - if any of them had the solution to my issue I won't have published this question.
Regards,
Michael
Wednesday, September 5, 2018 2:40 PM
The answer is to make all computers on the network have their function discovery services auto-started.
Thank you all once again.
Regards,
Michael
Wednesday, September 5, 2018 11:40 PM
Function discovery services auto-started does not work for me!!
Colin
Friday, September 7, 2018 10:40 AM
Do you mean computers with these services started don't see other computers and can't be discoverable by others?
I was using the method descibed here: https://michaelfirsov.wordpress.com/network-discovery-without-computer-browser-service/