Local network problems with 1903

Anonymous
2019-06-07T22:47:03+00:00

I have updated 3 of my 4 computers to 1903, now none of them can see each other in the explorer network section, but each of them can see the NAS drive on the network. I have checked the network sharing settings and they are all set as make this computer discoverable. Oddly the JRiver media centre servers show up in windows explorer, but the computers which they are on do not appear. Any suggestions?

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
Answer accepted by question author
Anonymous
2019-08-04T23:25:44+00:00

I think I may have finally resolved the issue.  Took some time, but finally have positive results... Let's see if this works for y'all.

First:  Make sure you have the correct services running.  Right click the start menu, click run and type in "services.msc"  Make sure all of the following services are set on automatic (delay start).  Note, if your system is fast enough, you may not have to put it on delay start.  I only did that not to bog down the boot time.

     DHCP Client

     Function Discovery Provider Host

     Function Discovery Resource Publication

     SSDP Discovery

     UPnP Device Host

Second: Make sure you have the correct Windows components running.  Open settings, click on Apps, and then in the upper right hand corner, you will find Programs and Features.  Now, on the upper left hand side of this new window, you will see Turn Windows Features On or Off, click that.  Make sure SMB 1.0/CIFS File Sharing Support and SMB Direct are both fully checked (not the black box, but a check mark.)  I also have Work Folders Client checked, but not sure if that will affect it.

Third:  Make sure you have Enable Remote Desktop enabled... even if you do not plan on accessing your computer remotely.  Always remember, if you don't have a password on your account, you can't access the computer remotely anyway.  This is found under Settings, then System, and finally the last choice on the bottom left.

Fourth and Final Step:  Make sure you are on a private network.  Click on the network icon on the toolbar, and select Network and Internet Settings.  If under your connection device, it says public, click on either the Ethernet or WiFi link, and change it to Private.

Now, reboot the computer, and see if this works. 

I have been trying to find a solution to this since May.  Please let me know if this helps.  If not, I will keep trying.  Someone has to work the bugs out.

Was this answer helpful?

30+ people found this answer helpful.
0 comments

111 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-08-19T15:06:35+00:00

    Did exactly that.. and if I used the computer name (RC-SURFACE3) as the network location, it would stall and finally give an error.  (I've long left mapping drives and use this method wherever possible.)  If I used the same methodology and used the IP address instead, it worked, i.e. the network shortcut was now available.  The list of network computers still included a NON-WORKING RC-SURFACE3 entry.  But explorer now contains a shortcut to my shared resources referenced by the IP address. The same holds true for mapping network drives. I simply can never reference the machine by its name.  This sounds like a DNS problem which I will be looking further into.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-19T14:36:23+00:00

    I discovered the same problem yesterday and tried most of what has been suggested here.  No luck.  And I have all Surface equipment.  A Surface Pro 3, Surface Pro 4, and a Surface Book 2.  The Surface Pro 3 is on 1903. All of the others are on 1809.  The Surface Pro 3 can be 'seen' by the other machines.  But the shares contained on that machine are not working. Toggling the Function Discovery Resource Publication (Triggered) does not seem to work for me.  I do have remote desktop enabled and SMB1 is turned off. When looking at the network resources on the Surface Pro 3 FROM the Surface Pro 3, they ARE visible. Any additional comments??

    If you right click/tap on 'This PC' then click/tap on 'Add Network Location' you can set up the link from there. I found that when I did that the location then appeared under 'Network' for some bizarre reason.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-19T14:06:45+00:00

    Just discovered a work around.  The name of the 1903 machine is RC-SURFACE3.  This appears in the list of network resources. But as I said, when clicking on it I get a long delay followed by an error message. So all of the shares are not reachable by any means (i.e. Explorer or NET USE).  But, If I replace the name of the machine with the IP address (\192.168.xx.xx) then it all appears to work. I did not mention that the Surface Pro 3 has its IP statically assigned for port forwarding reasons. Not sure whether this is of any help to anyone but worth a try.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-19T13:45:56+00:00

    A new update.  The Surface Pro 3 just received a cumulative 1903 update.  Hopes were high.  But no change in the behavior.  Toggled the FDRP.. still no shares visible or reachable.  Tried using the NET USE command with no luck. The machine (Surface Pro 3) appears on my list of network computers (from the Surface Book 2) but NO shares under that machine. I write software for a living and I need to get to the bottom of this. Any help would be greatly appreciated.  Very frustrating.

    Was this answer helpful?

    0 comments