Error code 0x2104 on RDP

Ajith Kottadi 1 Reputation point
2021-06-04T00:50:09.653+00:00

Getting below error message (code 0x2104) while trying to RDP to Windows 2016 server. The same server can be accessible from other machine(s). I don’t find any difference between the working and non-working client machines.

=====
Remote Desktop Connection

Because of a protocol error detected at the client (code 0x2104), this session will be disconnected.

Please try connecting to the remote computer again.

Note: we are trying to access the Servers via BeyondInsight portal - same user can access from other machine(s) but few machines throwing 0x2104 error code.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,511 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Andy YOU 3,076 Reputation points
    2021-06-04T07:29:48.047+00:00

    HI AjithThomas-7047,

    1.Error code 0x2104 indicate below:
    0x2104 ERROR_DS_DRA_NO_REPLICA
    The naming context is in the process of being removed or is not replicated from the specified server.

    2.Could you please enter winver in command prompt on both normal win10 computer and issue win10 then check which difference between them about the os version and os version number ?[for example windows 10 enterprise 1809 (os build 17763.316)]

    3.Could you please enter below command on both normal win10 computer and issue win10 then check which difference between them about group policy?
    gpresult /h c:\normal.html
    gpresult /h c:\issue.html

    4.Could you please share the workflow about your RDP?

    5."same user can access from other machine(s) but few machines throwing 0x2104 error code"
    For example:
    PC1 belongs to user1
    PC2 belongs to user2
    user1 has 0x2104 rdp error
    user2 workfine.

    if we let user1 to logon pc2,will the same issue happen on pc2?

    0 comments No comments

  2. Ajith Kottadi 1 Reputation point
    2021-06-07T08:42:56.153+00:00
    1. The error screenshot below: 102972-rdp.jpg
    2. Both working and non-working machines are Windows 10 Enterprise v2004. Looks like it is irrespective of OS Build versions.
    3. Both working and non-working machines are part of same OU and same GPO settings are applied.
    4. Workflow as follows: User will login to BeyondInsight portal with their AD credentials, after successful login, they can see the servers published to their profile. Refer screenshot below. User to click on the button next to server name (highlighted in YELLOW color in the screenshot) to download the RDP file. Screenshot of the RDP file also attached here: 102965-biportal.jpg
      103021-rdp-file.jpg
    5. Yes, both PC1 and PC2 are of the same config. PC1 works for both User1 and User2 but PC2 throwing Error code 0x2104 for both User1 and User2. This is the scenario and I believe it is a machine level issue rather than UserProfile issue.

  3. Andy YOU 3,076 Reputation points
    2021-06-07T15:14:11.913+00:00

    HI AjithThomas-7047,

    1.Please do clean boot on issue pc then check if the same issue happen in clean boot mode?
    How to perform a clean boot in Windows
    https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
    2.Please run below command on both normal pc and issue pc then check which difference between them?
    Get-NetAdapterBinding

    3.Can you enter below command on both normal pc and issue pc then check which difference between them?
    get-hotfix

    4.Are both normal pc and issue pc using the same version broswer?
    Did you try to using other broswer on problematical pc then check if the same issue happen?

    5.Logon both normal pc and issue pc by using the same domain user account (like u1) then run network monitor as admin,
    meanwhile logon the sepcified server(like server1) by using domain admin account and run network monitor as admin.
    download rdp file from BeyondInsight portal and remote access the the same server(server1). Finally, stop capturing the network monitor log for both normal pc,issue pc, remote server1 then check if there is any difference between normal network monitor log and issue network monitor log.
    so there will be 4 logs:
    issue net logs are captured on issue pc and on server1
    normal net logs are captured on normal pc and on server1

    network monitor 3.4
    https://www.microsoft.com/en-us/download/details.aspx?id=4865

    ============================================
    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Andy YOU 3,076 Reputation points
    2021-06-22T02:03:17.607+00:00

    HI AjithThomas-7047,

    Do you find new key thread?

    ============================================
    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.