What Error 10060 Means
Error 10060 (socket code WSAETIMEDOUT) is a standard Windows message for a connection timeout. It means your program (browser, email client, game, Skype) sent a connection request to a remote server but did not receive any response within the system-defined time.
Typical full error text in English:
Could not connect to the server. The connection was terminated or the server did not respond to the request. Error: 10060 (socket).
This error blocks further interaction with the server and makes it inaccessible. The problem always lies on the client side (your PC) or within the intermediate network (router, ISP), and less frequently—with the server being unavailable or overloaded.
Common Causes
Error 10060 isn't "magical"—it has specific technical reasons:
- Firewall or antivirus blocking. The most frequent cause. Security software (including the built-in Windows Defender Firewall) blocks an outgoing connection on a specific port your program uses.
- Incorrect proxy settings. System or application proxy settings point to a non-existent or non-responsive address, causing packets to fail to reach the target server.
- DNS resolution issues. Your or your ISP's DNS server cannot correctly resolve a domain name (e.g.,
smtp.gmail.com) into an IP address, or returns an outdated/incorrect address. - Server is overloaded or down. The server you're trying to connect to might be under a DDoS attack, undergoing maintenance, or temporarily offline.
- Windows TCP/IP stack corruption. Damaged or incorrect network stack settings (Winsock, TCP/IP parameters) prevent a proper connection from being established.
- ISP-level blocking. Some ISPs block specific ports (e.g., for P2P networks) or have routing issues to particular networks.
- Incorrect system time. A significant system time discrepancy can disrupt security protocols (SSL/TLS), causing the connection to drop during the handshake phase.
Solutions
It's recommended to perform the solutions in the specified order, from the most likely and simplest to more complex.
Solution 1: Quick Test — Disable Firewall and Antivirus
This is the fastest way to determine if security software is at fault.
- Press
Win + R, typefirewall.cpl, and press Enter. In the Windows Defender Firewall window, select 'Turn Windows Defender Firewall on or off' from the left. For both Private and Public networks, temporarily disable the firewall. Click OK. - Open your third-party antivirus interface (ESET, Kaspersky, Avast, etc.) and find settings for real-time protection or the firewall. Temporarily disable them.
- Try to perform the action that triggered the error (send an email, connect in a game, call on Skype).
- If the error disappears — the problem is definitely a block. Re-enable your firewall and antivirus. Now you need to add an exception for your program.
- For Windows Firewall:
Control Panel->Windows Defender Firewall->Allow an app or feature through Windows Defender Firewall. Find your program in the list and allow access for Private and/or Public networks. If the program isn't listed, click 'Allow another app...' and browse to its executable file (.exe). - For your antivirus: Find the 'Exceptions', 'Trusted Applications', or 'Network Shield' section in its settings and add the program's executable file or the specific port it needs.
- For Windows Firewall:
- If the error remains — proceed to the next solution. Do not leave your firewall and antivirus disabled for long!
Solution 2: Reset Network Settings and DNS Cache
This method fixes most problems related to Windows configuration corruption.
- Close all programs using the internet.
- Press
Win + R, typecmd, and pressCtrl + Shift + Enterto run Command Prompt as Administrator. - Sequentially type and execute the following commands (press Enter after each):
ipconfig /flushdns netsh winsock reset netsh int ip reset netsh advfirewall resetipconfig /flushdns— clears the local DNS cache.netsh winsock reset— resets the Winsock library settings (handles network interaction for programs).netsh int ip reset— resets TCP/IP settings.netsh advfirewall reset— restores the firewall to default settings (useful if you misconfigured it).
- Important: After executing all commands, restart your computer. A restart is critical for changes to apply, especially for Winsock.
- After restarting, test the connection.
Solution 3: Change DNS Servers to Public Ones (Google DNS or Cloudflare)
If the issue is DNS-related, this step will resolve it.
- Open Control Panel (you can use
Win + R->control). - Navigate to
Network and Internet->Network and Sharing Center. - On the left, click
Change adapter settings. - Find your active connection (usually 'Ethernet' or 'Wi-Fi'). Right-click it and select
Properties. - In the list of components, find and select
Internet Protocol Version 4 (TCP/IPv4). ClickProperties. - In the new window, uncheck 'Obtain DNS server address automatically' and set:
- Preferred DNS server:
8.8.8.8 - Alternate DNS server:
8.8.4.4(These are Google's public DNS. You can use Cloudflare:1.1.1.1and1.0.0.1).
- Preferred DNS server:
- Click OK, close all windows. Test the connection.
Solution 4: Check and Disable Proxy Settings in Windows
An incorrect system proxy "intercepts" and blocks traffic.
- Open Windows Settings (
Win + I). - Go to
Network & Internet->Proxy. - Under 'Automatically detect settings', uncheck 'Automatically detect settings'.
- Under 'Manual proxy setup', ensure the 'Use a proxy server' toggle is off.
- Click OK.
- Also check proxy settings inside the specific program causing the error (e.g., in Skype:
Tools->Options->Connection->Proxy server). Ensure 'No proxy' or 'Auto-detect' is selected.
Solution 5: Check Server Availability and Program Settings
The problem might be with the server itself or the specific software's configuration.
- Check if the server is up. Try accessing the service's website from another device (a smartphone on a different network). If it fails there too—the problem is on the server side; wait for its administrators to fix it.
- Check the port. If you know which port the program uses (e.g., 25 for SMTP, 587 for secure SMTP, 443 for HTTPS), try checking its accessibility. In Command Prompt (as admin), run:
For example:telnet <server_address> <port>telnet smtp.gmail.com 587. If the connection fails (blank screen or error), the port is blocked along the path. - Check the program's settings. Go into the settings of the program showing the error (email client, messenger, game). Ensure you have entered the correct server address (SMTP/POP3/IMAP for email, game server) and the correct port. Try using alternative ports (e.g., 587 instead of 25 for email).
- Update the program. An outdated client version may use obsolete protocols or ports. Install the latest version.
Prevention
To prevent error 10060 from recurring:
- Don't disable your firewall completely. Instead, configure proper exceptions for trusted programs.
- Use stable DNS servers. Configure public DNS (Google or Cloudflare) on your router or each computer to avoid relying on your ISP's DNS.
- Keep your OS and critical software updated. Windows, antivirus, and network driver updates often contain fixes for the network stack.
- Verify program settings. When changing ISPs or setting up new software, carefully check the entered server addresses and ports.
- Avoid "grey market" software versions. Unlicensed or modified software may contain malicious modules that disrupt network functionality.
Additional Steps (If Nothing Helped)
If you've completed all main steps and error 10060 persists:
- Try a different network connection. Connect via mobile internet (tether from your phone). If the error disappears—the problem is definitely in your home/office network (router, ISP).
- Update your network adapter drivers. Go to
Device Manager(devmgmt.msc), expand 'Network adapters', right-click your adapter, and select 'Update driver'. It's best to download the latest driver from the manufacturer's website (motherboard or laptop vendor). - Create a new network configuration. In
Windows Settings->Network & Internet->Advanced network settings->Network reset. This operation will remove all saved Wi-Fi networks, VPN connections, and virtual adapters, resetting network settings to factory defaults. Use with caution. - Contact your network administrator or ISP. If the error occurs when connecting to a work server, ask your system administrator if a corporate firewall is blocking your IP or if a special port is needed. If the problem is widespread (nothing works), contact your ISP's technical support.