Win 10 Pro cannot see new Hyper-V Server 2019, but sees other machines

Michael Faklis 41 Reputation points

My Windows 10 Pro x64 machine can see all machines in my domain except for my new Hyper-V Server 2019 machine. Explorer -> Network lists all of my other domain machines which are powered on, but it doesn't list my new Hyper-V Server 2019 machine, even though it is a member of my domain.
For my visible machines, when I click on the machine name, it lists all of that machine's shares. I can still access the Hyper-V Sever 2019 shares, if I enter them explicitly.
Since Windows 10 Pro can list the other domain machines, I believe the roadblock is in the Hyper-V Server 2019 machine.
What can I do to make this new machine visible?

A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,530 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Dave Patrick 426K Reputation points MVP

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

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


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

  2. Michael Faklis 41 Reputation points

    @Dave Patrick
    I am trying to find a way to update the firewall. Hyper-V Server 2019 doesn't have a GUI.
    The firewall has rules for Network Discovery, both incoming and outgoing. All of them are for "All" profiles. I tend to not open ports for "Private, much less "Public" profiles, so I came up with custom rules for the "Domain" profile. Unfortunately the script I found to import rules from a CSV file, didn't work, so I'm looking for a different method to input these new rules.

    0 comments No comments

  3. Michael Faklis 41 Reputation points


    "Also, check whether the following services are running (they should be in the automatic startup state to correctly display your network environment). Run the services.mcs console and check the services state:

    FdPHost – Function Discovery Provider Host (responsible for other computers discovering on the network);
    FDResPub – Function Discovery Resource Publication (allows other computers to detect your device on the network);
    Dnscache – DNS Client;
    SSDPSrv – SSDP Discovery;
    Upnphost – PnP Device Host."

    Starting these services in Server 2019 with GUI, made that server visible in the Network Explorer.


    FdPHost, FDResPub, SSDPSrv, and Upnphost are not included in Hyper-V Server 2019.

    I haven't verified whether these five services are included in Server Core 2019.

    0 comments No comments