6 Ways to Fix Socket Error 10054 Connection Reset by Peer
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.
Fixing Socket Error 10054 Connection Reset by Peer:
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.
- 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.
- 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.
- 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.
- 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.