Hi Kate,
Thank you, yes I did see that thread, and led me to verify the Internet Options for TLS and SSL (they were already previously enabled/disabled respectively).
I also found the following thread https://community.logmein.com/t5/Pro-Discussions/LogmeIn-Client-shows-offline-Cannot-connect-to-it/td-p/308877, which shows the same error in the UI, however the solution, if there was one, was not shared.
There was also this thread: https://community.logmein.com/t5/Pro-Discussions/LMI-Control-Panel-can-t-connect-to-network/m-p/309411, which also shows the same issue, along with a Win 7 machine.
In response to your question, the other systems are not Windows 7, the issue seems to only be affecting Windows 7.
It's interesting to note that the issues above, including the one you posted, are all within the last two months.
Thank you for your attention to this.
*edit, just after posting this, I noticed another new thread by user philbud with apparently all of a sudden new connection issues... also Win 7 machine.
Hi mcon thanks for the further information. There have been a few reports recently with Windows 7, I agree.
The Community experiences have been reported to the team. The current recommendation is to make sure you are fully updated especially on security-related patches for windows, this one in particular.
Hi KateG ,
I thought I would give an update as I'm seeing new behavior.
Previously I was unable to use any kind of control other than the limited functionality via the web browser. Clicking on remote control on the website would download a temporary client but would encounter the same offline error. This was retried just now and the downloaded termporary client now connects without any errors.
Thinking the issue was resolved, the installed app client on the problem system was retried, and resulted in the same offlilne 12031 error. Reinstalling the client had the same result. However, after reinstallation, launching the client from the website as indicated in the previous paragraph, no longer downloads a temporary client and asks if it's possible to use the LMIIgnition.exe in the installation folder on the problem computer (this was allowed), and it connects without issue.
To restate the problem as it currently stands. The installed client still shows an error if used on its own. However it is now possible to launch the installed client from the website. Ie, the standalone client requires a weblogin prior to functioning.
I have a 10 and have had this problem for over 2 weeks. Rescue can't even stay connected and offers no solutions. No it is not my firewall. Uninstalled and problem persisted.
venusparts welcome to the GoTo Community.
Can you let me know a bit more about your experience? Are you seeing the same error message? Are you able to connect via the website but not the client?
