Forum Discussion

Active Contributor

4 years ago

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...

Jimz18
4 years ago
Pressing F5 to refresh screen (Connection closed.) fixed for me.

New Contributor

4 years ago

I have this issue as well. Nothing changed recently except for Windows Updates. All OS are Windows 10 20H2 or 21H1, Security with Bitdefender Endpoint Security Tools (no configuration changes in it, as I administer it). I know it worked in July. Noticed it at least started happening last week. Turning Firewall on or off make no difference.

AGJL
New Contributor
4 years ago
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.
- KB-BC
  Visitor
  4 years ago
  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.
  - jowsr
    Active Contributor
    4 years ago
    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.