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.

Socket Error 10054, Connection reset by peer

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:

  1. Check Peer to Peer connection.
  2. Disable your firewall.
  3. Reset TCP/IP and flush the DNS cache.
  4. Modify your Registry (for LogMeIn).
  5. Set up your HTTP Sensor settings (if applicable).
  6. 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

disable 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:

HKEY_LOCAL_MACHINE\SOFTWARE\LOGMEIN\V5\Net\NATUDP

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.

Socket Error 10054 Connection Reset by Peer

Socket Error 10054 Connection Reset by Peer

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:

  1. 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
    Typing in “cmd” in the dialogue box
  2. 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
  3. 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:

  1. 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
    Opening the Registry Editor by typing in “regedit” in the run prompt
  2. 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.
  3. Change the “Value” of the key from “0” to “1” and save your changes.
  4. Exit out of the Registry Editor and again open the “Run Prompt” by pressing “Windows + R“.
  5. Now, type in “services.msc” and press “Enter” to launch into the service management window.
    Typing in "services.msc" in the Run prompt
    Typing in “services.msc” in the Run prompt
  6. Here, right-click on the host service and select the “Restart” button.
  7. 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

  1. 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.
  2. 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.
  3. Completely power off your computer, remove the power plugs, and power it back on.
  4. 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:

  1. 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.
  2. 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.
  3. After doing so, select the “Settings” icon from the right side and then activate the “SNI Inheritance” option.
  4. 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 to fix Socket Error 10054 Connection Reset by Peer
    Selecting the “Do not inherit the SNI from Parent Device” option
  5. 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:

  1. Go to the “Configure” option and select the “Comms” button.
  2. Now, select the “Advanced Setup” button.
  3. From here, navigate through the “Miscellaneous” section.
  4. In the Keep Alive field in this section, enter any value, it should be from “60” to “120”.
  5. 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.
  6. 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.

Photo of Burt Macklin

A man of Technology geared towards providing solutions to the most annoying errors that occur while using your favorite apps or hardware.

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Contents

  • 1 Download 29 Socket Error 10054 Eol Connection Reset By Peer
  • 2 Socket Error 10054 Connection Reset By Peer On Windows
    • 2.1 Conclusion
      • 2.1.1 Related image with download 29 socket error 10054 eol connection reset by peer
      • 2.1.2 Related image with download 29 socket error 10054 eol connection reset by peer

Welcome to the fascinating world of technology, where innovation knows no bounds. Join us on an exhilarating journey as we explore cutting-edge advancements, share insightful analyses, and unravel the mysteries of the digital age in our Download 29 Socket Error 10054 Eol Connection Reset By Peer section. The in even either- or the should something browser according cipher their work Error but you this rules- closed means a tried because an case server not not ok version address be that a connection- also the your as it ssl why own to ip detected from that server could 10054

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer
2 answers sorted by: 1060 it’s fatal. the remote server has sent you a rst packet, which indicates an immediate dropping of the connection, rather than the usual handshake. this bypasses the normal half closed state transition. i like this description: “connection reset by peer” is the tcp ip equivalent of slamming the phone back on the hook. Contact the server administrator and ask them to restart the service and the daemons in such scenario. if you have access to the server, you can do it yourself. first, verify that the services and the daemons are running using systemctl command. restart the relevant daemons.

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer
🔴 follow thewindowsclub 🔴 if you are getting the socket error 10054 with “connection reset by peer” error message on windows 11 10, use these proven fixes. Error 10054 means that the server closed the connection. why? because the server detected something not ok according to their rules. this could be an ssl version as you tried, but also a cipher or even your own ip address (in that case it should not work from a browser either). Contents hide method 1: flush the dns method 2: prevent firewall blocking method 3: disable peer to peer functionality method 4: try some generic fixes method 5: reconfigure http sensor settings method 6: fix error with ttwin3 application method 1: flush the dns. 0 your vote: dear support, the sensor tested is “http advanced” and it shows the error “connection reset by peer (socket error # 10054)” how can i solve this? could you please help me? regards, natasha. connection http advanced prtg9 created on oct 18, 2011 11:57:26 am by daniel lemos (50) 1 1 permalink 4 replies votes: 1 your vote:.

Common Causes Of Socket Error 10054 And How To Fix Tl Dev Tech

Common Causes Of Socket Error 10054 And How To Fix Tl Dev Tech

Common Causes Of Socket Error 10054 And How To Fix Tl Dev Tech
Contents hide method 1: flush the dns method 2: prevent firewall blocking method 3: disable peer to peer functionality method 4: try some generic fixes method 5: reconfigure http sensor settings method 6: fix error with ttwin3 application method 1: flush the dns. 0 your vote: dear support, the sensor tested is “http advanced” and it shows the error “connection reset by peer (socket error # 10054)” how can i solve this? could you please help me? regards, natasha. connection http advanced prtg9 created on oct 18, 2011 11:57:26 am by daniel lemos (50) 1 1 permalink 4 replies votes: 1 your vote:. Wsaeconnreset (10054) connection reset by peer. a existing connection was forcibly closed by the remote host. this issue occurs because the tcp ip driver does not close an incomplete tcp connection. Execute the command. run “tracert” and the server address to see if the request is successful. execute “telnet” and enter the server address to see if the local machine ports are open.

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer
Wsaeconnreset (10054) connection reset by peer. a existing connection was forcibly closed by the remote host. this issue occurs because the tcp ip driver does not close an incomplete tcp connection. Execute the command. run “tracert” and the server address to see if the request is successful. execute “telnet” and enter the server address to see if the local machine ports are open.

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Download 29 Socket Error 10054 Eol Connection Reset By Peer

Socket Error 10054 Connection Reset By Peer On Windows

Socket Error 10054 Connection Reset By Peer On Windows

in this tutorial i will show you, socket error 10054 connection reset by peer on windows. here’s how to fix socket error 10054, connection reset by peer. how to fix winsock error 10054 #windows11 #howtofix. learn seven methods to fix err connection reset. start your online journey using hostinger web hosting how to fix windows sockets initialization failed error in windows 10. you can fix it without too much of a hassle. this tutorial will in this vedio, i will show you how to fixed network socket error problem of wo mic microphone apps. wo mic client,wo mic tutorial thank you everyone so much for watch my video on ” how to fix windows sockets initialization failed error on windows raw socket error 10013 #error 10013 #solve raw socket error 10013 #raw socket 10013 w tym filmiku pokazuję, jak naprawić błąd “network socket error 10054” w aplikacji wo mic. devops & sysadmins: zebra printer socket error 10054 helpful? please support me on patreon: this troubleshooting guide will help you fix an existing connection was forcibly closed by the remote host error in windows windows : windows udp sockets: recvfrom() fails with error 10054 to access my live chat page, on google, search for “hows

Conclusion

Having examined the subject matter thoroughly, there is no doubt that post delivers informative insights regarding Download 29 Socket Error 10054 Eol Connection Reset By Peer. From start to finish, the author demonstrates an impressive level of expertise about the subject matter. Notably, the discussion of Y stands out as particularly informative. Thank you for reading this post. If you have any questions, please do not hesitate to contact me through email. I look forward to hearing from you. Additionally, here are some relevant posts that you may find useful:

It’s almost definitely a bug in your code. Most likely, one side thinks the other side has timed out and so closes the connection abnormally. The most common way this happens it that you call a receive function to get data, but you actually already got that data and just didn’t realize it. So you’re waiting for data that you have already received and thus time out.

For example:

1) Client sends a message.

2) Client sends another message.

3) Server reads both messages but thinks it only got one, sends an acknowledge.

4) Client receives acknowledge, waits for second acknowledge which server will never send.

5) Server waits for second message which it actually already received.

Now the server is waiting for the client and the client is waiting for the server. The server was coded incorrectly and didn’t realize that it actually got two messages in one go. TCP does not preserve message boundaries.

If you tell me more about your protocol, I can probably tell you in more detail what went wrong. What constitutes a message? Which side sends when? Are there any acknowledgements? And so on.

But the short version is that each side is probably waiting for the other.

Most likely, the connection reset by peer is a symptom. Your problem occurs, one side times out and aborts the connection. That causes the other side to get a connection reset because the other side aborted the connection.

Logo

Pingman Tools logo

Knowledge Base

Question

I’m getting this error whenever I test an email alert: ‘Socket error 10054 – connection reset by peer’. What’s causing this?

Solution

This error happens when a connection is started (and working), but then closed by the other side of things before the SMTP conversation is completed. This can also be caused by a firewall in between you and the server that might be ‘proxying’ the SMTP conversation, and then terminates it.

There are several common reasons:

  • The wrong SMTP server was specified (Edit -> Options, Email). Check your email client to see what it’s using for an SMTP server, or talk to your system administratory.
  • There is a firewall or antivirus package running that’s aborting the SMTP conversation. This might be something running on your machine (like Norton Antivirus), or some hardware firewall that does stateful inspection. If other software works, but PingPlotter/MultiPing does not, then it’s probably local to your machine – something that is filtering by which application is sending data.
  • There might be something wrong with the SMTP server. Try using another email client and make sure the same SMTP server works with that.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *