Are you experiencing Socket Error 10054 on Windows PC? This error is accompanied by a “Connection reset by peer” error message. Now, what is this error, and how you can fix it, let us find out in this post.
What does Socket Error 10054 mean?
The Socket Error 10054 basically occurs when the connection was abruptly terminated by the remote host. When triggered, you will get the “Connection reset by peer” error message. It basically indicates peer-to-peer connection issues including the remote network interface being turned off, the remote host using a hard close, etc. There can be other reasons for this error as well. Firewall blockage is a common reason for this error. This error can also be triggered due to corrupted DNS and network settings.
Also, if your computer is infected with malware that is blocking you from using specific ports, this error might occur. In any case, if you are one of the affected users, you can use the working solutions we have mentioned here to fix it. So, let us check out the solutions.
How do I fix Winsock error 10054?
Winsock error 10054 or Socket Error 10054 can be fixed by ensuring that there are no peer-to-peer connection problems. Apart from that, you can disable your firewall temporarily or allow the problematic applications or domains through your firewall or router configurations. You can also reset your network configurations or contact your ISP to fix the error. We have shared these fixes in detail, so check them out.
If you experience Socket Error 10054 on your Windows PC, here are the solutions you can use to fix the error:
- Check Peer to Peer connection.
- Disable your firewall.
- Reset TCP/IP and flush the DNS cache.
- Modify your Registry (for LogMeIn).
- Set up your HTTP Sensor settings (if applicable).
- Contact your Internet Service Provider (ISP).
Before trying the below fixes, run a malware scan on your computer and ensure that your computer doesn’t contain any virus or malicious program.
1] Check Peer to Peer connection
You might experience Socket Error 10054 if the peer application on the remote host is abruptly closed. Some other scenarios of this error include the host or remote network interface being disabled, the host being restarted, and the remote host using a hard close. Additionally, if a connection broke because of the fact that keep-alive activity detected a failure when an operation was in progress, this error might be triggered.
Hence, you can check the peer-to-peer connection and rule out the above possibilities. This includes checking if the entered network path is correct, ensuring that your computer is not blocked, and making sure that the network between you and other PC is enabled. If the error still occurs, you can move on to the next fix.
Read: An error occurred while renewing interface Ethernet on Windows.
2] Disable your firewall
This error is likely to cause due to interference by your firewall. So, you need to ensure that your firewall is not blocking between the client and the servers. You can try disabling your firewall temporarily and see if the error is fixed. For that, open Windows Defender Firewall using Windows Search and click on the Turn Windows Defender Firewall on or off option from the left-side pane. After that, select the Turn off Windows Defender Firewall option under Private as well as Public network settings. Once done, check if the error is resolved.
If you have stopped receiving Socket Error 10054 after turning off your firewall, you can allow your application through Windows Firewall to permanently fix the error.
Additionally, make sure that the domains of the applications that you are using are allowed in your router’s settings.
See: Fix PuTTy Fatal Error, Network error on Windows computers.
3] Reset TCP/IP and flush the DNS cache
Corrupted DNS and network configurations can also cause Socket Error 10054. Hence, if the scenario is applicable, you can reset TCP/IP stack and flush the DNS cache to resolve the error. To do so, there are certain commands that you need to execute. Here are those commands:
First, open the Command Prompt as an administrator; click on the taskbar search button, type CMD in the search box, hover your mouse over the Command Prompt app, and then choose the Run as administrator option.
Now, enter the below commands one by one:
netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns
When all these commands are successfully completed, reboot your computer. On the next system startup, check if the error is fixed or not.
Read: Error 0x80072745, An established connection was aborted.
4] Modify your Registry (for LogMeIn)
If you are experiencing this error with LogMeIn, you can make a certain registry tweak to fix the error. This fix has been recommended by the official LogMeIn Support team as mentioned on a public forum. So, you can use it and check if the error is resolved.
Note: Before proceeding, make sure to create a backup of your Registry as any unintended or incorrect changes to registry keys and values can cause severe damage to your system.
Now, here are the steps to change the Registry:
First, evoke the Run command box using Win+R and enter regedit in the Open box to quickly open the Registry Editor app.
Next, move to the following key in the address bar:
Now, double-click on the DisableEx key and change the value of this key to 1.
After that, restart your PC to let the change take effect. Once done, check if the error is fixed or not.
Read: ERR_SOCKET_NOT_CONNECTED error on Chrome.
5] Set up your HTTP Sensor settings (if applicable)
If you are experiencing this error while setting up HTTP sensors, you can try changing some configurations and see if it works. First, open your HTTP Sensor settings and then locate the SNI Inheritance option. After that, set it to the “Do not inherit SNI from parent device” option. Check if the error is resolved or not.
6] Contact your Internet Service Provider (ISP)
The last resort to fix the error is to contact your Internet Service Provider (ISP). They should be able to fix the error for you.
Hope this helps!
Now read: Error 10013, An attempt was made to access a socket.
The “Socket Error 10054 Connection Reset by Peer” error is faced by users usually when the remote application or server is stopped and the connection is closed. The issue usually occurs due to an incorrect configuration of the firewall, a glitch in the system, or when the connection gets a spike in traffic that can lead to instability.
In this detailed article, we will guide you through all the possible reasons that can trigger this issue and take you through the step-by-step process of fixing it. Make sure to go through the guide below and follow along with the listed steps.
Why do you get the Socket Error 10054 Connection Reset by Peer Message while Connecting?
Some of the more common causes of the issue have been listed below. Keep in mind that these are usually the generic reasons behind the occurrence of this issue and there can be other reasons as well.
- Router Configuration Issue: Router misconfiguration can range from an incorrect DNS configuration to addressing resolution issues. We have listed the ways to resolve router misconfiguration in the solutions below.
- Malware: If a virus or malware has plagued the computer, it might prevent you from using or opening certain ports and if a process is using them already, it might close them which can result in Socket Error 1054.
- Peer-to-Peer Connection: Another common reason behind its occurrence is the enabling of the Peer-to-Peer functionality on the computer which allows for a peer-to-peer connection. This sort of connection quite commonly runs into issues such as the “Socket Error 10054 Connection Reset by Peer” message.
Now that you have a gist of why the Socket Error is being triggered, you can move on to implementing the fixes that we have mentioned below.
Method 1: Flush the DNS
DNS Configurations manages the connection and its establishment, however, sometimes, if corrupted, it can cause the connection to be closed and trigger the “Socket Error 10054 Connection Reset by Peer” error. Therefore, we can flush the DNS cache to make sure that isn’t the case. For that:
- Press “Windows + R” to start the run prompt, type in “cmd” and press “SHIFT + CTRL + Enter” to launch with admin permissions.
Typing in “cmd” in the dialogue box
- From here, type in the following commands one by one and press “Enter” after each to completely reset the DNS cache.
netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns
- After executing the commands, check and verify if the Socket Error has been fixed.
Method 2: Prevent Firewall Blocking
It is important that your Firewall isn’t blocking the application from being able to establish a connection with its servers, this is done in most firewalls that have the intrusion detection feature. To fix this, you can simply add an exception for the particular application and its servers or you can try to disable the firewall temporarily to check if that is indeed causing the issue.
Method 3: Disable Peer-to-Peer Functionality
This solution is only valid for those that are facing Socket Error 10054 with the Logmein application. For this, you will be disabling the Peer-to-Peer functionality of the application by modifying the Windows Registry. For that:
- Press “Windows + R” to launch into the Run prompt, from there, type in “regedit” and press “Enter” to start the Registry editor.
Opening the Registry Editor by typing in “regedit” in the run prompt
- In the registry editor, navigate to the “HKEY_LOCAL_MACHINE\SOFTWARE\LOGMEIN\V5\Net\NATUDP” address, and in there, double-click on the “DisableEx” key.
- Change the “Value” of the key from “0” to “1” and save your changes.
- Exit out of the Registry Editor and again open the “Run Prompt” by pressing “Windows + R“.
- Now, type in “services.msc” and press “Enter” to launch into the service management window.
Typing in “services.msc” in the Run prompt
- Here, right-click on the host service and select the “Restart” button.
- Make sure to exit out of this window and check to see if the Socket Host Error 10054 is now fixed.
Method 4: Try Some Generic Fixes
- Make sure that the Default Gateway that your connection is using is different from the IP address that has been assigned by the DHCP service.
- Verify that your computer hasn’t been plagued by malware. You can do this by running an in-depth virus scan on your computer that will check the presence of known viruses on it.
- Completely power off your computer, remove the power plugs, and power it back on.
- Try to connect using another port.
Method 5: Reconfigure HTTP Sensor Settings
Some users were facing this issue while configuring HTTP sensors and according to our investigation, we were able to fix it by changing some configurations. For that:
- You can use the Multi-edit feature of the PRTG to edit and reconfigure the settings of multiple sensors at once instead of having to configure each sensor.
- To do that, navigate to the “Sensors > By Type > H.. > HTTP” options and select the sensors that you would like to reconfigure by checking their respective boxes.
- After doing so, select the “Settings” icon from the right side and then activate the “SNI Inheritance” option.
- Now that you have activated this option, make sure to check the “Do not inherit the SNI from Parent Device” option.
Selecting the “Do not inherit the SNI from Parent Device” option
- This should now fix the Socket Error 10054 Connection Reset by Peer with HTTP sensors.
Method 6: Fix Error with TTWin3 Application
If your users are trying to connect using an ISDN connection, it can automatically be closed with the “Socket Error 10054 Connection Reset by Peer” error if the connection is idle for a while. We can use the KeepAlive feature in the TTWin3 Settings to keep the connection alive. For that:
- Go to the “Configure” option and select the “Comms” button.
- Now, select the “Advanced Setup” button.
- From here, navigate through the “Miscellaneous” section.
- In the Keep Alive field in this section, enter any value, it should be from “60” to “120”.
- Click on “File>Save” to save the changes that we have made and it will now ping the application after the entered number of seconds to keep the connection alive.
- This should fix the Socket Error 10054 error with the TTWin3 Application.
In most cases, the error should now have been fixed by one of these solutions but if you still get the Socket Error 10054 Connection Reset by Peer issue, you can contact us for further assistance.
A man of Technology geared towards providing solutions to the most annoying errors that occur while using your favorite apps or hardware.
I receive the ftp socket error 10054 when I try to connect to FTP for an upload. Please fix this problem.
That was a recent support ticket received from one of our customers as part of our Dedicated Support Services.
This FTP error occurs when the existing remote connection is forcibly closed by the remote host.
Today, let’s see the top 6 reasons for the ftp socket error 10054 and how our Support Engineers fix them.
FTP socket error 10054 – A Brief explanation
A socket is the endpoint of client-server communication.
FTP socket error 10054 indicates that the remote host has forcibly terminated or reset the existing connection of the FTP client. And, users see the complete error message as shown below.
Upload failed. Socket Error # 10054 Connection reset by peer.
This broken connection can be at the FTP server side or at the user’s side. So, our Support Engineers primarily check the server logs to determine if this is a network error at the client side or at the server side.
FTP socket error 10054 – Reasons & Solutions
Now, let’s see the main causes of this error and how our Support Engineers rule out each possibility to fix this problem.
1) Remote server issues
FTP socket error 10054 can occur due to the problems at the remote server end. This error usually occurs during the following scenarios.
- The remote host is suddenly rebooted or restarted.
- Network interface of the remote server is disabled.
- User’s account on the remote server is disabled or restricted.
- Too many users logged on to the server.
How we fix?
Firstly, our Support Experts check the availability of the remote host using the ping command.
In addition to that, we check the uptime of the server to verify that a reboot has been initiated on the server.
Thus, we can confirm whether the server reboot created problems for the user. Moreover, we ensure that the network settings on the server are intact and the FTP user is allowed to connect to the remote host.
2) Invalid FTP host
Once we’ve confirmed that there are no issues at the remote host, we then check the FTP client settings. And, one of the common reasons for this error is the use of invalid FTP host address.
Users should enter the hostname details in the FTP host field to initiate a connection. For example, customers usually give it as ftp.servername.com or servername.com.
However, a typo in the FTP hostname or missing hostname field can result in this error. Even a single additional space in the FTP hostname can create problems.
How we fix?
Firstly our Support Experts confirm the DNS connectivity of the FTP host using the dig command.
Further, we double check and confirm that customer is using the correct FTP host address in their FTP client.
3) Firewall restrictions
Similarly, firewalls can act up and break the FTP connection. Moreover, Antivirus or Antispyware tools can act as a second layer firewall and close the connections. Even the firewalls at the ISP end, firewall on a router can block connections through FTP ports.
How we fix?
In such cases, we ask the customers to temporarily disable the security applications such as Windows firewall, Antivirus, etc. one by one on their system. This helps us to identify the application that’s exactly creating problems and fix it’s settings.
Likewise, to resolve the firewall issues at the network level, our Support Engineers ask the customers to disable gateways and routers to establish a direct connection. Thus, we can verify if the problem lies at the intermediate level. Once we’ve confirmed that the problem is with the intermediate devices, we ask the customers to work with their ISPs to configure ISP firewall to allow connections to FTP ports.
[Messed up firewall rules on your server? Click here and get one of our Server Experts to fix your firewall rules.]
4) Issues with File transfer mode
File transfer can happen in 2 types – Active and Passive mode, and most of the FTP clients use Passive mode by default. However, some remote servers accept the connections only in Active mode or PORT mode resulting in this error.
How we fix?
The steps to enable Active mode differs based on the FTP client software used by the customers.
So, our Dedicated Engineers get the FTP client details from the users, and help them navigate the settings and enable Active mode. For example, we enable Active mode in Filezilla from Site Manager > Transfer settings > Transfer mode.
5) Connection timeout issues
Ftp socket error 10054 occurs when users try to upload relatively large files which conflict with the internal timeout settings of the FTP client. In other words, when user uploads a large file, the upload process may fail if it’s not completed within the predefined connection timeout limit.
How we fix?
In such cases, we recommend users to increase the connection timeout settings in their FTP client. For example, we increase the connection timeout limit from Edit > Settings > Connection > Timeout > Timeout in seconds.
Alternatively, in some cases we disable this timeout value by making it’s value as 0.
6) Advanced FTP client settings
Some of the FTP clients such as CuteFTP use advanced configurations which may not be compatible with the remote server you’re connecting. For example, some remote servers may be configured to allow only a limited number of connections or sessions. However, some users configure their FTP client to set large number of concurrent file transfers. In such cases, remote server terminates the connection and result in ftp socket error 10054.
Similarly, users set large values for send and receive buffer sizes in their FTP client settings. However, this may conflict with the remote server values and causes problems.
How we fix?
In such cases, our Dedicated Engineers help the customers navigate the FTP client settings and limit the number of concurrent connections. For example, on CuteFTP client, we change this parameter from Tools > Global options > Connection > Per site max concurrent transfers >Transfer.
Moreover, we tweak the send and receive buffer size values accordingly. For instance, we change the buffer size from Tools > Global options > Transfer in CuteFTP.
[Need help in resolving your FTP issue? Our Support Experts can help you here.]
In short, ftp socket error 10054 can occur due to remote server issues, firewall restrictions, and more. Today, we’ve discussed the top 6 reasons for this error and how our Dedicated Engineers fix them.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
var google_conversion_label = “owonCMyG5nEQ0aD71QM”;
When I call the function
IdFtp.List(myList, '', false);
afterwards I have logged in and changed the ftp directory, I get a socket-error #10054 exception (“Connection reset by peer.”) occesionally.
When I call that function e.g. 20 times consecutively I get that exception 1 time.
That problem I have only encountered on Vista OS.
Does anybody know what the problem is or how I can avoid it?
asked Mar 28, 2012 at 13:12
Not much you can do about this, because the disconnection is done by the FTP server.
You have a few choices:
- Increase (or disable) the timeout settings (every FTP server has a different name for it) on your FTP Server connection settings.
- Tell server that you are alive by sending
NOOPcommand periodically (switching to Passive mode can also help).
- Catch that exception and reconnect silently (This is my preferred solution because we have many FTP servers and I don’t trust the sys-admins to change the FTP server time-out settings).
Here is a screen-shot from
FileZilla FTP server time-out settings:
Note that with the above settings, the FTP client will be disconnected after 2 min of non-activity.
setting that value to 0, will disable the time-out.
answered Mar 28, 2012 at 23:27
21k4 gold badges62 silver badges121 bronze badges
The FTP protocol uses multiple socket connections. Every time you call
List(), a new socket connection is established to transfer the requested listing data. It sounds like the FTP server is not always closing the socket correctly at the end of a transfer.
answered Mar 28, 2012 at 20:24
Remy LebeauRemy Lebeau
558k31 gold badges460 silver badges777 bronze badges
In the component “IdFTP”, change the following properties:
- “Passive” = “False”
- “TransferType” = “ftASCII”
1,8561 gold badge16 silver badges35 bronze badges
answered Feb 17, 2016 at 19:22
Windows Sockets are an application program interface (API) that allow communication between two systems over a network. Socket errors can be caused by various issues including connectivity problems on the network, client or server computers or due to a firewall, antivirus or a proxy server.
This article provides information about common socket errors you may encounter when using FTP, Cloud, SBMS or Email with SyncBack:
Socket error # 10013, Permission denied
This error occurs when the socket connection to the remote server is denied. The possible reasons are a firewall or antivirus (AV) software is blocking the connection, the port used is blocked or unreachable.
Temporarily disable firewall/AV program and check the connection after restarting your computer.
Socket Error # 10039, Destination address required
There may be a problem getting the IP address for the hostname.
Socket error # 10052, Network dropped connection on reset
The host you are connecting to crashed or rebooted. Retry later.
Socket error # 10053, Software caused connection abort
An established connection was closed by software on your local host. Possibly a firewall, AV or something else on your local computer aborted the connection, or the connection to the remote server timed out.
Socket Error # 10054, Connection reset by peer
The remote server or some other software is forcibly closing or resetting the established connection. This may be a problem with your network, firewall or AV configuration, the remote server is stopped or rebooted.
Ensure that the hostname or IP address of the remote server is correct and check if the remote server is reachable.
Socket error # 10055, No buffer space available
This error indicate that Windows has run out of socket buffers. The most common causes of this error are running a high number of applications simultaneously and insufficient system resources (memory or disk space).
Close unwanted programs that are running, restart the computer to free up resources. If you are backing-up to a cloud server, then reduce the number of threads to use from Cloud > Advanced settings page.
Socket error # 10060, Connection timed out
This is a connection timeout error, which means the remote server did not properly respond after a period of time. It generally suggests firewall or network issues e.g. a firewall may be permitting some commands/responses but blocking others or may be the hostname/port is incorrect.
Socket error # 10061, Connection refused
A connection to the server cannot be established as the remote server actively refused the connection. The common causes are the server is not running, incorrect connection parameters are used when establishing a connection (e.g. a wrong port number is used), a firewall or antivirus is blocking the connection.
Check if the server connection details are configured correctly and ensure the firewall is not blocking the connection.
Socket error # 10106, Service provider failed to initialize
This error can be caused by corrupted Windows system files, incomplete installation/uninstallation of applications or the computer is infected by a virus or malware.
Re-install SyncBack. Run a disk check and virus scan to detect and fix errors.
Socket error # 11001, Host not found
Check that the hostname or IP address has been entered correctly.
Socket error # 11002, Nonauthoritative host not found
This is a temporary error during hostname resolution, which means the hostname could not be resolved to an IP address. Try reconnecting later.