Windows 10, Version 1809. Network does not show computers

"The problem is if your network is already Private the trigger is not activated and FDResPub is not started."

As I said in my reply on page 20 I have for PC's (with nine installed Windows) and all of those network is set to Private and FDResPub (Manual, Triggered) start running when PC is started. Only some of those have that networking issue while others are working without issues.

On Asus desktop this issue is only with onboard ethernet adapter, when separate NIC card has no issues.

As already said in this thread, removing trigger and setting FDResPub to automatic is one workaround, but main thing is that those default settings are working with some PC's / network adapters, but not on all.

@Pauli O,

Just F.Y.I.

With build 21318, cannot reproduce this bug on any machines regardless of the type of Ethernet adapter used.

This again shows that the problem has been going on and off with different builds.

It could be just a coincidence of different timing, I don't think they fixed this intentionally.

We'll see how long it lasts with next windows Builds. 😉

Yes, it's seem to be working without any workarounds. I test this with two installed 21318 (Pro and Enterprise) on my ASUS desktop which had this issue and all other computer see it as soon as it was up and running.

Let's that hope what ever they did isn't just by accident and this continue on future builds and goes also to all 1904x versions with some CU.

I don't lnow if it is significant but the invisible machine is wired, other machines are on WiFi.

I think it is. I have two machines. PC1 on WIFI (has ethernet, but haven't used it in a while) always shows up on Network Explorer.

PC2, laptop, connects Ethernet or WIFI depending whether at desk or about. PC2 didn't show on Network unless I restarted Function Discovery Resource Publication, was about to schedule that reset, but read your comment. Tested by connecting PC2 through WIFI, rebooted both and the PC2 did show up on Network.

Have to look into it, but I think Discovery Services uses Computer Name, Workgroup and Network Location to match network buddies. Connecting WIFI vs Ethernet gives my connection a different Network Location Name. I have Network and Network 2. Can't remember if that was a Windows decision or it asked me, but I always found it strange that connecting to same router with different network names depending on WIFI or ETH would cause problems someday.

Now, on Network browsing, PC1 shows both machines on Network Location "Network 2". PC2 shows both on Network Location "Network"...different names, though both on WIFI. Each machine, separately identifies same Access Point as "Network". So, I don't know if Network Location is just a label for each windows installation and not the actual Access Point name.

Anyway, workaround is restarting FDRP service if PC2 on ETH, or switching it to WIFI. I feel network browsing should work independently of connection by WIFI or ETH, so I'll keep looking.

"Anyway, workaround is restarting FDRP service if PC2 on ETH, or switching it to WIFI."

Another workaround mentioned by fg2001 in this thread is to Enable remote desktop connections.

@IvanTorres,

Hi Ivan,

Depending on the router you could have 2 different network names for Ethernet and Wi-Fi 2.4Ghz and a different name for Wi-Fi 5Ghz.

That is not the cause of the problem you are having with ethernet.

This is a bug that has been going on an off for quite a long time with different versions of windows and needs to be properly fixed by Microsoft.

In the mean time there are a couple of different workarounds described in this thread.

What version and Build of windows is on your 2 machines ?

What is Brand and type of router you are using ?

Perhaps your laptop is connecting to Wi-Fi 5Ghz while the Desktop connects to Wi-Fi 2.4 and that could explain the 2 different network names.