Component connection issues
If ESA components fail to connect to the ESA Authentication Server, adjust the connection parameters in the C:\Program Files\ESET Secure Authentication\EIP.Core.WindowsService.EXE.config file.
•EsaServiceIdleTimeout: Indicate how long to leave connections opened. Applies to Active Directory Integration mode.
Default value: Two minutes
•http.sys: Indicate how long to leave HTTP connections opened (Web Console, customer API). It applies to Standalone installation mode.
To display the existing timeout setting, execute the following command in PowerShell:
netsh http show timeout
To change the timeout, execute the following command in PowerShell:
netsh http add timeout timeouttype=idleconnectiontimeout value=<seconds>
Replace <seconds> with the desired timeout in seconds.
•EsaMaxSessions: Throttling—maximum concurrent sessions
Default value: 100 times processor count
•EsaMaxCalls: Throttling—maximum concurrent calls
Default value: 16 times processor count
•EsaMaxThreads: .NET thread pool—maximum count of threads in the pool; influences maximum count of simultaneously handled requests
Default value: 1000
•EsaMinThreads: .NET thread pool—create threads immediately up to this count; influences how quickly the thread pool reacts to the increasing count of incoming connections
Default value: Count of processor cores
|
Example of an altered EIP.Core.WindowsService.EXE.config file <?xml version="1.0" encoding="utf-8"?> <configuration> <appSettings> <add key="EsaServiceIdleTimeout" value="00:01:00" /> <add key="EsaMaxSessions" value="100" /> <add key="EsaMaxCalls" value="20" /> <add key="EsaMaxThreads" value="2000" /> <add key="EsaMinThreads" value="1000" /> </appSettings> </configuration> |
•EsaServiceIdleTimeout: hours:minutes:seconds format