Disable the Windows firewall once this error occurs
by Henderson Jayden Harper
Passionate about technology, Crypto, software, Windows, and everything computer-related, he spends most of his time developing new skills and learning more about the tech world. He also enjoys… read more
Updated on May 22, 2023
Reviewed by
Alex Serban
After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more
- Running into the Winsock error 10054 indicates the connection has been reset by peer, or it has been closed by the remote host.
- It can occur due to poor network connection and firewall interference.
- Disabling Windows Defender Firewall on your PC will stop it from accessing and impeding your connections.
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
- Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
- Click Start Scan to find Windows issues that could be causing PC problems.
- Click Repair All to fix issues affecting your computer’s security and performance
- Restoro has been downloaded by 0 readers this month.
Winsock error 10054 can appear with a message saying Connection reset by peer, or An existing connection was forcibly closed by the remote host. It means the target host closed the connection unexpectedly. Hence, we’ll explain why it happened and how to fix it.
Also, you may be interested in our guide about fixing socket error 10060 connection timed out on Windows PC.
What causes the Winsock error 10054?
Some factors that can cause the error are:
- Closing the connection midway – Just as the error message says, Windows 10054 can occur when you abruptly close or shut down the session while the computer tries to connect with a server.
- Internet connection issues -If there is network congestion between the peer servers or the network is not stable, it can cause the connection to reset or be closed forcibly. Also, it can disable the server connections when connected to a proxy server.
- Firewall interference with the connection – The activities of Windows Defender Firewall or other antivirus software may impede the connection between the servers. It checks every connection that goes in and out of the PC and can cause a delay in the process.
- Outdated network driver – When the network drivers on your computer are outdated, they can affect your network performance. Also, it can cause incorrect assembling of the TCP/IP transport packets.
Depending on the circumstances of occurrence, these causes may vary on different computers. However, you can resolve the error by following the fixes in this article.
How can I fix the Winsock error 10054?
Observe the following preliminary checks before trying any advanced troubleshooting steps:
- Restart the computer – It will refresh the system and is the quickest way to fix temporary issues affecting the computer.
- Fix network-related issues – Power cycling the modem or router and updating the router firmware can resolve network issues.
- Add Winsock to Firewall’s exception list – This will ensure that the Windows Defender Firewall will not flag anything related to Winsock as a threat or disrupt its activities.
If you can resolve the Winsock error, proceed with the solutions below:
1. Disable Windows Firewall
- Press Windows + R key to open the Run dialog box, type control, then press Enter to open the Control Panel.
- Click on the Windows Defender Firewall option.
- Click the Turn Windows Defender Firewall on or off option.
- Go to the Private and Public network settings, then click the radio buttons for the option to Turn off Windows Defender Firewall (not recommended).
- Restart your PC.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
Disabling the Windows Defender Firewall resolves any interference it’s causing your computer from connecting to the peer server.
You can read about how to disable Windows Defender if you encounter issues with it.
2. Update the network driver
- Press Windows + R keys to prompt the Run window, type devmgmt.msc, and click OK.
- Expand the Network adapters, right-click on the driver, then click Update driver from the drop-down.
- Select the Search automatically for drivers option and wait till the update finishes.
- Restart your PC and check if the error persists.
Updating the network driver will fix bugs and install the latest features to improve your computer driver performance. Check other steps for updating drivers on Windows 11 if you have any issues.
Various errors are the result of a malfunctioning driver. When this is the case, you may need to update or reinstall completely this specific component. As the process is not straight-forward to complete, we recommend using an automated tool for the job. Here’s how to do it:
- Download and install DriverFix.
- Launch the app.
- Wait for the software to detect all your faulty drivers.
- You will now be presented with a list of all the drivers that have issues, and you just need to select the ones you’d liked fixed.
- Wait for DriverFix to download and install the newest drivers.
- Restart your PC for the changes to take effect.
DriverFix
Keep your Windows safe from any type of errors caused by corrupted drivers, by installing and using DriverFix today!
Disclaimer: this program needs to be upgraded from the free version in order to perform some specific actions.
3. Reset TCP/IP Stack
- Left-click the Start button, type Command Prompt, and click the Run as administrator option.
- Click Yes on the User Account Control (UAC) prompt.
- Type the following in the command bar and press Enter:
netsh int ip reset c:resetlog.txtipconfig /releaseipconfig /renewipconfig /flushdns
- Restart your computer.
Resetting the TCP/IP will restore its default settings and fix any configuration issues causing the winsock error 10054. Check our guide on how to fix Command Prompt not working on your PC.
Further, do not hesitate to check how to resolve the network connections’ unexpected error on Windows 11.
Also, we have a detailed explanation of the causes and ways to fix the requested address is not valid in its context error on the PC.
Still having issues? Fix them with this tool:
SPONSORED
If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.
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.
- Remove From My Forums
-
Question
-
Hi
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
-
Hi Chanmy,
Try the following link I found on mdaemon forum and let me know the result.
http://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-02012.
Regards,
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
Tuesday, March 18, 2014 7:32 AM
-
Marked as answer by
Причины возникновения
Причины этой ошибки разняться по своей «природе», но их объединяето то, что уже существующее (т.е. ранее установленое) соединение с клиентом разрывает сервер.
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 ошибку можно получить на релизах <= 8.1.12.98 при ри конвертации конвертором ИБ 77(DBF) -> 81(SQL) в типовой ТиС (демо, взятой с ИТС) релиз. 954 в клиент-серверном варианте.
обойти можно так:
— выполните конвертацию в файловый фариант информационной базы 1С:Предприятия 8.1,
— выгрузите полученную информационную базу в файл,
— загрузите в клиент-серверный вариант информационной базы 1С:Предприятия 8.1.
Подробнее на www.gilev.ru
Содержание
- 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.
Источник
THE INFORMATION IN THIS ARTICLE APPLIES TO:
- All Windows-based products
DISCUSSION
The table below lists some common Winsock error codes. Also refer to the Microsoft MSDN Library article «Winsock Error Codes» at http://msdn.microsoft.com/en-us/library/aa924071.aspx.
| Return Code | Value | Description |
|---|---|---|
| WSAEINTR | 10004 | Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| WSAEACCES | 10013 |
Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option. |
| WSAEFAULT | 10014 |
Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr). |
| WSAEINVAL | 10022 |
Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. |
| WSAEMFILE | 10024 |
Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. |
| WSAEWOULDBLOCK | 10035 |
Resource temporarily unavailable. This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established. |
| WSAEINPROGRESS | 10036 |
Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. |
| WSAEALREADY | 10037 |
Operation already in progress. An operation was attempted on a non-blocking socket with an operation already in progress—that is, calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. |
| WSAENOTSOCK | 10038 | Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. |
| WSAEDESTADDRREQ | 10039 |
Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY. |
| WSAEMSGSIZE | 10040 |
Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself. |
| WSAEPROTOTYPE | 10041 |
Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. |
| WSAENOPROTOOPT | 10042 |
Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. |
| WSAEPROTONOSUPPORT | 10043 |
Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. |
| WSAESOCKTNOSUPPORT | 10044 |
Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. |
| WSAEOPNOTSUPP | 10045 |
Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket. |
| WSAEPFNOSUPPORT | 10046 |
Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT. |
| WSAEAFNOSUPPORT | 10047 |
Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto. |
| WSAEADDRINUSE | 10048 |
Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all— connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. |
| WSAEADDRNOTAVAIL | 10049 |
Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0). |
| WSAENETDOWN | 10050 |
Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself. |
| WSAENETUNREACH | 10051 |
Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. |
| WSAENETRESET | 10052 |
Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. |
| WSAECONNABORTED | 10053 |
Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error. |
| WSAECONNRESET | 10054 |
Connection reset by peer. An 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, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. For more information see GlobalSCAPE Knowledge Base Article #10235 |
| WSAENOBUFS | 10055 |
No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. This error indicates a shortage of resources on your system. It can occur if you’re trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn’t return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. Another possible solution is to increase the available virtual memory by increasing the size of the Windows paging file. For more information see GlobalSCAPE Knowledge Base Article |
| WSAEISCONN | 10056 |
Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence. |
| WSAENOTCONN | 10057 |
Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset. |
| WSAESHUTDOWN | 10058 |
Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued. |
| WSAETIMEDOUT | 10060 |
Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. For more information see GlobalSCAPE Knowledge Base Article |
| WSAECONNREFUSED | 10061 |
Connection refused. |
| WSAEHOSTDOWN | 10064 |
Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT. |
| WSAEHOSTUNREACH | 10065 |
No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH. |
| WSAEPROCLIM | 10067 |
Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously.WSAStartup may fail with this error if the limit has been reached. |
| WSASYSNOTREADY | 10091 | Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:
|
| WSAVERNOTSUPPORTED | 192 | Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. |
| WSANOTINITIALISED | 10093 | Successful WSAStartup not yet performed. Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times. |
| WSAEDISCON | 10101 |
Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence. |
| WSATYPE_NOT_FOUND | 10109 |
Class type not found. The specified class was not found. |
| WSAHOST_NOT_FOUND | 11001 |
Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. |
| WSATRY_AGAIN | 11002 | Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. |
| WSANO_RECOVERY | 11003 | This is a nonrecoverable error. This indicates that some sort of non-recoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error. |
| WSANO_DATA | 11004 |
Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. |
| WSA_INVALID_HANDLE | OS Dependent |
Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid. |
| WSA_INVALID_PARAMETER | OS Dependent |
One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters. |
| WSA_IO_INCOMPLETE | OS Dependent |
Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete. |
| WSA_IO_PENDING | OS Dependent | Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. |
| WSA_NOT_ENOUGH_MEMORY | OS Dependent |
Insufficient memory available. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. |
| WSA_OPERATION_ABORTED | OS Dependent |
Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl. |
| WSAINVALIDPROCTABLE | OS Dependent |
Invalid procedure table from service provider. A service provider returned a bogus procedure table to Ws2_32.dll. (This is usually caused by one or more of the function pointers being null.) |
| WSAINVALIDPROVIDER | OS Dependent |
Invalid service provider version number. A service provider returned a version number other than 2.0. |
| WSAPROVIDERFAILEDINIT | OS Dependent |
Unable to initialize a service provider. Either a service provider’s DLL could not be loaded (LoadLibrary failed) or the provider’s WSPStartup/NSPStartup function failed. |
| WSASYSCALLFAILURE | OS Dependent |
System call failure. Generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs. Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error. |