Windows 10: Network Discovery will not stay on

I have a strange problem and can't find a fix.

I've lost the ability to connect to a Win 7 computer on my network. It has worked for a very long time but stopped working after I replaced my SSD on the Win 10 desktop computer. I cloned a new Samsung 860 1TB SSD drive from the old Samsung 850 512GB SSD drive using the Samsung Data Migration software. (This worked with one other exception. I have to reauthorize MS Office)

I also have a Win 10 laptop on the network and am able to connect to it.

In the Network and Sharing Center, Network Discovery will not stick in the On setting for Private and Guest or Public areas. It is On and stays On in the All Networks area.

File and Printer sharing is on.

I have looked at the threads in this forum as well as the following threads:
Network Discovery will not stay on - Microsoft Community
https://support.microsoft.com/en-ca/...ring-center-in
All of the services mentioned are turned on correctly .

I pinged the Win 7 computer and get a correct ping.

I can see the Win 7 computer in File Explorer but can't access it. (I get the window "Windows cannot access\\Win7). The detail is Error code 0x80070035.

I ran the Windows network trouble shooter and it was unable to find the problem.

I turned off both Windows Defender and Defender Firewall and this didn't fix the issue either.

This seems very odd because I can access the Win 10 laptop but not the Win 7 desktop. The only thing that has changed since it worked correctly was the change and cloning of the Win 10 desktop SSD.

Any suggestions?

:)

 

Cannot keep Network Discovery Enabled.

Hi,

Thank you for the response.

I would suggest that you change the settings in the Firewall to allow Network discovery so that the Firewall stays On while allowing the Network discovery to be enabled.

Follow the steps.

a . Open Control panel.

b. Small icons from the drop down.

c. Click on Windows Firewall.

d. Click on Allow programs or feature through Firewall.

e. Scroll the list and check Network Discovery.

If you need additional assistance then let us know.

 

Network discovery will not stay on and Function Discovery wont start

I did see that, but I've gone through it again and tried the suggestion on renaming the computer/workgroup...no help.

 

Network Discovery Spotty

Hello,



For each of the machines experiencing this behavior, will you please perform the following:

• 
  Ensure Network Discovery is enabled.
  
  • 
    Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings
    
    • 
      For each Network Category (Public, Private, Domain) you wish to have the feature enabled, click the arrow to the right of the category to expand it, and select “Turn on network discovery” & check “Turn on automatic setup of network
      connected devices”
      
• 
  Ensure that Network Discovery is allowed inbound in the Windows Firewall (in addition to any other firewall in use).
  
  • 
    [Windows Key + R] > Firewall.cpl
    
    • 
      Click “Allow an app or feature through Windows Firewall” in the left pane.
      
    • 
      In the Allowed apps and features scroll box, find “Network Discovery”.
      
    • 
      Make sure it is checked for all of the Network categories that you have enabled.
      
• 
  Ensure the necessary services are started.
  
  • 
    [Windows Key + R] > Services.msc
    
    • 
      Base Filtering Engine
      (BFE)
      
    • 
      Computer Browser
      (Browser)
      
    • 
      DHCP Client
      (DHCP)
      
    • 
      DNS Client
      (DNSCache)
      
    • 
      Network Connection
      (NetMan)
      
    • 
      Network Location Awareness (NLASvc)
      
    • 
      Remote Procedure Call (RPC) (RPCSS)
      
    • 
      Server
      (LANManServer)
      
    • 
      SSDP Discovery
      (SSDPSrv)
      
    • 
      TCP/IP NetBIOS Helper
      (LMHosts)
      
    • 
      Workstation
      (LANManWorkstation)
      
• 
  Ensure the network interface that is connected to the network you want devices discovered is in the appropriate network category.
  
  • 
    [Windows Key + R] > Cmd.exe
    
    • 
      Type “PowerShell.exe Get-NetConnectionProfile”
      

In this output you will find Network Category, which needs to correspond to the category enabled through the firewall, as well as when Network Discovery is turned on.

• • • • • 
          For machines with multiple interfaces, you will need to know the name of the interface which is connected to the network with the devices you wish to be discovered
          
• 
  Ensure your Network bindings are correct.
  
  • 
    [Windows + R] > NCPA.cpl
    
    • 
      Right click the interface and select Properties
      
    • 
      Ensure the bindings are bound
      
      • 
        Client for Microsoft Networks
        
      • 
        File and Printer Sharing for Microsoft Networks
        
      • 
        Link-Layer Topology Discovery Mapper I/O Driver
        
      • 
        Link-Layer Topology Discovery Responder
        
      • 
        Microsoft LLDP Protocol Driver
        
      • 
        Internet Protocol Version 4 (TCP/IPv4)
        
      • 
        Internet Protocol Version 6 (TCP/IPv6)
        
    • 
      If any of these are unbound, try rebinding, and if that still doesn’t work, from an elevated command prompt, run
      “NetCfg.exe –d”
      

Hope this helps