Your session may have timed out or the host may have gone offline

Hi AchC,

Sorry, the number of PoSReady 09 machines are minimal. The issue we are experiencing are on PoSReady 7 machines and Windows 10 machines. My mistake, this was a typo, albeit, we do have LogMeIn running on the PoSReady 2009 machines.

My issue is currently being dealt with by LogMeIn support. Numerous logs have been provided together with screen shots. So hoping to get an answer soon.

Thanks

Dave

DaveSC  I am sorry we don't directly support machines running PoSReady 09 ourselves, but you may be able to complete the task in this manner:

1. stop service
2. in Device Manager delete all Hamachi-related interfaces (hidden devices too if any)
3. run in admin cmd:  hamachi-2.exe --add-tap Hamachi
4. insert a new line in h2-engine.cfg file:  Vpn.Reinstall 1
5. restart the service

100's of our machines are running PoS tills and therefore running PoSReady 2009. I saw a posting on this community that had this same issue on XP and PoSReady2009 machines and the problem was the root certificate for XP had expired. Bear in mind PoSReady2009 is still supported by Microsoft. 

The link for this discussion is, "https://community.logmein.com/t5/LogMeIn-Central-Discussions/LogMeIn-Central-machines-dropping-offline-Can-t-reach-support/td-p/111459". The link within is no longer available.

Based on this, can anyone suggest if this is the issue and how the PoSReady2009 Root certificate could be updated?

I have litterally 100's of machines out there with this problem running PoSReady 2009.

Any help/advise very much appreciated.

@casascoco My issue is that once I cannot remote into the host, I cannot get the log files. Unfortunately, by default, the logging is disabled, therefore the struggle of creating a new host preference and associating it to the hosts and sending it down is a major challenge in that it does not sent it!

So my catch 22 is that I cannot get the logs enabled and if I have, then once it fails I cannot get the logs!

I have the logs from the client app, but apparently, those are of no use on their own.

casascoco If you have debug logs engaged, go ahead and send the logs to 'gotoservice@logmein.com', and confirm the login email spelling used for your support ticket.

Debug activation reference:  https://help.logmein.com/articles/en_US/Documentation/logmein-t-host-preferences-log/ 

casascoco DaveSC  Debug logs could certainly lead to a fruitful ticket here.  Did you guys send those into support by chance?

Hey DaveSC,

Sadly no. The issue still continues to pop up on a regular basis.  From what I've gathered it appears to be a problem with the LogMeIn Service, or one of its dependencies. This may be a shot in the dark but you could try setting up a recovery response for the LogMeIn Service.  My thought is for first and second failure restart the service at 1 and 2 minutes, and on subsequent failures restart the computer.  I have not tested this theory yet, but please let me know if you have success trying it out. I'll keep you updated if I have the time to try this fix.

AshC I have tried calling support when on site, and they ask for remote access to the host, which my clients do not authorize due to NDA's and privacy policies.  I would be happy to try to walk through the problem with support without them creating a remote session to my client's host.  However, phone support appears to be unwilling to help in this manner.

2nd April 2019

Hi,

Did you mange to get to the bottom of this problem? Support have been trying to resolve this issue for me for the past 4 months and I still have this issue on 100's of hosts.

I would really appreciate if you could let me know if the issue has been resolved and if so, how.

A desperate LogMeIn Central User