Bug in Remote Desktop Client for Android v10.0.19.1279 when run rdp file

Anonymous
2024-06-18T13:37:50+00:00

When I run RDP file from the device it causes an error "We can't connect ...", but the previous version works well

Also, this happens when I try to call the app with Intent "rdp://full address=s:127.0.0.1:3389&username=s:user"

RDP file structure be like -

full address:s:127.0.0.1:3389

alternate full address:s:127.0.0.1:3389

username:s:user

***moved from Windows / Windows 11 / Apps / Windows apps***

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

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

8 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-19T16:46:01+00:00

    Hello,

    May I know if this problem occur suddenly after the Android Remote Desktop client is upgraded to a new version?

    Please recheck the configuration of the RDP file after the client is updated. In addition to the URI call application using the Remote Desktop Protocol you mentioned, please try to log in directly in the Android Microsoft Remote Desktop using the full remote PC name or IP, as well as the full Windows username and password.

    In addition, please make sure that your device and remote PC are connected to the network normally and the network connection is stable. You can use the ping command on the Remote Desktop (RD) PC to test the network connection to the mobile phone.

    References:

    Get started with the Android client | Microsoft Learn

    Remote Desktop URI scheme | Microsoft Learn

    I hope this helps.

    Best regards

    0 comments No comments
  2. Anonymous
    2024-06-20T10:04:24+00:00

    As written above, after the update, I lost the ability to connect to a remote machine. The ability to connect is only when I connect directly from the client. In the case of connection via "URI scheme" or via a file - an error appears. This is not due to an incorrect file configuration, poor connection or configuration of the local and remote machines.

    Clear Steps to Reproduce -

    1. v10.0.19.1279 is installed on an Android phone or simulator
    2. any valid rdp file is created
    3. open the rdp file using the Android client
    4. you get an error

    P.S. all versions below worked fine

    0 comments No comments
  3. Anonymous
    2024-06-20T20:33:25+00:00

    Hello, is the account you used to log in to the remote desktop on Android the same as the account you used to log in to the PC client? Please make sure that the account you logged in to on the mobile phone has been added to the Remote Desktop User group on the destination computer. Then log back into the Android Microsoft Remote desktop with your full Windows username and password.

    0 comments No comments
  4. Anonymous
    2024-06-20T21:20:41+00:00

    Can you reproduce the issue that I described?

    Please read carefully what I described and try to reproduce this error. All possible configurations for remote access are configured correctly.

    Сreate rdp file and open (ip address you should use one to which you have access. This address is only available to me).

    P.S. On Play Store latest available version is 10.0.19.1280 this version also doesn't work

    RDP file structure

    A version of RDP client that works

    RDP file that is stored on phone

    Result after pressing on file

    A version of RDP client that does not work

    Result after pressing on file

    Also I can open this file on the Mac

    0 comments No comments
  5. Anonymous
    2024-06-21T06:13:42+00:00

    Hello,

    I have the same issue, my RDP file perfectly works on my Windows 11, but when I open it in the new version of Microsoft Remote Desktop on my Android it display the same error.

    The problem come from the new update not from a bad configuration at our side.

    1 person found this answer helpful.
    0 comments No comments