In some cases, third-party anti-viruses and firewalls can block NetBIOS name resolution requests, WDS and broadcast DNS queries (there was definitely a problem with ESET NOD32).
mcs console and check the services state:
In this case, all old protocol settings for the network card will be reset.Īlso, check whether the following services are running (they should be in the automatic startup state to correctly display your network environment). Windows should automatically detect your network adapter and install the appropriate drivers. In some cases, you need to completely remove your network adapter using the Device Manager (run the devmgmt.msc console -> Network Adapters -> your network card -> Delete device). To do this, open the Settings -> Network and Internet -> Status -> Homegroup. You need to change the network location to Private. Most likely your local network was recognized as Public. If after rebooting the computer appeared in a network environment, but you can’t access it, check the network profile type (location) on your computer. After that, you need to restart the computer. In the Join Domain or Workgroup Wizard that opens, select: This computer is part of a business network -> My company uses a network without a domain -> enter your workgroup name. Go to the Control Panel -> System and Security -> System -> Change Settings -> Network ID.
Try to re-add this computer to the workgroup. In some cases, Windows computer may not be displayed in the network environment due to incorrect workgroup settings. Also, you can manually enable the Network Discovery protocol for at least the Private network in the Windows Defender Firewall settings (Control Panel\All Control Panel Items\Windows Defender Firewall\Allowed apps).
0 kommentar(er)
