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
21k4 gold badges62 silver badges121 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
557k31 gold badges460 silver badges774 bronze badges
2
In the component «IdFTP», change the following properties:
- «Passive» = «False»
- «TransferType» = «ftASCII»
Litty
1,8561 gold badge16 silver badges35 bronze badges
answered Feb 17, 2016 at 19:22
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 208 votes.
Article has been viewed 355K 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
21k4 gold badges62 silver badges121 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
557k31 gold badges460 silver badges774 bronze badges
2
In the component «IdFTP», change the following properties:
- «Passive» = «False»
- «TransferType» = «ftASCII»
Litty
1,8561 gold badge16 silver badges35 bronze badges
answered Feb 17, 2016 at 19:22
Table of Contents
If you cannot read from data socket. socket error = # 10054 on your computer, this guide may help you.
Approved
The software to fix your PC is just a click away — download it now.
g.Bad socket 10054 could be the result of that particular remote server or other history of network devices forcibly closing or dropping the connection. The most common cause of output error 10054 is the use of an invalid FTP exclusive address. Check this to make sure you are on the correct FTP host address.
g. Receive
I am getting FTP socket error 10054 when I try to connect to FTP to download. Please fix this type of problem.
This is a reserve ticket recently received from one of our customers through our dedicated support team.
This FTP error occurs whenever an existing remote connection is forcibly closed by a private host.
Today we are going to take a look at the eight most common causes of outbound FTP error 10054 and how to fix them.
FTP Connection Error 10054 – Short Explanation
Check if the point of the computer or host is correct.Check another computer or even a host to make sure everything is on or off right away.Make surethat the entire network between you and the other computer is still active.Check this network configuration of another home PC if it is not available.
FTP socket error 10054, in which the remote host usually ends or forcibly drops the existing connection for most FTP clients. And users will get the complete error message as described below.
Approved
The ASR Pro repair tool is the solution for a Windows PC that’s running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don’t suffer from a sluggish computer any longer — try ASR Pro today!
Failed to download.Socket error 10054Resets the peer connection number.
This closed connection can be on the FTP server side or, presumablyExceptionally, on the user side. Therefore, our support specialists mainly check the server logs to make sure it is just a network that only runs on the client side or only on the server side.
FTP Connection Error 10054 – Reasons And Solutions
Now let’s take a look at the root causes of this error and how the support specialists rule out any possibility of fixing this problem.
1) Problems with the remote server
FTP socket 10054 can fail due to a problem on the remote server side. This error usually occurs when continuing with a new script.
- The remote host reboots or reboots very suddenly.
- The network of the remote server is usually down.
- The user account on the remote web server can be disabled or.
- Too many users are accurately connected to the server.
Interface
How to fix it?
First, each support technician checks the number of remote hosts using the ping command.
pingtest.remotehost.com
К In addition, we check the server time to make sure the server restart has started.
Availability
This way I can actually confirm if restarting the device caused any problems for the consumer. In addition, we ensure that Circle’s online settings on the server remain intact and that the FTP user can connect to the isolated host.
2) Invalid FTP host
After we confirm there are problems with the remote host, each person will review the FTP client draft. One of the most common elements of this error is dealing with an invalid FTP host address.
Users must always enter the hostname information associated with the ftp host field in order to connect. For example, clients almost always include ftp.servername.com and servername.com.
However, a typo in the FTP hostname or the missing hostname field may well lead to this error. Even one additional FTP hostname can cause problems.
How to solve the problem?
First of all, our support team confirms the DNS connection from FTP hosts to the exmouths that don’t get enough command.
dig ftp.servername.com
Also make sure the client is actually using the correct FTP hosting plan in their FTP client.
3) Firewall
Similar restrictions
Firewalls can interfere and disrupt the connection to the FTP site. Also, antivirus or anti-spyware tools should absolutely act like second layer software and close connections. Even plan your firewalls on the ISP side so that the router can block people from communicating through the FTP ports.
How do I fix these two?
Telephone
In some cases, we ask customers to disable security applications such as Windows Firewall, Antivirus, etc. on at least one of their systems, one by one. This helps us identify the application that … is causing the problem and fixing its settings.
To troubleshoot network-level firewall issues, our support staff also require customers to turn off their routers and gateways in order to install the network Calling along the channel. This way we can check the actual event that the problem is at an intermediate level. After we confirm that the problem is with staging resources, we ask customers to work diligently with their ISPs to configure the ISP’s firewall to allow connections to the FTP ports.
[Is there a firewall violation on your server? Click here and ask one of our server experts to fix your firewall rules.]
4) Problems with file transfer mode
Moving files can be done in two different ways: active and passive mode, best and FTP clients switch to passive mode by default. Suffice it to say that remote servers only accept connections in active or PORT mode, which results in this error.
As we used to
Solution?
The steps to enter active mode depend on the FTP client software used by the client.
In this way, our dedicated engineers receive the detailsProvide information about the FTP client of specific users and help them navigate those specific settings and actively activate the mode. For example, we activate active mode in Filezilla via Site Manager Transfer> settings Transfer> mode.
5) Connection timeout problems
FTP outbound error 10054 occurs when users try to upload relatively large files that conflict with the FTP client’s internal timeout settings. For other content, the download process may fail if the user is downloading large amounts of content if it does not complete within the connection timeout.
How do my wife and I fix this?
However, in such cases, we increase the number of users to increase the fine timeout settings in their FTP client. For example, we increase the connection timeout via Edit> Preferences> Connection> Timeout> Timeout in seconds.
Alternatively, in some cases, many people disable this timeout value by adding its value 0.
6) Advanced FTP Client Settings
from
Some FTP clients, such asThose like CuteFTP use advanced configurations that may not be compatible with the remote system you are connecting to. For example, some remote servers can be configured to allow a limited number of flight sessions or. However, some users manage their FTP client to schedule a large number of concurrent file transfers. In such cases, the remote server ends the connection and raises an error in the file transfer protocol, socket 10054.
Likewise, in FTP client functions, users oversize the send and receive stream sizes. However, this can often conflict with the values on the remote server and cause problems.
How to fix it?
Telephone
In some cases, our dedicated technicians help clients select FTP clients and limit the number of failover connections. For example, on the CuteFTP responder, change this setting under Tools> Global Options> Connection> Max Concurrent Trainer Transfers persite “>” Transfer “.
We also optimize email and hence get buffer size values. For example, we resize the stream in Tools> World Options> Stream to CuteFTP.
[Do you need help with your FTP problem? Our support specialists can really help you here.]
Conclusion
In short, FTP-10054 plugin error can occur due to remote server issues, firewall restrictions, etc. Today we discussed 6 ideal reasons for this failure that our dedicated engineers should take action to resolve.
PREVENT YOUR SERVER FROM DAMAGE!
Never lose clients suffering from device speed again! Let us help you.
Our training server monitors and maintains your business server 24 hours a day to make it super fast and secure.
The software to fix your PC is just a click away — download it now.
Socket error 10054 often means that the Internet connection has been lost. The root cause of this socket error is because the connection to the server was ignored by something outside the server. In most cases, this is an action intentionally or accidentally triggered by the user.
FTP logout error 10054 indicates that the exotic host has forcibly terminated or dropped an existing FTP client connection. This interrupted connection may be due to mentoring from the FTP server side or from the user side.
