Sharing Broken Solved

  1.    #1

    Sharing Broken


    OK, here's the details of my little home network:

    Desktop PC:
    • Name - RAVEN
    • OS - Windows 10 Pro 64-Bit (1803 17134.228)
    • Network - Ethernet connection to WiFi router
    • IP - Static 192.168.0.100

    Laptop PC:
    • Name - COYOTE
    • OS - Windows 10 Home 64-Bit (1803 17134.228)
    • Network - Wireless connection to WiFi router
    • IP - Static 192.168.0.102

    Prior to the latest update which MS forced upon me, file sharing had been working flawlessly for years. Not so any longer...

    To the best of my understanding, I have diligently followed Brink's excellent tutorial: Share Files and Folders Over a Network in Windows 10

    However, it just doesn't work. Here's what I've done so far on both machines:
    • File Sharing Wizard On
    • Function Discovery Resource Publication and Function Discovery Provider Host set to automatic.

    Question 1: Even though both services are set to automatic, the Function Discovery Provider Host doesn't start after a reboot. If I manually start the service, the machines can see each other on the network. I have never encounter a situation where a service set to automatic does not start. Ideas???

    I have also:
    • Turned on network discovery
    • Turned on File and Printer Sharing
    • Turned on Public folder sharing
    • Turned off password protected sharing
    • Set file sharing connections encryption level to 128-bit

    Actually, all of these settings carried forward from before when file sharing worked.

    I have tried all the methods in Brink's tutorial to create shares on both machines. In File Explorer I can see both machines under Network. I can also see the shares on a given machine from that machine. However, if I tried to view a share on the other machine, I receive an error.

    Click image for larger version. 

Name:	error.png 
Views:	30 
Size:	7.4 KB 
ID:	201245

    As usual, the Troubleshooter never resolves the issue.

    Question 2: Any idea how to fix this so file sharing actually works (the way it used to before MS )?
      My ComputerSystem Spec

  2.    #2

    Question 1: Even though both services are set to automatic, the Function Discovery Provider Host doesn't start after a reboot. If I manually start the service, the machines can see each other on the network. I have never encounter a situation where a service set to automatic does not start. Ideas???
    Set both Function Discovery Services Startup Type to Automatic Delay. (Don't know why it doesn't always start set to Automatic)

    Question 2: Any idea how to fix this so file sharing actually works (the way it used to before MS )?
    This is known issue with 1803 and accessing file shares by HostName. As long as you can access the shared PC's by IP (File Explorer> Address Bar > \\192.168.0.100) then it is just a HostName issue ... see below ...

    People have had varying success with the following ... these are in no particular order, but obviously only do on at a time :)
    1. Disable IPv6 - Enable or Disable IPv6 in Windows | Windows 10 Tutorials
    Note: If you prefer NOT to disable IPV6, you can use the Prefer IPv4 over IPv6 - https://support.microsoft.com/en-us/...advanced-users
    2. Rename PC's - Change Computer Name in Windows 10 | Windows 10 Tutorials
    3. Hosts File - Edit Hosts file on both PC's and Map IP to PCNAME.
    192.168.0.100 RAVEN
    192.168.0.102 COYOTE
    4. Map a Network Drive - Since you're using Static IP's, you could just map your shares by IP - Map Network Drive in Windows 10 | Windows 10 Tutorials
      My ComputersSystem Spec

  3.    #3

    Thanks Eagle51!

    It was indeed a HostName issue.

    Disabling IPv6 worked, but I wanted to explore other options.

    I settled with editing C:\Windows\System32\Drivers\etc\hosts. That seemed the least invasive.

    Even with services set to automatic (delayed) it often takes 10-15 minutes for the service to start. During that time, the shares are not visible in File Explorer (unless started manually).

    The best solution I've found is to add the shares to Quick Access. Appears this is essentially the same as mapping a network drive. Even when the services have not started and the machines do not appear in File Explorer Network, the shares are still immediately available.

    Thanks again for the rapid, accurate reply!
      My ComputerSystem Spec

  4.    #4

    Glad you got it sorted out :)

    Even with services set to automatic (delayed) it often takes 10-15 minutes for the service to start. During that time, the shares are not visible in File Explorer (unless started manually).
    I haven't seen it take that long, usually just a couple of minutes. However, for the Function Discovery Provider Host > Properties > Recovery .. I did set it on the 1st and 2nd Failure to Restart the Service after 1 min. That might be why I haven't seen it take that long.

    FYI and AFAIK .. This is just a Windows Defender thing and I'm not sure everyone see's it.
    I've noticed on a reboot, even tho Windows Defender Icon (systray) shows a green check mark, if you immediately open it you may see the Virus & Threat Protection / Firewall & Network Protection saying "Getting Protection Info ...." and until that finishes the PC doesn't show in File Explorer > Network ... I think this could be adding additional time (maybe a couple mins).

    The best solution I've found is to add the shares to Quick Access. Appears this is essentially the same as mapping a network drive. Even when the services have not started and the machines do not appear in File Explorer Network, the shares are still immediately available.
    Yep, pretty much the same :)
      My ComputersSystem Spec


  5. Posts : 713
    Microsoft Windows 10 Pro 64-bit
       #5

    The only other service I can think of is to set "Network Location Awareness" to "Automatic (Delayed Start)" in Services.msc.

    Since you said you are using a public network setting i'm not sure if it will help though.
      My ComputerSystem Spec


 

Related Threads
I have Windows 10 Pro 1703 Build 15063.483. About 2 weeks ago, after restarting my PC, I got 0x80070035 when accessed shared folder. It was fine the day before I restarted my PC. I tried most of things mentioned about 0x80070035, like checking...
hi guys, so I was searching for the past 3 hours for a concrete solution for this... here's the scenario, I have one win10 PC and 2 win 7 PCs over Ethernet, all working decently, until today I noticed that the other win 7 comps cannot see the win...
This is a weird one... Just installed Win 10 1709 on a laptop and everything went fine until I got to the point where I wanted to share drives on the laptop (the data partition - D:) with other machines on my home network. Right-clicked on D:...
Hey everyone. First let me blow some steam by stating that Microsoft Account is a convoluted feature that is very poorly thought out and integrated. /end rant That being said, here is my situation. I fresh installed Windows 10 on my laptop and...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:53.
Find Us