How To Find My Network Places In Windows 7

I have received several emails from readers asking for help in resolving the problem of displaying computers in a network environs on the latest Windows 10 and xi builds. Indeed, there are device network discovery issues in the latest releases of Windows x: you tin can't see other computers on a network, or your Windows 10 is not showing up in the Workgroup environment. Let's see how to gear up the Network Discovery issue in the latest Windows 10 builds (upwardly to 21H2).

Contents:

• Windows Tin can't See Other Computers on a Network
• How to Enable Network Discovery on Windows ten and 11?
• Computer Browser Service and SMB 1.0 Protocol in Windows 10/11
• Cannot See Shared Folders from a Windows Device

Windows Tin can't See Other Computers on a Network

Users are experiencing issues with displaying neighboring computers on the workgroup LAN starting from Windows 10 1703. After installing this (or a newer version of Windows 10), your computer may terminate seeing neighboring computers on the network. An error occurs when you lot try to view the device listing in the network by clicking the Network icon in File Explorer:

Network discovery is turned off. Network computers and devices are non visible. Please turn on network discovery in Network and Sharing Center.

When trying to bear witness a list of computers in the network environment with the cyberspace view command, an error appears:

System fault 6118 has occurred. The list of servers for this workgroup is not currently available.

Check the following settings to bear witness the network devices on your Windows network:

Go to Control Console -> Network and Sharing Eye -> Change advanced sharing settings (you can run the control: control.exe /proper name Microsoft.NetworkAndSharingCenter /page Advanced).

Make certain that the following options are checked in the Private network profile section:

• Plough on network discovery + Plough on automated setup of network connected devices;
• Turn on file and printer sharing;
• Allow Windows to manage homegroup connections (recommended).

Then enable the following options in the All networks department:

• Turn on Public Folder sharing so anyone with network access can read and write files in the Public folders (optional);
• Plough off password protected sharing (if you trust all the devices in your network);

  Thus, yous tin can open anonymous network admission to your computer. And so, when you enable this option, you must correctly set the permissions on the shared network folders and printers.

• If there are legacy network devices in your network (old Windows version, Samba shares, NAS devices), enable the choice "Enable file sharing for devices that use twoscore-bit or 56-flake encryption".

Then go to Settings -> Network and Cyberspace -> Ethernet (or select Wi-Fi, if you are connected to a local network through a wireless connectedness). Click the network icon and verify that the Make this PC discoverable option is enabled.

Flush the DNS cache on the computer:

ipconfig /flushdns

To enable the Network Discovery traffic in Windows Defender Firewall, you must run the following command in the elevated command prompt:

netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes

Or yous can enable the network discovery traffic in Windows Firewall with the PowerShell :

Become-NetFirewallRule -DisplayGroup "Network Discovery" -Enabled True -Activity Allow -Management Entering

As well, yous can manually enable the Network Discovery protocol for at to the lowest degree the Individual network in the Windows Defender Firewall settings (Command Console\All Control Panel Items\Windows Defender Firewall\Allowed apps).

In some cases, Windows computers may not be displayed in the network environment due to incorrect workgroup settings. Endeavor to rejoin this computer in the workgroup. Go to the Command Panel -> System and Security -> Arrangement -> Change Settings -> Network ID.

In the Join Domain or Workgroup Magician that opens, select: This computer is function of a business organisation network -> My company uses a network without a domain -> enter your workgroup proper name. After that, you lot need to restart the figurer.

Make sure that the same workgroup name is ready for all devices on the local network. You can employ PowerShell to detect out if your computer is in a workgroup and display its name:

(Get-WmiObject -Class Win32_ComputerSystem).PartOfDomain
(Get-WmiObject Win32_ComputerSystem).domain

In this example, the computer is joined to the WKGP workgroup. To alter the figurer's workgroup name to WORKGROUP:

(Go-WmiObject Win32_ComputerSystem).JoinDomainOrWorkgroup("WORKGROUP")

Restart your computer:

Restart-Calculator

If after rebooting the computer appeared in a network environment, but you can't access it, check the network profile type (location) on your reckoner. Most likely your local network was recognized as Public. You need to change the network location to Individual. To practice this, open the Settings -> Network and Net -> Status -> select your network connectedness (Ethernet ii in my case) and click Properties. Bank check that the Network Profile is set to Private (if it's fix to Public, change the network type to Private).

Restart your reckoner, open the Network and bank check if nearby Windows computers are displayed.

If these tips did not help, and the computers in the workgroup are still not displayed, try to reset the network settings (Settings -> Network and Net -> Condition -> Network Reset).

Y'all can also reset the network settings and Windows Defender firewall rules with the commands:

netsh int ip reset reset.txt
netsh winsock reset
netsh advfirewall reset

Then yous need to reboot the computer.

 In some cases, yous need to completely remove your network adapter using the Device Manager (run the devmgmt.msc console -> aggrandize Network Adapters -> select your NIC -> Uninstall device). Check if there are any hidden network adapters in the list (View -> Bear witness hidden device).

And then restart your computer. Windows should automatically detect your network adapter and install the appropriate drivers. In this case, all old protocol settings for the network adapter will exist reset.

Also, cheque whether the following services are running (they should be in the automatic startup state to correctly display your network surroundings). Run the services.mcs console and cheque the services state:

• FdPHost – Function Discovery Provider Host (responsible for discovering other computers on the network);
• FDResPub – Function Discovery Resource Publication (allows other computers to discover your device on the network);
• Dnscache – DNS Client;
• SSDPSrv – SSDP Discovery;
• Upnphost – PnP Device Host.

In some cases, third-party antiviruses, firewalls, or VPN clients tin block NetBIOS proper name resolution requests, WDS, and circulate DNS queries (at that place was definitely a problem with ESET NOD32). Try to temporarily disable your antivirus/firewall/VPN and check if the network discovery works properly on your Windows device.

For instance, in the NordVPN customer, yous need to disable the "Invisibility on LAN" selection. Bank check if there are similar options in your installed programs.

How to Enable Network Discovery on Windows ten and xi?

Starting with Windows ten 1803 (Leap Creators Update), Microsoft developers removed the ability to create a HomeGroup. In addition, other Windows 10 and Windows 11 computers are no longer displayed in the network environment of File Explorer when viewing network devices.

From Microsoft's point of view, a HomeGroup is a legacy way to create a local surface area network to share folders and printers. Instead of using a WorkGroup, Microsoft suggests using its deject services (OneDrive or admission through Microsoft Accounts).

In order to access the shared resources on another computer over the local network from a Windows 10 device, you lot need to know its hostname (\\pcname1) or IP address (\\192.168.1.xc), just neighboring computers in the network are not displayed. However, this can be fixed.

You can create desktop shortcuts to neighboring computers past specifying the UNC path to them (by figurer proper name or IP accost).

The thing is that a separate Part Discovery Provider Host service is responsible for discovering neighboring computers on a Windows 10 network. Another service, Function Discovery Resources Publication, is responsible for discovering your computer.

The FdPHost service uses the Simple Services Discovery Protocol (SSDP) and Web Services Discovery (WS-Discovery) protocols to discover devices on the network.

These protocols replace the NetBIOS over TCP/IP, which has historically been used to discover devices on Microsoft Windows networks with Principal Browser. Appropriately, you can safely disable the NetBIOS protocol for your network adapters.

Afterward installing the latest Windows x builds, these services tin be disabled (the startup type changed from Automatic to Disabled). If these services are stopped, the computer is not discovered on the network by other computers and cannot see others. You can enable the network discovery services in Windows ten as follows.

1. Open up the Windows Services Management panel (services.msc);
2. Alter the service startup type from Manual to Automatic (Delayed Start)
3. In the list of services, find the Function Discovery Resources Publication service;
4. In the same style, enable the Function Discovery Provider Host service;

   Yous tin can set these services to starting time automatically with the following one-line PowerShell: go-Service fdPHost,FDResPub|Set-Service  -startuptype automatic -passthru|Commencement-Service

5. Restart your reckoner

After rebooting, other computers on the local network volition be able to discover this computer and its resources (shared network printers and folders).

Figurer Browser Service and SMB i.0 Protocol in Windows 10/11

It happens that problems with displaying computers in a network environment are related to the Computer Browser service. This service is responsible for generating and maintaining a list of active computers on the local network. There can be simply one active computer with the Chief Browser role on a local network.

You can place the current Master Browser host in your network past running the following command on each computer in your network:

nbtstat -a ComputerName

The computer that is the Master Browser is the merely one that has the value __MSBROWSE__.

On Windows 10 1703, the Computer Browser service works incorrectly. Information technology is recommended to completely disable this service on Windows 10 and employ the calculator with Windows 8.i/Windows Server 2012 R2 equally the Master Browser on your network. You tin can set the Main Browser computer via the registry.

To disable the Computer Browser become to the registry primal HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters and change the value of the MaintainServerList parameter to No. To strength set which computer is the network Principal Browser, change the value of MaintainServerList to Yes.

In addition, in Windows ten 1709 and newer (1803 upward to 21H2), the Computer Browser service and the SMB v1.0 protocol are disabled by default. The Computer Browser service is responsible for building a list of computers on the network and displaying them (this discovery protocol is widely used earlier switching to the SSDP and WS-Discovery protocols).

You can cheque the status of the SMBv1 protocol on your computer using the command:

Dism /online /Become-Features /format:table | find "SMB1Protocol"

If you have simply computers running Win ten 1709 and newer in your local network (see the table of SMB versions), and yous still want to utilize the Reckoner Browser, yous will accept to enable the SMB v1.0 protocol on at to the lowest degree one figurer (it's not safe!). This estimator will be used as the Master Browser on your network.

Yous can enable the SMB ane.0 back up past enabling the following Windows features from the Control Panel (OptionalFeatures.exe):

• SMB 1.0 /CIFS Client;
• SMB one.0 /CIFS Server.

Or yous can enable SMB 1.0 features with the DISM commands:

Dism /online /Enable-Characteristic /FeatureName:"SMB1Protocol-Customer"
Dism /online /Enable-Feature /FeatureName:"SMB1Protocol-Server"

Nosotros remind you that information technology is not recommended to enable the client or, moreover, the SMB1 server in Windows. The SMB 1.0 protocol is not secure and a lot of SMB1 vulnerabilities can be easily exploited remotely.

If yous enabled the SMB1 protocol, then in order to set the electric current computer as the Master Browser on the network, run the following commands:

reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Browser\Parameters" /v IsDomainMaster /t REG_SZ  /d True /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v MaintainServerList /t REG_SZ  /d Yes /f

This computer volition be the Master Browser in your network.

Cannot Meet Shared Folders from a Windows Device

In some cases, Windows 10 tin run across and explore a neighboring device in a workgroup environment, but cannot display a listing of shared network folders on it. This is well-nigh often accompanied by the error "0x80070035 – Network path not found". The solution to this trouble is described in this commodity.

If a neighboring estimator (device) is visible on the network, but when you lot attempt to open any shared network folder from the Network Neighborhood or by the UNC path (\\Hostname_or_IP), an error appears "Y'all tin can't admission this shared folder because your system'south security policies block unauthenticated guest access". In this instance, you demand to enable the AllowInsecureGuestAuth registry parameter using the command (for details, see the article Tin can't Admission Shared Folder on Windows 10):

reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /

If all else fails and the computers are even so not visible in the local network environment:

• Plough off all computers and restart your router or Wi-Fi admission point;
• If your LAN is based on a Wi-Fi router, check if the client isolation feature is disabled on it(wireless isolation, client isolation, or AP isolation).In TP-Link Wi-Fi routers, this option is located in the "Avant-garde Settings" section;
• If your computer has an active VPN connection, effort disconnecting it and checking for network discovery on your local network;
• If your computer has several active network interfaces (for instance, Wi-Fi and Ethernet), endeavor to disable all interfaces except those connected to the local network with other devices;
• Try temporarily disabling your antivirus and/or firewall software;
• Disable the IPv6 protocol in the properties of your network connection;
• Check the availability of computers in your LAN using standard Windows tools:
  ping IP or ping hostname
Test-NetConnection hostname -port 445

Source: http://woshub.com/network-computers-not-showing-windows-10/

Posted by: lugobeivieve.blogspot.com

Share this post