Windows 10, Version 1809. Network does not show computers

The problem affects computers that have both the Ethernet and the wi-fi adapter and they are connected to the router via Ethernet.

The Plarini command script works fine for me. I would just like to say, contrary to fg2001's comment, that neither of my two computers have WiFi adapters. They are both connected to the modem by ethernet cable.

Peter

The problem seems to be occurring with specific Ethernet adapter, in my case the 2 computers affected had both Ethernet and Wi-Fi, but I have seen other people reporting the problem on machines with just Ethernet.

The problem affects computers that have both the Ethernet and the wi-fi adapter and they are connected to the router via Ethernet.

The Plarini command script works fine for me. I would just like to say, contrary to fg2001's comment, that neither of my two computers have WiFi adapters. They are both connected to the modem by ethernet cable.

Peter

Works only on first restart.  I use the scrpit to turn function discovery off then on.

Question will be should we keep this bug or after it is fixed deal with new ones.

CSAMD, 

The script to restart Function Discovery Resource Publication is just a workaround, the bug needs to be fixed properly.

It looks to me that the discovery services are initiated before the ethernet adapter is ready and for that reason the discovery fails. I think the Ethernet adapter needs to be ready before starting the discovery services.

Something is out of sync, given that this works fine with windows 10 v1803.

Works only on first restart.  I use the scrpit to turn function discovery off then on.

Question will be should we keep this bug or after it is fixed deal with new ones.

Hi Albertk_77,

There is still a problem that is not fixed in the latest 17763.195.

The problem affects computers that have both the Ethernet and the wi-fi adapter and they are connected to the router via Ethernet.

For those cases the workaround is to restart the service Function Discovery Resource Publication.

There is a workaround procedure to make the restart automatically described in another thread by  

Plarini.

A restart of the FDResPub service gets it working properly. I came up with a workaround to restart the service automatically at system startup. You may have already done this, but others may benefit.

1. Create a command script named FDResPub.cmd with these two lines:

cmd /c net stop FDResPub

cmd /c net start FDResPub

2. Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
3. Use Task Scheduler to create a new task:

Name: FDResPub

Description: Restart the FDResPub service.

Run whether user is logged on or not.

Run with highest privileges.

Configure for: Windows 10

Triggers: At Startup

Actions: Start a program   C:\Scripts\FDResPub.cmd

Optional start at: C:\Scripts

This has worked for both restarts and shutdowns with Fast Start disabled.