Connect failed. (10060) connection failed not properly respo

Here you can write your Problems with Backups.

Moderator: sepma

Post Reply
deyjvu
Posts: 7
Joined: May 9th, 2007, 7:10 am

Connect failed. (10060) connection failed not properly respo

Post by deyjvu » September 6th, 2011, 2:40 am

One site is getting this error a lot but the wording is sometimes a little different but the result is the same "connect() failed. (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to " the backup fails.

From the backup job it shows as:

2011-09-06 10:06:36: sbc-1009: Error: XBSA Call BSACreateObject failed with message: Access to the requested object is not possible. connect() failed. (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2011-09-06 10:06:36: sbc-3005: Info: Closing saveset.
2011-09-06 10:06:36: sbc-3052: Info: Items processed correctly: [0]. Not processed or incorrectly processed items: [0].
2011-09-06 10:06:36: sbc-1156: Error: Operation failed!

What I found is that the path in these backups, which are all of Windows servers by the way, are usually missing or the name changed or something along these lines. It isn't really an error on the part of SEP but more a problem with the names of directories being changed but the backup jobs not being changed subsequently.

Thought I would share this with others who may also see these errors and wonder what they meant.

fosep
Posts: 15
Joined: May 18th, 2005, 7:02 pm
Location: Miesbach

Re: Connect failed. (10060) connection failed not properly r

Post by fosep » November 9th, 2011, 12:41 am

Hi,

this error can occur when having a firewall respectively a virus protection. SEP sesam establishes a data- and a control connection between a client and the server and the second connection will be established by the Sesam server (like active FTP). If there is a firewall, which does not allow to open ports at the client site, you could receive 10060. Also a virus protection could block the request.
Otherwise the problem could have to do with NAT (network address translation), if the client and the server are not in the same subnet (or connected via VPN) and a router is necessary to connect both endpoints. In this case you would have to adjust the way back to the Sesam client.

BR, Florian

Post Reply