Explorer/Network shown everything except Computer

Might be the SMBv1 Uninstalled by Update 1709 issue?

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


It certainly isn't a "friendly" write up that is for sure .....written for IT Pros I think but I found I only needed the SMB1.0 Client re-enabled for things to be fine again after playing with different settings.

T.D.L :
FCU 1709 disables and removes SMBv1 after 15days if it hasn't been used, (eg turning on my old Synology NAS i found I couldn't connect to do a backup), But you can turn it back on in:

THE FIX

Goto Control Panel>Programs and Features>Turn Windows Features on and Off>SMB 1.0/CIFS

and checking just the SMB1.0 Client box worked for me.

Once you do this Win10 will no longer disable it automatically as it assumes you need it, if you it turned back on.

AFAIK this issue with SMBv1 was mainly related to WinXP and is not an issue on Win10 , so personally I was not worried about turning it back on.

Or if you need pics ? .....do the reverse of this article
How to Disable SMBv1 and Protect Your Windows PC From Attack


For Others to try 1st Per Microsoft ..........

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:

1. Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start).
2. 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. Contact your other vendors and manufacturers if their devices still don't appear in this browse list after the Windows devices appear. It is possible they have this protocol disabled or that they support only SMBv1.

Note We recommend that you map drives and printers instead of enabling this feature, which still requires searching and browsing for their devices. Mapped resources are easier to locate, require less training, and are safer to use. This is especially true if these resources are provided automatically through Group Policy. An administrator can configure printers for location by methods other than the legacy Computer Browser service by using IP addresses, Active Directory Domain Services (AD DS), Bonjour, mDNS, uPnP, and so on.

Hey GARoss,
What didn't work, can you be more specific?

Note: If you did Kbirds THE FIX and you don't have a NAS or Router USB File Sharing, you're probably going to have to install the SMBv1 Server.

Eagle51 said:

Hey GARoss,
What didn't work, can you be more specific?

Note: If you did Kbirds THE FIX and you don't have a NAS or Router USB File Sharing, you're probably going to have to install the SMBv1 Server.

Eagle51 maybe correct GARoss I have both on my network , I tried it with the Server Option too and it worked as well, but I found I didn't need , when experimenting, so removed it.


KB.

Hey GARoss,
Are you both running the same Win10 Vers ?

it may help perhaps to make the computer that is usually on maintain a list of other on the network....

I still do this and us the info in this text file :