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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-08-05T13:06:13+00:00

    I do coding and run an organization that gives away computers to people in need.  Also, I actually listened to people's complaints about Windows 10, so... I recoded it from the image up.  Every time they put out a new major update, I debug it and use it for installs.  I kind of blended Windows 7 and 10 together.  I got Win 10 Pro 64 to run at about 1% CPU and 0.9 GB at idle on Core 2 Duos.

    I am also an insider, so I get the releases a little early.  Usually I have the bugs worked out before the release date, but this time it took a while.  I got most of the bugs out in 2 weeks... but this network issue took me a while.  I am glad it worked for you.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-05T01:30:33+00:00

    You beauty, that's perfect, although I have no concept of how smb 1.0 could have any bearing on the problem - it works. Automatic without the delay start on the services works fine by the way. How did you ever come up with this solution?!!!! Thank you so many times you will become bored hearing it!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-07-31T16:12:01+00:00

    I had one update this week but it didn't fix the issue. Mine is on 1903. I will check again for more updates.

    In the meantime, I got a tip from another Network Admin about how he got around this.

    He opened the Run command and entered \ComputerName\C$. It takes you directly to the C drive of the named computer. It will then show up in the list under Network in File Explorer where you can right-click it and select Pin to Quick Access. When you close File Explorer it will remove itself from the Network list but remain in the Quick Access menu.

    You can also use the IP address of the machine instead of it's name and you also type it directly into the address bar of File Explorer instead of using the Run command.

    It's not a perfect solution but it works to get around Microsoft's antics.

    Thanks,

    Jessica

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-07-31T15:22:38+00:00

    The one computer that had the 1903 and therefore the network problem just had an update this week.  I updated the computer and then looked at the various permissions and made sure it was checked that all could see all.   It worked!  Now I can see all the computers!  Did the update on the one computer that had the 1903 fix the problem?  Who knows?

    Was this answer helpful?

    0 comments