Creating a local area network between computers in a modern home or office is no longer the preserve of system administrators at large corporations. Today, when every user has a laptop, smart TV, or network storage device, the ability to quickly transfer a movie, document, or game over the air is becoming critical. Operating system Windows 10 has powerful built-in tools for organizing such interactions, but hidden security settings often make this process non-obvious to the average user.
Unlike previous OS versions, Windows 10 requires a more careful approach to network profiles and access rights. Many users encounter a situation where computers are connected to the same router but cannot see each other in the network environment. SMB protocol, responsible for data exchange, can be blocked by default by antivirus or firewall settings, which creates the illusion that the equipment is not working.
In this guide, we'll walk you through every setup step, from verifying the physical connection to fine-tuning group policies. You'll learn how to transform disparate devices into a unified ecosystem where files are instantly accessible without the need for flash drives or cloud storage. It's crucial to follow each step sequentially, as missing even one setting can disrupt the entire connection chain.
Checking the basic connection conditions
Before moving on to complex operating system settings, you need to ensure that the physical and logical structure of your network is correct. A fundamental requirement is that all devices are on the same network. subnetsThis means that if you share internet from your phone to one laptop, and the second is connected to your home router, they physically won't be able to exchange data directly without additional bridging.
Make sure all computers that need to connect to the network have the same network profile type. Windows 10 divides connections into "Public" and "Private." In "Public" mode, the system minimizes device visibility to protect against hackers in cafes or airports, making it impossible to create a private network.
- 📡 Check that all devices are connected to the same SSID (name) of the Wi-Fi network.
- 🔒 Make sure the network type is set to "Private" in Wi-Fi settings.
- 📶 The Wi-Fi signal must be stable, without constant connection interruptions.
- 🔌 The router must support the Client Isolation function when disabled.
⚠️ Note: Some ISPs or corporate routers enable the "Wi-Fi Isolation" feature by default. In this mode, devices are prevented from communicating with each other, even within the network. If your Windows settings are correct but there's no connection, check this setting in the router interface.
Setting up sharing and discovery
The central configuration element is the Network and Sharing Center. This is where services are activated that allow computers to "announce" their presence and respond to requests from other devices. Without these features enabled, your system will remain "invisible" to network neighbors, regardless of signal strength.
To get started, go to the control panel and find the section responsible for changing the settings public accessYou'll need to expand the "Private (Current Profile)" profile. This contains a key, often overlooked setting: enabling network discovery. It's also recommended to enable automatic installation of network-connected devices, which will simplify working with peripherals.
☑️ Sharing setup checklist
Pay special attention to the "File and Printer Sharing" setting. Enabling it opens the ports needed for data transfer. If this setting is disabled, you'll be able to see computers in the list, but access to their folders will be blocked by the security system.
⚠️ Important: Enabling passwordless sharing (disabling password protection) is only allowed on trusted home networks. If unauthorized users can connect to your Wi-Fi, they will have full access to your public folders. In such cases, it's best to leave password protection enabled and create accounts with the same passwords on all PCs.
Enabling required Windows services
Even with the correct interface settings, Windows background services can block local network operation. The operating system uses specific services to publish resources and discover other nodes. If a service is stopped or its startup type is set to "Disabled," no amount of adjustments in the settings menu will help.
To access the service management, press the key combination Win + R and enter the command services.mscIn the list that opens, you need to find several critical components. The first service we're interested in is the "Function Discovery Resource Publication" service. This service is responsible for advertising your computer to the network.
Also check the status of the "Computer" and "Internet Connection Manager" services. Make sure their startup type is set to "Automatic." If the service status is "Stopped," right-click it and select "Start." Restarting the computer after applying the settings often helps the changes take effect.
List of services to check
Function Discovery Resource Publication|SSDP Discovery Node|HomeGroup Discovery Service (if using legacy)|NetBIOS over TCP/IP Helper Service
Configuring network settings via PowerShell
For experienced users or when the graphical interface is unresponsive, the command line and PowerShell are excellent tools. This method allows you to quickly switch a network profile from public to private, often solving the visibility issue. Using commands eliminates human error and mouse click errors.
Launch PowerShell as administrator. Enter the following command to get the current status of network profiles:
Get-NetConnectionProfile
The output will show the network name and current status (Public or Private). To change the profile to private, use the command:
Set-NetConnectionProfile -Name"YourNetworkName" -NetworkCategory Private
This method is especially useful if Windows stubbornly considers your home network to be public and blocks all configuration attempts through the standard menu. You can also use PowerShell to reset the TCP/IP stack if you're experiencing packet loss issues.
SMB 1.0 Protocol Issues and Security
One of the most common reasons why older network attached storage (NAS) devices or Windows 7 computers are not visible in Windows 10 is because the protocol is disabled. SMB 1.0Microsoft has disabled this protocol by default due to security vulnerabilities (such as the WannaCry virus), but it is still required for compatibility in local isolated networks.
If you need to connect an older device, you'll need to manually enable SMB 1.0 support. This can be done through Control Panel: "Programs and Features" → "Turn Windows features on or off." Find "SMB 1.0/CIFS file sharing support" in the list and enable both the client and server.
| SMB version | Security | Compatibility | Status in Win 10 |
|---|---|---|---|
| SMB 1.0 | Low (vulnerable) | Win XP, Win 7, old NAS | Disabled by default |
| SMB 2.0 | Average | Win Vista, Win 7 | On |
| SMB 3.0 | High | Win 8, Win 10, Win 11 | On (primary) |
Using SMB 1.0 carries risks, so enable it only when absolutely necessary, and try updating older devices to firmware versions that support SMB 2.0 or 3.0. After connecting older devices, it is recommended to disable this feature again.
Accessing folders and troubleshooting errors
Once the computers can see each other, you need to share specific folders. Right-click the folder, select "Properties" → "Sharing" tab → "Advanced." Here, check "Share" and configure permissions for the "Everyone" group if you don't use passwords.
A common issue is the "Access Denied" error, even when everything is configured correctly. This may be due to NTFS permissions. Go to the "Security" tab in the folder properties and ensure that the "Everyone" user or group has read and execute permissions. Without this step, network access will be blocked at the file system level.
- 📂 Make sure the folder path does not contain Cyrillic characters if you are connecting from Linux or macOS.
- 🔑 Check if your antivirus is blocking network communication.
- 🔄 Try accessing by IP address (\\192.168.1.X) rather than by computer name.
⚠️ Note: Interfaces and menu item names may vary slightly depending on your Windows 10 build version (Home, Pro, Enterprise) and installed security updates. If you don't see an item, check Microsoft Help for the latest information or update your system.
Frequently Asked Questions (FAQ)
Why can my computer see the network but not other computers?
The problem is most likely with your network profile. If it's set to "Public," Windows is hiding other PCs. Also, check the Discovery Resource Publishing service and make sure your firewall isn't blocking your private network.
Is it possible to play on a local network via Wi-Fi with a different IP address?
No, for a local area network (LAN) to function, all devices must be on the same subnet (e.g., 192.168.1.X). If the IP addresses are significantly different (e.g., 192.168.0.X and 10.0.0.X), the devices will not be able to find each other without configuring static routes.
How do I find out the IP address of another computer on the network?
On the target computer, open a command prompt (cmd) and type ipconfigYou're interested in the "IPv4 address" line. This address (in the format \\192.168.1.XX) is the most convenient way to connect to shared folders.
Does Wi-Fi speed affect LAN gaming?
Yes, directly. For modern games with high detail levels and fast data transfer, it's recommended to use the 802.11ac (Wi-Fi 5) or 802.11ax (Wi-Fi 6) standard in the 5 GHz band. The older 2.4 GHz standard can cause latency (ping) and stuttering.
The secret of stability
For LAN gaming via Wi-Fi, it's critical that both computers operate in the 5 GHz band. The 2.4 GHz band is often clogged with signals from neighboring computers and microwave ovens, resulting in unstable ping.