I receive the ftp socket error 10054 when I try to connect to FTP for an upload. Please fix this problem.
That was a recent support ticket received from one of our customers as part of our Dedicated Support Services.
This FTP error occurs when the existing remote connection is forcibly closed by the remote host.
Today, let’s see the top 6 reasons for the ftp socket error 10054 and how our Support Engineers fix them.
FTP socket error 10054 – A Brief explanation
A socket is the endpoint of client-server communication.
FTP socket error 10054 indicates that the remote host has forcibly terminated or reset the existing connection of the FTP client. And, users see the complete error message as shown below.
Upload failed. Socket Error # 10054 Connection reset by peer.
This broken connection can be at the FTP server side or at the user’s side. So, our Support Engineers primarily check the server logs to determine if this is a network error at the client side or at the server side.
FTP socket error 10054 – Reasons & Solutions
Now, let’s see the main causes of this error and how our Support Engineers rule out each possibility to fix this problem.
1) Remote server issues
FTP socket error 10054 can occur due to the problems at the remote server end. This error usually occurs during the following scenarios.
- The remote host is suddenly rebooted or restarted.
- Network interface of the remote server is disabled.
- User’s account on the remote server is disabled or restricted.
- Too many users logged on to the server.
How we fix?
Firstly, our Support Experts check the availability of the remote host using the ping command.
ping test.remotehost.comIn addition to that, we check the uptime of the server to verify that a reboot has been initiated on the server.
uptimeThus, we can confirm whether the server reboot created problems for the user. Moreover, we ensure that the network settings on the server are intact and the FTP user is allowed to connect to the remote host.
2) Invalid FTP host
Once we’ve confirmed that there are no issues at the remote host, we then check the FTP client settings. And, one of the common reasons for this error is the use of invalid FTP host address.
Users should enter the hostname details in the FTP host field to initiate a connection. For example, customers usually give it as ftp.servername.com or servername.com.
However, a typo in the FTP hostname or missing hostname field can result in this error. Even a single additional space in the FTP hostname can create problems.
How we fix?
Firstly our Support Experts confirm the DNS connectivity of the FTP host using the dig command.
dig ftp.servername.comFurther, we double check and confirm that customer is using the correct FTP host address in their FTP client.
3) Firewall restrictions
Similarly, firewalls can act up and break the FTP connection. Moreover, Antivirus or Antispyware tools can act as a second layer firewall and close the connections. Even the firewalls at the ISP end, firewall on a router can block connections through FTP ports.
How we fix?
In such cases, we ask the customers to temporarily disable the security applications such as Windows firewall, Antivirus, etc. one by one on their system. This helps us to identify the application that’s exactly creating problems and fix it’s settings.
Likewise, to resolve the firewall issues at the network level, our Support Engineers ask the customers to disable gateways and routers to establish a direct connection. Thus, we can verify if the problem lies at the intermediate level. Once we’ve confirmed that the problem is with the intermediate devices, we ask the customers to work with their ISPs to configure ISP firewall to allow connections to FTP ports.
[Messed up firewall rules on your server? Click here and get one of our Server Experts to fix your firewall rules.]
4) Issues with File transfer mode
File transfer can happen in 2 types – Active and Passive mode, and most of the FTP clients use Passive mode by default. However, some remote servers accept the connections only in Active mode or PORT mode resulting in this error.
How we fix?
The steps to enable Active mode differs based on the FTP client software used by the customers.
So, our Dedicated Engineers get the FTP client details from the users, and help them navigate the settings and enable Active mode. For example, we enable Active mode in Filezilla from Site Manager > Transfer settings > Transfer mode.
5) Connection timeout issues
Ftp socket error 10054 occurs when users try to upload relatively large files which conflict with the internal timeout settings of the FTP client. In other words, when user uploads a large file, the upload process may fail if it’s not completed within the predefined connection timeout limit.
How we fix?
In such cases, we recommend users to increase the connection timeout settings in their FTP client. For example, we increase the connection timeout limit from Edit > Settings > Connection > Timeout > Timeout in seconds.
Alternatively, in some cases we disable this timeout value by making it’s value as 0.
6) Advanced FTP client settings
Some of the FTP clients such as CuteFTP use advanced configurations which may not be compatible with the remote server you’re connecting. For example, some remote servers may be configured to allow only a limited number of connections or sessions. However, some users configure their FTP client to set large number of concurrent file transfers. In such cases, remote server terminates the connection and result in ftp socket error 10054.
Similarly, users set large values for send and receive buffer sizes in their FTP client settings. However, this may conflict with the remote server values and causes problems.
How we fix?
In such cases, our Dedicated Engineers help the customers navigate the FTP client settings and limit the number of concurrent connections. For example, on CuteFTP client, we change this parameter from Tools > Global options > Connection > Per site max concurrent transfers >Transfer.
Moreover, we tweak the send and receive buffer size values accordingly. For instance, we change the buffer size from Tools > Global options > Transfer in CuteFTP.
[Need help in resolving your FTP issue? Our Support Experts can help you here.]
Conclusion
In short, ftp socket error 10054 can occur due to remote server issues, firewall restrictions, and more. Today, we’ve discussed the top 6 reasons for this error and how our Dedicated Engineers fix them.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
THE INFORMATION IN THIS ARTICLE APPLIES TO:
- CuteFTP® Home (All Versions)
- CuteFTP Pro® (All Versions)
SYMPTOMS
During an FTP session, the following error is encountered:
ERROR:> Can’t read from control socket. Socket error = #10054.
CAUSE & RESOLUTION
A socket error 10054 may be the result of the remote server or some other piece of network equipment forcibly closing or resetting the connection. In some other situations a change to the default CuteFTP connection settings may be needed for connections to this particular remote FTP server.
- The most common cause for a socket error 10054 is the use of an invalid FTP host address. Double-check to make sure that you are using the correct FTP host address.
- Before making any changes to the default configuration for CuteFTP, wait and retry your connection later. A socket error 10054 can also be caused by any of the following reasons:
- The remote server was stopped or restarted.
- The remote network interface is disabled for some reason.
- There are too many users logged on to the server.
- Your account on the remote server is restricted for some reason.
- If this error started happening after a recent upgrade to your Web browser, (for example, after upgrading to Internet Explorer 7.0) please browse to KB Article ID 10294 for instructions.
- If you are satisfied that the remote server or user account is not at fault, and you encountered this error either when first establishing the connection or when starting a file transfer, then it may be necessary to change the data connection type. CuteFTP uses passive (PASV) mode by default but for this remote server you may need to use active (PORT) mode instead.
- To make the switch from PASV mode to PORT mode in CuteFTP Home, open the Site Manager and click once on the the name of the problem site on the left side of the window. On the Type tab change the Data Connection Type to Use Port.
- If you are using CuteFTP Professional, in the Site Manager, right-click on the name of the problem site and click Site Properties. On the Type tab, change the Data Connection Type to Use Port.
- Note: If changing the data connection type has no effect then you should return this setting to the default of Use global settings.
- In some other situations, the remote FTP server may have difficulty dealing with some of the more advanced capabilities used by the default configuration of CuteFTP Professional. In such situations, configuring CuteFTP Professional so that only one file at a time is transferred, may help.
- If the solutions provided above do not resolve this problem then it is possible that the transfer send and receive buffer size may be set too high. See the resolution provided in KB Article ID 10293 for further instructions.
Share Article
On a scale of 1-5, please rate the helpfulness of this article
Optionally provide additional feedback to help us improve this article…
Thank you for your feedback!
Last Modified: 8 Years Ago
Last Modified By: kmarsh
Type: ERRMSG
Rated 2 stars based on 207 votes.
Article has been viewed 352K times.
When I call the function
IdFtp.List(myList, '', false);
afterwards I have logged in and changed the ftp directory, I get a socket-error #10054 exception («Connection reset by peer.») occesionally.
When I call that function e.g. 20 times consecutively I get that exception 1 time.
That problem I have only encountered on Vista OS.
Does anybody know what the problem is or how I can avoid it?
asked Mar 28, 2012 at 13:12
1
Not much you can do about this, because the disconnection is done by the FTP server.
You have a few choices:
- Increase (or disable) the timeout settings (every FTP server has a different name for it) on your FTP Server connection settings.
- Tell server that you are alive by sending
NOOPcommand periodically (switching to Passive mode can also help). - Catch that exception and reconnect silently (This is my preferred solution because we have many FTP servers and I don’t trust the sys-admins to change the FTP server time-out settings).
Here is a screen-shot from FileZilla FTP server time-out settings:
Note that with the above settings, the FTP client will be disconnected after 2 min of non-activity.
setting that value to 0, will disable the time-out.
answered Mar 28, 2012 at 23:27
kobikkobik
20.9k4 gold badges60 silver badges118 bronze badges
1
The FTP protocol uses multiple socket connections. Every time you call List(), a new socket connection is established to transfer the requested listing data. It sounds like the FTP server is not always closing the socket correctly at the end of a transfer.
answered Mar 28, 2012 at 20:24
Remy LebeauRemy Lebeau
536k30 gold badges444 silver badges750 bronze badges
2
In the component «IdFTP», change the following properties:
- «Passive» = «False»
- «TransferType» = «ftASCII»
Litty
1,8561 gold badge16 silver badges34 bronze badges
answered Feb 17, 2016 at 19:22
Moderators: Dorian (MJT support), JRL
-
gknopf
- Newbie
- Posts: 12
- Joined: Thu Feb 10, 2011 11:11 pm
- Location: Germany
FTP Socket Error 10054 Connection reset by peer
I have a script that uses FTP commands. Running it on an XP environment it quits with the error message
«Socket error # 10054 Connection reset by peer»
after a while 
. The compiled script and MSCHED.EXE are whitelisted in the firewall settings. So this should actually not happen.
What surprises me is that when I turn off the XP firewall the script will run without any problem. Same for the compiled script. Thus, it should be a standard XP firewall issue.
Has anyone encountered this issue and found a solution to it?
Thanks a lot!
-
olllllliii
- Pro Scripter
- Posts: 60
- Joined: Tue Dec 22, 2009 9:51 am
- Location: Mannheim ( Germany )
- Contact:
Post
by olllllliii » Fri Nov 09, 2012 3:17 pm
Which kind of firewall do u use…??
Which ports are opend ?
Do u use a VPN ?
————— most time it is following ———————
This error indicates that an existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, ( not in your case ..i know ) the host is rebooted or the remote network was somehow disabled. (i know without the firewall its working )
A socket error 10054 can also be caused by any of the following reasons:
** Attempt configuring your FTP connection by enabling or disabling passive transfer (select or clear Passive file transfer ). (A,I)
** Try adding the Macro Scheduler to the list of trusted applications of your firewall.
Oliver Hilger Mannheim
alias Olllllliii
-
gknopf
- Newbie
- Posts: 12
- Joined: Thu Feb 10, 2011 11:11 pm
- Location: Germany
Post
by gknopf » Sat Nov 10, 2012 11:06 am
Hi olllllliii,
Which kind of firewall do u use…??
Which ports are opend ?
Do u use a VPN ?
I use a Fritz!box router with standard setup (no port changes) and a XP computer with the Windows standard firewall. VPN is not in use and the compiled script is on the whitelist of the firewall. With Win7 this problem does not occur.
Changing active / passive did not produce a different result.
Содержание
- Pasv Offline 2 Error=10054
- Socket Error 10054 — kb.globalscape.com
- Error 10054 Connection Reset — Causes and Fixes — Net Onboard
- delphi — Indy «Connection Reset by Peer» Err. 10054 on .
- FTP issues Can’t connect to remote server. Socket error .
- SFXCL Command Failing with error 10054 — VanDyke Software .
- delphi — IdFtp.List throws socket-error #10054 .
- FTP PASV problem with Windows 7 firewall
- PASV command failed — SmartFTP Forums
- 1904412 — DBA cockpit connection XXX cannot be established .
- Troubleshooting — Troubleshooting FTP Connections .
- Pasv Offline 2 Error=10054 Fixes & Solutions
- Pasv offline2 error 10054
Pasv Offline 2 Error=10054
We have collected for you the most relevant information on Pasv Offline 2 Error=10054, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Pasv Offline 2 Error=10054 before you, so use the ready-made solutions.
Socket Error 10054 — kb.globalscape.com
- https://kb.globalscape.com/Knowledgebase/10235/Socket-Error-10054?Keywords=Compensating-controls
- CuteFTP uses passive (PASV) mode by default but for this remote server you may need to use active (PORT) mode instead. To make the switch from PASV mode to PORT mode in CuteFTP Home, open the Site Manager and click once on the the name of …
Error 10054 Connection Reset — Causes and Fixes — Net Onboard
- https://help.netonboard.com/knowledge-base/error-10054-connection-reset/
- Jun 23, 2020 · Error 10054 Connection Reset – Causes and Fixes Remote server or some other piece of network equipment forcibly closing or resetting the connection.
delphi — Indy «Connection Reset by Peer» Err. 10054 on .
- https://stackoverflow.com/questions/53601870/indy-connection-reset-by-peer-err-10054-on-specific-website
- The website in question (https://donet.rfi.it) does not accept TLS 1.0 anymore (probably why it went offline, to update its software), it will accept only TLS 1.1+ now. TIdHTTP is able to successfully establish a TCP/IP connection to donet.rfi.it:443 , but as soon as TIdSSLIOHandlerSocketOpenSSL sends a TLS 1.0 handshake request, the server .
FTP issues Can’t connect to remote server. Socket error .
- https://forums.cpanel.net/threads/ftp-issues-cant-connect-to-remote-server-socket-error-10054.52323/
- Apr 28, 2006 · Your suggestion for changing from passive to port would work if I was using passive. PASV However, the setting are for PORT and I’ve tried it both ways and I’ve tried auto detect. He is using cute ftp pro 7.1 I think. If anyone else has a suggestion let me know as I will try to change what or look at what sawbuck has suggested. Thanks Sawbuck.
SFXCL Command Failing with error 10054 — VanDyke Software .
- https://forums.vandyke.com/showthread.php?t=3750
- Aug 04, 2009 · I believe the above bit of information will help to resolve this issue. In the ‘File Transfer / FTP’ category of SecureCRT’s Global Options, enable ‘Limit local ports used for PORT connections’, then change the low to 8100.
delphi — IdFtp.List throws socket-error #10054 .
- https://stackoverflow.com/questions/9908265/idftp-list-throws-socket-error-10054-occasionally
- 2,811 2 2 gold badges 22 22 silver badges 36 36 bronze badges I got a similar issue when connecting, due to the FEAT command not being supported on my server, I set idftp.AutoIssueFEAT to false and the problem went away.
FTP PASV problem with Windows 7 firewall
- https://social.msdn.microsoft.com/forums/en-US/59f76b48-36e0-429f-a199-b9d6bfae5001/ftp-pasv-problem-with-windows-7-firewall
- Dec 28, 2010 · Hello, we have implemented a simple FTP server for Windows CE. We experience strange problems if we try to use FTP passive mode from a client running under Windows 7 x64 while the firewall is enabled. It turned out that the response to the PASV command will be rejected from the firewall (even . · Egmont – I have determined the problem is not within .
PASV command failed — SmartFTP Forums
- https://www.smartftp.com/static/forums/14/5793/pasv-command-failed/
- Jun 17, 2003 · PASV 501 PASV command failed — Unable to contact server——Connection with other FTP work . Log from other FTP-Client: WINSOCK.DLL: WinSock 2.0 — — connecting to 172.168.0.11:21 Connected to 172.168.0.11 port 21 220-InterScan FTP VirusWall NT 3.51 (Proxy Mode), PASV mode, Virus scan on 220 Secure Gateway FTP server ready.
1904412 — DBA cockpit connection XXX cannot be established .
- https://apps.support.sap.com/sap/support/knowledge/en/1904412
- About this page This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required). Search for additional results. Visit SAP Support Portal’s SAP Notes and KBA Search.
Troubleshooting — Troubleshooting FTP Connections .
- https://docs.netgate.com/pfsense/en/latest/troubleshooting/ftp.html
- Sep 01, 2020 · In pfSense® software versions 2.0.x and 2.1.x, the FTP proxy is in -kernel. The only options to control its behavior are an on/off switch and a list of ports to be used by the proxy. In pfSense software version 2.2.x and newer, there is no built-in FTP proxy. See Using NAT and FTP without a Proxy.
Pasv Offline 2 Error=10054 Fixes & Solutions
We are confident that the above descriptions of Pasv Offline 2 Error=10054 and how to fix it will be useful to you. If you have another solution to Pasv Offline 2 Error=10054 or some notes on the existing ways to solve it, then please drop us an email.
Источник
Pasv offline2 error 10054
С 1 июля 2017 прекращена поддержка программного продукта Frontol 4
С 9 ноября 2019 прекращена поддержка программного продукта Frontol 5
пруф
С 3 августа 2017 восстановление лицензий производится ТОЛЬКО через СервисДеск
Просьба обращаться к партнерам компании для оформления заявок в СД
Завсегдатай 
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
добрый! Ошибка при обмене через ftp — socket error #10054 connection reset by peer
Frontol 5-13-1 Лицензия Торговля 54ФЗ.
Чистой базой пробовал тот же результат.
POS АТОЛ Магазин у дома.
Через браузер заходит на FTP
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Специалисты
Сообщений: 5 968
Регистрация: 15.8.2012
Пользователь №: 57 857
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Партнеры
Сообщений: 14 906
Регистрация: 17.2.2007
Из: Москва
Пользователь №: 10 778
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
Я думал уже об этом Паш, но фишка в том что это не новая касса. Тут просто обновили с 4 на 5
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Специалисты
Сообщений: 5 968
Регистрация: 15.8.2012
Пользователь №: 57 857
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
Да. И с ней и без нее и по айпи и по доменному имени
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Специалисты
Сообщений: 5 968
Регистрация: 15.8.2012
Пользователь №: 57 857
Странно.
На 5.16 без опции «пассивный режим» вообще получаю ошибку «Server cannot accept argument.»
Проверил на 5.13.1 — тоже с включенной опцией «пассивный режим» — все грузится.
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
Странно.
На 5.16 без опции «пассивный режим» вообще получаю ошибку «Server cannot accept argument.»
Проверил на 5.13.1 — тоже с включенной опцией «пассивный режим» — все грузится.
Нам, то что сейчас проверить? Магазин как дураки уже неделю руками туда сюда обмены гоняем.
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Специалисты
Сообщений: 5 968
Регистрация: 15.8.2012
Пользователь №: 57 857
Давайте больше подробностей.
Как давно используется обмен по FTP?
Как часто случается эта ошибка?
Происходит ли хоть один обмен успешно?
Менялось ли что-нибудь в сетевом подключении? Провайдер, GSM-модем, настройки ОС?
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
Давайте больше подробностей.
Как давно используется обмен по FTP?
Как часто случается эта ошибка?
Происходит ли хоть один обмен успешно?
Менялось ли что-нибудь в сетевом подключении? Провайдер, GSM-модем, настройки ОС?
Давайте! на фронтол 4 работал этот же обмен с FTP. Работал он уже года 3. К слову с точно такими же параметрами (только другая папка обмена) работают еще 100 касс.
Ошибка всегда
Удачного обмена с момента обновления на фронтол 5 не было.
Ни чего кроме обновления фронтол не было. Все по старому.
И только что обновили кассу в другом месте из этой сети и снова ошибка такая же. При этом в день парни делают по 4 касс обновлений на 5 и используют одни и теже параметры подключения.
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Пользователи
Сообщений: 4 706
Регистрация: 30.10.2007
Пользователь №: 12 033
Завсегдатай
Группа: Партнеры
Сообщений: 342
Регистрация: 21.7.2008
Из: Екатеринбург
Пользователь №: 14 058
да, я тоже об этом сижу пару дней думаю. Программа хорошая много раз меня выручала.
Но хотелось бы без костылей
—Знание-страшная штука! А не знание-глупая!
Магистр слова
Группа: Специалисты
Сообщений: 5 968
Регистрация: 15.8.2012
Пользователь №: 57 857
А проблемы и из админки и из службы?
Может их в исключения файрвола/антивируса добавить?
Если и это не поможет, то попробуйте тяжелую артиллерию:
Настройте на одной из касс WireShark на подключение к этому FTP и запишите попытку обмена.
Судя по тому, что я успешно загружаю обмен с этого ФТП — проблема не в сервере и не во фронтоле.
Магистр слова
Группа: Специалисты
Сообщений: 4 072
Регистрация: 16.5.2008
Пользователь №: 13 449
Тестировщик на вашем FTP сервере не смог воспроизвести проблему. У меня складывается впечатление, что проблема в сетевых настройках.
Инфо из гугла по тексту ошибки
http://www.programmersforum.ru/showthread.php?t=238918
«Блиииииин. После пятой рюмки коньяка отключил антивирус Avast и все пошло без ошибок. Вот всегда приходится чьи-то корявые руки искать. «
«Рассмотрим следующий сценарий:
У вас есть компьютер под управлением Windows 7 или Windows Server 2008 R2.
На компьютере установлен драйвер фильтра интерфейс драйвера транспорта (TDI). Например драйвер фильтра TDI устанавливается при установке антивирусной программы McAfee VirusScan.
Приложение открывает прослушивания порта TCP на прием подключений.
В этом случае приложение может появиться следующее сообщение об ошибке:
WSAECONNRESET (10054) сброс подключения другим компьютером.
Существующее соединение было принудительно закрыто удаленным узлом.
Эта проблема возникает, поскольку драйвер TCP/IP не приводит к закрытию незавершенные подключения TCP. Вместо этого в драйвер TCP/IP отправляет уведомление, что драйвер TCP/IP готова к приему данных при создании незавершенные подключения TCP. Таким образом приложение получает экземпляр 10054 ошибку, которая указывает, что подключение сбрасывается при получении приложением данных из соединения.»
Источник
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.