cancel
Showing results for 
Search instead for 
Did you mean: 
New Contributor

[SOLVED] Connection to the host computer has been lost. Do you want to reconnect?

We have been using LogMeIn Central for a number of years without many issues but recently we've had reports of several of our machines being "unconnectable".  What happens is that the client attempts to connect and prompts the user for acceptance but as soon as the user accepts the agent gets a message saying "Connection to the host computer has been lost. Do you want to reconnect?" and the user get's booted to the CTRL+ALT+DEL screen.  It seems to be fairly random, what machines this happens on and the machines that are affected are in a minority but they do all seem to be running on an HP Elitebook 830 G6 running Windows 10 1903.

 

I've been searching through the forums but I haven't seen anything that machines this particularly.  The below are the lines generate din the log file from when the connect attempt is initiated to when it fails.  An image version of this as well as the error message are attached.

 

Hopefully someone can help.

 

Cheers,

 

-- Gord

 

LOG RECORDS

2020-10-14 14:48:26.222 - Warning - LogMeIn - WGRANT\privstewago - 05280 - 0x00003564 - template - Cannot access settings from template: WebSvc.DLFF
2020-10-14 14:48:26.222 - Info - LogMeIn - WGRANT\privstewago - 05280 - 0x00003564 - Session - 88.98.244.99/88.98.244.99.bcube.co.uk:WGRANT\PrivStewaGo - Request for /?hostpath=/default.html returned redirect to main.html
2020-10-14 14:48:26.499 - Warning - LogMeIn - WGRANT\privstewago - 05280 - 0x00003564 - template - Cannot access settings from template: WebSvc.DLFF
2020-10-14 14:48:27.904 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05280 - 0x00003564 - Session - 88.98.244.99/88.98.244.99.bcube.co.uk:WGRANT\PrivStewaGo - Request for /main.html returned 200 OK (1455 bytes).
2020-10-14 14:48:28.183 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05280 - 0x00003564 - Session - 88.98.244.99/88.98.244.99.bcube.co.uk:WGRANT\PrivStewaGo - Request for /remctrl.xml?view=0 returned 200 OK (8611 bytes).
2020-10-14 14:48:31.304 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05280 - 0x00002C20 - Session - 88.98.244.99/88.98.244.99.bcube.co.uk:WGRANT\PrivStewaGo - Unsupported client options: REACTIVESUPPORT
2020-10-14 14:48:33.992 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 07896 - 0x00002F98 - Logger - The NixSyslogWriter disabled
2020-10-14 14:48:33.992 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 07896 - 0x00002F98 - Logger - Can't initialize NixSyslogWriter
2020-10-14 14:48:33.992 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 07896 - 0x00002F98 - Logger - ------------------- Start ------------------
2020-10-14 14:48:33.992 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 07896 - 0x00002F98 - Logger - Log level: 6. Logger using settings: 'Log'.
2020-10-14 14:48:34.154 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 07896 - 0x00002F98 - Logger - ------------------- Stop -------------------
2020-10-14 14:48:34.204 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - The NixSyslogWriter disabled
2020-10-14 14:48:34.205 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - Can't initialize NixSyslogWriter
2020-10-14 14:48:34.205 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - ------------------- Start ------------------
2020-10-14 14:48:34.205 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - Log level: 6. Logger using settings: 'Log'.
2020-10-14 14:48:34.488 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - RARC ------------------- Start ------------------
2020-10-14 14:48:34.488 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - Log level: 6. Logger using settings: 'Log'.
2020-10-14 14:48:34.496 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Startup - Starting up
2020-10-14 14:48:34.498 - Info - LogMeIn - LMIKeyboard - CLMIKbHost - Created new keyboard host instance. LMIKeyboard library version: 2.0.0.119. build date: 2020-10-14 14:48:34.498
2020-10-14 14:48:34.509 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Startup - Waiting for authorization by the interactive user.
2020-10-14 14:48:36.226 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Startup - The interactive user authorized the remote control process.
2020-10-14 14:48:36.286 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Startup - Failed to load rahook.dll. Error: 126
2020-10-14 14:48:36.287 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Main - Locked the console.
2020-10-14 14:48:36.289 - Warning - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - rahooksupport - rahook.dll was not loaded to unload
2020-10-14 14:48:36.291 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Main - Set return code 0x19731002
2020-10-14 14:48:36.299 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 05936 - 0x000023D8 - Logger - RARC ------------------- Stop -------------------

 

LogMeIn01.pngLogMeIn02.png

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
New Contributor

Re: Connection to the host computer has been lost. Do you want to reconnect?

I was able to resolve this by updating the Windows host client on the affected machines.  Our version was a little out of date (4.1.11066) and I installed the latest version from the website (4.1.13774) and this has resolved all of the known instances of this.

View solution in original post

2 REPLIES 2
Highlighted
LogMeIn Contributor

Re: Connection to the host computer has been lost. Do you want to reconnect?

Hello,

We have some troubleshooting steps that you may want to try here first:  https://support.logmeininc.com/pro/help/cant-connect-try-this-first-logmein-c-common-troubleshooting...

 

Unfortunately the viewer logs will only show disconnect times, so you may have to correlate the time there with Windows event logs on the Host side.

Highlighted
New Contributor

Re: Connection to the host computer has been lost. Do you want to reconnect?

I was able to resolve this by updating the Windows host client on the affected machines.  Our version was a little out of date (4.1.11066) and I installed the latest version from the website (4.1.13774) and this has resolved all of the known instances of this.

View solution in original post