Windows 10, Version 1809. Network does not show computers

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.

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.

"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. 😉

In other words, a win8.1 administrative login is required before any win10 computer can access that box.

Hope this info is helpful,

Beverly Howard

@BaveHoward,

Unfortunately I don't have any win 8.1  left on my network to verify the case you are describing.

You should open a separate thread and topic for that specific case.

With Windows 10 I don't have any problem accessing another computer even if it is logged in as a standard user without Administrator privileges. 

This thread is dealing with a specific windows 10 problem on publishing the name of the computer on the network due to FDResPub service starting up before the Ethernet adapter is ready, when the problem occurs the Win 10 computer simply does not show up in the network.

Some more info on why my win10 can't see w8.1 computers. I have not had the need recently to access a win8.1 computer from this win10 computer, and, sure enough, could not do so when I needed to today.

Went to the win8.1 computer and it had no problem accessing the win10 computer and, after doing so, went back to the win10 computer and confirmed that it could still not access the win8.1 computer

Stopped the FDResPub service (it was running) and re started it.  Didn't help.

Then;

• went to the win8.1 computer
• restarted it
• logged in as administrator
• then immediately logged out
• then logged in as the non-admin user which is the norm for this computer
• went to the win10 computer
• was able to access the win8.1 computer

It did take a while for win10 file explorer to display the win8.1 icon, and it balked when I first tried to open the share, but eventually it connected and allowed me to access and transfer win8.1 files.

In other words, a win8.1 administrative login is required before any win10 computer can access that box.

Hope this info is helpful,

Beverly Howard