locked
Unsolicited Remote Assistance Fails w/COM Object Error, Event Code 9 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    W7/64 Enterprise SP1
    Windows Server 2008 R2 SP1

    This is a new W7 installation. Unsolicited Remote Assistance works without
    issue to Windows XP SP3 clients from W7 client.

    When attempting to offer unsolicited remote assistance (msra /offer) between
    W7 clients the connection fails:

    Event Log entry

    All required permissions are in place. Required GPO's are configured.

    Fails with and without Symantec AV (SEP).

    Wednesday, June 20, 2012 8:16 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Resolved!

    Apparently, the Offer Remote Assistance Helper GPO property must be populated with whatever AD account/group you use to administer user's computers. I "assumed" that, if the AD administrative account I used which has Domain Admin permissions, that this was sufficiant for Unsolicited Remote Assistance to connect properly. I was wrong. Lesson learned... Assume nothing!

    • Marked as answer by GPOChallenged Thursday, June 28, 2012 1:36 PM
    Thursday, June 28, 2012 1:36 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Try the connection with firewall disabled.

    2. Command should read as

    msra /offera

    3. If 1&2 does not help, then look for item (from Event log) with the help of DCOMCNFG.EXE

    Regards

    Milos

    Wednesday, June 20, 2012 9:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,


    Based on my research, please try the following:

    1. Check the error by referring to Event ID: 9 Source: RemoteAssistance.

    2. Check the whether the users who want to offer remote assistance exist in Offer Remote Assistance Helpers in lusrmgr.msc.

    3. Remote Assistance uses DCOM and the DCOM reg path is HKEY_LOCAL_MACHINE\Software\Microsoft\Ole with a String value of EnableDCOM = Y. If this value is set to 'N' or is missing, remote assistance will not work.


    In addition, you can also refer to the similar thread: Problem using Remote Assistance from Server 2008 R2 to Windows 7 Enterprise 64-bit


    Hope this helps.

    Jeremy Wu

    TechNet Community Support

    Monday, June 25, 2012 10:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the replys, unfortunatley this issue is not resolved.

    The correct command is "msra /offerra" we both had it wrong.

    The Event ID: 9 returned null at EventID.net

    Remote assistance helpers are configured correctly

    EnableDCOM=Y is correctly configured

    The thread reference says they resolved their issue by altering some "cryptolevel". No idea what that is about but, I have not implemented anything related I believe.

    Monday, June 25, 2012 8:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    1. Please install KB939820 if you are using Windows Server 2003 DC:
    http://support.microsoft.com/kb/939820

    2. Check if you have configured to the following:
    Computer Configuration\Administrative Templates\System\Remote Procedure Call\
    Restrictions for Unauthenticated RPC Clients was set to -> Enabled Authenticated without Exceptions

    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by Zero Xia Thursday, June 28, 2012 12:15 PM
    Thursday, June 28, 2012 12:14 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Resolved!

    Apparently, the Offer Remote Assistance Helper GPO property must be populated with whatever AD account/group you use to administer user's computers. I "assumed" that, if the AD administrative account I used which has Domain Admin permissions, that this was sufficiant for Unsolicited Remote Assistance to connect properly. I was wrong. Lesson learned... Assume nothing!

    • Marked as answer by GPOChallenged Thursday, June 28, 2012 1:36 PM
    Thursday, June 28, 2012 1:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi GPOChallenged!

    Thanks for your efforts in solving this... but can you explain that in detail?
    Sorry...im kind of noob about GPO's and i cant get this to work...

    Im member of Domain Admin's group... So...where should i populate that "property" you refer in the GPO?

    Thanks in advance!
    Friday, January 4, 2013 9:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is a screen capture of the GPO in question. Click the 'Show...' button for the 'Show Contents' prompt to appear. The path to this GPO is in a box at the bottom of the capture.

    Thursday, January 17, 2013 2:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    In our case the issue with RA not working was due to a mismatch in encryption.  DCs were using RC4 and Win10 clients are using AES128/256/future.

    2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'
    Friday, January 24, 2020 9:42 PM