The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

hiran's avatar
hiran
Active Contributor
5 years ago
Solved

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...
AshC's avatar
AshC
Retired GoTo Contributor
4 years ago

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. 

Marlana's avatar
Marlana
New Contributor
4 years ago

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's avatar
    Marlana
    New Contributor
    4 years ago

    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. 

  • AshC's avatar
    AshC
    Retired GoTo Contributor
    4 years ago

    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?