Remote desktop disconnected 1-2 secs after connection

Anonymous
2015-08-20T12:45:56+00:00

I've upgraded two machines to windows 10 (clean installation), and when I try to connect via remote desktop from other to another, the remote desktop is immediately disconnected after the login ( I see the remote screen for 1-2 seconds), with the message that the connection is interrupted because another use has logon (which is not true).

This happens only if in the remote computer the user already did the login locally (i.e. at startup).

If I disconnect the user of the remote computer, and try again, the remote connection works.

It seems that windows detect the remote connection as a concurrent login, even if the user used it's exactly the same (and the only one on the pc) which did the local login.

Also, I can see that in the remote desktop screen for a moment that it's loggin "Another User" instead of the user name I used in the credentials.

Probably that's a bug, but I could not find a way to workaround it (except disconnecting the user locally before doing the remote desktop connection).

Qb

Windows Server Remote and virtual desktops Session connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2015-08-20T17:51:20+00:00

    Hi,

    Thank you for being part of the Windows 10 family.

    Sorry to know that you are facing issues with the Windows 10.

    In order to help you better, please provide the information:

    1. Is your Windows 10 activated?
    2. Which network connections you are using for remote connection establishment? Is it a wired network or wireless network connection? 

    Refer to the below methods and check if it helps. 

    Method 1: I suggest you to perform the Internet Connections troubleshooter.

    1. Tap on Windows Key and click on search bar.
    2. Type “Troubleshooting” without the quotes and click on Troubleshooting.
    3. Then click on View All on the left panel of the screen.
    4. Click on Internet Connections.
    5. Click on Next and follow the prompts to run the troubleshooter.

    If the issue still persist, refer to the below method.

    **** 

    Method 2: I suggest you to perform the Network Adapter troubleshooter.

    1. Tap on Windows Key and click on search bar.
    2. Type “Troubleshooting” without the quotes and click on Troubleshooting.
    3. Then click on View All on the left panel of the screen.
    4. Click on Network Adapter.
    5. Click on Next and follow the prompts to run the troubleshooter.

    Reply to us with the information, so that we can assist you better.

    Get back to us if you need any further assistance on Windows related issues and we will be glad to help.

    0 comments No comments
  2. Anonymous
    2015-08-28T09:45:01+00:00

    Hi,

    I don't think it's related with network issues, but I still run the diagnostic tools and the issue is still there.

    Both PCs are activated and use a LAN connection.

    I have other details:

    • The issue manifests only if the user is logon automatically at startup. If I disconnect ("logout") the user on the remote PC physically, the remote desktop login start to work. Also, if I then disconnect from remote desktop and connect again, it still works.

    Seems to be related to the startup auto-login.

    • When I connect remotely it shows "Other User" in the big username string (?)
    • The remote user password is empty , so I enabled the "Login with empty password" in the local security policies.

    I also applyed all the updates as today but no luck.

    Qb

    0 comments No comments
  3. Anonymous
    2015-09-18T15:02:48+00:00

    - The remote user password is empty , so I enabled the "Login with empty password" in the local security policies

    There seems to be a problem with Windows 10, blank login passwords and remote desktop connection. I used to also edit the policies to allow blank password logins which are not from local console. 

    If you revert back to 'limit blank password logons to local console only' and give the remote computer a password ... everything will work fine and remote desktop does not disconnect.

    I know maybe you did not want to give your remote computer a password but this is the only way remote desktop will work without disconnecting

    I hope this helps!

    2 people found this answer helpful.
    0 comments No comments