Local network problems with 1903

Anonymous

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?

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

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.

0 comments

111 additional answers

Anonymous

2019-10-29T21:27:49+00:00

OK. Thanks for that confirmation. It was on page 2 of that other thread, then,...

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-version-1809-network-does-not-show/d5241167-97e6-4b6d-a7e6-96238f876d27?page=2

Windows 10, Version 1809. Network does not show computers

...that I proved my computer is not afflicted. All I have to do is switch to Privateat "START, Settings, Network & Internet, Change connection properties", & suddenly PCRsComputer will show up where you say. And that's whether I am on Wi-Fi or Ethernet. So I've got an immunity to the problem - but don't come running for blood samples. Your stop/start of FedResPub should cure everyone else just fine.

Good work on your part & plarini, Pauli O & galileo1564.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2019-10-29T21:02:22+00:00

But I do believe I don't have the problem subject of this thread anyway, judging by the limited testing I could do owing to I'm not on a Network (or not on one with more than just this one computer a member).

PCR,

Win 10 Home edition does not support Remote Desktop.

Anyway, even with a single computer connected to the router you should be able to see if your PC shows in the Network and file explorer.

If you see your own machine, you don't have the bug that I have, if you cannot see your own PC it would not be visible to other machines in the network either.
Was this answer helpful?

0 comments No comments
Anonymous

2019-10-29T20:06:10+00:00

Can it be just me, or will everyone with Home Edition see...?...

But I do believe I don't have the problem subject of this thread anyway, judging by the limited testing I could do owing to I'm not on a Network (or not on one with more than just this one computer a member).
Was this answer helpful?

0 comments No comments
Anonymous

2019-10-29T07:20:12+00:00

Hi CharitableComputing,

I had the problem where my PC would not show on the network after a computer restart since I moved to windows 10 1809 and then 1903 and also insider builds 20H1.

Up to now I used a workaround in task scheduler to stop and restart FDResPub at startup as suggested in other threads, that always worked fine for the failing machines.

In my case the failing machines were 3 out of 5 and they are connected via ethernet, I did not see this happening in the same machines when I used the Wi-Fi connection.

Anyway, searching today I saw your entry, at the third point, you had something I didn't try before so I decided to see if it made any difference, with my surprise it actually did seem to fix the problem in my machines.

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.

Without changing any other settings I disabled the workaround I had in Task Scheduler and just Enabled Remote Desktop.

That appears to fix the problems on Win 10 1903 and also 20H1 (I don't use 1809 anymore so I cannot give you the results for 1809)

This is interesting even if I don't understand why Enabling Remote Desktop changed the behavior.

Any comments ?

Thanks. FG
Was this answer helpful?

0 comments No comments