Remote Tools fails with "Agent did not receive a valid connection attempt within the time limit.

Session will be terminated.

Try to connect to the WMI of the remote client: 1. To do that from the Site Server, Open the WBEMTEST.

2. Then in the WBEMTEST, type following \\machine name\root\cimv2 [DO this from a Remote Machine site server could be used] 3. Machine Name could be the NETBIOS/FQDN of the machine which is experiencing the issue. 4. And then click on connect, If you have issues connecting to remote WMI

Then; Forget about remote tools fix WMI first. If we are able to connect to the remote WMI, You are on the right track and keep reading further.
In the second hurdle we need to check if the client is getting the po licy for the permitted viewer:

Well add a user account/Group in the permitted viewers tab on the ConfigMgr Console. Once you have done that, Try checking the client side registry settings; either the client is able to receive the newly added user account /group. To specify a new remote tools permitted viewer account 1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site server name> / Site Settings / Client Agents. 2. In the results pane, right-click Remote Tools Client Agent and then click Properties.

3.

In the Remote Tools Client Agent Properties dialog box, click the Security tab.

4. Click the new button to open the New Viewer dialog box, and then specify an existing Microsoft Windows user account or group name. 5. Click OK to close the dialog box, and then click OK to close the Remote Tools Client Agent Properties dialog box.

Once you have added the user accounts in the ConfigMgr console, Please go back to the client and force the Machine Policy Retrieval. Once that is done we should check the client after 2-3 minutes to verify the Permitted Viewer account that we added in the console should be listed under : HKLM\Software\Microsoft\SMS\Client\Client Components\Remote Control

In the right hand side you should see, Permitted Viewer and its value must contain the user account/group that we added in the ConfigMgr console as explained above.

If thats not the case; Stop here and check why the policy is not getting delivered to the client.

If you see the account/group in the permitted viewers then move to the next steps:

Here are the miscellaneous steps that we can use, Also please note that if you can capture the NETMON trace. Heres one article that gives you how you can leverage the NETMON http://support.microsoft.com/kb/812953

OR

You can also use the WireShark as well. Click here to download the latest version of Wireshark.
1. Check the log created RemoteControl.log Ccmsetup \ client is having problems. 2. Check the log RemoteTools.log created in% temp% in the computer that is initiating the connection. 3. Verify that the ConfigMgr Remote Control Users group is correctly configured on the client. 4. Check the security settings for DCOM are applied correctly. 5. Ensure that ports TCP 2701, TCP 2702, TCP 135 are released into the firewall. If you are using Remote Desktop or Remote Assistance check if TCP port 3389 is released in the firewall. 6. Make sure the file c: \ windows \ system32 \ RCAgent.exe is also released into the firewall. 7. Make sure the file c: \ windows \ PCHealth \ HelpCtr \ binaries \ Helpsvc.exe is also released into the firewall or the File and Printer Sharing. 8. Make sure the anti-virus is not blocking the remote connection. 9. Verify that no other remote connection to the same customer. 10. Groups linked with Remote Tools do not work, that is, one should place the main group. 11. When capturing network packets by Wireshark, check for: isystemactivator a. For successful connection has only one pair of ISystemActivator RemoteGetClassObject ISystemActivator RemoteGetClassObject request and response

12. b. To have connection without success:

a. When the user does not have permission DCOM: ISystemActivator RemoteGetClassObject request and another could be DCERPC Fault: call_id: 10 ctx_id: 0 Status: nca_s_fault_access_denied

b. When the user has permission DCOM, there will be several times the double ISystemActivator RemoteGetClassObject request and another ISystemActivator RemoteGetClassObject response. 13. See http://technet.microsoft.com/en-us/library/bb735873.aspx for a list of error codes using Remote Tools.