Pressing F5 to refresh screen (Connection closed.) fixed for me.
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.
Clearly this is NOT a solution as it involves disturbing end users when as their IT administrator I need to run scripts or kill processes off in the background.
Stop proposing idiot answers and get it fixed, you have had plenty of time and are charging premium rates for a subscription product that simply does not work as advertised.
That's not a solution. Of course we can disturb the user and make them not able to work while we work on a problem. If we don't want to disturb the user and run in the background, we need the PowerShell remote to work.
Hello all,
Logmein Client updated today to version 1.3.5311
Copy/Paste problem in Powershell NOT solved:
- Logmein to remote host
- open remote Powershell
- type a command, works as expected
- select string and Copy (either CTRL-C or contextual menu)
- CTRL-V does not paste, context menu "Paste" does not paste
Remote host Logmein service upgraded from 14512 to newer 15582: Copy/Paste still does NOT work.
Please let us know when this issue will be resolved.
Regards
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
Hi Team,
It looks like someone has made this worse. Now I get two 'connection closed' messages and the f5 refresh no longer works......
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.
Thanks for your patience. We are actively investigating the cause of this problem. I hope to have more information soon.
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.
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!!!
Hi, all.
We re actively investigating this behavior and should have some answers soon.
F5 works for me as well
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!
