Setting up a local area network (LAN) in a home or small office is fundamental to file sharing, printer sharing, and gaming sessions. Modern Wi-Fi router acts as a central hub, automatically distributing IP addresses and managing traffic between devices. However, when the environment contains computers with different operating system versions, such as outdated ones Windows 7 or Windows 8 along with modern ones Windows 10 And Windows 11, specific difficulties arise in setting up security and exchange protocols.
The main problem lies in Microsoft's gradual changes to its security policies, disabling older protocols (such as SMBv1) and modifying network device discovery algorithms. Users often encounter situations where computers see the Wi-Fi network but are unable to see each other in the network environment. To successfully integrate all nodes into a single infrastructure, it's important to understand that the settings must be synchronized on each device, taking into account its OS version. In this article, we'll outline a step-by-step procedure to help resolve version conflicts and establish stable data exchange.
Before beginning the in-depth setup, make sure all devices are physically (or via Wi-Fi) connected to the same router. If you use a wired connection for desktop PCs and a wireless connection for laptops, this isn't a problem, as the router combines them into a single broadcast domain. It's important that the IP address range is in the same subnet, which usually happens automatically when you enable DHCP server router.
Basic router setup and connection testing
The first step is to check that the router itself is configured correctly to work with the local network. In most cases, the factory settings of routers (from TP-Link, Asus, Keenetic or Mikrotik) already contain optimal parameters, but in corporate or secure networks, exchange functions may be blocked. You need to ensure that the protocol is activated on the router. UPnP (Universal Plug and Play) and there are no hard restrictions on Client Isolation, as this feature specifically prevents devices from seeing each other.
Check the address range. All computers should receive IP addresses from the same subnet, for example, 192.168.1.x. If one computer has the address 192.168.0.5 and the other has 192.168.1.5, they will not be able to communicate without manual reconfiguration. To check the current status, enter the command ipconfig and compare the "Default Gateway" and "IPv4 Address" values on all machines.
⚠️ Please note: Some ISPs or corporate network administrators may implement changes to router configurations remotely. If you notice settings being reset or network parameters being changed without your intervention, please check your ISP's current terms of service.
It's also worth paying attention to the Wi-Fi frequency range. If the router broadcasts two networks (2.4 GHz and 5 GHz) with different names (SSIDs), make sure all devices are connected to one of them, although modern routers typically combine them into a single logical interface. Separating the two into a guest network can also hinder device visibility, so use the main network when setting up the local network.
Single workgroup and computer names
A critical requirement for computers to be visible in the network environment ("Network") is that their workgroup names match. By default, this value is set to WORKGROUPIf one computer is in a group WORKGROUP, and the other in MSHOME or has a unique name, they may not automatically discover each other even if the physical connection is good.
To check and change the workgroup name in Windows 10 and 11, click Win + R, enter sysdm.cpl and go to the "Computer Name" tab. Here you can also change the name of the computer itself, making it unique and understandable (for example, PC-LIVING or OFFICE-PC), avoiding Cyrillic and special characters, since older systems (Windows 7) may not handle such names correctly in the network list.
Pay special attention to computers with Windows 7, as these settings are located in the path Control Panel → SystemMake sure that computer names are unique across all devices on the network. Duplicate names will cause addressing conflicts and prevent a stable connection to shared resources.
☑️ Checking basic network parameters
After changing the workgroup name or the computer itself, the system will require a reboot. This is necessary to apply the registry changes and register the new name on the local network via the NetBIOS protocol. Without a reboot, the changes may not take effect, and the computer will remain invisible to network neighbors.
Configuring the network profile and discovery services
Windows has several network profiles: "Private" (Home/Work) and "Public." For a local network to work, the profile must be set to "Private." In "Public" mode, the system blocks incoming connections and hides the computer from detection for security reasons, which is the default behavior when first connecting to a new Wi-Fi network.
In Windows 10 and 11, you can switch profiles via Settings → Network & Internet → Status (or the connection's "Properties"). Find the active connection and select "Private." In Windows 7, the first time you connect, the system will ask you for the network type—select "Home Network." If you missed this step, you can change the type through the Network and Sharing Center.
Next, you need to enable discovery services. Go to Control Panel → Network and Sharing Center → Change advanced sharing settingsHere, for the current network profile (Private), you need to enable the following options:
- 🔍 Enable network discovery.
- 🔍 Enable file and printer sharing.
- 🔍 Allow Windows to manage HomeGroup connections (if applicable).
It's also important to enable the "Turn on sharing so network users can read and write files in shared folders" option. Without this, you'll be able to see your computer, but access to files will be restricted. For the Guest profile (Public network), it's best to leave these settings disabled to avoid exposing data when connecting in cafes or airports.
Why isn't network discovery working?
The Function Discovery service may be stopped. Press Win+R, enter services.msc, find "Function Discovery Resource Publication" and set the startup type to "Automatic," then start the service. This is often required in Windows 10/11.
Sharing folders and setting permissions
Once the network is set up, you need to grant access to specific resources. Simply enabling sharing isn't enough—you need to explicitly specify which folders will be accessible to other users. You can share any folder by right-clicking it, selecting "Properties," and then going to the "Sharing" tab.
Click the "Advanced" button, check "Share this folder," and click "Permissions." Here you can set access levels: "Full Control" allows you to modify and delete files, "Change" allows you to edit, and "Read" allows you to only view files. For a home network, it's often convenient to grant full permissions to the "Everyone" group, but in an office environment, this can be unsafe.
There's also a "Security" tab in the folder's properties. Make sure the "Everyone" user (or a specific user) with the appropriate permissions is added there. Sometimes, permissions are granted in the "Access" tab, but access is blocked in "Security" (NTFS permissions), resulting in a "Deny" error when attempting to log in.
| Action | Windows 7 / 8 | Windows 10 / 11 |
|---|---|---|
| Opening folder properties | Right-click → Properties → Access | Right-click → Properties → Access |
| Extended rights | The "Share..." button | "Advanced settings" button |
| User Management | Control Panel | Settings → Shared Folders |
| Password protection | Network and Sharing Center | Network and Sharing Center |
To simplify access on small, trusted networks, you can disable password protection. In the "All Networks" section of the sharing settings, find "Password-protected sharing" and select "Disable." This will allow you to log in to your computer without entering your username and password, which is convenient but reduces security.
Resolving SMB protocol compatibility issues
One of the most common reasons why old computers (Windows XP, Vista, 7) don't see new ones (Windows 10, 11), is disabling the SMB protocol version 1.0. In newer systems, Microsoft disabled this protocol by default due to vulnerabilities (for example, the WannaCry virus), but older operating systems use it for communication.
If you need to connect an older computer or network printer to a modern network, you'll need to manually enable SMB 1.0 support on the modern computer. Only do this if you're confident your local network is secure and vulnerable hosts don't have internet access. This feature can be enabled via Control Panel → Programs and Features → Turn Windows features on or off → check "Support SMB 1.0/CIFS file sharing."
⚠️ Warning: Enabling SMB 1.0 on a computer connected to the Internet creates a serious security hole. If possible, update the software on your old device or use a third-party file manager (such as Total Commander with plugins) that supports the new SMB v2/v3 protocols.
On the other hand, modern Windows 10 and 11 use SMB v2 and v3 by default. If computers can't see each other, make sure these protocols aren't disabled on the receiving end (where the files are stored). You can check this status using the PowerShell command Get-SmbServerConfiguration.
Diagnostics and entering a static IP
For stable network operation, especially if you plan to frequently access shared folders or connect a network printer, it is recommended to assign a static IP address to key computers. A dynamic address (DHCP) may change after a router reboot, causing links to resources to stop working.
To pin an address, go to Control Panel → Network Connections, right-click your connection (Wi-Fi or Ethernet) and select "Properties." Find "Internet Protocol Version 4 (TCP/IPv4)," select "Use the following IP address," and enter the following information:
- 🌐 IP address: for example, 192.168.1.200 (to be outside the router's DHCP range).
- 🌐 Subnet mask: 255.255.255.0.
- 🌐 Default gateway: the IP address of your router (usually 192.168.1.1).
Also, in the IPv4 protocol properties, specify your preferred DNS server (you can use the router's address or Google's public DNS: 8.8.8.8). After applying the settings, test the connection with the command ping from another computer. In the command line (cmd) enter ping 192.168.1.200 -tIf responses are coming ("Response from..."), then the physical and network layers are working correctly.
If ping fails, check your Windows Firewall. It may be blocking ICMP requests. Try temporarily disabling the firewall to test. If communication resumes after disabling it, add an exception rule for the "Shared Folder" or allow ICMP echo requests in the firewall settings.
Frequently Asked Questions (FAQ)
Why do computers see each other but require a password to log in?
This is how the password protection mechanism works. Either disable it in the sharing settings (under "All Networks"), or create a user account on both computers with the same name and password. Windows will attempt to log in automatically using this information.
Is it possible to connect Windows 11 and Windows XP to the same network?
Physically, yes. Logically, it's complicated. Windows 11 doesn't support SMBv1 by default, which is what XP requires. You'll need to enable SMB 1.0 on Windows 11 (not recommended for security reasons) or install a third-party SMB v2/v3 client on XP, if it supports it.
How to quickly open a network folder if it is not shown in the list?
Use the direct route. Click Win + R and enter \\Computer IP address or \\Computer-nameIf the folder is shared correctly, it will open instantly, bypassing the lengthy network search process.
Does Wi-Fi speed affect file transfer speed on a local network?
Yes, directly. The local network speed is limited by the slowest link. If the router supports Wi-Fi 5 (AC), but one of the laptops has an older Wi-Fi 4 (N) module, the entire network will operate at standard N speeds. For large files, it's better to use an Ethernet cable.
What should I do if the network is identified as "Public" and does not change?
Try changing the network type through the registry or PowerShell. In PowerShell (as administrator), use the following command: Set-NetConnectionProfile -InterfaceAlias"Network_Adapter_Name" -NetworkCategory PrivateThe adapter name can be found using the command Get-NetConnectionProfile.