The server logs report Error 10053 during a backup session from one client. What can cause these errors, and how do I fix it? I also see Error 10057 occasionally on the server. Note: These are non-critical errors (warnings, really) and are do not cause software failure.

Causes: There are several, all caused by issues unrelated to the RBS software itself. This is a general warning caused by 1) a temporary loss of network connectivity; 2) misconfigured Server-side router or firewall; 3) bad Network Interface Card; 4) Server Monitoring service

Solution:

First make sure that your RBS Server tests fine using the Online Server Tester: http://remote-backup.com/support/testr bs.htm

If the above test fails, it is most likely that your RBS Server’s router or firewall isn’t properly configured. Recheck your server settings and router/firewall settings. Use the following article as a guide:

DATACON: ERROR: 10057 SERVER IS UNABLE TO CONNECT TO CLIENT http://remote-backup.com/rbstech/TS10 0290.HTM

This issue is caused when the Client or the Server attempts to open a connection, and the connection never completes. If a client opens the connection, but sends no message, the port eventually gives up and issues an error 10053.

This can be caused by several reasons:

1. Server Monitors can cause this error, because they connect to test the Server, but the port resets because no data are transferred. The Server Monitor provided by RBS does not cause this issue.

2. Command Port (21 or 2774) of the RBS Server is improperly routed through the router serving the RBS Server. For example: If the server’s internal IP address is 10.0.0.2, the port forwarding rule for command port should be routed to 10.0.0.2 address.

Make sure the right ports are open on your server-side router. The ports required on the server are below:

21 or 2774 (Primary or Command port of RBS Server)

1024-2048 (Passive mode port range or Data ports). This range should match the Data Port range defined under Tools-Properties on RBS Manager.

This error has also been attributed to the following:

* A hiccup in the network. * A bad network interface card (NIC) on server. * Faulty routers. * Other applications interfering with connections.

 Print This Page  Email This Page