Recently, after the client's win7 joins the win2019server domain, the networks on win7 can see hundreds of computers, but only a dozen computers are left after joining. The group policy has enabled network exploration and the firewall has been turned off for testing. The network configuration files have all been confirmed to be explored, the related services DNS Client, Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host are all confirmed to be enabled, and it is found that it is feasible to use the unc path to type ip, but the name is instead. Ex: \\192.168.0.1 (O), \\ap-server (X) cannot be resolved. However, it is feasible before joining the domain. I don’t know if the predecessors have encountered it. I have checked many forums.
(google translation)