Windows Server 2016 - Problem with network discovery

Jonathan Weidner 96 Reputation points
2021-04-06T10:02:53.107+00:00

Hi guys!

I hope you can help me. A customer needs to see the other domain servers in network area of the Windows Explorer for some Siemens legacy software. Following some other articles that should be very easy, but I'm experiencing a problem: The servers in the domain can't see each other, at least in the network area of the explorer, they can only see them self. Except for one of the 5 servers, which can see the other 4 members. I compared the settings a couple times and the only visible difference was the already activated SMBv1 feature, but even after reactivating that old stuff on 2 other domain members doesn't made it somehow better.

We are talking about 5 Windows Server 2016 VMs, which are in the same subnet and can access each other without problems.

What I've done so far:

  • Ensured, that DNS, Function Discovery (both services), SSDP and UPnP services are running
  • also read something about WinRM - it's active too
  • Re-enabled SMBv1 and made sure, that Computer Browser is running (shouldn't be necessary, but it doesn't works anyway)
  • activated network discovery in network and sharing center
  • also set "Turn on Mapper I/O (LLTDIO) driver" and "Turn on Responder (RSPNDR) driver" to enabled for domain via GPO
  • triplechecked, that Windows Firewall is turned off
  • reset network settings on one server via "netsh int ip reset" and "netsh winsock reset"
  • several server restarts

I really don't know what's the problem, I hope somebody can help!

Best Regards
Jonathan

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,465 questions
0 comments No comments
{count} votes

Accepted answer
  1. Jonathan Weidner 96 Reputation points
    2021-05-07T12:03:01.647+00:00

    We were finally able to solve the problem! The source of our problem was a bug in our firewall appliance. The necessary igmp querier for Multicast (WS Discovery) didn't work properly. After an update package from the manufacterer, we were able to use the network discovery feature like intended.

    Thank you all for your time!

    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Candy Luo 12,701 Reputation points Microsoft Vendor
    2021-04-07T02:41:53.503+00:00

    Hi ,

    Function Discovery Resource Publication and Function Discovery Provider Host relates to the "Network Discovery". Please refer to the following steps:

    1.Please set Function Discovery Resource Publication and Function Discovery Provider Host service to Automatic (Delayed Start). As picture below:

    85105-image.png

    2.Reboot Computer and then check that Function Discovery Provider Host and Function Discovery Resource Publication are running and set to Automatic (Delayed Start).

    3.If you have multiple server 2016then these steps need to be taken on each of them.

    4.Check if windows server 2016 can see all other domain servers. Additionally you might be prompted by Windows about enabling network discovery and you should accept this prompt.

    Hope this can help you.

    Best Regards,
    Candy


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

  2. Anonymous
    2021-04-06T14:38:40.14+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\problemmember.txt

    then put unzipped text files up on [OneDrive][1] and share a link.


  3. Anonymous
    2021-04-07T13:59:32.84+00:00

    Regarding your answer I want to say, that both DCs are in a different subnet as that 5 member servers, but the connection is unlocked in the firewall between the both subnets.

    all looked good, some errors in event logs that may be worth investigating, I did not bother to translate them as the source and IDs are not present here.

    For the newer OS's enabling network discovery may help.

    Check these services are started on all members involved DNS Client, Function Discovery Resource Publication, SSDP Discovery UPnP Device Host, TCP/IP NetBIOS Helper and also check that any firewalls allow Network Discovery for the network profile you're using (in my example below using domain).

    85340-image.png

    --please don't forget to Accept as answer if the reply is helpful--


  4. Anonymous
    2021-04-07T14:27:55.697+00:00

    Should work out of the box. You can also start a case here with product support.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.