Содержание
- Socket error 10054 соединение было перезапущено на другом конце
- Answered by:
- Question
- Answers
- All replies
- An application may receive the «10054» error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed
- Symptoms
- Resolution
- Hotfix information
- Prerequisites
- Registry information
- Restart requirement
- Hotfix replacement information
- File information
- Mdaemon 14.5 Winsock Error 10054
- Popular Topics in Email
- 6 Replies
- Read these next.
- poor wifi, school’s third floor
- Need help crafting a job posting for an IT Pro
- Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal
- Spark! Pro series – 13th January 2023
- Ошибка Windows Sockets 10054
Socket error 10054 соединение было перезапущено на другом конце
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I am using SMTPClient to send email. However, I get feedback from customer that, some user doesn’t receive email from our application. it only happens randomly.
From our application, no exception was thrown. However, when check on their email server log, we found the below
I have tried suggestions found from google
1. Wrapped SMTPClient and implement IDisposable — tested no working
Any other ideas?
Answers
Try the following link I found on mdaemon forum and let me know the result.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
- Marked as answer by Herro wong Microsoft contingent staff Tuesday, March 18, 2014 7:32 AM
Winsock error 10054 shows that server encounter some mistake and then the connection is closed by the server. For more information about Winsock error, please refer to the following link. http://msdn.microsoft.com/en-us/library/aa924071.aspx.
If you control the server, I think you should do some troubleshooting on server. If not, I recommend you wait some time and then reconnect to server after you catch this error.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
From the .NET code, no exception is actually captured.
What to troublesbhoot at server side ?
From the description of the log, I know that the server turn off the connection when the remote host is suddenly stopped or the remote host uses a hard close. If you are using IIS SMTP Server, I recommend you post thread on IIS forum for effective response. http://forums.iis.net/1047.aspx/1?Setup.
If you just want to work around this issue, you can write some code to reconnect to server after a while.
> From the .NET code, no exception is actually captured.
Really? How did you know there is an exception when server closes the connection?
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
Источник
An application may receive the «10054» error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed
Symptoms
Consider the following scenario:
You have a computer that is running Windows 7 or Windows Server 2008 R2.
A Transport Driver Interface (TDI) filter driver is installed on the computer. For example, a TDI filter driver is installed when you install McAfee VirusScan.
An application opens a TCP listening port to receive connections.
In this scenario, the application may receive the following error message:
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. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection.
Resolution
To resolve this issue, install this hotfix.
Note This hotfix temporarily resolves this issue for application vendors before they migrate their implementation to Windows Filtering Platform (WFP). These application vendors use the TDI filter driver or the TDI extension driver (TDX) on a computer that is running Windows 7 or Windows Server 2008 R2.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo enable the hotfix in this package, follow these steps:
In Registry Editor, locate the following registry subkey:
If you are running a 32-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD Value.If you are running a 64-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD (32-bit) Value.
Rename the new registry entry to TdxPrematureConnectIndDisabled and set the value to 1.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
Источник
Mdaemon 14.5 Winsock Error 10054
i am facing issue with my mdaemon server, its working accordingly and most of my email send through mdaemon and clients are getting my mail too but some email not sending i dont know whats the actual problem i have been talk with many professionals but still getting same error, i am sharing email server log kindly help me.
- local_offer Tagged Items
Popular Topics in Email
Brand Representative for MDaemon Technologies
Winsock 10054 errors usually indicate that the other server is resetting the connection.
Is this happening with messages from specific senders/domains?
Do you have a firewall, proxy, or other device that mail is routed through before it reaches MDaemon?
You can find more troubleshooting tips in this discussion on our forums:
- local_offer Tagged Items
MDaemon Email Server star 4.4
MDaemon Email Server star 4.4
Brand Representative for MDaemon Technologies
yes we are using firewall which is ASA 5508-X but we are not blocking inside traffic
Brand Representative for MDaemon Technologies
Your router’s MTU settings might be a possible cause. Here’s more:
thanks for your support issue has been solved my firewall logs showed esmtp session block i just run a command on firewall no esmtp inspect.
Brand Representative for MDaemon Technologies
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Read these next.
poor wifi, school’s third floor
I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.
Need help crafting a job posting for an IT Pro
I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.
Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal
Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.
Spark! Pro series – 13th January 2023
Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .
Источник
Ошибка Windows Sockets 10054
Причины возникновения
Причины этой ошибки разняться по своей «природе», но их объединяето то, что уже существующее (т.е. ранее установленое) соединение с клиентом разрывает сервер.
1. С версии 8.1.11 включен циклический перезапуск процессов, по наступлению интервала происходит автоматический перезапуск рабочих процессов rphost.
2. В некоторых случаях причиной ошибки могут стать утечки памяти.
3. Действия администратора в консоли (команда удалить пользователя)
4. Процесс rphost на серверном компьютере завершился аварийно
5. Ошибочное принятие высокой интенсивности пользователей за атаку на протокол в некоторых случаях Windows
6. Устаревание данных в кэшах
7. Плохо отслеживаемые события в фоновых процессах
8. Нестандартные запросы могут приводить к падениям rphost
Способы устранения
1. с 8.1.11 включен циклический перезапуск процессов, для анализа этого события на компьютере сервера 1С:Предприятия необходимо включить запись в технологический журнал событий PROC (пример файла logcfg.xml).
Когда процесс выключается, будет выведено событие PROC со свойством Txt=Process become disable.
Когда процесс останавливается, будет выведено событие PROC со свойством Txt=Process terminated. Any clients finished with error. Если аварийные завершения работы пользователей совпадают по времени с выводом этого события, то причиной является принудительная остановка рабочего процесса либо администратором (через консоль кластера), либо вследствие автоматического перезапуска.
2. перезагрузить сервер
3. убедиться, что причиной являются/не являются действия администратора в консоли
4. создать на сервере приложения два или более рабочих процесса, чтобы иметь возможность переподключиться в случаи сбоя рабочего процесса
5. Запусти программу regedit.exe, добавь новое значение типа DWORD с именем SynAttackProtect в раздел реестра HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters и присвой ему значение 00000000
Имеет смысл делать для ОС Windows 2003 SP1 (http://msdn.microsoft.com/ru-ru/library/ms189083.aspx).
6. arp -d *
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
nbtstat -RR
7. отключить фоновые процессы во всех базах
8. найти технологическим журналом запрос, приводящий к падению
p.s. Кроме того, 54 ошибку можно получить на релизах 81(SQL) в типовой ТиС (демо, взятой с ИТС) релиз. 954 в клиент-серверном варианте.
обойти можно так:
— выполните конвертацию в файловый фариант информационной базы 1С:Предприятия 8.1,
— выгрузите полученную информационную базу в файл,
— загрузите в клиент-серверный вариант информационной базы 1С:Предприятия 8.1.
Источник
Symptoms
Consider the following scenario:
-
You have a computer that is running Windows 7 or Windows Server 2008 R2.
-
A Transport Driver Interface (TDI) filter driver is installed on the computer. For example, a TDI filter driver is installed when you install McAfee VirusScan.
-
An application opens a TCP listening port to receive connections.
In this scenario, the application may receive the following error message:
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. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection.
Resolution
To resolve this issue, install this hotfix.
Note This hotfix temporarily resolves this issue for application vendors before they migrate their implementation to Windows Filtering Platform (WFP). These application vendors use the TDI filter driver or the TDI extension driver (TDX) on a computer that is running Windows 7 or Windows Server 2008 R2.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo enable the hotfix in this package, follow these steps:
-
In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesTcpipParameters
-
If you are running a 32-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD Value.If you are running a 64-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD (32-bit) Value.
-
Rename the new registry entry to TdxPrematureConnectIndDisabled and set the value to 1.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
74,752 |
09-Sep-2010 |
02:19 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
101,376 |
09-Sep-2010 |
02:52 |
x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
236,032 |
09-Sep-2010 |
01:47 |
IA-64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about WFP, visit the following Microsoft website:
General information about WFPFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,820 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_2_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,825 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_3_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,805 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,421 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
X86_bfb7f2e54887b839240a44ae0de89137_31bf3856ad364e35_6.1.7600.20796_none_3f3df7432361a4c5.manifest |
|
File version |
Not Applicable |
|
File size |
702 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
X86_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_ea93f14a568e0aaf.manifest |
|
File version |
Not Applicable |
|
File size |
2,924 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
04:58 |
|
Platform |
Not Applicable |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
Amd64_8e30a6e4951f89c20ce3f8a1c04b9f2a_31bf3856ad364e35_6.1.7600.20796_none_8d28eb4c99ddf2d4.manifest |
|
File version |
Not Applicable |
|
File size |
706 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Amd64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_46b28cce0eeb7be5.manifest |
|
File version |
Not Applicable |
|
File size |
2,926 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
06:11 |
|
Platform |
Not Applicable |
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,830 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_2_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,057 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_3_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,815 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,659 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_0bb425f9d3502a4be9efc4af61147428_31bf3856ad364e35_6.1.7600.20796_none_09467879be47b542.manifest |
|
File version |
Not Applicable |
|
File size |
704 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Ia64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_ea959540568c13ab.manifest |
|
File version |
Not Applicable |
|
File size |
2,925 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
05:48 |
|
Platform |
Not Applicable |
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~ia64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,051 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~ia64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,683 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
Need more help?
1. Ошибка при попытке передать почту на почтовый ящик.
 |
| Ошибка Outlook. Ошибка сокета: 10054. Код ошибки: 0x800CCC0E |
Ошибка при соединении с сервером. Учетная запись: ‘КартинаM’, Сервер: ‘smtp.mail.ru’, Протокол: SMTP, Порт: 25, Защита (SSL): Нет, Ошибка сокета: 10054, Код ошибки: 0x800CCC0E
1.1 Собрал файлы, описывающие ошибку сокета 10054 и другие ошибки Winsock. Также собрал файлы описывающие код ошибки 0x800CCC0E и другие почтовой программы Outlook. Все в одном файле — здесь: 10054-800CCC0E.rar или здесь : 10054-800CCC0E.rar
2. Ошибка сокета: 10054
2.1 Вот что говорит Help Microsoft Windows Sockets 2 Reference
WSAECONNRESET (10054) Connection reset by peer.
A existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a «hard close» (see setsockopt for more information on the SO_LINGER option on the remote socket.)
2.2 Без описаний список кодов всех ошибок WinSock можно найти из файлов WinSock.pas и winsock.h
2.3 Список кодов ошибок и краткое описание ошибок от Microsoft MSDN Windows Sockets Error Codes и от Microsoft Support Windows sockets error codes, values, and meanings
2.4 На русском языке Коды ошибок TCP/IP описывают ошибку 10054 следующим образом :
10054
WSAECONNRESET Connection reset by peer (Соединение сброшено удаленной системой).
Существующее соединение принудительно закрыто удаленной стороной. Обычно это случается в случае неожиданного останова приложения на удаленной стороне, при перезагрузке удаленной машины, или в случае, когда удаленный хост использует «жесткое закрытие» ( setsockopt(SO_LINGER)) удаленного сокета.
2.5 По ссылке Socket error 10054 when testing email alerts описана ошибка и несколько возможных причин
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
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.
2.6 По описанию ошибки сокета 10054 можно сделать предварительный вывод, что соединение начинает работать, следовательно ,скорее всего, с сетью проблем нет. Однако какие то проблемы с сервером ‘smtp.mail.ru’ (в данном конкретном случае).Если ошибка не устраняется сама через некоторое время, то скорее всего, ошибка в настройках SMTP — сервера Надо внимательно проверить настройки SMTP- сервера.
3. Код ошибки: 0x800CCC0E
0x800CCC0E IXP_E_FAILED_TO_CONNECT Не удается подключиться к серверу
3.2. В интернет документе Коды ошибок электронной почты приведены некоторые методы устранения этой и некоторых других ошибок:
0x800CCC0E FAILED_TO_CONNECT. Не удается подключиться к серверу
—Если Нортон Антивирус установлен, то возможно проблема в нем .
—Можете ли вы открыть веб-страницы? Если это так, то вы может просто неправильно ввели адрес почтового сервера на учетной записи или сервер именно сейчас может быть недоступен.
—Если вы не можете открыть веб-страницы, то разорвите интернет соединение и попробуйте подключиться снова
—Перезагрузите компьютер и повторите попытку.
—Если он по-прежнему не работает, и вы не получаете любые веб-страницы, то данные могут передаваться через сеть надлежащим образом. Проверить настройки DNS, удалить и переустановить TCP / IP в Панель управления> Сеть (Control Panel > Network).
—Можно попробовать удалить кэш DNS командой ipconfig /flushdns (Пуск -> Все программы -> Стандартные -> Командная строка. Вести в командную строку ipconfig /flushdns)
—Эта ошибка может появиться, если у вас есть опция ‘уведомьте меня, если есть какие-нибудь новые группы новостей’ выбран, но не имеете созданной учетной записи новостей. Зайдите в меню Сервис> Свойства обозревателя> Общие TAB (TOOLS > OPTIONS > GENERAL TAB) и отключите эту опцию.
3.3 В описаниях ошибки сказано , что возможно вы неправильно ввели адрес сервера в учетной записи . Так что в совокупности ошибок сокета и Outlook –а , вероятнее всего какая то ошибка в настройках сервера ‘smtp.mail.ru’.
4. Причина ошибки.
—Оказалась в настройках сервера ‘smtp.mail.ru’ Надо было заменить порт сервера на 587.Раньше стоял 25. Видимо, на mail.ru решили отключить 25 порт, на котором работал сервер раньше
5. Повторю . Собрал файлы, описывающие ошибку сокета 10054 и другие ошибки Winsock. Также собрал файлы описывающие код ошибки 0x800CCC0E и другие почтовой программы Outlook. Все в одном файле — здесь: 10054-800CCC0E.rar или здесь : 10054-800CCC0E.rar
Socket errors are one of the most common problems that can occur when using a computer. The socket error 10054 is caused by an existing connection that is forcibly closed by the remote. The error could be solved by restarting your router, checking if the address of the computer or host is correct, scanning for malware and lastly trying to connect through a different port.
This is an error that occurred when attempting to connect with the server. The primary reason for this issue is due to a software or network problem. Error 10054 might also be caused by accidentally shutting down or disconnecting a program while the computer is attempting to establish contact with a server.
There might be a problem with your Internet connection or a proxy server shutting down server connections. The firewall might be malfunctioning and causing the connection to break, as it does with all concerns.
How to Fix Socket Error 10054
Restart Your Router or DNS
When you are connecting to a new network, it is best to restart your router. If the computer is able to make a direct connection with the internet, then the problem lies somewhere else and not with your network.
You can follow these steps to clear DNS cache:
- Click Windows Start and type Command Prompt.
- Right-click the Command prompt and select Run as Administrator.
- In the Command Prompt, type netsh winsock reset and press Enter key.
- Type netsh int ip reset and press Enter key.
- Type ipconfig /release and press Enter key.
- Type ipconfig /renew and press Enter key.
- Type ipconfig /flushdns and press Enter key.
Check if The Address of Your Computer or Host Is Correct
The default gateway address should be different from the IP address assigned by DHCP (Dynamic Host Configuration Protocol). When there’s no difference in these values, it shows that something might be wrong with the settings in all programs that are related to the internet like firewalls.
You can check this by typing in “ipconfig /all” on Command Prompt (which will show your IP address and default gateway).
Scan for Malware
When you suspect that malware might be causing the issue, then it’s time to scan again with an antivirus if necessary. Sometimes, even after restarting your computer and router, malware can still cause problems as they are installed on a deeper level into the system.
It is best to scan for Malware at least twice to make sure that any remaining traces of malicious programs have been detected. If the problem persists even after removing them from your computer, then you may need a deeper analysis or a complete reformatting of your machine.
Reboot Your Computer
It doesn’t matter whether you want to call it a “warm reboot” or a “cold boot”, but rebooting your computer is a basic step in troubleshooting any problems that could affect your PC performance.
Check Your Settings In All Programs That Are Related to the Internet (Like Firewalls)
If you don’t have enough knowledge about networking, then it’s best to consult with a network specialist when dealing with internet-related problems. Or if you still think that you can handle it on your own, then make sure to check and change all of your settings in every program related to the internet.
For instance, anything related to Skype or Firefox should be disabled especially if you suspect that these programs might cause this issue.
Try Connecting Through a Different Port
If nothing seems out of order regarding your router and hardware settings but socket error 10054 keeps on occurring, then it is best to try connecting through a different port.
These errors usually mean that there’s a problem with the connection settings where it creates a faulty connection between two programs for a specific port number. This means that you have to configure your network so that outgoing connections use other ports instead of the default one.