Type Public
Category Configuration
Subject Getting Windows socket errors 10060 -- From iAgent to iServer
Rating 0% rating out of 0 vote(s).
Navigation Previous - Next - iTivity Remote Support Software - DoubleVision TTY Terminal Remote Control

Getting Windows socket errors 10060 -- From iAgent to iServer

Windows socket error 10060.
Which stands for :

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.j

Basically this means that any point in the connection from the iAgent over to the iServer there is a longer than normal delay. Remember that there are hops in between any 2 points in a socket connection. If you run the windows
TRACERT ( that is trace route ) program, you would be able to see which hop(s) is/are causing the problem.

Fortunately with the iAgent we can control HOW long a connection will time out before it is closed.

Below are the registry settings that I suggest you adjust their value to. Basically what we are doing here
is to DOUBLE how long the iAgent will wait before it closes a connection. ( To be exact, it is the underlying
networking sub-system of Windows that actually makes that descision. We only tell it HOW long we think we
should wait, within reason ).


On 32 bit Windows systems:

iTivity Unattended iAgent on Windows

[HKLM\Software\Tridia\iTivity\connector_rc]
"directVerifySessionFlag"=dword:00000001
"directVerifySessionTimeout"=dword:0000000F
"iasVerifySessionFlag"=dword:00000001
"iasVerifySessionTimeout"=dword:0000000F
"endToEndKeepAlive"=dword:00000001
"transportTimeout"=dword:00015F90



iTivity Attended iAgent on Windows

[HKLM\Software\Tridia\iTivity\connector_od]
"directVerifySessionFlag"=dword:00000001
"directVerifySessionTimeout"=dword:0000000F
"iasVerifySessionFlag"=dword:00000001
"iasVerifySessionTimeout"=dword:0000000F
"endToEndKeepAlive"=dword:00000001
"transportTimeout"=dword:00015F90

On 64 bit Windows systems:

iTivity Unattended iAgent on Windows

[HKLM\Software\Wow6432Node\Tridia\iTivity\connector_rc]
"directVerifySessionFlag"=dword:00000001
"directVerifySessionTimeout"=dword:0000000F
"iasVerifySessionFlag"=dword:00000001
"iasVerifySessionTimeout"=dword:0000000F
"endToEndKeepAlive"=dword:00000001
"transportTimeout"=dword:00015F90



iTivity Attended iAgent on Windows

[HKLM\Software\Wow6432\Tridia\iTivity\connector_od]
"directVerifySessionFlag"=dword:00000001
"directVerifySessionTimeout"=dword:0000000F
"iasVerifySessionFlag"=dword:00000001
"iasVerifySessionTimeout"=dword:0000000F
"endToEndKeepAlive"=dword:00000001
"transportTimeout"=dword:00015F90


Also make sure that there are NO user customized entries for the
UnAttended iAgent under the HKCU registry as shown below :

[HKCU\Software\Tridia\iTivity\connector_od]
"directVerifySessionFlag"=dword:00000001
"directVerifySessionTimeout"=dword:0000000F
"iasVerifySessionFlag"=dword:00000001
"iasVerifySessionTimeout"=dword:0000000F
"endToEndKeepAlive"=dword:00000001
"transportTimeout"=dword:00015F90


Did this answer your question? Be heard!
5 4 3 2 1   
Yes! Getting warm Keep looking Not Really No!