Windows 10, Version 1809. Network does not show computers

Anonymous
2018-10-19T21:34:40+00:00

In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.

I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.

Any ideas?

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

243 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2020-11-09T00:56:38+00:00

    Running the test batchfile in an elevated CMD prompt on an offending computer to show up in the network then it disappears 20 to 30 minutes later.

    Router has been powered off and recently upgraded. This issue has been ongoing since SMB 1.0 was deprecated due to security issues and as someone else indicated activating Remote Access is also a security issue which had gapping holes that MS patched recently

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-08T23:40:16+00:00

    The only thing that I can think of is to turn the network discovery service off manually then to restart in manually.

    One last effort would be to clear the network map on your router. This will clear up conflicts or mismatched ip addresses and computer names. (For most people, they will have have to reset the router.)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-08T23:29:00+00:00

    Tried that script months ago and does not fix the issue between a 2004 and 20H2 machine. Neither are visible to the other. Have to use \computername. in Windows file explorer to see the shares on either machine.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-08T22:51:38+00:00

    I am not sure what you are referring to regarding disabling the trigger. The script type of command that I put in Task Scheduler turns functional discovery off then back on.

    I have some machines that run 2004 that are happy with this solution.

    Try this with NO modifications.

    Start the offending computer and check for misbehavior. then run the following as a command script or just do so at an ELEVATED prompt.

    @echo off

    cmd /c net stop FDResPub

    cmd /c net start FDResPub

    If the above works then your machine is unhappy with Discovery Function. Some put this script to be run at startup.  The problem is that it must be located in the directory that you specify and not be moved or deleted. To get around that limitation, the following is put into Task Scheduler directly.

    And, this can be achieved without a script file by defining the task as follows in Task Scheduler:

    Name:  FDResPub

    Description:  Restart the FDResPub service.

    Run whether user is logged on or not - Do not store password.

    Configure for:  Windows 10

    Trigger:  At Startup

    Actions:  (here is the magic for no script)

        - Action:  Start a program

        - Program/script:  cmd

        - Add arguments:  /c net stop FDResPub && net start FDResPub

        - Start in:  (leave empty)

    Conditions:  start only if the following network connection is available - Any connection

    Settings:  (leave defaults)

    Hope it works for you like it did for me.

    Was this answer helpful?

    0 comments