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 via web version.
I recently deployed a script to install a certificate via the LogMeIn task. It got failed on these computers by giving an error "Access Denied". That's where I came to know about this. I don't know whether these are related.
I normally use the LogMeIn client and this is happening to me for few days. LogMeIn client is up to date and I even reinstalled it.
Any idea why is this happening?
Solved! Go to Solution.
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.
@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?
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.
@Partner07 The fix for this has been released, so please let us know if you continue to experience the same error, on what operating system, and which LogMeIn version.