Problems with Client connecting to server

Questions, problems, and other issues for Ascendis Caller ID that aren't covered by the other forums.
Post Reply
redimix
Posts: 4
Joined: Sat Mar 05, 2016 8:51 am

Problems with Client connecting to server

Post by redimix »

All PC running windows 10 Pro
using Whooz Calling Deluxe Ethernet Link.

Server is online and reporting calls correctly.
Not able to connect the client to read data from the Server.
Verified port 62965 is open on the server and the client, (open ports in the firewalls and even tried without any firewall)
Data log on the client keeps reporting.

EldSocketError #10060

I assume the client is not able to see the link to the Server.

Any help would be appreciated. javascript:emoticon(':oops:')

below is the complete read out log

3/5/2016 10:25:28 AM [INFO ] - Started instance $6070C
3/5/2016 10:25:29 AM [INFO ] - Ascendis Caller ID Version 3.0.0.0 (10/14/2011 9:46:32 AM) (RELEASE build type)
3/5/2016 10:25:29 AM [INFO ] - C:\Program Files (x86)\Ascendis Software\Ascendis Caller ID 3\CallerID.EXE
3/5/2016 10:25:29 AM [INFO ] - DBISAM engine version = 4.29 Build 4
3/5/2016 10:25:30 AM [INFO ] - Could not find a modem to use. In Control Panel, double-click the Modems icon to install a modem to use for monitoring calls.
3/5/2016 10:25:30 AM [INFO ] - cxFormatController.DateEditFormat="MM/dd/yyyy", SysUtils.ShortDateFormat="M/d/yyyy"
3/5/2016 10:25:51 AM [ERROR ] - Real-time client exception EIdSocketError: Socket Error # 10060 Connection timed out.
3/5/2016 10:26:51 AM [ERROR ] - Real-time client exception EIdSocketError: Socket Error # 10060 Connection timed out.
3/5/2016 10:27:51 AM [ERROR ] - (Repeat(s) of previous message suppressed) :oops: :oops: :oops:
Bill Root
Site Admin
Posts: 1025
Joined: Mon Jan 19, 2004 1:29 pm
Location: Perrysburg, OH
Contact:

Re: Problems with Client connecting to server

Post by Bill Root »

Hi redimix,

You are correct about the error code: 10060 means
Connection timed out.

A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
So, for some reason, the client can't talk to the server in spite of the firewall settings.

Can any client talk to the server? If not, the problem is on the server side. If yes, the problem is on the client side.

Can the client ping the server? (Run "ping" in a command window on the client computer)

Are you using any other security software on the client or server that might include a firewall? Examples include Norton, McAfee, Commodo, Avast, etc. If so, they will need configuration so Ascendis Caller ID can go through them, certainly on the server but possibly on the client as well.
redimix
Posts: 4
Joined: Sat Mar 05, 2016 8:51 am

Post by redimix »

You were right on,,, AVG was blocking the connection.
Post Reply