1803 disable finding computers by name?


  1. Posts : 16
    Windows 10
       #1

    1803 disable finding computers by name?


    Tried several fixes online, but still same. Can use ip address to find them.
      My Computer

  2. Access Denied's Avatar
    Posts : 10,507
    Win10 x64
       #2

    Hello, see if this will fix your network :)

    There is a service you need to set to Automatic(Delayed Start)

    Function Discovery Resource Publication

    Right click the Start button and click on Run near the bottom of the menu that shows. Type services.msc in the Run box and press enter to open the Services List. Scroll down until you find the Function Discovery Resource Publication.
    Double click it to open the Properties. Change the Startup type to Automatic(Delayed Start). Then click the Start button below. Click Apply then OK. Your PC will now show on the network.
    Last edited by Access Denied; 07 May 2018 at 18:41.
      My Computer

  3. Barman58's Avatar
    Posts : 3,627
    Windows 10 Pro x64 2004 - 19041 - 264 XP/Vista/Win7/Win8.1 in VM for testing
       #3

    Although the Automatic start should work fine, for some reason the official option is stated as Automatic (Delayed Start), which would suggest there is some potential for cross Service interference if started immediately on boot
      My Computers

  4. Access Denied's Avatar
    Posts : 10,507
    Win10 x64
       #4

    Barman58 said:
    Although the Automatic start should work fine, for some reason the official option is stated as Automatic (Delayed Start), which would suggest there is some potential for cross Service interference if started immediately on boot
    I edited to make it right. I typed that up last night to have it on easy copy and paste until they fix this with a CU. :) Thanks Barman
      My Computer

  5. AndreyT's Avatar
    Posts : 406
    Windows 10 Pro
       #5

    The only way I could restore normal access to Windows network shares was to reinstall SMB 1.0 support in Windows features. After update to 1803 it got removed from one of my machines (not from others), and that machine immediately stopped seeing network shares from other machines. (Complaining about being unable to find the other machines by name).

    Meanwhile, name resolution continues to work, i.e. I could remote desktop to other machines by name. Only accessing network shares failed consistently.

    After re-installing SMB 1.0 on the problematic machine everything went back to normal.



    Without SMB 1.0, "Function Discovery Resource Publication" service to Automatic kinda helps one machine to see other machines in "Network". But network share access still does not work: trying to access a machine immediately generates an error stating that it can't resolve the network name.
      My Computer


 

Related Threads
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 22:05.
Find Us




Windows 10 Forums