I have a client who uses this software.
They are complaining it is not connecting suddenly starting on 5.30.16.
It has been working for over a year. We are a MSP so I have all tickets documented, and we have no firewall changes requested on that day. In fact we do not block any outbound ports on our firewalls.
when i try to telnet to your server, server.rultils.com on 563 it fails. That tells me your server is not accepting connections on 563.
28.05.2016---02:36:21:487 96 Internet-ID: Connection established ID: 293-446-546; Port: 563; Try count: 2
29.05.2016---02:35:31:361 96 Internet-ID: Connection established ID: 293-446-546; Port: 5655; Try count: 1
30.05.2016---02:35:26:366 63 Exception: Socket Error # 10054 Connection reset by peer. (EIdSocketError). Information
30.05.2016---02:35:26:471 63 Exception: Socket Error # 10054 Connection reset by peer. (EIdSocketError). Information
30.05.2016---02:35:31:514 96 Internet-ID ErrorCode <> 0 Error code: 1
30.05.2016---02:39:35:178 96 Internet-ID: Unable to connect to ID server. Address: server.rutils.com; Port: 563; Connect timed out.(EIdConnectTimeout)
30.05.2016---02:39:40:183 96 Internet-ID ErrorCode <> 0 Error code: 1
30.05.2016---02:43:43:858 96 Internet-ID: Unable to connect to ID server. Address: server.rutils.com; Port: 563; Connect timed out.(EIdConnectTimeout)
30.05.2016---02:43:48:863 96 Internet-ID ErrorCode <> 0 Error code: 1
30.05.2016---02:47:52:512 96 Internet-ID: Unable to connect to ID server. Address: server.rutils.com; Port: 563; Connect timed out.(EIdConnectTimeout)
30.05.2016---02:47:57:519 96 Internet-ID ErrorCode <> 0 Error code: 1
30.05.2016---02:52:01:161 96 Internet-ID: Unable to connect to ID server. Address: server.rutils.com; Port: 563; Connect timed out.(EIdConnectTimeout)
30.05.2016---02:52:06:167 96 Internet-ID ErrorCode <> 0 Error code: 1
30.05.2016---02:56:09:776 96 Internet-ID: Unable to connect to ID server. Address: server.rutils.com; Port: 563; Connect timed out.(EIdConnectTimeout)
I have tried to install this internally on on test machines and get the same error.
They have 6 machines doing this and it all started on 5/30/16.