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
hiran
5 years agoActive Contributor
Remote CMD - Connection Closed error
Hi Guys, When I try to open the remote CMD, I'm getting this "Connection closed" message. This happens only with some of the computers. Others are ok. But I can access these computers' CMD v...
- 5 years ago
I have been having the same issue hiran this post might help also test to see if you are able to use CMD from the web portal vs. the LMI client.
Solved: Re: Command prompt closes immediately on connectin... - LogMeIn Community
CC-MSP
4 years agoVisitor
Has this been fixed? All of my computers that have updated their client (4.1.0.14512) close connection. F5 won't clear it. I've got several hundred clients I need to deploy software via cmd. HELP!
AshC
4 years agoRetired GoTo Contributor
CC-MSP I believe the release date for the final fix is sometime in the next 20 days. As soon as I have an update I'll share it with the Community here.
- Marlana4 years agoNew Contributor
Any update on this issue? We have many computers we cannot access under our account due to this connection closed error. It will let us sign in with our password but the actual remote disconnects us automatically.
- AshC4 years agoRetired GoTo Contributor
Marlana If this is strictly connection related, and not pertaining to CMD prompts while in session, do you have any local firewalls active at the host end that may be shutting down LogMeIn during initialization?
- Marlana4 years agoNew Contributor
I have found a correlation between the accounts shutting down the remote controller. They all have 4107 error "Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file."
Date and time are right.