Chào mừng bạn đến blog Ynghialagi.com Trang Chủ

Table of Content

Trang chủ
Bài đăng

Remote Desktop Connection Broker Client failed to redirect the user error:NULL 2022

Mẹo Hướng dẫn Remote Desktop Connection Broker Client failed to redirect the user error:NULL 2022


Bạn đang tìm kiếm từ khóa Remote Desktop Connection Broker Client failed to redirect the user error:NULL được Update vào lúc : 2022-02-22 08:50:01 . Với phương châm chia sẻ Bí kíp về trong nội dung bài viết một cách Chi Tiết 2022. Nếu sau khi tìm hiểu thêm nội dung bài viết vẫn ko hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Admin lý giải và hướng dẫn lại nha.



Windows 2022 RDS sự kiện 1306 Connection Broker Client failed to redirect the user… Error: NULL



Archived Forums


Nội dung chính



  • Windows 2022 RDS sự kiện 1306 Connection Broker Client failed to redirect the user… Error: NULL




  • Answers


  • All replies

  • Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User : Error: Remote Desktop Connection Broker is not ready for RPC communication.


    • >


    Remote Desktop Services (Terminal Services)



    • Question





    • Question


      Sign in to vote


      1


      Sign in to vote


      I’m attempting to setup a Windows 2022 RDS Standard Deployment for Session Hosting. The layout is as follows:

      RDS01 – RDS Connection Broker and Web Access

      TS02 – RDS Session Host

      TS03 – RDS Session Host


      The domain these servers are part of has (1) Windows 2008 Server and (2) Windows 2022 Servers acting as DCs. The domain is running Windows 2003 Functional Level.


      All servers are on a single routed network with no firewall between them. All DNS A and PTR records for all servers exist and resolve on all hosts. All servers can be pinged by each other. In other words, there are no network connectivity issues.


      I’ve setup the RDS deployment several times w/ the same results.


      The Issue

      I can login via the RDWeb interface on RDS01 from a Win10 desktop and connect to the published RDP desktop without issue (i.e. no error messages to the user) and no errors in the logs. When I try to directly RDP to RDS01, I successfully authenticate as

      a user (per the sự kiện log) but get an error stating that the user doesn’t have access to the system. In the sự kiện log I get sự kiện id 1306 with the message of “Remote Desktop Connection Broker Client failed to redirect the user <domain><test

      user>. Error: NULL”.



      – <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/sự kiện”>

      – <System>

      <Provider Name=”Microsoft-Windows-TerminalServices-SessionBroker-Client” Guid=”2184B5C9-1C83-4304-9C58-A9E76F718993″ />

      <EventID>1306</EventID>

      <Version>0</Version>

      <Level>2</Level>

      <Task>104</Task>

      <Opcode>13</Opcode>

      <Keywords>0x2000000000000000</Keywords>

      <TimeCreated SystemTime=”2022-12-29T16:47:27.634726700Z” />

      <EventRecordID>47</EventRecordID>

      <Correlation ActivityID=”F4209120-29ED-44E4-845A-25A2570F0000″ />

      <Execution ProcessID=”828″ ThreadID=”3668″ />

      <Channel>Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational</Channel>

      <Computer>rds01.[redacted.domain]</Computer>

      <Security UserID=”S-1-5-20″ />

      </System>

      – <UserData>

      – <EventXML xmlns=”Event_NS”>

      <param1>[redacted.domain]</param1>

      <param2>[redacted.user]</param2>

      <param3>NULL</param3>

      </EventXML>

      </UserData>

      </Event>



      If I RDP to RDS01 as an administrator, I get the same error message but the RDP session opens and presents the desktop on RDS01.


      I can RDP directly to TS02 or TS03 and login as a user and open the RDP session. Redirection to some degree appears to be working in that I can disconnect a user session from TS02 and RDP to TS03 and the session is redirected back to TS02. The sự kiện

      logs on RDS01 record this happening as well.


      What I’ve tried already

      1. In searching this sự kiện 1306 issue, I found several posts with this exact same behavior in WS 2012/R2. Most “solutions” suggested point to the fact that the RDS Session Broker doesn’t have sufficient authority to look up the users AD group

      membership via the tokenGroupsGlobalAndUniversal attribute or AuthzInitializeContextFromSid API function which leverages the tokenGroupsGlobalAndUniversal attribute. (Example: https://social.technet.microsoft.com/Forums/windowsserver/en-US/29733a87-dbda-47bc-8b37-6eeac5ab5a0a/2012-rds-nonadministrators-can-not-access-vdi-pool?forum=winserverTS#97d883f1-7a64-4d02-9492-309638f92e79

      )


      The service is running as “Network Service” which does have network access via the Computer Object’s authority in AD. So following Microsoft’s instructions (https://tư vấn.microsoft.com/en-us/kb/331951), I’ve added RDS01 to both the Windows

      Authorization Access Group and Pre-Windows 2000 Compatibility Access groups and rebooted RDS01 with the same results.


      2. I’ve verified the Windows Authorization Access Group has rights to read the tokenGroupsGlobalAndUniversal property/attribute on my test users and the computer objects of the servers.


      3. I’ve setup an AD Service account following Microsoft’s instructions (https://tư vấn.microsoft.com/en-us/kb/842423) with a similarly described access issue. The service account user was added to the Windows Authorization Access Group. This was

      unsuccessfully as well w/ the same sự kiện 1306 error.


      4. I ran the following powershell commands to verify access of the Connection Broker to the OU (https://technet.microsoft.com/en-us/library/jj215512.aspx#)


      Test-RDOUAccess -Domain [redacted.domain] -OU “Computers” -ConnectionBroker rds01.[redacted.domain] -verbose



      This failed so I ran the following to grant access


      Grant-RDOUAccess -Domain watsons.local -OU “Computers” -ConnectionBroker rds01.watsons.local -verbose



      The Test-RDOUAccess then succeeded.


      I repeated this for the OUs that contained the users and the server computer objects.


      I’ve disabled all GPOs to ensure there’s no conflicts but have seen no change in the behavior or error messages.


      With all that, I’ve exhausted every option that I can find to resolve this error to gain the expected functionality. As a work around for the moment, I’ve setup a round-robin DNS A record that points to TS02 and TS03 w/ a very short TTL. This gives

      the test users the ability to login and atleast test the desktop functionality.


      Sorry for being so long winded with this but I thought it better to put all the cards on the table.


      I’m open to any and all suggestions.


      Thx!




      • Edited by

        f-n-b

        Saturday, December 31, 2022 7:13 PM

        formatting

      Saturday, December 31, 2022 7:06 PM




    Answers




    • Question


      Sign in to vote


      1


      Sign in to vote


      Hi,


      For the problem, I have tested for this on Windows Server 2022.


      For the RD Connection Broker do not redirect the session to RDSH in a new RDS environment, you need configure the default collection on RDCB in registry.


      You should create the registry value
      DefaultTsvUrlunder the path below with
      tsv://MS Terminal Services Plugin.1.<collection alias>
      on RDCB.


      HKLMSYSTEMCurrentControlSetControlTerminal ServerClusterSettings


      For the value, you could find it in Event Viewer on RDCB like below.




      Note: you should make back up before modifying registry.


      Here is a similar thread below for your reference.


      https://social.technet.microsoft.com/Forums/en-US/09c884f3-5bad-4a30-b707-99ea02c50c63/rd-session-broker-will-not-work-with-desktop-sessions?forum=winserverTS


      Best Regards,


      Jay


      Please remember to mark the replies as answers if they help.

      If you have feedback for TechNet Subscriber Support, contact

      .




      • Proposed as answer by

        Jay Gu

        Tuesday, January 3, 2022 11:28 AM


      • Marked as answer by

        f-n-b

        Wednesday, January 4, 2022 1:54 AM

      Tuesday, January 3, 2022 11:28 AM




    All replies




    • Question


      Sign in to vote


      1


      Sign in to vote


      Hi,


      For the problem, I have tested for this on Windows Server 2022.


      For the RD Connection Broker do not redirect the session to RDSH in a new RDS environment, you need configure the default collection on RDCB in registry.


      You should create the registry value
      DefaultTsvUrlunder the path below with
      tsv://MS Terminal Services Plugin.1.<collection alias>
      on RDCB.


      HKLMSYSTEMCurrentControlSetControlTerminal ServerClusterSettings


      For the value, you could find it in Event Viewer on RDCB like below.




      Note: you should make back up before modifying registry.


      Here is a similar thread below for your reference.


      https://social.technet.microsoft.com/Forums/en-US/09c884f3-5bad-4a30-b707-99ea02c50c63/rd-session-broker-will-not-work-with-desktop-sessions?forum=winserverTS


      Best Regards,


      Jay


      Please remember to mark the replies as answers if they help.

      If you have feedback for TechNet Subscriber Support, contact

      .




      • Proposed as answer by

        Jay Gu

        Tuesday, January 3, 2022 11:28 AM


      • Marked as answer by

        f-n-b

        Wednesday, January 4, 2022 1:54 AM

      Tuesday, January 3, 2022 11:28 AM





    • Question


      Sign in to vote


      0


      Sign in to vote


      Jay,



      Thank you for the information as that fixed my issue.


      Cheers!


      Wednesday, January 4, 2022 1:56 AM





    • Question


      Sign in to vote


      0


      Sign in to vote


      Hello,


      I create the string value, adding the value, but not working.



      DP to brokers servers do not working anymore.



      Any update??



      Wednesday, April 11, 2022 5:40 PM





    • Question


      Sign in to vote


      0


      Sign in to vote


      I get the same error,



      When I add broker to HA, no more able to connect to session host servers. (1305 and 1296 error==< FAIL TO REDIRECT THE CLIENT. I use rdweb before so collections setting is present on .rdp file)



      Any update?



      Wednesday, May 8, 2022 11:15 AM





    • Question


      Sign in to vote


      1


      Sign in to vote


      I just checked the sự kiện viewer and I couldn’t find the necessary value , I don’t have Error 800 only 832.


      Any other ways to find it ?


      


      Tuesday, July 9, 2022 7:29 AM



    7 Replies


    · · ·



    Mhumphries


    Jalapeno


    OP


    Mhumphries


    May 24, 2022 14:32 UTC


    one more error that we are seeing


    Remote Desktop Connection Broker Client failed to redirect the user domainuser
    Error: The RPC server is unavailable.


    0


    · · ·



    Justin1250


    Mace


    OP


    Justin1250


    This person is a Verified Professional



    This person is a verified professional.



    Verify your account

    to enable IT peers to see that you are a professional.



    May 24, 2022 15:33 UTC


    Mhumphries wrote:


    the last 2 days i have noted that our one beta user, is trying to connect in the morning and it connects to the actual RDCB instead of the farm behind it.


    They are likely just opening up the RDP client instead of using an icon file or RDWeb as the client doesn’t know that about the LB entry. Which looks like this:


    Text


    loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.SesssionHost


    Have you watched this user try to login?


    0


    · · ·



    Mhumphries


    Jalapeno


    OP


    Mhumphries


    May 24, 2022 17:30 UTC


    the client is using a thin client so there is a setting for the broker that then shows them the Collection and allows them to log in.


    0


    · · ·



    ericroy2


    Pimiento


    OP


    ericroy2


    Jul 14, 2022 02:18 UTC


    1st Post


    Hi,


    i have the same issue. In the morning, i need to restart my RDP server. Im not getting this issue everyday.


    0


    · · ·



    paulvanboerdonk


    Pimiento


    OP


    paulvanboerdonk


    Sep 19, 2022 07:46 UTC


    1st Post



    Hi Michael,


    Did you manage to fix this issue? I am running into the same errors this moment.


    Thnx,


    Paul


    0


    · · ·



    Mhumphries


    Jalapeno


    OP


    Mhumphries


    Sep 19, 2022 12:00 UTC


    Since this was in beta and not production i ended up rebuilding the entire server farm again and i have not had any issues since. i know that is not the answer you are looking for but i never got it working without that.


    0


    · · ·


    · · ·



    gabrielgarza


    Pimiento


    OP


    gabrielgarza


    Jan 24, 2022 23:54 UTC


    We were having similar issue with WSrv 2022 RDHS (single server) after a power outage (dirty shutdown).


    As described inhttp://blog.ronnypot.nl/?p.=1013, the error sometimes happens when (1) you haven’t configured a collection, or (2) the collection configuration becomes corrupt. Solution is to recreate the collection. If you have a lot of apps (or special settings), could probably make a script based onhttps://stackoverflow.com/questions/25518071/powershell-re-create-rds-remote-apps-by-loopingto persist the RemoteApps list and settings to a CSV


    , delete it, and then recreate the collection.


    In our case, we made some changes to the collection using the UI, and then rebooted the server, and it is now functional.


    1



    This topic has been locked by an administrator and is no longer open for commenting.



    To continue this discussion, please

    ask a new question.


    Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User : Error: Remote Desktop Connection Broker is not ready for RPC communication.


    Posted on 11th October 2022 by



    I was getting this in my sự kiện log and users could no longer connect to RDS when trialling it –


    Event ID – 1296


    Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
    User : DOMAINUSER
    Error: Remote Desktop Connection Broker is not ready for RPC communication.


    and then


    Event ID – 1306


    Remote Desktop Connection Broker Client failed to redirect the user DOMAINUSER.
    Error: NULL



    I found the Fix for me was –


    If you edit the properties of your Session Collection, click on the Security on the left. There is a setting for Security Layer. By default it is Negotiate. Try toset it to RDP Security Layer


    My users could then connect again, i made the change in group policy for all TS (RDS) servers


    – Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostSecurity


    – Edit ‘Require use of specific security layer from rermote (RDP) connections to Security Layer-RDP


    This entry was posted in Tech Post and tagged 1296, 1306, broker, connection, sự kiện id, rds, ts. Bookmark the permalink.


    Reply

    7

    0

    Chia sẻ



    Question


    Question



    Question


    Question



    Question


    Question



    Question


    Question



    Question


    Question



    Question


    Question



    Question


    Question


    Chia Sẻ Link Down Remote Desktop Connection Broker Client failed to redirect the user error:NULL miễn phí


    Bạn vừa Read nội dung bài viết Với Một số hướng dẫn một cách rõ ràng hơn về Clip Remote Desktop Connection Broker Client failed to redirect the user error:NULL tiên tiến và phát triển nhất và ShareLink Download Remote Desktop Connection Broker Client failed to redirect the user error:NULL Free.



    Thảo Luận vướng mắc về Remote Desktop Connection Broker Client failed to redirect the user error:NULL


    Nếu sau khi đọc nội dung bài viết Remote Desktop Connection Broker Client failed to redirect the user error:NULL vẫn chưa hiểu thì hoàn toàn có thể lại Comment ở cuối bài để Mình lý giải và hướng dẫn lại nha

    #Remote #Desktop #Connection #Broker #Client #failed #redirect #user #errorNULL

Đăng nhận xét