Error Bpbrm Socket Read Failed, an Existing Connection Was Forcibly Closed by the Remote Host

Socket Errors 10060, 10061, 10064, 10065

A socket mistake in the 10060 range is a Winsock error. Information technology is generally caused by either outgoing connexion bug or connectedness problems on the host finish.

Outgoing connections tin be affected by the presence of firewall or anti-virus software on the local computer or network connection. Either can block the ports needed to make a successful FTP connection to the remote server. For a regular FTP session, either disable the firewall or anti-virus software or configure them to permit CuteFTP to establish an FTP session over ports 20 and 21.  Consult the documentation or help file for your specific firewall or antivirus software product for instructions. Usually the manufacturer of the device or software will as well have specific instructions available on their Web site. If you lot proceed to receive the same error afterwards insuring ports 20 and 21 are open, contact the administrator of the site you lot are trying to connect to.

For more fault lawmaking data, refer to Knowledge Base article 10140 at http://kb.globalscape.com.

WSAETIMEDOUT (10060)

10060 is a connection-timeout error that commonly appears when the client does not receive a response from the server for a specific command. This fault oft occurs when you try to connect in PASV manner to a server that prefers PORT for information connections. If you lot see an mistake log similar to the 1 below, in the Site Backdrop of the problem site, click the Blazon tab, then change the Data Connectedness Type to Use PORT.

Command:> PASV

227 Entering Passive Style (thirty,xx,xxx,twenty,x,thirty).

Command:> LIST

Status:> Connecting ftp data socket xxx.xx.xxx.xx:xxxx...

ERROR:> Can't connect to remote server. Socket error = #10060.

ERROR:> Failed to found data socket.

If you yet receive a 10060 error, the server may exist trying to send a listing for a very big directory (with many thousands of files) causing the client to time-out while waiting. Endeavour increasing the fourth dimension-out value in the Global Options dialog box (Tools > Global Options > Transfer > Reconnect and resume in [ northward ] seconds if null received ) to a higher value, such equally 45 or 60 seconds.

1. The connectedness fails due to an error or timeout.

2. Verify that the destination IP address is correct.

3. Increase the connection timeout threshold under Global Settings > Connectedness .

4. Switch to the reverse data connection type (PASV or PORT) under Site Settings > Type tab.

5. Verify that the problem is not local by trying to connect to an alternate server.

6. If a server proper name was used, verify information technology resolves to the correct accost.

7. If using a local server tabular array for server name resolution, check to see that information technology doesn't resolve to an obsolete address.

8. Try pinging the address. (See Troubleshooting Tips for details.)

9. If you are using a router, verify the router is up and running (check by pinging information technology and so ping an address outside of the router).

10. Do a traceroute to the destination to verify all routers along the connection path are operational. (See Troubleshooting Tips for details.)

11. Verify that your subnet mask is setup properly.

WSAECONNREFUSED (10061)

10061 is a Connection Refused mistake sent to y'all by the server. You lot could not make a connectedness because the target reckoner actively refused information technology. The most mutual cause is an incorrectly configured server, full server, or wrong Port specified past the client.

To change your connection Port for an FTP site

1. Open the Site Manager , then click the site.

2. On the main carte, click File > Properties.

3. Click the Type tab.

4. In the Port box, type the right port number.

Sometimes a 10061 error is caused by either a firewall or anti-virus software presence on the local computer or network connection.  Either one may be blocking the ports needed to make a successful FTP connectedness to the server.

For a regular FTP session, please either disable the firewall or anti-virus software or configure it to allow CuteFTP to establish an FTP session over ports 20 and 21. Please consult the documentation or aid file for your specific firewall or antivirus software product for farther instructions. Usually, the manufacturer of the device or software has specific instructions available on their Web site.

If you keep to receive the same error later on insuring ports twenty and 21 are open up, please contact the administrator of the site where you are trying to connect.

1. The remote host actively refused the attempt to connect to information technology.

2. Verify that the destination server name or IP address is correct

3. Verify that the connection port number is right (under Site Settings > Blazon tab).

4. The remote server may be temporarily or permanently inaccessible (try once more later).

5. Verify that you lot have chosen the right protocol (SSH2, SSL, FTP, etc.) and have setup all required options for that protocol.

6. Verify that the destination IP address and port numbers are correct.

7. The remote server may be refusing multiple connections from the aforementioned client. Try using only one connexion thread when connecting to this item server (Site Settings > Options).

8. Endeavour pinging the address.

9. If you are using a router, verify the router is up and running (check past pinging information technology then ping an address outside of the router).

10. Do a traceroute to the destination to verify all routers along the connection path are operational.

11. Verify that your subnet mask is setup properly.

WSAESERVERDOWN (10064)

• The server is temporarily or permanently unreachable. Verify that the destination host name or IP address is correct and endeavour again later.

WSAESERVERUNREACH (10065)

• The server is unreachable. Verify that the destination host name or IP address is correct and endeavour again later.

bogardbefind.blogspot.com

Source: https://help.globalscape.com/help/archive/cuteftp8/Socket_errors_10060_10061_10064_10065.htm

Share this post