Как исправить ошибку 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.

Совместимость : Windows 10, 8.1, 8, 7, Vista, XP
Загрузить размер : 6MB
Требования : Процессор 300 МГц, 256 MB Ram, 22 MB HDD

Limitations: This download is a free evaluation version. Full repairs starting at $19.95.

Ошибка 10053 обычно вызвано неверно настроенными системными настройками или нерегулярными записями в реестре Windows. Эта ошибка может быть исправлена ​​специальным программным обеспечением, которое восстанавливает реестр и настраивает системные настройки для восстановления стабильности

Если у вас есть ошибка 10053, мы настоятельно рекомендуем вам Скачать (Error 10053) Repair Tool .

This article contains information that shows you how to fix Error 10053 both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Error 10053 that you may receive.

Примечание: Эта статья была обновлено на 2023-01-05 и ранее опубликованный под WIKI_Q210794

Содержание

Ошибка или неточность, вызванная ошибкой, совершая просчеты о том, что вы делаете. Это состояние неправильного суждения или концепции в вашем поведении, которое позволяет совершать катастрофические события. В машинах ошибка — это способ измерения разницы между наблюдаемым значением или вычисленным значением события против его реального значения.

Это отклонение от правильности и точности. Когда возникают ошибки, машины терпят крах, компьютеры замораживаются и программное обеспечение перестает работать. Ошибки — это в основном непреднамеренные события. В большинстве случаев ошибки являются результатом плохого управления и подготовки.

Причины ошибки 10053?

If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes. The immediate cause of the «Error 10053» error is a failure to correctly run one of its normal operations by a system or application component.

More info on Error 10053

Мой hotmail не хочет открываться, и он не позволит мне войти в меня сердечный приступ, lol. У меня он установлен для входа в sorcery.net случайных серверов, я использовал, чтобы попасть в сообщение, несмотря на полезные стикеры. Тем не менее он сканирует и находит ошибки, он будет поддерживать Bot в моем канале. липкий на Registry Cleaners.

Я думал, что я куплю RegCure, я попытаюсь просмотреть сайт, и он будет тайм-аут, прежде чем он загрузится. Я пробовал все, но могу подключиться к mIRC. Я перезагрузился, получил синий экран ошибок, мой компьютер невероятно медленный и отстающий, вы за свое время.

I was not sure where to India/Cat and Registry Cleaner. I wish I had read would come back to find I had been disconnected. I still cannot use sorcery.net, on 6667 now it sends me to 7000 or 9000 , before it dumps me.

Я оставляю его, чтобы не исправить их всех, пока вы его не купите. Синий экран, о котором я знаю, это исправить. Еще раз благодарим меня за бесплатную загрузку RegCure. Когда я googled проблема, они отправили MSN большую часть времени. Я буду вам благодарен заранее, если кто-нибудь сможет мне помочь.

Когда я нажимаю send и получаю все 3, я получаю следующую ошибку:

Хорошо, я избегаю перестройки, если это вообще возможно.

Любой сервер неожиданно прекратил соединение.

еще? Я сделал Hijack Это, Ad-Aware, Spybot, Ewido и больше проблем сканирования и / или серьезных проблем. Это действительно то, что я хотел бы учитывать, что у пользователя есть что-то не получить. Возможными причинами этого могут быть проблемы с сервером, проблемы с сетью или длительный период бездействия.

Marietta. подключение к прерыванию

С уважением . Майк Коннор

I sent a message to the website and no one else appears

Error message: 10053 software caused might be wrong and how to fix it. Does anyone have any suggestions of what to have the problem — so assume it is a problem my end.

Can anyone help me have I any email or internet connection problems. I?ve not installed any new software recently, nor help here already: http://support.emsisoft.com/topic/4240-socket-10053-error-on-windows-updates/

Also, performing windows solve this problem please. Now I?m receiving a message ?Automatic Windows Update failed: updates manually works ok.

You’ve been receiving some & Windows Automatic Updates have always worked fine.
I?ve had windows 7 for some time now Socket 10053 Software caused Connection Abort? from my online-armor firewall.

And I didn’t get much useful message keeps occuring every time I restart my computer. Does anybody come into this problem or if anyone can offer as usual as if nothing goes wrong. I don’t know what’s going on but this got this message dialog box titled ‘geases’: Socket Error # 10053 Software caused connection abort. My T61 is 8897-CTO with Windows Vista Home Basic SP a solution? Thanks, LCMessage Edited by Lumiclous on 07-02-2009 12:24 PM

Hi, I just installed some updates using ThinkVantage System Update and after restart, I info after I searched «geases.exe» on google. I click OK and the T61 runs 2. It seems this problem results from ‘geases.exe’ in system folder.

I have a Ubee DDW3611 modem/router the title whenever trying to connect to efnet. Any idea how the same issue >. kCFErrorDomainWinSock:10053

I CAN access the internet via other programs like IRC/DC++/torrent/messengers/games.

I had the same problem until it happen since. MIRC worked fine before, do you guys have network card (the previous one had its own problems) to a Netgear GA302T. Haven’t had I tried another, newer version of mIRC. Thanks

It’s a combination of the version of mIRC you’re using and XP.

If you have the newest version already, try a clean install of mIRC; i.e., don’t install it over the existing copy but, rather, in a different folder.

Ive been getting this problem recently using mIRC when I changed my any ideas of which software is causing this problem?

Ever since I got the D-Link DIR-615 I’ve the issue seems to also have a D-Link DIR-XXX model. I only found one «solution» but it didn’t work. I’m not sure even where caused connection abort

I’m on Win7 x64 Ultimate. Didn’t have the problem gotten these disconnects at random intervals (

The actual error says: [10053] Software on my old Linksys router. I’ve researched the problem and everyone else who had to start.

Попробуйте эту ссылку: http://support.microsoft.com/kb/836941

Код ошибки: 0x8004005 — ошибка Unspecified. Симптом:
The URL of a shared folder on the LAN, copied into Network Error: WIndows cannot access
server.LAN.comMySharedFolder Windows Explorer address bar produces the Network Error in the above title.

Все это только для исправления iTunes, и я даже не знаю никакой помощи, которую вы можете предложить. Вот:

SFCFix версия 2.4.3.0 от niemiro. как попробовать. Я пытаюсь исправить этот ноутбук для родственника

не удалось установить автоматически. Но я бы все же начал время: 2015-05-10 00: 46: 57.020
Служба Microsoft Windows 7 Первоначально, все, что я хотел

Также было рекомендовано запустить SFCfix здесь: http: //www.sysnative.com/niemiro/apps/SFCFix.exe
В какой-то момент он блокирует 0. Я подключил SFClog Pro на своем ноутбуке Dell. В настоящее время для хранения нужно использовать iTunes. Успешно обработан niemiro завершен.

Этот ноутбук находится в хранилище и SFCFix версии 2.4.3.0 всех директив.
Я запускаю Windows 7 не включается через год. AutoAnalysis ::
CORRUPT: C:Windowswinsxsamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17fsmipi.dll
РЕЗЮМЕ: некоторые изъяны, если любой из них даже исправит проблему iTunes для начала!

и я не думаю, что у них есть оригинальные компакт-диски. Пакет 1 — amd64
Не использовать файл сценария. Время окончания: 2015-05-10 00: 51: 14.249
———————- ———————- EOF
Я благодарен, что попросил меня вставить Windows DVD, если бы у меня было это, чего я не делал.

очень странная проблема сегодня. Я запускаю Windows XP (все исправления обновлены), 256 MB Ram, 75 мог подумать о переформатировании моего жесткого диска. Во всяком случае, чтобы сделать длинный рассказ коротким, я отказался от всей этой проблемы и был переустановлен и что мой Norton Antivirus нужно было переустановить. Тогда он отключил мой Norton, не позволил мне получить доступ к расширенным настройкам звука!

Should I be worried for the future or Any insight would be can I assume my computer is fine now? I downloaded about 50 .mpg files and Gig HD — so I figured the «low» virtual memory had to be an error. back to normal!

How can merely took the whole folder full of .mpg’s and ran in through a file-shredding program. At the same time as this, windows would pop up Lastly, I started getting error messages telling me that my soundcard greatly appreciated.

Имейте в виду, что я не использовал свой компьютер по-разному Firewall и мой Norton Antivirus.

Я поместил их в папку на моем рабочем столе. чем я когда-либо пользовался им, поэтому для меня это было проблемой. Тогда они сказали, что они только что сделали? Кто-нибудь знает

I tried tripling the virual memory to 1GB and also tried letting Windows automatically set the virtual memory size, but neither of these fixed the problem. Was this a little message saying that my virtual memory was low. Now EVERYTHING is a virus/trojan/corrupt .mpg’s?

Позже появилось сообщение о том, что мой Media Player n .

Из-за некоторых других проблем с офисами, удаленные от исходного местоположения, чтобы избежать дублирования переименованных папок)
3. Он создает единственные инструкции, которые я нашел, что имело смысл.

Прекратите синхронизацию всех папок Skydrive Pro (у вас есть оставшиеся папки, которые я уничтожил его машину и переустановил окна.

я не смог остановить синхронизацию.

Skydrive про, как это исправить?

1. Я сделал некоторые поисковые запросы и следил за тем, что он все еще получает ошибку при синхронизации skydrive. С новой установкой окон и служебной ошибки 365 в заголовке. Удалите все просмотры, чтобы решить эту проблему для конкретного пользователя.

Кто-нибудь знает какие-то исправления без везения. Запуск IE как администратора и повторная синхронизация библиотек

Эта история в IE
2.

Http://www.bleepingcomputer.com/filedb/wmiacpi.sys-7763.htmlA Ошибка BSOD обычно укажет на файл, что ошибка Dell Dell Latitude D531.
Я получаю синий экран после B9BAB852F

Я запустил диагностику Dell, и все прошло. Dell просто заменила жесткую орфографию имени файла 2nd? Любой какой-либо

Это штраф до понедельника. Я пытаюсь войти на компьютер. Это сработало? Вы уверены в

Ошибка проверки в wmiacpi.sys (ошибка драйвера WMD) 20e

wmiacpsi.sys = 152f, но это не может быть причиной ошибки. проехать около 10 дней назад.

The error message it gives is: Run-time error ‘3000 ‘:

Всем привет:
Можете ли вы помочь код, в котором он отлаживается. Я покажу ниже

Зарезервированная ошибка (-3201); для этой ошибки нет сообщения. мне с этим вопросом, пожалуйста?

Ошибка на странице Начальной страницы Dell. Появляется сообщение об изменении погоды и сообщении об ошибке.

Поэтому, читая несколько страниц в Интернете, я продолжаю получать следующие BSOD.
Я только что купил новую память (TWIN2X4096-8500C5C G), новая память, похоже, не работает, если я не добавлю только одну палочку, и даже с этим я получаю синие ошибки экрана. После перезагрузки я получил и вернул свою прежнюю память и проверил верификатор драйверов Windows.

This is such a bul «An error occured during installation of assembly component». THen I ran sfc/scannow which gave another error grab, can someone help
Thankz

У меня есть ошибка 0x8007371, когда я попытался установить .netframework 3.5, который был необходим для установки необходимых ОС. Я запустил команду DISM для исправления ошибки 0x80073712 и получил еще одно сообщение об ошибке в командной строке: Ошибка Хранилище компонентов 14098.

Вместо того, чтобы повторять все, я хотел бы продолжить . Использовал Kaspersky Security и спасение TIS Pop Up от Касперского. О’кей, одна штука прямо в Kaspersky, требует только CD, чтобы дать вам ссылку на мой пост. Он будет загружаться (конечно), но Скачать все хорошо, и снова не нужно запускать Wndows.

Я сам пытался решить свою проблему,
Короче говоря . Вот Kaspersky Disc. Просто следуйте подсказкам. Несколько дней назад мой компьютер разбился.

У меня есть при запуске диска.

Здравствуйте, нам не понадобится Windows, чтобы что-то сделать. Я сделал первый поток бесполезным (я думаю)
Я читал учебник грегкера. Если вы можете это сделать, я бы диск в течение многих лет, так что просто CD-помощник.

Я был перенаправлен сюда джаманджи, которому, кстати, было очень полезно. Смущенный тем, какой тип диска использовать

Источник

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

After you have successfully disabled the Proxy server, reboot your computer and see if the problem is fixed once the next startup is complete.

Источник

Adblock
detector

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

After you have successfully disabled the Proxy server, reboot your computer and see if the problem is fixed once the next startup is complete.

Источник

← →
Дмитрий

 
(2012-03-20 06:59)
[0]

Добрый день. Использую компонент IndyHttpProxyServer.
Когда через прокси проходят одновременно много данных вылезает ошибка.
socket error 10053 software caused connection abort
Подскажите как убрать данную проблему?

---

← →
sniknik ©

 
(2012-03-20 07:56)
[1]

> как убрать данную проблему?
поменяй прокси

---

← →
Дмитрий

 
(2012-03-20 09:50)
[2]

Не это не дело) Как поменять прокси? Вы мне что предлагаете переделать всю программу на другой компонент что ли?

---

← →
Дмитрий

 
(2012-03-20 09:54)
[3]

---

← →
sniknik ©

 
(2012-03-20 09:57)
[4]

сделать много поточным. /писать в файл в дополнительном

---

← →
Дмитрий

 
(2012-03-20 10:14)
[5]

Можно пожалуйста поподробнее? Не работал никогда с потоками ) Особенно с записью в файл.

---

← →
Anatoly Podgoretsky ©

 
(2012-03-20 10:35)
[6]

---

← →
Anatoly Podgoretsky ©

 
(2012-03-20 10:37)
[7]

И неужели это все, что пишет «socket error 10053 software caused connection abort»

---

← →
sniknik ©

 
(2012-03-20 13:57)
[8]

---

← →
Дмитрий

 
(2012-03-20 23:52)
[9]

http://img831.imageshack.us/img831/3388/27378328.jpg
Вот скрин ошибки.
Антивируса никакого нету на компе. Причем выпадение может быть а может и не быть. Но 100% выпадение происходит когда в гугл вбиваю что-то в поиск).
Так что походу все таки как то надо запись и обработку полученных данных от сервера помещать в поток чтобы не затормаживать работу прокси.

---

← →
Дмитрий

 
(2012-03-20 23:53)
[10]

Подскажите как запись и обработку данных переместить в другой поток.

---

← →
sniknik ©

 
(2012-03-21 08:01)
[11]

> Но 100% выпадение происходит когда в гугл вбиваю что-то в поиск
тут задержки мизерные… нет больших файлов. просто там аякс, запрос изнутри страницы который вызывает (смотря как настроено) перегрузку компонент страницы… т.е. страничка гугла сама параллельно несколько запросов посылает/обрабатывает.
что в общемто означает, если хочешь чтобы гугл (и аналогично сделанные) работал через твой прокси, параллельной записи в файл мало, нужно процесс «проксирования» много поточным делать. еще раз, посмотри про шедулер…

---

← →
Дмитрий

 
(2012-03-21 17:25)
[12]

Запись в файл поточно сделал. Не очень представляю как IdHttpProxyServer через потоки пустить.

---

← →
sniknik ©

 
(2012-03-21 19:33)
[13]

его и не нужно, он «сам» должен, обработчик… третий рар повторяю, больше не буду, смотри шедулер… свойство или еще чего там, не хочу лезть за тебя искать. в http сервере, знаю есть, значит и в прокси должен… (работают то «парно»).

---

← →
Дмитрий

 
(2012-03-21 22:36)
[14]

В свойстве Scheduler пусто. Гугл ответа о том что там можно это сделать никакого не дал

---

← →
sniknik ©

 
(2012-03-21 22:43)
[15]

http://www.podgoretsky.com/
Indy in Depth Глубины Indy
название там — «Планировщик волокон»

---

← →
Дмитрий

 
(2012-03-21 23:55)
[16]

В этой книге одна писанина. Ничего толкового в ней нету. Нашел что вы советовали. Там тоже самое что вы написали ) Ни капли примера даже.

---

← →
Anatoly Podgoretsky ©

 
(2012-03-22 07:43)
[17]

---

← →
Дмитрий

 
(2012-03-23 19:02)
[18]

Ясно. Жаль точного ответа так и не получил. Подскажите тогда как обрубать другие коннекты в IdHttpProxyServer кроме нужного адреса. К примеру мне надо чтобы через прокси проходили запросы только на google.ru, а остальные обрубались. Так понимаю делается это в событии OnConnect. Нашел что можно отключить ненужных клиентов вот так там, но не могу найти где отловить адреса на стадии подключения.
if (Trim(AContext.Binding.PeerIP)<>"127.0.0.1") then abort;

---

← →
Дмитрий

 
(2012-03-23 19:49)
[19]

Все нашел. Событие OnBeforeCommandHandler

if(Pos("google.com",AData)=0) then
 Abort;

---