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 t...
Pressing F5 to refresh screen (Connection closed.) fixed for me.
UPDATE: Troubleshooting this morning I discovered that I am able to remotely connect to some machines and not others. I can connect to some but not others on the same subnet, some but not others on different subnets behind different physical firewalls. I can reboot a machine that I cannot connect to, try again and still cannot connect. Still troubleshooting...will post updates.
I am having the exact same issue. From what I have determined, I can connect to any client that uses the Command Prompt (there are few). All others usually connect to a remote PowerShell instead, those are all failing.
Oddly enough, if I open the computer's dashboard from the web portal, I can connect to the remote shell without issue (Computer Management->Command Prompt). It's only doing so from the "LogMeIn Client" app that fails.
I can also confirm that this is happening from the Logmein Client and can only access sites that get cmd prompt instead of powershell.
Access via the web dashboard does work as KB-BC mentioned but is so much slower to access than the direct option in the Logmein Client.Same is happening to me. I really need a fix. We set a group policy setting to use cmd by default rather than ps, but it made no difference. This is a vital part of my workflow that needs to be addressed!
