Сетевая ошибка WINSOCK 10055
mur60
Ср сен 13, 2023 6:07 pm
Ср сен 13, 2023 6:07 pm
#49848
При входе пользователя появляется сообщение с двумя,ошибками:
Ошибка 0224 и сетевая ошибка 10055
и текст: no buffer cpace available
При этом на 15 компах в этой сети всё нормально встало и работает.
mur60
Ср сен 13, 2023 6:23 pm
Ср сен 13, 2023 6:23 pm
#49850
Просто на всех остальных компах все заработало сразу и только на одном нестандартные настройки сети?
Я не в курсе этого. Мы не можем управлять сетевыми настройками вашей системы, если получаем сетевую ошибку TCP/IP стека — то обязаны её показать для диагностики, а что делать дальше — работа системного администратора.
Team lead
Чат со мной
mur60
Ср сен 13, 2023 6:26 pm
Ср сен 13, 2023 6:26 pm
#49852
mur60
Ср сен 13, 2023 6:50 pm
Ср сен 13, 2023 6:50 pm
#49853
Вот только там win7 pro, а в статье о win server 2012 , win10
Я привёл вам первую ссылку на сайте Microsoft, которую нагуглил. Вы можете это сделать лучше меня.
Team lead
Чат со мной
mur60
Ср сен 13, 2023 6:54 pm
Ср сен 13, 2023 6:54 pm
#49856
Возможно, но после того как на этом компе вылезла такая ошибка, на следующем компе всё встало и заработало без проблем. Это проблема именно этого компа получается, а не настройки сети
Я имел в виду «настройка сетевого стека на компьютере, на котором вы получаете эту Winsock ошибку».
Team lead
Чат со мной
mur60
Ср сен 13, 2023 7:01 pm
Ср сен 13, 2023 7:01 pm
#49858
Вот это сообщение
Вложения
Вот это сообщение
20230912_131528.jpg (4.9 МБ) Просмотров: 1412
Да, это сетевая ошибка WINSOCK 10055, всё верно.
Team lead
Чат со мной
Windows Sockets are an application program interface (API) that allow communication between two systems over a network. Socket errors can be caused by various issues including connectivity problems on the network, client or server computers or due to a firewall, antivirus or a proxy server.
This article provides information about common socket errors you may encounter when using FTP, Cloud, SBMS or Email with SyncBack:
Socket error # 10013, Permission denied
This error occurs when the socket connection to the remote server is denied. The possible reasons are a firewall or antivirus (AV) software is blocking the connection, the port used is blocked or unreachable.
Temporarily disable firewall/AV program and check the connection after restarting your computer.
Socket Error # 10039, Destination address required
There may be a problem getting the IP address for the hostname.
Socket error # 10052, Network dropped connection on reset
The host you are connecting to crashed or rebooted. Retry later.
Socket error # 10053, Software caused connection abort
An established connection was closed by software on your local host. Possibly a firewall, AV or something else on your local computer aborted the connection, or the connection to the remote server timed out.
Socket Error # 10054, Connection reset by peer
The remote server or some other software is forcibly closing or resetting the established connection. This may be a problem with your network, firewall or AV configuration, the remote server is stopped or rebooted.
Ensure that the hostname or IP address of the remote server is correct and check if the remote server is reachable.
Socket error # 10055, No buffer space available
This error indicate that Windows has run out of socket buffers. The most common causes of this error are running a high number of applications simultaneously and insufficient system resources (memory or disk space).
Close unwanted programs that are running, restart the computer to free up resources. If you are backing-up to a cloud server, then reduce the number of threads to use from Cloud > Advanced settings page.
Socket error # 10060, Connection timed out
This is a connection timeout error, which means the remote server did not properly respond after a period of time. It generally suggests firewall or network issues e.g. a firewall may be permitting some commands/responses but blocking others or may be the hostname/port is incorrect.
Socket error # 10061, Connection refused
A connection to the server cannot be established as the remote server actively refused the connection. The common causes are the server is not running, incorrect connection parameters are used when establishing a connection (e.g. a wrong port number is used), a firewall or antivirus is blocking the connection.
Check if the server connection details are configured correctly and ensure the firewall is not blocking the connection.
Socket error # 10106, Service provider failed to initialize
This error can be caused by corrupted Windows system files, incomplete installation/uninstallation of applications or the computer is infected by a virus or malware.
Re-install SyncBack. Run a disk check and virus scan to detect and fix errors.
Socket error # 11001, Host not found
Check that the hostname or IP address has been entered correctly.
Socket error # 11002, Nonauthoritative host not found
This is a temporary error during hostname resolution, which means the hostname could not be resolved to an IP address. Try reconnecting later.
According to Microsoft, winsocket error 10055 means that your socket or pipe is failing due to lack of buffer.
When this happens, not only Splunk ports but also other general ports cannot be accessed. Telnet to any port would fail most likely. So, Splunk might not be causing the issue.
You have to reboot your machine to get rid of the error. But if you cannot identify a cause of the issue, eventually the same error might come back.
For Splunk, you should check your splunkd.log and see any errors related to network; such as Deployment Server, Deployment Client, TcpOutputFd, TcpOutputProc, TcpInputFd, TcpInputProc etc. Then, check if configuration file is okay, and network issue such as slow Reverse DNS or DNS lookup.
The last time we solved the issue Deployment Server and Deployment Client were running on the same Splunk instance. But, the configuration was not proper. As a result, there were a lot of Deployment Client connection errors.
What is Error 10055?
Error 10055 is a kind of Runtime error that is found in the Microsoft Windows operating systems. The file can be found for Safari. kCFErrorDomainWinSock: 10055 has a popularity rating of 1 / 10.
Errors
This tutorial contains information on Error 10055 or otherwise known as kCFErrorDomainWinSock: 10055. Errors such as kCFErrorDomainWinSock: 10055 indicate your machine has faulty hardware or software that should be fixed when possible. Below is information on how to repair Error 10055 and get your computer back to normal.
Signs of Error 10055:
- When your computer freezes or locks up at random.
- When your computer crashes when you are running Safari.
- If kCFErrorDomainWinSock: 10055 pops up and causes a program to shutdown or your computer to crash.
- Your computer is running slow, taking a long time to boot up, and you suspect Error 10055 by Safari is the cause.
What Causes Runtime Errors Like Error 10055?
There are several causes of runtime errors like kCFErrorDomainWinSock: 10055, such as viruses, out of date drivers, missing files or folders, incomplete or poor installation, and registry errors. They can also occur due to an issue with the computer’s memory, which may often be due to a hardware problem. In some cases there was an issue installing Safari and an error occurred.
How to Fix kCFErrorDomainWinSock: 10055
Follow the step by step instructions below to fix the Error 10055 problem. We recommend you do each in order. If you wish to skip these steps because they are too time consuming or you are not a computer expert, see our easier solution below.
Step 1 — Uninstall and Reinstall Safari
If the kCFErrorDomainWinSock: 10055 is a result of using Safari, you may want to try reinstalling it and see if the problem is fixed. Please follow these steps:
Windows XP
- Click “Start Menu”.
- Click “Control Panel”.
- Select the “Add or Remove” program icon.
- Find the Error 10055 associated program.
- Click the Change/Remove button on the right side.
- The uninstaller pop up will give you instructions. Click “okay” or “next” or “yes” until it is complete.
- Reinstall the software.
Windows 7 and Windows Vista
- Click “Start Menu”.
- Click “Control Panel”.
- Click “Uninstall a Program” which is under the “Programs” header.
- Find the Error 10055 associated program.
- Right click on it and select “Uninstall”.
- The uninstaller pop up will give you instructions. Click “okay” or “next” or “yes” until it is complete.
- Reinstall the software and run the program.
Windows 8, 8.1, and 10
- Click “Start Menu”.
- Click “Programs and Features”.
- Find the software that is linked to **insert file name**.
- Click Uninstall/Change.
- The uninstaller will pop up and give you instructions. Click “okay” and “next” until it is complete.
- Restart your computer.
- Reinstall the software and run the program.
Step 2 — Remove Registry Entry related to Error 10055
WARNING: Do NOT edit the Windows Registry unless you absolutely know what you are doing. You may end up causing more trouble than you start with. Proceed at your OWN RISK.
- Create a backup of registry files.
- Click “Start”.
- Type regedit, select it, and grant permission in order to proceed.
- Click HKEY LOCAL MACHINE>>SOFTWARE>>Microsoft>>Windows>>Current Version>>Uninstall.
- Find the kCFErrorDomainWinSock: 10055 software from the list you wish to uninstall.
- Select the software and double click the UninstallString icon on the right side.
- Copy the highlighted text.
- Exit and go to the search field.
- Paste the data.
- Select Okay in order to uninstall the program.
- Reinstall the software.
Step 3 – Ensure Junk Isn’t Causing kCFErrorDomainWinSock: 10055
Any space that isn’t regularly cleaned out tends to accumulate junk. Your personal computer is no exception. Constant web browsing, installation of applications, and even browser thumbnail caches slow down your device and in the absence of adequate memory, can also trigger a kCFErrorDomainWinSock: 10055 error.
So how do you get around this problem?
- You can either use the Disk Cleanup Tool that comes baked into your Windows operating system.
- Or you can use a more specialized hard drive clean up solution that does a thorough job and flushes the most stubborn temporary files from your system.
Both solutions may take several minutes to complete the processing of your system data if you haven’t conducted a clean up in a while.
The browser caches are almost a lost cause because they tend to fill up quite rapidly, thanks to our constantly connected and on the go lifestyle.
Here’s how you can run the Window’s Disk Cleanup Tool, without performance issues or surprises.
- For Windows XP and Windows 7, the program can be ran from “Start” and from the “Command Prompt”.
- Click “Start”, go to All Programs > Accessories > System Tools, click Disk Cleanup. Next choose the type of files you wish to remove, click OK, followed by “Delete Files”.
- Open up the Command Prompt, type “c:\windows\cleanmgr.exe /d” for XP and “cleanmgr” for Windows 7. Finish by pressing “Enter”.
- For Windows 8 and Windows 8.1, the Disk Cleanup Tool can be accessed directly from “Settings”. Click “Control Panel” and then “Administrative Tools”. You can select the drive that you want to run the clean up on. Select the files you want to get rid of and then click “OK” and “Delete Files”.
- For Windows 10, the process is simplified further. Type Disk Cleanup directly in the search bar and press “Enter”. Choose the drive and then the files that you wish to wipe. Click “OK”, followed by “Delete Files”.
The progressive ease with which the Cleanup Tool can be used points to the growing importance of regularly deleting temporary files and its place in preventing kCFErrorDomainWinSock: 10055.
PRO TIP:
Remember to run the Disk Cleanup as an administrator.
Step 4 – Fix Infections and Eliminate Malware in Your PC
How do you gauge if your system is infected with a malware and virus?
Well, for one, you may find certain applications misbehaving.
And you may also see the occurrence of Error 10055.
Infections and malware are the result of:
- Browsing the Internet using open or unencrypted public Wi-Fi connections
- Downloading applications from unknown and untrustworthy sources
- Intentional planting of viruses in your home and office networks
But thankfully, their impact can be contained.
- Enter “safe mode” by pressing the F8 key repeatedly when your device is restarting. Choose “Safe Mode with Networking” from the Advanced Boot Options menu.
- Back up all the data in your device to a secure location. This is preferably a storage unit that is not connected to your existing network.
- Leave program files as is. They are where the infection generally spreads from and may have been compromised.
- Run a thorough full-system scan or check of an on-demand scanner. If you already have an antivirus or anti-malware program installed, let it do the heavy lifting.
- Restart your computer once the process has run its course.
- Lastly, change all your passwords and update your drivers and operating system.
PRO TIP: Are you annoyed by the frequent updates to your antivirus program? Don’t be! These regular updates add new virus signatures to your software database for exponentially better protection.
Step 5 – Return to the Past to Eliminate Error 10055
The steps outlined up until this point in the tutorial should have fixed kCFErrorDomainWinSock: 10055 error. But the process of tracking what has caused an error is a series of educated guesses. So in case the situation persists, move to Step 5.
Windows devices give users the ability to travel back in time and restore system settings to an uncorrupted, error free state.
This can be done through the convenient “System Restore” program. The best part of the process is the fact that using System Restore doesn’t affect your personal data. There is no need to take backups of new songs and pictures in your hard drive.
- Open “Control Panel” and click on “System & Security”.
- Choose the option “System”.
- To the left of the modal, click on “System Protection”.
- The System Properties window should pop-up. You’ll be able to see the option “System Restore”. Click on it.
- Go with “Recommended restore” for the path of least hassles and surprises.
- Choose a system restore point (by date) that will guarantee taking your device back to the time when Error 10055 hasn’t been triggered yet.
- Tap “Next” and wrap up by clicking “Finish”.
If you’re using Windows 7 OS, you can reach “System Restore” by following the path Start > All Programs > Accessories > System Tools.
Step 6 — Error 10055 Caused by Outdated Drivers
Updating a driver is not as common as updating your operating system or an application used to run front-end interface tasks.
Drivers are software snippets in charge of the different hardware units that keep your device functional.
So when you detect an kCFErrorDomainWinSock: 10055 error, updating your drivers may be a good bet. But it is time consuming and shouldn’t be viewed as a quick fix.
Here’s the step-by-step process you can go through to update drivers for Windows 8, Windows 8.1 and Windows 10.
- Check the site of your hardware maker for the latest versions of all the drivers you need. Download and extract them. We strongly advice going with original drivers. In most cases, they are available for free on the vendor website. Installing an incompatible driver causes more problems than it can ever fix.
- Open “Device Manager” from the Control Panel.
- Go through the various hardware component groupings and choose the ones you would like to update.
- On Windows 10 and Windows 8, right-click on the icon of the hardware you would like to update and click “Update Driver”.
- On Windows 7 and Vista, you right-click the hardware icon, choose “Properties”, navigate to the Driver panel, and then click “Update Driver”.
- Next you can let your device automatically search for the most compatible drivers, or you can choose to update the drivers from the versions you have on your hard drive. If you have an installer disk, then the latter should be your preferred course of action. The former may often get the driver selection incorrect.
- You may need to navigate a host of warnings from the Windows OS as you finalize the driver update. These include “Windows can’t verify that the driver is compatible” and “Windows can’t verify the publisher of this driver”. If you know that you have the right one in line, click “Yes”.
- Restart the system and hopefully the kCFErrorDomainWinSock: 10055 error should have been fixed.
Step 7 – Call the Windows System File Checker into Action
By now the kCFErrorDomainWinSock: 10055 plaguing your device should have been fixed. But if you haven’t resolved the issue yet, you can explore the Windows File Checker option.
With the Windows File Checker, you can audit all the system files your device needs to operate, locate missing ones, and restore them.
Sound familiar? It is almost like “System Restore”, but not quite. The System Restore essentially takes you back in time to a supposedly perfect set up of system files. The File Checker is more exhaustive.
It identifies what is amiss and fills the gaps.
- First and foremost, open up an elevated command prompt.
- Next, if you are using Windows 8, 8.1 or 10, enter “DISM.exe /Online /Cleanup-image /Restorehealth” into the window and press Enter.
- The process of running the Deployment Image Servicing and Management (DISM) tool may take several minutes.
- Once it completes, type the following command into the prompt “sfc /scannow”.
- Your device will now go through all protected files and if it detects an anomaly, it will replace the compromised version with a cached version that resides at %WinDir%\System32\dllcache.
Step 8 – Is your RAM Corrupted? Find Out.
Is it possible? Can the memory sticks of your device trigger Error 10055?
It is unlikely – because the RAM chips have no moving parts and consume little power. But at this stage, if all else has failed, diagnosing your RAM may be a good move.
You can use the Windows Memory Diagnostics Tool to get the job done. Users who are on a Linux or Mac and are experiencing crashes can use memtest86.
- Open up your device and go straight to the “Control Panel”.
- Click on “Administrative Tools”.
- Choose “Windows Memory Diagnostic”.
- What this built-in option does is it burns an ISO image of your RAM and boots the computer from this image.
- The process takes a while to complete. Once it is done, the “Status” field at the bottom of the screen populates with the result of the diagnosis. If there are no issues with your RAM/memory, you’ll see “No problems have been detected”.
One drawback of the Windows Memory Diagnostic tool pertains to the number of passes it runs and the RAM segments it checks.
Memtest86 methodically goes over all the segments of your memory – irrespective of whether it is occupied or not.
But the Windows alternative only checks the occupied memory segments and may be ineffective in gauging the cause of the kCFErrorDomainWinSock: 10055 error.
Step 9 – Is your Hard Drive Corrupted? Find Out.
Your RAM or working memory isn’t the only culprit that may precipitate an kCFErrorDomainWinSock: 10055 error. The hard drive of your device also warrants close inspection.
The symptoms of hard drive error and corruption span:
- Frequent crashes and the Blue Screen of Death (BSoD).
- Performance issues like excessively slow responses.
- Errors like Error 10055.
Hard drives are definitely robust, but they don’t last forever.
There are three things that you can do to diagnose the health of your permanent memory.
- It is possible that your device may have a hard time reading your drive. This can be the cause of an kCFErrorDomainWinSock: 10055 error. You should eliminate this possibility by connecting your drive to another device and checking for the recurrence of the issue. If nothing happens, your drive health is okay.
- Collect S.M.A.R.T data by using the WMIC (Windows Management Instrumentation Command-line) in the command prompt. To do this, simply type “wmic” into the command prompt and press Enter. Next follow it up with “diskdrive get status”. The S.M.A.R.T status reading is a reliable indicator of the longevity of your drive.
- Fix what’s corrupt. Let’s assume you do find that all isn’t well with your hard drive. Before you invest in an expensive replacement, using Check Disk or chkdsk is worth a shot.
- Open the command prompt. Make sure you are in Admin mode.
- Type “chkdsk C: /F /X /R” and press “Enter”. “C” here is the drive letter and “R” recovers data, if possible, from the bad sectors.
- Allow the system to restart if the prompt shows up.
- And you should be done.
These steps can lead to the resolution you’re seeking. Otherwise the kCFErrorDomainWinSock: 10055 may appear again. If it does, move to Step 10.
Step 10 – Update Windows OS
Like the software applications you use to render specific tasks on your device, the Operating System also requires periodic updates.
Yes, we’ve all heard the troubling stories.
Devices often develop problems post unfinished updates that do not go through. But these OS updates include important security patches. Not having them applied to your system leaves it vulnerable to viruses and malware.
And may also trigger Error 10055.
So here’s how Windows 7, Windows 8, Windows 8.1 and Windows 10 users can check for the latest updates and push them through:
- Click the “Start” button on the lower left-hand corner of your device.
- Type “Updates” in the search bar. There should be a “Windows Update” or “Check for Updates” option, based on the OS version you’re using.
- Click it. The system will let you know if any updates are available.
- You have the convenience of choosing the components of the update you’d like to push through. Always prioritize the security updates.
- Click “OK” followed by “Install Updates”.
Step 11 – Refresh the OS to Eliminate Persistent kCFErrorDomainWinSock: 10055 Error
“Windows Refresh” is a lifesaver.
For those of you who are still with us and nothing has worked to eliminate the Error 10055, until recently, a fresh install of Windows would have been the only option.
Not anymore.
The Windows Refresh is similar to reinstalling your Windows OS, but without touching your personal data. That’s hours of backup time saved in a jiffy.
Through the Refresh, all your system files become good as new. The only minor annoyance is the fact that any custom apps you’ve installed are gone and the system applications you had uninstalled are back.
Still, it is the best bet as the final step of this process.
- Enter the “Settings” of your PC and click on “Change Settings”.
- Click “Update and recovery” and then choose “Recovery”.
- Select “Keep my files”. This removes apps and settings, but lets your personal files live on.
- You’ll get some warning messages about the apps that will be uninstalled. If you’ve gone through a recent OS upgrade, the Refresh process makes it so that you can’t go back to your previous OS version – if you should ever feel the need to do it.
- Click the “Refresh” button.
Are you using an older version of Windows that doesn’t come with the power to “Refresh”?
Maybe it is time to start from scratch.
- Enter your BIOS set-up.
- This is where you need to change your computer’s boot order. Make it so that the boot happens not from the existing system files, but from the CD/DVD Drive.
- Place the original Windows disk in the CD/DVD drive.
- Turn on or restart the device.
- Choose where you’d like the system files to be installed.
- Your PC will restart several times as the process runs its course.
FAQ’s
What are Runtime Errors?
A runtime error, also often known as a program error, occurs while the program is active and running. The result of the error may lead to a program crash. However, there are other types of similar program errors such as logic errors and memory leaks. More commonly known as bugs, such errors are usually identified during the debugging process.
Can I Fix Runtime Errors Myself?
You can solve Runtime Errors like kCFErrorDomainWinSock: 10055 on your own, however we only recommend this for folks who are a little more experienced than others with diagnosing and fixing computer errors. The right way to fix the error depends largely on the cause of the error, which may be a little hard to diagnose if you do not know much about computers. Also there is a danger of unintentionally causing additional problems.
Should I Restore My Computer to Fix Runtime Errors Like Error 10055?
Restoring your computer to an earlier version may solve the problem, depending on what’s causing the runtime error. For example, if it’s due to a hardware issue then restoring your computer to an earlier date may not solve the problem. However, if it’s because of a newly installed program, then restoring to a date before the corrupt program was installed may do the trick.
Start Download Now
Author:
Curtis Hansen has been using, fiddling with, and repairing computers ever since he was a little kid. He contributes to this website to help others solve their computer issues without having to buy a new one.
Socket Error 10055 — No Buffer Space Available
Error 10055 means that Windows has run out of TCP/IP socket buffers because too many connections are open at once.
Things to check if this happens are:
-
Is there any other TCP/IP software running on the same PC as VPOP3 — eg a proxy server
-
Use a virus scanner to check for malware, as some malware is badly written and will use a lot of connections
-
Use a program such as TCPView or NETSTAT (with the -b parameter) to see which programs have connections open
Current versions of Windows can support many thousands of IP connections at once. Server versions can support more than desktop versions if you have a busy server, so it is unlikely that VPOP3 on its own will deplete the socket buffers, and the problem is usually some other software.