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
Solved
Command prompt closes immediately on connecting
I have various client machines which for no obvious reason refuse to let me open working command prompts, when I do so all that happens is a black window opens with a 110x41 sign in the middle that then clears to show nothing more than "Connection closed." at the top left.
Nothing seems to resolve this, I have removed and reloaded the software at both ends of the connection with no change to the problem.
It is really inconvenient to have to remotely take control of a machine rather than be able to run a background cleanup script or to stop/start services without disrupting a client.
Anyone have any bright ideas or know of any reason that this might be happening?
Pressing F5 to refresh screen (Connection closed.) fixed for me.
50 Replies
Dear all,
just to confirm that Logmein Client version 1.3.5380, released by Logmein today, apparently has solved the copy/paste issue.
Also, the overall stability of the remote Powershell appears to be much improved, without random disconnections and visual artifacts.
Thank you all and Regards
GG
- All nice and easy except that doing so on some Windows servers will then lock the machine out of everything except local keyboard access. Might be fine on workstations but be careful as this is also exposes the machine to all manner of network nasties.
It works for a little bit, then the next version breaks it, then they fix it again.
We did set a GPO to disable the firewall (still set to Domain), since our AV has its own anyways, and we haven't had problems with this latest version. We had it disabled for over a year though and it didn't help with the last version, so it's hit or miss.
Might need to log out and back into logmein for cmd prompt to work after disabling Windows Firewall.
Steps done:
Remoted into computer.
Disabled Window Firewall for Domain, Private, Public.
Set computer network to private.
Logged out of LMI and back in.
Opened cmd prompt.
I got it working by remoting into the host and disabling Windows firewall. Then refreshing LMI window and opening a new cmd prompt.
Hi Glenn, thank you for updating.
> The workaround we are currently recommending is to connect using our client application
Actually the problem IS the client application.
Thank you again and Regards
GG
Hi @LockonCC,
Sorry for the frustration. My understanding is we are in the process of deploying a fix, but it will take time to be available for all. The workaround we are currently recommending is to connect using our client application https://support.logmeininc.com/pro/help/how-to-connect-using-the-logmein-client-desktop-app-logmein-c-lmi-connecttohost-client
Any fix for this?
This seriously hampers my work because then instead of being able to perform tasks I have to contact the user to get a remote session.
PLEASE post a fix or workaround asap!
Thank you.
I would like to report that F5 is no longer working to remedy this issue.
Agree that this issue is adding significant time to my day when trying to resolve issues.
Having to re-type scripts into or out of the cmd window is wasting valuable time and means that more often than not taking over the users session is required to efficiently resolve issues (but obviously now interrupting the end user and wasting their time)
Please get this resolved soon!
