Getting this error when connecting to a client.
So far only one member of my team can connect to this client but everyone else gets this error.
Solved! Go to Solution.
Here is the solution for computers showing this error due to an expired certificate:
As admin, open the command prompt of my computer in LogMeIn Client
1. cd "C:\Program Files (x86)\LogMeIn\x64"
2. cmd
3. logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%"
4. net stop LogMeIn && net start LogMeIn
(Thank you @Michal_orc )
Depending on where the computer is located, you may run into an error "Country too long".
The problem is that Windows returns a 3-digit "sub-region-code" instead of the 2-character "alpha-2" country code. Check for example: https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes/blob/master/all/all.csv
To overcome on this problem you have to explicitly specify the 2-digit code of your country. So find the "alpha-2" code of your country in the table above and issue the following command in an administrator command prompt:
"C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "<alpha-2 code of your coutry>" -createsc
For example if you are in Mexico, then issue the following command:
"C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "MX" -createsc
On Mac the certificates are stored in files:
- /Library/Application Support/LogMeIn/CA.pem
- /Library/Application Support/LogMeIn/server_ex.pem
First these files have to be deleted:
- sudo rm /Library/Application Support/LogMeIn/CA.pem
- sudo rm /Library/Application Support/LogMeIn/server_ex.pem
Then restart the daemon:
- sudo launchctl stop com.logmein.logmeinserver
@Danny6 Welcome to the GoTo Community
What OS system is the team running? For the member who can't connect have they checked which version of TLS is enabled on the machine?
Hi @Danny6 Have you tried a full uninstallation of LMI including the registry keys?
If not can you Uninstall the affected computer, reboot the computer, install again, and test the connection?
I have the same problems. I reinstall LMI; the issue still exists
but
I can login from LogMeIn Client to MainMenu.
I can't start Remote Control
I also noticed that the problem occurs more often on Windows 11
Unfortunately I don't have a solution yet
I send a message to HelpDesk, but I was unable to call
Hi @Michal_orc, welcome to the community.
Are you seeing the exact same error message? Do you have the latest version of Host software 4.1.0.15428 installed?
Yes, I have 4.1.0.1542. On Saturday I connected to the sample computer.
I have a problem with about 15 computers out of 300 that I manage in in various networks and locations. Almost all of them are on Windows 11. This is not a firewall or routers problem, I connect to other computers on this network.
My error is very simmilar 0A000410:lib(20);;reason(1040)
Okay, I can you enable logging in the LMI software settings so we can get some more clues? Typically these kinds of connection errors do end up being firewall related, our IPs change so we recommend allow listing our domains instead.
Yes, I turned on logging.
I copied the logmein.log content from the last two minutes to my computer via PowerShell. During this time I tried to run remote control
By the way, I noticed that File Transfer and remote control also do not work
How should I send the content of the logmein.log file?
Hi
After the update numbered 4.1.0.15428 (Mar 14, 2024) was installed on our host computers, we are unable to establish remote connections.
We kindly request your urgent support regarding this matter.