none
Rermote Desktop Connection Problem

    Question

  • Hello,

    Though it has always worked OK, for over a year, I just started geting the following error, whenever I attempt to
    connect to any other computer: "Remote Desktop Connection has encountered a problem and needs to
    close."  It then only gives me the option of sending a report to Microsoft or not, and to click
    "OK" to close.  In the technical details of the message to Microsoft, the "Code:" is "0xc0000005". 
    The error signature is: "AppName: mstsc.exe     AppVer: 6.0.6001.18000     ModName: mstscax.dll  
      ModVer: 6.0.6001.18000     Offset: 0015b2f5"

    This behavior started after I had resolved a boot-up problem (various processes [including
    occasionally, Windows Explorer] would report an initialization failure, and that module would
    not be available to use until after another reboot, and the specific one or two modules/processes
    would vary from reboot to reboot), which I finally resolved by using the boot menu to "boot using
    last known good configuration".  After doing that "last known good" reboot, the system settled
    down and there were no more module initialization errors.  However, I then noticed the Remote
    Desktop problem that I described above.

    I have used the "netdiag" utility (netdiag /test:winsock /v) and the TCP/IP and winsock configurations
    look OK.  I have no trouble connecting to websites or FTP sites, and I also have no problem connecting
    to the same group of remote computers, at various IP Addresses, by using Real VNC.  However I do prefer
    the functionality of MS Remote Desktop.

    Here's my system (no recent changes):
      Compaq EVO W4000 Workstation, P4 2.4GHz, 2 GB PC2100 DDR RAM; NVIDIA Quadro NVS (dual head); Intel
      PRO/100 VM Network Adapter;
      Windows XP Pro SP3; WatchGuard Mobile VPN Lite Client (with Deterministic Network Enhancer & SafeNet
      Virtual Net Adapter); Net2Printer RDP Client software

    I've uninstalled and re-installed the WatchGuard and Net2Printer software, with reboot and testing
    between uninstalls and re-installs, without any effect on the problem.  I've also copied the files,
    mstsc.exe and mstscax.dll, from a known good WinXP SP3 machine into the problem system without any
    effect on the problem.

    Quoted below, is the complete text of the error file created by the error-reporting function:
    *****Begin Quote*****
    <?xml version="1.0" encoding="UTF-16"?>
    <DATABASE>
    <EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">
        <MATCHING_FILE NAME="advapi32.dll" SIZE="617472" CHECKSUM="0xA0887D0D" BIN_FILE_VERSION="5.1.2600.5755" BIN_PRODUCT_VERSION="5.1.2600.5755" PRODUCT_VERSION="5.1.2600.5755" FILE_DESCRIPTION="Advanced Windows 32 Base API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)" ORIGINAL_FILENAME="advapi32.dll" INTERNAL_NAME="advapi32.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xA5BB8" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5755" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5755" LINK_DATE="02/09/2009 12:10:48" UPTO_LINK_DATE="02/09/2009 12:10:48" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="gdi32.dll" SIZE="286720" CHECKSUM="0x98314A3F" BIN_FILE_VERSION="5.1.2600.5698" BIN_PRODUCT_VERSION="5.1.2600.5698" PRODUCT_VERSION="5.1.2600.5698" FILE_DESCRIPTION="GDI Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5698 (xpsp_sp3_gdr.081022-1932)" ORIGINAL_FILENAME="gdi32" INTERNAL_NAME="gdi32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4CE95" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5698" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5698" LINK_DATE="10/23/2008 12:36:14" UPTO_LINK_DATE="10/23/2008 12:36:14" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x2D998938" BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781" PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5781" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58" UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="ntdll.dll" SIZE="714752" CHECKSUM="0xC695BA95" BIN_FILE_VERSION="5.1.2600.5755" BIN_PRODUCT_VERSION="5.1.2600.5755" PRODUCT_VERSION="5.1.2600.5755" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xBC674" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5755" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5755" LINK_DATE="02/09/2009 12:10:48" UPTO_LINK_DATE="02/09/2009 12:10:48" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="ole32.dll" SIZE="1287168" CHECKSUM="0xB764FEEA" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Microsoft OLE for Windows" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2108)" ORIGINAL_FILENAME="OLE32.DLL" INTERNAL_NAME="OLE32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x14744B" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:10:57" UPTO_LINK_DATE="04/14/2008 00:10:57" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="oleaut32.dll" SIZE="551936" CHECKSUM="0xE8E0E87" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" COMPANY_NAME="Microsoft Corporation" FILE_VERSION="5.1.2600.5512" INTERNAL_NAME="OLEAUT32.DLL" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1993-2001." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x8D4E3" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:10:58" UPTO_LINK_DATE="04/14/2008 00:10:58" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="shell32.dll" SIZE="8461312" CHECKSUM="0x229B7DE8" BIN_FILE_VERSION="6.0.2900.5622" BIN_PRODUCT_VERSION="6.0.2900.5622" PRODUCT_VERSION="6.00.2900.5622" FILE_DESCRIPTION="Windows Shell Common Dll" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.00.2900.5622 (xpsp_sp3_gdr.080617-1319)" ORIGINAL_FILENAME="SHELL32.DLL" INTERNAL_NAME="SHELL32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x812125" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="6.0.2900.5622" UPTO_BIN_PRODUCT_VERSION="6.0.2900.5622" LINK_DATE="06/17/2008 19:02:17" UPTO_LINK_DATE="06/17/2008 19:02:17" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="user32.dll" SIZE="578560" CHECKSUM="0x6280E825" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Windows XP USER API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2105)" ORIGINAL_FILENAME="user32" INTERNAL_NAME="user32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x8FC76" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:07" UPTO_LINK_DATE="04/14/2008 00:11:07" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="wininet.dll" SIZE="915456" CHECKSUM="0xF831E25E" BIN_FILE_VERSION="8.0.6001.18783" BIN_PRODUCT_VERSION="8.0.6001.18783" PRODUCT_VERSION="8.00.6001.18783" FILE_DESCRIPTION="Internet Extensions for Win32" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Windows® Internet Explorer" FILE_VERSION="8.00.6001.18783 (longhorn_ie8_gdr.090508-1700)" ORIGINAL_FILENAME="wininet.dll" INTERNAL_NAME="wininet.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xE9EC0" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="8.0.6001.18783" UPTO_BIN_PRODUCT_VERSION="8.0.6001.18783" LINK_DATE="05/13/2009 05:15:55" UPTO_LINK_DATE="05/13/2009 05:15:55" VER_LANGUAGE="English (United States) [0x409]" />
        <MATCHING_FILE NAME="winsock.dll" SIZE="2864" CHECKSUM="0x73AE8088" BIN_FILE_VERSION="3.10.0.103" BIN_PRODUCT_VERSION="3.10.0.103" PRODUCT_VERSION="3.10" FILE_DESCRIPTION="Windows Socket 16-Bit DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows(TM) Operating System" FILE_VERSION="3.10" ORIGINAL_FILENAME="WINSOCK.DLL" INTERNAL_NAME="WINSOCK" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1981-1996" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16" S16BIT_DESCRIPTION="BSD Socket API for Windows" S16BIT_MODULE_NAME="WINSOCK" UPTO_BIN_FILE_VERSION="3.10.0.103" UPTO_BIN_PRODUCT_VERSION="3.10.0.103" VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    <EXE NAME="mstscax.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
        <MATCHING_FILE NAME="mstscax.dll" SIZE="2061824" CHECKSUM="0xB9F36C05" BIN_FILE_VERSION="6.0.6001.18000" BIN_PRODUCT_VERSION="6.0.6001.18000" PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="Terminal Services ActiveX Client" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6001.18000 (longhorn_rtm.080118-1840)" ORIGINAL_FILENAME="mstscax.dll" INTERNAL_NAME="mstscax.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1F8DBB" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6001.18000" UPTO_BIN_PRODUCT_VERSION="6.0.6001.18000" LINK_DATE="04/14/2008 00:11:33" UPTO_LINK_DATE="04/14/2008 00:11:33" VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    </DATABASE>
    *****End Quote*****

    Please advise.  I'm stumped!  Thanks.

    Regards,
    Bob Hakes
    Monday, June 22, 2009 9:54 PM

All replies

  • Well, 175 folks read that, but nobody replied!

    Since my post, I ran my then current Anti-Virus scanner, but it did not detect anything.  Then I ran the latest Microsoft Malicious Software Removal Tool, and it found that my NDIS.SYS file was infected with the Win32.Cutwail.F Trojan, but it was unable to remove the infection, and suggested that I run an A-V scanner.

    I ultimately located an Anti-Virus provider whose Anti-Virus Encyclopedia had a listing for the trojan in question (Avast!, and Symantec, and a couple of others did not list that quite new spam-bot, which was just discovered on June 1st of this year).  So, I purchased a copy of Bit Defender, installed and updated it, and ran it's Deep System Scan Task.  It took quite a while to complete its scanning of my four WDC Caviar 180 GB drives, but when it finished it had detected and completely cleaned up all of the pieces of the trojan, and my system worked properly, including the flawless operation of the Remote Desktop Connection Client.

    Obviously, my Remote Desktop Connection Client applet did not appreciate the way that the spam-bot was hooking into my system!

    Well worth the 1-year single-PC license fee of $24.95!!

    Regards,
    Bob Hakes
    Friday, June 26, 2009 6:54 PM
  • Hi Bob,

    Just this week my computer starting exhibiting the same exact symptoms (and error code) with RDT that you listed on your June 22 message. But with my system there was no definable( or at least recognized) event preceeding the problem. There might have been a MS update but I wasn't paying too much attention to those earlier this week.
    I'm running the MSRT as I write......... 25% complete on the C drive only after an hour.

    Thank you for the posting. I hope this works!

    My system:
    IBM T60
    T2500 2.9 GHz
    3GB RAM
    200 GB internal Drive
    1TB external drive
    Windows XP SP3
    Office 2007 professional
    Saturday, June 27, 2009 4:27 AM