How to connect to a computer via Wi-Fi on a local network: 5 working methods

Remote connection to a computer via Wi-Fi network Saves time and simplifies working with files, programs, or settings on another device. For example, you can control your home PC from a laptop on the couch, help relatives with system setup, or administer office machines without physical access. But how do you do this correctly to ensure a stable and secure connection?

Many users mistakenly think that remote access requires the Internet or paid programs like TeamViewer. In fact, if both devices are connected to the same local Wi-Fi network, you can get by with standard tools Windows, macOS or LinuxThe key is to understand the nuances of setup and potential pitfalls, such as firewalls, dynamic IP addresses, or OS version limitations.

In this article we will analyze 5 proven methods connections - from built-in RDP to alternative solutions for different operating systems. We'll also explain how to avoid common errors and why connections sometimes drop after a few minutes.

1. Connecting via RDP (Remote Desktop Protocol) in Windows

First of all, check the version Windows on the target PC. To do this, click Win + R, enter winver and look at the editorial. If this Home, you will have to use workarounds (we will discuss them below) or choose another method from this article.

If the version is suitable, enable remote access:

1. Open Settings → System → Remote Desktop.
2. Activate the slider Enable Remote Desktop.
3. In the section System properties (available at this link) Additional options) Make sure that connections from any version of RDP are allowed (or specify a specific one).

Now find IP address target PC. To do this, enter in the command line (Win + R → cmd):

ipconfig

Look for the line IPv4 address in the block Wireless LAN adapter. For example, 192.168.1.105.

Launch the application from the connected device (laptop, tablet) Remote Desktop Connection (included in Windows (default) and enter the found IP address. When you first connect, the system will ask for the login and password for the target PC account.

⚠️ Attention: If an error appears after entering the password Remote Desktop cannot connect to the remote computer., check if your firewall is blocking the connection. Add a port exception. 3389 (default for RDP) in settings Windows Defender Firewall.

Make sure the target PC is running Windows Pro/Enterprise

Enable remote access in system settings

Remember the IP address of the target PC (or set it to static)

Disable sleep/hibernation mode on the target PC

Check that both devices are connected to the same Wi-Fi network-->

2. RDP Alternatives: TeamViewer, AnyDesk, and Chrome Remote Desktop

If Windows Home or cross-platform support is needed (for example, connecting with macOS or Android), use third-party programs. They work over the Internet, but if both devices are on the same local network, traffic will not go to the external network, which will speed up the connection.

Comparison of popular programs:

To connect via TeamViewer:

1. Download the program from official website and install on both devices.
2. On the target PC, write down ID And Password (they are updated at each launch).
3. On the connecting device, enter this data in the field Remote computer control.

The advantage of such programs is their ease of setup and additional features (such as file transfer or voice chat). However, they can slow down on low-end PCs due to the high CPU load associated with video encoding.

TeamViewer|AnyDesk|Chrome Remote Desktop|RDP (built into Windows)|Other-->

3. Connecting via SSH (for Linux and macOS)

To enable SSH on the target PC with Ubuntu/Debian:

sudo apt update && sudo apt install openssh-server
sudo systemctl enable --now ssh

For macOS:

1. Open System Preferences → Sharing.
2. Activate the checkbox Remote login.

Now find the IP address of the target device (similarly ipconfig V Windows, but in Linux/macOS use the command ifconfig or ip a). From the connecting PC, enter:

ssh user@ip-address

For example: ssh ivan@192.168.1.105. When connecting for the first time, confirm adding the host key (enter yes), then enter the password.

SSH uses port 22 by default. If your router is blocking local connections, check its settings or reconfigure SSH to a different port (e.g. 2222) in the /etc/ssh/sshd_config file.

⚠️ Attention: Never open the port 22 for external access (from the Internet) without configuration fail2ban or changing the default port. This is one of the most popular targets for brute-force attacks.

4. Using VNC for a graphical interface

If you need full access to graphical interface (not just the command line like in SSH), use VNC (Virtual Network Computing). This protocol transmits a screen image, which is convenient for remotely working with programs or configuring the operating system.

For Windows will do TightVNC or RealVNC, For Linux — x11vnc or TigerVNCInstall the server component on the target PC and the client component on the device from which you will connect.

Example of setup TightVNC V Windows:

1. Download and install TightVNC Server With official website.
2. Launch TightVNC Server and set a password in the settings.
3. Find the IP address of the target PC (as in the RDP section).
4. On the connecting device, open TightVNC Viewer and enter the IP address.

VNC transmits an unprocessed screen image, so it can be slow on slow Wi-Fi networks. To speed things up, reduce the color depth in the client settings (for example, to 16 bits) or turn it off desktop wallpaper on the target PC.

⚠️ Attention: VNC does not encrypt traffic by default! For a secure connection, use SSH tunnel or configure encryption in the server settings (for example, VeNCrypt V TigerVNC).

ssh -L 5901:localhost:5900 user@ip-address

5. Connecting via PowerShell (for Windows 10/11)

If you need to run several commands or scripts on a remote PC, but don't want to install additional software, use PowerShell RemotingThis method works through the protocol WinRM (Windows Remote Management) and does not require a graphical interface.

Turn it on first WinRM on the target PC:

Enable-PSRemoting -Force

If you get an error, run PowerShell as administrator.

Now add the connecting PC to the list of trusted hosts (on the target PC):

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "IP_address_of_the_connecting_PC" -Force

For example: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "192.168.1.100" -Force.

From the connected PC, run the command:

Enter-PSSession -ComputerName IP-address of target_PC -Credential (Get-Credential)

The system will prompt you for the login and password for the target PC account. Once successfully connected, you'll be able to run PowerShell commands remotely.

This method is convenient for automating tasks or managing servers, but is not suitable for working with graphical applications. Also WinRM uses port by default 5985 (HTTP) or 5986 (HTTPS), so make sure they are open in your firewall.

6. Troubleshooting: Why isn't the connection working?

Even with proper settings, connections may drop or fail. Here are common causes and solutions:

Problem 1: The target PC cannot be pinged.

• 🔌 Check that both devices are connected to one Wi-Fi network (not to guest or different ranges 2.4/5 GHz).
• 🔄 Reboot your router—sometimes the DHCP server “forgets” to assign IP addresses.
• 📡 Make sure that the target PC is enabled File and Printer Sharing in the network settings (Control Panel → Network and Internet → Network and Sharing Center).

Problem 2: Connection drops after 1-2 minutes.

• ⏳ Turn off Sleep mode And Turn off the display in the power settings of the target PC.
• 🔒 Check if your antivirus is blocking the connection (for example, Kaspersky or Avast may close "suspicious" ports).
• 🔄 If you are using RDP, make sure that in Settings → System → Remote Desktop option disabled Optimize for low-speed connections.

Problem 3: Cannot connect to Windows Home.

• 🔧 Use a workaround: turn on Remote assistant (msra.exe) and send an invitation to yourself via file.
• 💻 Install a third-party RDP server, for example, RDP Wrapper (unofficial solution, may violate license agreement).
• 🔄 Upgrade to Windows Pro (if possible) or use TeamViewer/AnyDesk.