Can not connect with client app

Hola BENPRESENT,

puedes darme mas detalles? ¿Se ha conectado correctamente a esta computadora en el pasado?

Hola a  que se debe el siguiente error .

LogMeIn Cliente de Control Remoto
Copyright (C) 2003-2024 LogMeIn, Inc. Patented and patents pending.
Host envía versión 15370.
Versión cliente 5553.

Conectando...
console-amyfpwgbev.lmi-app12-13.logmein.com (216.219.115.42), port: 443
Conectado.

error:0A000410:lib(20)::reason(1040)

Thanks for the solution.

Thank you for your support.

I think the handshake from the host computer log to the client is failing.

I'm curious about the third line, (10054).

---<excerpt from>---

2022-06-25 07:43:21.961 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00000F8C - SessionDataReport - An existing SessionDataReport found for session: 452896118. Type:3 Socket:00000000081860D0
2022-06-25 07:43:21.961 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00000F8C - Socket - <client-ip>:60306/http - HandleSocket request finished(4): GET
2022-06-25 07:43:23.044 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00000F8C - Socket - <client-ip>:60306/http - Error (in recv): ??????????????[?g ?z?X?g??????I???f??????????B (10054)
2022-06-25 07:43:23.045 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00000F8C - Socket - <client-ip>:60306/http - Closed (rcvd 4946 bytes, sent 386233 bytes).
2022-06-25 07:43:23.045 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00000F8C - Socket - <client-ip>:60306/http - Disconnecting (served 4 http requests, 4946 bytes in, 386233 bytes out).
2022-06-25 07:43:23.645 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x0000184C - WebSvc - Opening raw ssl socket to web service gateway (id 1754823).
2022-06-25 07:43:23.646 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Main - Socket processing thread started.
2022-06-25 07:43:23.646 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - Setup socket for connecting to control.lmi-app22-02.logmein.com on port 443...
2022-06-25 07:43:23.646 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - Resolving address for control.lmi-app22-02.logmein.com...
2022-06-25 07:43:23.647 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - Connecting to control.lmi-app22-02.logmein.com on port 443...
2022-06-25 07:43:23.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - Connected (SSL: yes).
2022-06-25 07:43:23.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - SSL handshake started.
2022-06-25 07:43:23.947 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - Certificate chain verified, trust status: 0/100.
2022-06-25 07:43:23.947 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - 2: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3; S#=04:00:00:00:00:01:21:58:53:08:A2; trust 0/10c.
2022-06-25 07:43:23.948 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - 1: CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE; S#=01:EE:5F:22:1D:FC:62:3B:D4:33:3A:85:57; trust 0/102.
2022-06-25 07:43:23.948 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - 0: CN=*.lmi-app22-02.logmein.com, O="LOGMEIN, INC.", L=Boston, S=Massachusetts, C=US; S#=34:6F:CD:46:CB:FF:3A:12:0D:47:B5:67; trust 0/102.
2022-06-25 07:43:23.949 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - SSL handshake done.
2022-06-25 07:43:23.950 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - SSL cipher TLS_AES_256_GCM_SHA384 (256 bits) TLSv1.3 selected.
2022-06-25 07:43:23.950 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - SSL session: NEGOTIATED, timeout is 600 seconds
2022-06-25 07:43:23.950 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - 158.120.20.111:443 - Assigned remote address: <client-ip>:60307
2022-06-25 07:43:24.097 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - SSL shut down - socket stays connected
2022-06-25 07:43:24.098 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - SSL handshake started.
2022-06-25 07:43:24.098 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - SSL error: handshake failure (in write).
2022-06-25 07:43:24.099 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - SSL error: error (in accept).
2022-06-25 07:43:24.099 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - Error (in SSL_do_handshake): error:1417A0C1:lib(20):func(378):reason(193)
2022-06-25 07:43:24.099 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 03440 - 0x00002090 - Socket - <client-ip>:60307/rawssl - Closed (rcvd 4122 bytes, sent 771 bytes).

---<excerpt to>---

How should we respond to this?

Thank you,

Hi Arai , 

Connectivity issues can be related to:

• Network being choppy - Please run a trace route to secure.logmein.com on the host machine's Command Line and a continuous ping also.
• ISP (internet service provider) may be down - Please check with your local provider
• AV/ Firewall - Verify on your host machine if the connection is being blocked by a firewall or Antivirus.

Also, on the host computer, if you have set Debug Logs for Central, it will tell you why the connectivity was lost. These logs are under C:\ProgramData\LogMeIn on the host machine.

Please let us know of your findings?

Thank you!