Forum Discussion
paulquevedojdrf Thank you for creating a ticket. We should have a better understanding after the logs are reviewed.
If anyone else can help by doing the same, we can find a speedier resolution.
Pressing F5 to refresh screen (Connection closed.) fixed for me.
- Verricom4 years agoActive Contributor
Well what do you know, Jimz18 might have fixed it for me.
So far so good, any "connection closed" screen works when I hit F5 to refresh, not ideal if I am piping script into the remote prompt via an automation tool but at least it works for manual typed connections again... so far at least!
- paulquevedojdrf4 years agoActive Contributor
F5 works for me as well
- AshC4 years agoRetired GoTo Contributor
Hi, all.
We re actively investigating this behavior and should have some answers soon.
- AGJL4 years agoNew Contributor
Too bad LogMeIn isn't a mainframe system, then F5 would actually be a fix rather than a workaround. BTW, F5 gets me connected to the CLI as well. Good catch Jimz18!!!
- AGJL4 years agoNew Contributor
UPDATE: Can anyone at LMI give us an update for when this issue will be resolved? We're quickly approaching the end of month 3 since it was reported and it is still happening as of a minute ago.
- AshC4 years agoRetired GoTo Contributor
Thanks for your patience. We are actively investigating the cause of this problem. I hope to have more information soon.
- egrylls4 years agoNew Member
It might be because its opening POWERSHELL instead of a COMMAND PROMPT. Have your devs look at that. Seems someone changed something in the client or exe being called and now it's a different executable being brought to bear.
- jowsr4 years agoActive Contributor
Hi Team,
It looks like someone has made this worse. Now I get two 'connection closed' messages and the f5 refresh no longer works...... - G_G4 years agoActive Contributor
Hello all,
new Logmein Client version 1.3.5282, proposed as upgrade and installed today, actually fixes this Powershell issue.
Unfortunately it introduces another and worse bug: copy/paste in the Powershell does not work.
Please Logmein Support provide an official and secure download link for the previous Logmein Client (LogmeinIgnition.msi) version while this new bug is solved.
Thank you and Regards