Computers not visible on network

Topic

New Reply

Computers connected to my local network are no longer visible after completing the Windows 10 1809 upgrade on 10/02/2018.  Network discovery is on.  Some of my friends have observed this same issue.   This problem did not exist under the previous release and I haven’t read any reports regarding this problem.

Edit to remove HTML

TJH

Reply | Quote

Replies

We have seen reports of this. Please read the Thread on Win10 1809 bugs on the main blog. There may be a solution for you or links to one.

Your other alternative is to roll back to your previous version and wait for MS to fix the problem(s). You have 10 days to do so from the upgrade.

Installing a new upgrade just out of the gate is a dangerous thing with Win10. MS doesn’t test thoroughly anymore and the people who jump on the new versions are simply Guinea pigs, MS fodder.

Reply | Quote

@thomasharmon Yep hit the same problem here as usual, only this time it went one better try enabling these services in the link listed below then reboot, if not use the netcfg -d Admin CMD works a treat here. Its likely this may be fixed with the next update on “Patch Tuesday” (B) next week, sure that’s going to be a bumper one. If that works and the Services enable doesent then you can use the instructions to create a workaround.
https://www.askwoody.com/forums/topic/win10-version-1809-buglog-including-troubling-tales-of-lost-user-data/#post-221676
Hope that solves it for ya, its a semi regular thing doesent affect Win7 and 8.1’s they see the network participants fine better just to concentrate on a/or the machines that got upgraded first otherwise its a complicated Web of Network Fault finding.
PS I wouldn’t rule this out on any other Brand of networking card either Drivers or Win10 1809 incompatibility.

1 user thanked author for this post.

woody

Reply | Quote

After the update to 1809 I can no longer see any other Windows 10 computers in Network.  I can only see Windows 7 systems.  I have had SMB1 disabled for a while and I’m only using SMB2 and SMB3.  Function Discovery Provider Host and Function Discovery Resource Publication services are running and Network Discovery is enabled on all of the Windows 10 systems.  I tried using Network Reset but that didn’t work.  I can access the other computers by typing the URL in File Explorer and I have saved the links in Quick Access but WS-Discovery is broken after the update.  It was working before at least for Windows systems but WS-Discovery has never worked with Linux’s AVAHI mDNS service.

Re-enabling SMB1 works for Network Discovery of Windows and Linux systems but is less secure.  There’s also the bug that’s been around in Windows 10 since around version 1703.  If a Windows 10 system becomes the master browser for the LAN when using SMB1 it can see the other computers on the LAN but isn’t sharing that info with the other computers.  I have had to disable the master browser function on my Windows 10 systems by opening regedit.exe and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\ to change the value of MaintainServerList from Auto to No and then restart the computer.  I then have to keep a Linux system booted up on the LAN to act as the master browser.

Peer-to-peer networking in Windows 10 is all screwed and the master browser bug has been around for over 18 months so I guess the only solution is to run a dedicated DNS serve on a LAN.

 

seglertx

2 users thanked author for this post.

BobbyB, woody

Reply | Quote

Didn’t this happen way back between win7 and vista? Where at first there was no problem but latter became a problem through an update?

Reply | Quote

thomasharmon wrote:

Computers connected to my local network are no longer visible after completing the Windows 10 1809 upgrade on 10/02/2018. Network discovery is on. Some of my friends have observed this same issue. This problem did not exist under the previous release and I haven’t read any reports regarding this problem. Edit to remove HTML

After installing Windows 10 rereleased 1809 on 11/14/2018, I still can’t see my local computer displayed on the network.  Four calls made to Microsoft tech support did not fix this issue.  I was given a shortcut as a workaround and was told this might be a bug in the new improved version.

 

TJH

Reply | Quote

There are three threads here dealing with the but in 1809 concerning network drives. See if any of these help.

https://www.askwoody.com/forums/topic/patch-lady-1809-and-mapped-drives/

https://www.askwoody.com/forums/topic/patch-tuesday-problems-include-even-more-reported-bugs-with-win10-version-1809/

and

https://www.askwoody.com/forums/topic/patch-lady-a-bit-of-transparancy-for-1809/

Reply | Quote

@thomasharmon I take it you tried this: https://www.askwoody.com/forums/topic/win10-version-1809-buglog-including-troubling-tales-of-lost-user-data/#post-221676 and no joy eh? if you have Group Policy access you can run netcfg -d as a batch file under start up/shutdown scripts otherwise create an elevated shortcut, wouldn’t by any chance have a Realtek PCIe GBE Family Controller in device Manager by any chance?? Best I can figure is there’s a bit of an issue with Win10 1809 and Realtek Drivers but the workaround seems to work with minimal to no impact on performance or system. It went away with the first update anyways for me KB4464330. Strange no other Machines with 1809 and a Realtek NIC seem affected ahh well that’s Win10 I suppose full of odd quirks.

Reply | Quote