Some network devices do not appear in Windows (file) Explorer after adding a Server 2022 Domain Controller

RPVincent 46 Reputation points
2022-08-09T21:24:41.217+00:00

I am starting to upgrade my network from Server 2008 to Server 2022 and have an issue where many of my network devices are no longer listed under "Network" in Windows Explorer. The issue started after I added one of the 2022 servers as a domain controller. Details...

Current Forest and Domain functional levels are set to 2008. I have two 2008 DCs that are global catalogs and DNS servers.

I have two new Dell Poweredge R350 servers running Server 2022 Standard and created a Server 2022 VM to be used as a DC & DNS server. 2022 VM has been promoted to DC and listed in the Domain Controllers OU and as a GC and DNS server. AD has replicated and the 2022 VM shows all AD users, groups and computers as the 2008 DCs.

In Windows Explorer on the Server 2022 DC VM, all network devices are listed. However, on my Windows 10 pro desktop, 75% of the network devices are no longer listed. The 2008 DCs also no longer list all network devices in Windows Explorer. There's not pattern to the devices that are listed as they reside in different OUs in AD. Of the listed devices, some are 2008 servers, some are Windows 7 VMs and a couple of Synology NAS devices.

For troubleshooting purposes, I demoted the Server 2022 VM and removed the DNS role and my desktop was able to list all network devices again.

I have once again added the DNS role to the 2022 VM and promoted to DC serving as a global catalog and DNS server. I have manually updated the NIC settings on my desktop to use the 2022 VM as the preferred DNS and one of the 2008 DCs as the secondary DNS, but cannot see all network devices. I can still access the unlisted devices by typing the machine name into the Location bar in Windows Explorer.

The other odd thing is that on the Server 2022 VM, the network discovery setting will not stay turned on. I set it to ON and save the changes, but it reverts back to the OFF setting. Could this be the source of the problem? Network discovery is enabled on all other devices and Windows Defender Firewall is turned off on all devices.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,113 questions
0 comments
Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2022-08-09T21:41:00.39+00:00

    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).

    229695-image.png

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

    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. RPVincent 46 Reputation points
    2022-08-09T22:12:01.407+00:00

    Thanks for the quick response, DSPatrick.

    For the services: DNS Client, Function Discovery Resource Publication, SSDP Discovery UPnP Device Host, is the "running" state necessary for proper network discovery operation in Server 2019/2022? I ask because the native state of those services are sufficient if I remove the Server 2022 VM as a DC and just have the 2008 DCs running. Also, Windows Firewall is not enabled on the domain and will not interfere with network discovery.

  2. RPVincent 46 Reputation points
    2022-08-10T15:39:34.02+00:00

    Nothing new to add yet. I will need to do some testing with settings changes. To clarify, I did not say that Windows Firewall "needed" to be disabled, just that it is disabled and would not interfere with network discovery. I use a different firewall on our domain. I will update again after I have done some testing.

  3. RPVincent 46 Reputation points
    2022-08-11T00:11:41.497+00:00

    After doing some testing, I have found that the issue lies with the Function Discovery Resource Publication service not running. The SSDP Discovery and UPnP Device Host services are not necessary on my network and the firewall was not the issue either. Thank you for helping me resolve this.

  4. Justin Kantor 0 Reputation points
    2023-04-01T01:16:29.04+00:00

    Exact same scenario here.

    Windows firewall disabled and both new 2019 dc’s have the following enabled:

    • DNS Client
    • DNS Server
    • Function Discovery Provider Host
    • Function Discovery Resource Publication
    • SSDP Discovery
    • UPnP Device Host

    all domain attached workstations have the following enabled:

    • DNS Client
    • Function Discovery Provider Host
    • Function Discovery Resource Publication
    • SSDP Discovery
    • UPnP Device Host

    still same problem as the OP; not resolved for me.

    please help.

    thank you,

    justin

    0 comments