The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Danny6
2 years agoNew Contributor
Error when connecting. (Error occurred error: 14094410:lib(20):func(148):reason(1040))
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.
- 2 years ago
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
GlennD
2 years agoGoTo Manager
Michal_orc Danny6 I checked with Support and after reviewing another customer's log files it was suggested that reinstalling the LMI SSL Certificate may be the solution. Can you please try the following on one of your affected PCs?
- Launch command prompt (as administrator)
- Change directory to “C:\program files\logmein\x86” if it's a 32 bit OS or "C:\program files (x86)\logmein\x64" if its 64 bit.
- Issue the command :
logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%" - Turn off / on LogMeIn from the system tray icon.
If all goes well, the following should appear in the registry:
HKLM\Software\LogMeIn\v5\Net
Key (Dword) CertificateIDEx. Each value will have a bunch of gibberish
HKLM\Software\LogMeIn\v5\WebSvc
Key (Dword) HostCertIDSent and HostCertSent. Each value will have a bunch of gibberish - Try connecting again
vrajm
7 months agoActive Contributor
i don't see HostCertSent
I am running LMI on Win XP SP3
- GlennD7 months agoGoTo Manager
Hi vrajm, Windows XP is not supported