Folder/Drive sharing fubarred after 1803 upgrade...

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #11

    x509 said:
    NO NO NO NO (Yes, I'm shouting.)

    Over a year ago now, MS issued a security alert telling everyone to turn off this service, in response to a malware attack type. Microsoft Security Bulletin MS17-010 - Critical | Microsoft Docs


    You do NOT need SMB1 for drive and folder sharing in Windows, when it uses SMB3.xx. If you are having issues with sharing to/from an old Linux, some embedded device or really old Windows device, then it's a different story.

    In all other cases don't install SMB1 unless you absolutely must enable it.
      My Computers


  2. Posts : 4,201
    Windows 10 Pro x64 Latest RP
       #12

    The way I understand it the MSB was an emergency, temporary , Warning whilst things were checked . There was not much that needed to be changed on Windows 10 to harden against the potential threat, (unlike XP and to some extent Win7).

    There was an update, (I think it may be KB4012606), that corrected the slight issue in 10 a few days after the MSB, plus all the major Antimalware systems included protection against the potential option within hours of it's discovery.

    One place where Windows does have an issue with Workgroup networking is that it is still relient of the old NT Computer Browser, which it turn relies on SMB1, If the services noted above are not active.
      My Computers


  3. Posts : 11,247
    Windows / Linux : Arch Linux
       #13

    x509 said:
    NO NO NO NO (Yes, I'm shouting.)

    Over a year ago now, MS issued a security alert telling everyone to turn off this service, in response to a malware attack type. Microsoft Security Bulletin MS17-010 - Critical | Microsoft Docs


    Hi there

    Ms can scream all they like but if you are sharing with some NAS and Linux type systems - or even some older smart TV's / Amazon / Hulu type TV boxes you still need SMB1 support.

    Newer Linux distros / kernels can support SMB3 / CIFS protocols.

    I've often found after using a load of computers, booting up etc one or other just can't see another one for some stupid reason.

    I just simply reset the entire kybosh (reset router, extender, phones, TV's etc and reboot all machines -- this usually fixes it) -- not a scientific explanation but just use what works.

    I still regard Windows Networking as barely beyond the "Black Magic" stage and certainly a part of "the Black arts" to make it work properly-- you just have to take pot luck if it all works as when something doesn't all the great suggestions on the forums just don't seem to work for me.

    I reckon even Gandalf the wizard couldn't get some computers to network properly with Windows (any release). !!

    Strange thing is Linux / NAS etc work every time !!!

    Cheers
    jimbo
      My Computer


  4. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #14

    jimbo45 said:

    I reckon even Gandalf the wizard couldn't get some computers to network properly with Windows (any release). !!

    Strange thing is Linux / NAS etc work every time !!!

    Cheers
    jimbo
    Hahhah! You are so right about this! Why does it have to be so darn hard sometimes on Windows?
      My Computers


  5. Posts : 4,201
    Windows 10 Pro x64 Latest RP
       #15

    Of course fact that Gandalf the Wizard is a totally fictional character, and does not exist, would lower the chances for success to zero anyway
      My Computers


  6. Posts : 1
    Windows 10
       #16

    Access Denied said:
    You need to set two services to automatic (delayed start):

    Function Discovery Provider Host
    Function Discovery Resource Publication

    Right click Start, click on Run towards the bottom. type services.msc in the Run box and press enter to open the Services List. Scroll down until you find those two. Set them to automatic (delayed start). Then right click and start them both. That PC will now show up. Do this on each of your PC. Then your network will display as you like.

    Hope this helps. :)
    THANK YOU!!!

    I had heard about homegroup being ousted, so I quit the homegroup on all computers.

    I then set up sharing through the standard network.

    One of two computers received the 1803 update. It stopped sharing.

    The "Function Discovery Resource Publication" service was stopped. I set them both to auto/delayed as you recommended.
      My Computer


  7. Posts : 10,929
    Win10 x64
       #17

    TXJax said:
    THANK YOU!!!

    I had heard about homegroup being ousted, so I quit the homegroup on all computers.

    I then set up sharing through the standard network.

    One of two computers received the 1803 update. It stopped sharing.

    The "Function Discovery Resource Publication" service was stopped. I set them both to auto/delayed as you recommended.
    You're welcome. Glad it is working for you now. :)
      My Computer


  8. Posts : 1
    Windows 10
       #18

    Access Denied said:
    You need to set two services to automatic (delayed start):

    Function Discovery Provider Host
    Function Discovery Resource Publication

    Right click Start, click on Run towards the bottom. type services.msc in the Run box and press enter to open the Services List. Scroll down until you find those two. Set them to automatic (delayed start). Then right click and start them both. That PC will now show up. Do this on each of your PC. Then your network will display as you like.

    Hope this helps. :)
    Thought that I was doing so well, having a functioning network on my Media Server and Main PC, under Windows as well....!!

    Then 1803 came along and for hours I could no longer get them to see each other via the Network file manager.
    Mapping works fine, until the server sleeps and then when awake the Main PC will no longer see the dribes mapped until the Server is rebooted....!

    With the above "fix" it is all back to normal, many thanks.

    Goodness knows why MS has changed this behaviour - but then left me wondering what the heck has changed to get it to work as it had done previously...!
      My Computer


  9. Posts : 1,020
    Windows 10 Pro 20H2 19042.572
       #19

    Network Guys - I don't to hijack the OP's thread, but All three of my systems (1 pro, 2 Home) all at 1803 and all have "Function Discovery Resource Publication", in manual mode and none of the systems have any problem with network discovery. But they all have SMBv1 selected in Windows features ? Is everybody stating that if I un-check SMBv1, start "Function Discovery Resource Publication", then everything will work as it does today ?

    Inquiring Minds would like to know.
      My Computers


  10. Posts : 10,929
    Win10 x64
       #20

    storageman said:
    Network Guys - I don't to hijack the OP's thread, but All three of my systems (1 pro, 2 Home) all at 1803 and all have "Function Discovery Resource Publication", in manual mode and none of the systems have any problem with network discovery. But they all have SMBv1 selected in Windows features ? Is everybody stating that if I un-check SMBv1, start "Function Discovery Resource Publication", then everything will work as it does today ?

    Inquiring Minds would like to know.
    Yes. If turning SMBv1 off, you will need the service on auto delayed start for it to work. With SMBv1 on, it will work just fine on manual.

    I actually have SMBv1 turned on for one of my PC. If I stop the FDRP service, it disappears from the other PC's Network browsing. I think SMBv1 actually makes the service run where as it does not run properly when you turn off SMBv1.
      My Computer


 

  Related Discussions
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 14:00.
Find Us




Windows 10 Forums