Jump to content
kamiran.asia

Agent Conection Problem : GetAuthenticationSessionToken

Recommended Posts

Hi dears ESET Admins.

In one of our ESET Business Project we have a connection problem just with one Server , Agent Log is attached.

The Error is :

ERROR: InitializeConnection: Initiating replication connection to 'host: "192.168.10.5" port: 2222' failed with: GetAuthenticationSessionToken: Failed to fetch device session token in time

 

 

trace.zip

Untitled.jpg

Share this post


Link to post
Share on other sites

Hello,

Try to change connection time to server in agent policy from 1 to 10 minutes.

Also reboot server with ERA.

Thank you.

Edited by zloyDi

Share this post


Link to post
Share on other sites
2 minutes ago, zloyDi said:

Hello,

Try to change connection time to server in agent policy from 1 to 10 minutes.

Also reboot server with ERA.

Thank you.

It does not help. There is just one Server in network that has this problem all other 100 PCs work find.

Share this post


Link to post
Share on other sites
8 minutes ago, Marcos said:

Does the issue persist after reinstalling agent on the client?

Yes,The problem is same even by reinstalling agent.

Edited by kamiran.asia

Share this post


Link to post
Share on other sites

Please enable full tracing of AGENT (traceAll mechanisms has to e used in case it is not connecting) and capture few minutes after it's startup. It seems that there is problem with fetching so called HW fingerprint, that is required to identify device in ESMC. It is either too slow, or failing at all. I would recommend to collect also system logs using ESET Log Collector for further analysis. I would also recommend to contact ESET support with collected data, as it might require more complex analysis.

Share this post


Link to post
Share on other sites

My solution (Windows 10 / Dell Latitude 5490) :
- agent fails after generating hw fingerprint, checked status.html and trace.log (how to check trace log: https://support.eset.com/kb3630/?locale=en_US&viewlocale=en_US)
- there was a missing driver (Detection Notification - Realtek Audio), after installing it everything worked fine. Agent cannot identify a device without a proper driver.

Share this post


Link to post
Share on other sites

I enable trace log as described here:  https://support.eset.com/kb3630/?locale=en_US&viewlocale=en_US)

Found this error: " 2019-10-25 14:37:21 Information: AuthenticationModule [Thread 228c]: DeviceEnrollmentCommand: processing of EnrollmentResult - result type=[FAILURE] with error type=[4], error description=[Device creation suspended: administrator's confirmation about detected clonning required.]"

On ERA Console - Status Overview -Questions. Allow replicated hardware as describe here: https://help.eset.com/esmc_admin/70/en-US/vdi.html

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...