Windows sockets error code 10053

Some Windows users are encountering the 10053 error code while trying to connect their computer with an SMTP mail or when trying to perform a Winsock command. This problem is typically linked to router restrictions, overprotective firewalls or Proxies, and VPNs.

After investigating this particular issue, it turns out that there are several different causes that might be causing this error code. Here’s a shortlist of potential culprits:

Method 1: Disabling or Uninstalling Overprotective AV suites (if applicable)

If you’re using a 3rd party suite you’re encountering the 10053 error code when trying to perform a certain action having to do with your email client (like downloading or sending email via VPOP3), chances are this issue is being caused by your antivirus software.

According to some affected users, this problem is often caused by certain versions of McAfee VirusScan and Norton Antivirus – These are just two 3rd party AV that we discovered, but there might be other software causing the same kind of problem.

If this scenario looks like it could be applicable, you should start by disabling the real-time protection and seeing if the error code stops occurring – with most AV suites, you can disable the real-time protection by right-clicking the tray-bar icon and looking for an option that will disable the real-time shields.

If disabling the real-time protection didn’t end up fixing the issue, follow the instructions below to uninstall the problematic suite from your computer and clear any remnant file to fix the problem:

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘appwiz.cpl’ inside the text box and press Enter to open up the Programs and Files menu.
2. Once you’re inside the Programs and Features menu, scroll down through the list of installed programs and locate the problematic Antivirus or Firewall solution that’s causing the conflict.
3. When you see it, right-click on it and choose Uninstall from the newly appeared context menu to begin the uninstallation process.
4. Once the operation is complete, reboot your computer and wait for the next startup to complete.
5. After your computer boots back up, follow the instructions specific to your Antivirus to remove any remnant files left behind by your 3rd party Antivirus installation.
6. Once you manage to completely remove your 3rd party security suite from your AV, move down to the next potential fix below.

If the same problem still occurs after uninstalling your 3rd party suite or this method is not applicable, move down to the next potential fix below.

Method 2: Performing a Complete TCP / IP reset

If the 10053 error code occurs right after the TCP / IP connection is aborted by Windows, this is most likely a problem with the data transmission timeout or protocol error. As it turns out, this is most likely caused by a glitch with the network adapter or a classic case of bad DNS range.

According to some affected users, this problem can sometimes be fixed by performing a complete TCP / IP reset on every computer that’s part of the local workshop.

If you’re not sure how to do this, follow the instructions below to perform a complete TCP / IP reset from an elevated Command Prompt:

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘cmd’ inside the text box and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Once you’re inside the elevated Command Prompt, type the following commands in order and press Enter after each one to do a complete TCP / IP reset:

   ipconfig /flushdns
   nbtstat -R
   nbtstat -RR
   netsh int reset all
   netsh int ip reset
   netsh winsock reset

3. After every command is processed successfully, close the elevated Command Prompt and reboot your computer.
4. Once the next startup is complete, repeat the action that was previously causing the 10053 error code and see if the problem is now fixed.

Method 3: Rebooting or Resetting your router/modem

If the Winsock commands above didn’t fix the problem in your case, you should proceed by excluding your current network from the list of potential culprits.

According to some affected users, this problem is also expected to occur in instances where your ISP (Internet Service Provider) assigns a dynamic IP that conflicts with certain SMTP options.

In case this scenario is applicable, there are 2 ways to fix the problem and avoid getting the 10053 error code:

• Restarting the network device – This operation will end up refreshing the TCP and IP connection and force your router/modem to assign new information related to your connection.
• Resetting the network device – This will clear any custom settings your router or modem is currently enforcing and return your network device to its factory settings.

If you’re planning or enforcing this method, our advice to start with a simple restart and move out to the second procedure only if the first sub-guide (A) doesn’t fix the problem:

A. Restarting your router/modem

If you want to fix the problem without resetting any sensitive data that’s currently stored by your router or modem, this is the way to do it.

In order to perform a router reboot (restart), turn your attention to the rear part of your network device and press the On / Off button to power off the device. After you do this, also disconnect the power cable from the power outlet it’s currently connected to and wait for a full minute in order to ensure that the power capacitors are completely drained.

After you manage to restart your router, make sure to disconnect the power cable and wait for a full minute to ensure that the power capacitors are completely drained before restoring power.

Once the period is passed, re-connect the power cable and wait until the Internet access is re-established before repeating the action that was causing the error code before.

If the same problem is still occurring, move down to the next potential fix below.

B. Resetting your router/modem

If the first method didn’t work in your case, chances are you’re dealing with a more serious inconsistency that is rooted inside the settings menu of your router or modem.

In this case, you should reset your router or modem to its factory state, restore internet access, and see if this operation ends up fixing the 10053 error.

Important: Before you enforce this operation, keep in mind that it will end up clearing any settings that you have previously established for your router. This will include any saved PPPoE credentials, whitelisted or blocked posts, and forwarded TCP / IP data.

To initiate a router or modem reset, look for the reset button (typically located on the back of your router). When you manage to locate it, press the Reset button and keep it presses for 10 seconds or until you notice all the device LEDs flashing at the same time.

Note: With most router models, you will need a sharp object in order to be able to press and hold on the Reset button.

After the reset procedure is complete, wait until the Internet access is re-established, then see if the 10053 error code is now fixed. Keep in mind that if your ISP is using PPPoE, you will need to re-insert the correct credentials before Internet access is restored.

If this scenario was not applicable or you already tried this with no success, move down to the next potential fix below.

Method 4: Disable Proxy or VPN connection (if applicable)

If none of the methods above have fixed the issue in your case and you’re using a VPN client or a Proxy server to hide the origin of your connection, this is most likely the source of the 10053 error.

We managed to find a lot of user reports claiming this particular error was caused either by a VPN client or a proxy server that was enforced at a system level.

Depending on the anonymity solution that you’re using, you should be able to fix the problem either by disabling the proxy server or by uninstalling the system level VPN altogether.

We’ve covered both potential scenarios, so feel free to follow one of the sub-guides below to either disable the system-level proxy server or uninstall the VPN client:

A. Uninstalling System-level VPN

1. Press Windows key + R to open up a Run dialog box. Once you’re inside, type ‘appwiz.cpl’ inside the text box and press Enter to open up the Programs and Features menu. When you are prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Once you’re inside the Programs and Features screen, find the VPN client among the list of installed applications. When you find it, right-click on it and choose Uninstall from the newly appeared context menu.
3. From the insides of the installation screen, follow the on-screen prompts to complete the installation process, then reboot your computer once the operation is complete and see if the issue is fixed once the next startup is complete.

B. Disabling the Proxy Server

1. Open up a Run dialog box by pressing Windows key + R. Inside the text box, type ‘inetcpl.cpl’ and press Enter to pen up the Internet Properties tab. When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Once you’re inside the Internet Properties screen, go over the Connection tab from the horizontal menu on the top of the screen, then click on LAN Settings (right under Local Area Network LAN settings).
   
3.  Once you’re inside the Local Area Network (LAN) settings, access the Proxy server category and uncheck the box associated with Use a proxy server for your LAN.
   
4. After you have successfully disabled the Proxy server, reboot your computer and see if the problem is fixed once the next startup is complete.

Рекомендации по локализации причины ошибки 10053

Приведем описание ошибки:

Описание Беркли : Произошел разрыв соединения на локальном компьютере. Причиной разрыва послужило отсутствие места в очереди сокета, вследствие чего сокет не может принимать данные.

Описание Winsock : Эта ошибка может возникнуть, когда обрывается связь в локальной сети. WinSock обрывает установившееся соединение после неудачной попытки повторной передачи данных (получатель не получает подтверждения отправки данных).

Протоколы обмена почтовыми сообщениями (SMTP и POP3) для передачи данных используют прикладной протокол TCP. Для повышения надежности передачи данных протокол TCP ожидает подтверждения на каждый отправленный пакет данных. Иногда пакеты подтверждения могут теряться. В таком случае TCP будет отправлять не доставленные пакеты повторно, автоматически увеличивая время ожидания подтверждения, до тех пор, пока не истечет некоторый промежуток времени. По его истечении генерируется данная ошибка. Происхождение этой ошибки можно описать так: она возникает в том случае, когда локальный хост в течение длительного времени не получает подтверждения отправки пакета.

Подобная ошибка может возникать по множеству разнообразных причин. Приведем некоторые рекомендации по локализации источника проблемы:

• Воспользуйтесь утилитой ping для проверки соединения с удаленным хостом, на который отправляется почтовое сообщение. Если ответа нет, возможно, хост отключен от сети или имеются проблемы в сети на пути доставки сообщения. Если ответ есть, то, возможно, ошибка носит кратковременный характер. Попытайтесь отправить почтовое сообщение еще раз. Если сообщение по-прежнему не отправляется, то, возможно, что принимающий сервер не готов к его приему (например, на запущено приложение, отвечающее за прием сообщений на сервере).
• Воспользуйтесь утилитой ping для проверки соединения с локальным хостом для проверки функциональности локальной сети.
• Воспользуйтесь утилитой ping для проверки соединения с локальным маршрутизатором.
• Воспользуйтесь утилитой ping для проверки соединения с хостом подсети, в которую отсылается почтовое сообщение (если известен адрес). Это позволит установить факт работоспособности сети получателя.
• Воспользуйтесь утилитой tracert , в качестве параметра укажите хост, на который отправляется почтовое сообщение. Возможно, это поможет идентифицировать проблему на пути следования пакетов данных.

Источник

How to Fix Asynchronous Socket Error 10053 on Windows Operating System?

Some Windows users are encountering the 10053 error code while trying to connect their computer with an SMTP mail or when trying to perform a Winsock command. This problem is typically linked to router restrictions, overprotective firewalls or Proxies, and VPNs.

Asynchronous Socket Error 10053

After investigating this particular issue, it turns out that there are several different causes that might be causing this error code. Here’s a shortlist of potential culprits:

• Connection abort caused by your machine – As it turns out, this problem might occur because there is no space in the socket’s queue, so the socket cannot receive further connection. This type of issue is often related to an active Proxy or VPN network that end up taking up all the precious socket queue. In this case, disabling or uninstalling the Proxy server or VPN client should allow you to fix the issue.
• Recently aborted connection – Under certain circumstances, this problem can also occur if the local network system aborts a connection after data transmission fails. In this case, the receiver never acknowledges data sent on a data socket. This is typically caused by an overprotective antivirus or firewall.
• TCP / IP scenario – A troublesome connection can also be responsible for this error code if it timeouts after the local system doesn’t receive an acknowledgment for data sent. If this scenario is applicable, resetting your TCP / IP data should fix the problem and eliminate the error code. If this doesn’t work, you should reboot or reset your router or modem instead.

Method 1: Disabling or Uninstalling Overprotective AV suites (if applicable)

If you’re using a 3rd party suite you’re encountering the 10053 error code when trying to perform a certain action having to do with your email client (like downloading or sending email via VPOP3), chances are this issue is being caused by your antivirus software.

According to some affected users, this problem is often caused by certain versions of McAfee VirusScan and Norton Antivirus – These are just two 3rd party AV that we discovered, but there might be other software causing the same kind of problem.

If this scenario looks like it could be applicable, you should start by disabling the real-time protection and seeing if the error code stops occurring – with most AV suites, you can disable the real-time protection by right-clicking the tray-bar icon and looking for an option that will disable the real-time shields.

Right Click Avast Icon From System Tray To Disable Avast Temporarily

If disabling the real-time protection didn’t end up fixing the issue, follow the instructions below to uninstall the problematic suite from your computer and clear any remnant file to fix the problem:

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘appwiz.cpl’ inside the text box and press Enter to open up the Programs and Files menu. Type appwiz.cpl and Press Enter To Open Installed Programs Page
2. Once you’re inside the Programs and Features menu, scroll down through the list of installed programs and locate the problematic Antivirus or Firewall solution that’s causing the conflict.
3. When you see it, right-click on it and choose Uninstall from the newly appeared context menu to begin the uninstallation process. Uninstalling your antivirus
4. Once the operation is complete, reboot your computer and wait for the next startup to complete.
5. After your computer boots back up, follow the instructions specific to your Antivirus to remove any remnant files left behind by your 3rd party Antivirus installation.
6. Once you manage to completely remove your 3rd party security suite from your AV, move down to the next potential fix below.

If the same problem still occurs after uninstalling your 3rd party suite or this method is not applicable, move down to the next potential fix below.

Method 2: Performing a Complete TCP / IP reset

If the 10053 error code occurs right after the TCP / IP connection is aborted by Windows, this is most likely a problem with the data transmission timeout or protocol error. As it turns out, this is most likely caused by a glitch with the network adapter or a classic case of bad DNS range.

According to some affected users, this problem can sometimes be fixed by performing a complete TCP / IP reset on every computer that’s part of the local workshop.

If you’re not sure how to do this, follow the instructions below to perform a complete TCP / IP reset from an elevated Command Prompt:

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘cmd’ inside the text box and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When prompted by the UAC (User Account Control), click Yes to grant admin access. Running the Command Prompt
2. Once you’re inside the elevated Command Prompt, type the following commands in order and press Enter after each one to do a complete TCP / IP reset:
3. After every command is processed successfully, close the elevated Command Prompt and reboot your computer.
4. Once the next startup is complete, repeat the action that was previously causing the 10053 error code and see if the problem is now fixed.

Method 3: Rebooting or Resetting your router/modem

If the Winsock commands above didn’t fix the problem in your case, you should proceed by excluding your current network from the list of potential culprits.

According to some affected users, this problem is also expected to occur in instances where your ISP (Internet Service Provider) assigns a dynamic IP that conflicts with certain SMTP options.

In case this scenario is applicable, there are 2 ways to fix the problem and avoid getting the 10053 error code:

• Restarting the network device – This operation will end up refreshing the TCP and IP connection and force your router/modem to assign new information related to your connection.
• Resetting the network device – This will clear any custom settings your router or modem is currently enforcing and return your network device to its factory settings.

If you’re planning or enforcing this method, our advice to start with a simple restart and move out to the second procedure only if the first sub-guide (A) doesn’t fix the problem:

A. Restarting your router/modem

If you want to fix the problem without resetting any sensitive data that’s currently stored by your router or modem, this is the way to do it.

In order to perform a router reboot (restart), turn your attention to the rear part of your network device and press the On / Off button to power off the device. After you do this, also disconnect the power cable from the power outlet it’s currently connected to and wait for a full minute in order to ensure that the power capacitors are completely drained.

Rebooting Router

After you manage to restart your router, make sure to disconnect the power cable and wait for a full minute to ensure that the power capacitors are completely drained before restoring power.

Once the period is passed, re-connect the power cable and wait until the Internet access is re-established before repeating the action that was causing the error code before.

If the same problem is still occurring, move down to the next potential fix below.

B. Resetting your router/modem

If the first method didn’t work in your case, chances are you’re dealing with a more serious inconsistency that is rooted inside the settings menu of your router or modem.

In this case, you should reset your router or modem to its factory state, restore internet access, and see if this operation ends up fixing the 10053 error.

Important: Before you enforce this operation, keep in mind that it will end up clearing any settings that you have previously established for your router. This will include any saved PPPoE credentials, whitelisted or blocked posts, and forwarded TCP / IP data.

To initiate a router or modem reset, look for the reset button (typically located on the back of your router). When you manage to locate it, press the Reset button and keep it presses for 10 seconds or until you notice all the device LEDs flashing at the same time.

Resetting Router

Note: With most router models, you will need a sharp object in order to be able to press and hold on the Reset button.

After the reset procedure is complete, wait until the Internet access is re-established, then see if the 10053 error code is now fixed. Keep in mind that if your ISP is using PPPoE, you will need to re-insert the correct credentials before Internet access is restored.

If this scenario was not applicable or you already tried this with no success, move down to the next potential fix below.

Method 4: Disable Proxy or VPN connection (if applicable)

If none of the methods above have fixed the issue in your case and you’re using a VPN client or a Proxy server to hide the origin of your connection, this is most likely the source of the 10053 error.

We managed to find a lot of user reports claiming this particular error was caused either by a VPN client or a proxy server that was enforced at a system level.

Depending on the anonymity solution that you’re using, you should be able to fix the problem either by disabling the proxy server or by uninstalling the system level VPN altogether.

We’ve covered both potential scenarios, so feel free to follow one of the sub-guides below to either disable the system-level proxy server or uninstall the VPN client:

A. Uninstalling System-level VPN

1. Press Windows key + R to open up a Run dialog box. Once you’re inside, type ‘appwiz.cpl’ inside the text box and press Enter to open up the Programs and Features menu. When you are prompted by the UAC (User Account Control), click Yes to grant admin access. Type appwiz.cpl and Press Enter To Open Installed Programs Page
2. Once you’re inside the Programs and Features screen, find the VPN client among the list of installed applications. When you find it, right-click on it and choose Uninstall from the newly appeared context menu. Uninstalling a VPN tool
3. From the insides of the installation screen, follow the on-screen prompts to complete the installation process, then reboot your computer once the operation is complete and see if the issue is fixed once the next startup is complete.

B. Disabling the Proxy Server

1. Open up a Run dialog box by pressing Windows key + R. Inside the text box, type ‘inetcpl.cpl’ and press Enter to pen up the Internet Properties tab. When you’re prompted by the UAC (User Account Control), click Yes to grant admin access. Run dialog: inetcpl.cpl
2. Once you’re inside the Internet Properties screen, go over the Connection tab from the horizontal menu on the top of the screen, then click on LAN Settings (right under Local Area Network LAN settings).
   

Open LAN settings in Internet Options
Once you’re inside the Local Area Network (LAN) settings, access the Proxy server category and uncheck the box associated with Use a proxy server for your LAN.

Disabling the Proxy server

Источник

Socket Error 10053 — An established connection was aborted by the software in your host machine.

I have a Server and a Client Application, both on the same System.

The client connects to the system via a TCP-Socket, which works fine.
The Server has a loop in which it keeps accepting clients on a non-blocking listen socket.

The function body for the accepting loop:

std::unique_ptr<Connection> p_conn(nullptr);
    		bool connection_establish_pending = false;
    
    		while(!StopCondition_)
    		{
    			if(!connection_establish_pending)
    				p_conn.reset(new Connection);
    
    			// accept new connection
    			auto stat = p_conn->Accept(ListenSocket_);
    			if(stat == Connection::Error)
    				break;	// listen socket is unusable
    			if(stat  == Connection::Wouldblock)
    			{
    				connection_establish_pending = true;
    				std::this_thread::sleep_for(std::chrono::milliseconds(300));
    				continue;
    			}
    			// connection has been established
    			connection_establish_pending = false;
    			
    			// create client handling thread
    			std::thread t(_connection_handler_thread, p_conn.release(), this);
    			this->ThreadList_.push_back(std::move(t));	// add to list
    		}

void ConnectionHandler(std::unique_ptr<Connection> pConn)
    {
    	Message msg;
    	std::vector<char> buf;
    
    	try
    	{
    		// main loop
    		while(pConn->Recv(msg))		// receive a message
    		{
    			switch(msg.RequestCode())
    			{
    			case 1:
    				{
    					// prepare answer msg...
    					pConn->Send(msg);
    				}
    				break;
    			case 2:
    				// ...
    			}
    		} // while(recv)
    	}
    	catch(...)
    	{
    	}
    }

  std::string ip = "localhost", port = "12345";

            // Connect to server
            cout << "Establishing connection..." << endl;;
            Server.Connect(ip, port);
            cout << "Connection established to: " << ip << ":" << port << endl;

            /* Send a message to host*/
            const char Data[] = "Counter"; const size_t data_size = strlen(Data);
            cout << "Sending Message "" << Data << """ << endl;
            auto ret = Server.SendRequest(1, Data, data_size);
            if(!ret)
                cout << "Connection closed serverside" << endl;
            else
            {
                if(!Server.RecvAnswer(rq, vecData))
                    cout << "Connection closed serverside" << endl;
                else
                {
                    cout << "Answer:ntCode = " << rq  << "ntData:" << std::string(vecData.data(), vecData.size()) << endl;
                }

                // Now try to get the module info for "Counter"
                cout << "Requesting module info now... " << endl;
                ret = Server.SendRequest(2, Data, data_size);
                if(!ret)
                    cout << "Connection closed serverside" << endl;
                else
                {
                    if(!Server.RecvAnswer(rq, vecData))
                        cout << "Connection closed serverside";
                    else
                        cout << "Answer:ntCode = " << rq  << "ntData:" << std::string(vecData.data(), vecData.size()) << endl;
                }

            }

 //prepare a buffer to be used in calls to 'recv'
        std::unique_ptr<char[]> pBuf(new char[BytesToRecv]);

        int Ret = 0;
    size_t BytesReceived = 0;


    do
    {
        //clear the buffer
        memset(pBuf.get(), '', BytesToRecv);

        Ret = recv(Get(), pBuf.get(), BytesToRecv - BytesReceived, 0);
        if(Ret == 0)    // Graceful shutdown
            return Status::Closed;
        if (Ret == SOCKET_ERROR)
        {
            auto ret_code =  GetErrorStatus();    // Wouldblock, Disconnected/Unreachable, Aborted
            if(ret_code == Status::Error)
                throw(socket_exception(Get(), "Failed to recv"));
            return ret_code;
        }


        //Append to the Data-Buffer
        //Data.append(inc::StringToWString(std::string(pBuf.get(), Ret)));
        memcpy_s(&pData[BytesReceived], BytesToRecv - BytesReceived, pBuf.get(), Ret);


        //Count bytes received
        BytesReceived += static_cast<size_t>(Ret);


        //reset the return code
        Ret = 0;

    } while (BytesReceived < BytesToRecv);

size_t total = 0;                //total sent
        size_t bytesleft = DataSize;    //bytes left to be sent
        int ret = 0;

        //as long as there is data to send...
        while (total < DataSize)
        {
            //...send what's left
            ret = send(Get(), pData + total, bytesleft, 0);
            if(ret == SOCKET_ERROR)
            {
                auto ret = GetErrorStatus();    // Aborted, Wouldblock, Unreachable/Disconnected
                if(ret == Status::Error)
                    throw(socket_exception(Get(), "Failed to send"));
                return ret;
            }

            total += ret;
            bytesleft -= ret;
        }

 bool RecvAnswer(request_type& Request, std::vector<char>& vecData)
    {
        Message Msg;
        if(!pimpl->Connection_.Recv(Msg))
            return false;

        vecData = Msg.Data();
        Request = Msg.RequestCode();

        return true;
    }

The problem that occurs is, that when i run the client without breakpoints, step-through, etc it successfully sends the first request and receives data from the server. After the second request when i call recv it returns the 10053-Error.

Funnily, when i step through the code i get the 10053-error right on the first call to recv.

Turning off firewall and antivirus software does not help.

Strange thing to me is, that it workswhen i put the listening(!) socket into blocking mode.

Any help would be greatly appreciated.

Thank You!

If required, i could also add someone to my visualstudio.com-project (if she/he as an visualstudio-account) so the full code could be read.