Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare MRC displays "Waiting for Initial Screen" when trying to connect to XP/2003 clients

DameWare MRC displays "Waiting for Initial Screen" when trying to connect to XP/2003 clients

Created by Marlo Bidayan, last modified by MindTouch on Jun 23, 2016

Views: 134 Votes: 1 Revisions: 5

Overview

When you initiate an MRC connection to a remote Windows XP or Windows Server 2003 client, MRC displays the message, "Waiting for Initial Screen" and does not show the remote screen.

Environment

All DameWare Mini Remote Control versions

Cause

This issue occurs when it takes too long for the network connection to go from the MRC host to the client system. For example, some customers experience this issue when running Sophos Anti-Virus 10.0 on XP systems since Sophos intercepts MRC traffic in order to bypass AV filtering.

Resolution

There are two workarounds for this issue:

  • Modify the MRC Registry settings on the remote system to accommodate slow connections. First, add the first key to the Registry on the remote system. If this does not work, add the second one.
    • [HKLM\SOFTWARE\DameWare Development\Mini Remote Control Service\Settings]
      "Disable WXL"=dword:00000001
    • [HKLM\SOFTWARE\DameWare Development\Mini Remote Control Service\Settings]
      "Disable WXL Check"=dword:00000001

       

         Make sure you back up the registry

         https://support.microsoft.com/en-us/kb/322756

 

  • Use the Send > Send Refresh command in MRC to force the connection.

 

Last modified
18:59, 22 Jun 2016

Tags

Classifications

Public