Network discovery problem

I have 4 computers all connected to a switch via ethernet cable. The switch is ethernet connected to the router/modem and all IP address are reserved/administered in the router by the individual MAC address of each computer.

All computers are win 10 pro, either ver 1803 or 1809.

I am having a problem with a computer not being able to see itself on the network, the other computers cant see it as well, the problem computer can see the other computers fine.


I have turned on network discovery, file discovery etc, etc.


What I have been able to do is...
I have entered services.msc and if I turn off and then turn back on the function discovery (FD) provider host and FD resource publication then the computer can see itself and the others can see the problem computer as well, ie the problem is solved.

But when I restart the computer I am back to the original problem and need to manually turn off/on the FD services. The FD services are set to automatic start, I have also tried delayed automatic start as well.

All this started when I changed a Microsoft win 10 login from an outlook account to a local user account on the computer.

On another computer I changed the outlook login user account to a local account and the same problem has arisen on that computer as well.


All the computers are logged in with an administrator account status.

Is there a fix to stop then restart Function Discovery services or is there a script I can run that does this.

Thanks for the reply,

I have smb v1 turned on, etc.

I had another play with this problem, I did a new win 10 install for 1 computer and that is working fine now but for the other computer which I don’t want to perform a complete reinstall on I have set the start up logon on to requiring a password (previously I had turned it off via Cmd, netplwiz) this seems to be working for now, I can’t explain why it’s working this way,