ContributionsMost RecentMost LikesSolutionsRe: Your session may have timed out or the host may have gone offlineSadly, the only fix I've found is a reboot of the remote host.Re: Your session may have timed out or the host may have gone offline DaveSCThank you for the update! Please follow up once you hear something from support. Re: Your session may have timed out or the host may have gone offlineI offered to, but they were insisting on remoting in instead of looking at logs.Re: Your session may have timed out or the host may have gone offline HeyDaveSC, 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. AshCI 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. Re: Your session may have timed out or the host may have gone offline AshC Only after the initial connection attempt Re: Your session may have timed out or the host may have gone offline AshCthe age of the PC's vary from brand new to 5+ years old. The issue is not more frequent at any one location. Isolating the times is difficult because it is only discovered when remoting in, which can be as long as 6 months between remote sessions. If you direct me to the relevant log file directory I'll get the most recent occurance uploaded for engineering to review. Re: Your session may have timed out or the host may have gone offline Thanks for the responseAshC The connection types have been wireless or wired, on both Verizon fios and Comcast. PC hardware is all different. OS has been Windows 7 32 & 64 bit, Windows 8.1 64 Bit, and Windows 10 32 & 64 bit. Avaibility time online can range from Months to minutes. LMI support said to restart the PC locally and/or reinstall LMI, and from my experience a restart typically fixes the problem, until the next time. Some of these clients are out of state so a restart is not a simple solution, and due to the new sign in requirements for a logmein install, getting the client to install does not work. 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 when trying to remote I receive the error "Your session may have timed out or the host may have gone offline. Please try again." and offers Reconnect or Close options. The reconnect button causes the same error. It appears to be a problem when first accessing the dashboard. After speaking with phone support they recommend restarting the remote machine, which can't be done until the client is back on site, defeating the purpose of having remote access. I have had this same issue with multiple remote hosts, running different operating systems. Any other solutions? Besides switching remote software providers. SolvedRe: Session Hung? Icon Green? Can't connect... Extremely inconvenient. The same problem happens to me on random computers, requiring my clients to reset their computer before it will allow a reconnect. I've actually had to have clients install different remote software (Veam Tiewer) just so I am able do the work remotely. This is unnacceptable for a paid product.