The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
casascoco
7 years agoActive Contributor
Your session may have timed out or the host may have gone offline
The error occurs after opening the dashboard of the remote host using the logmein client software, then trying a remote connection from the dashboard. The remote host says it is in session however w...
AshC
7 years agoRetired GoTo Contributor
casascoco DaveSC Debug logs could certainly lead to a fruitful ticket here. Did you guys send those into support by chance?
DaveSC
7 years agoActive Contributor
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.
- DaveSC7 years agoActive Contributor
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
- AshC7 years agoRetired GoTo Contributor
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:
- stop service
- in Device Manager delete all Hamachi-related interfaces (hidden devices too if any)
- run in admin cmd: hamachi-2.exe --add-tap Hamachi
- insert a new line in h2-engine.cfg file: Vpn.Reinstall 1
- restart the service