Remote Desktop Connection has stop'd working.

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: mstsc.exe
  Application Version: 6.2.9200.16384
  Application Timestamp: 50108ae1
  Fault Module Name: ntdll.dll
  Fault Module Version: 6.2.9200.16384
  Fault Module Timestamp: 5010acd2
  Exception Code: c0000005
  Exception Offset: 0000000000005512
  OS Version: 6.2.9200.2.0.0.256.48
  Locale ID: 1033
  Additional Information 1: 2534
  Additional Information 2: 25341db0b9a417145dca7b48f0cbb4e4
  Additional Information 3: a713
  Additional Information 4: a71352bbdf06cb9997aaf28933a5ca7d

Hi,
Based on the current situation, this error means mstsc.exe made a call into ntdll.dll (which is part of the Windows operating system) and whatever they're doing, they're doing it wrong because it caused a crash.
Let us try capture a dump file  and upload your app dump file.
First enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\mstsc.exe]
"DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\
  00,6d,00,70,00,73,00,00,00
"DumpCount"=dword:00000010
"DumpType"=dword:00000001
"CustomDumpFlags"=dword:00000000
Then, do a Remote Desktop Connection which may cause the issue. If error appeared, please find the crashdump file under c:\.
Note: I highly recommend you use SkyDrive to upload collected files and to post screen shots/pictures. Although you might not be used to it, SkyDrive features a lot of free advanced functionality around file storage capacity, sharing, privacy, and collaboration:
http://skydrive.com
Keep post.
Regards,
Kelvin hsu
TechNet Community Support

Similar Messages

  • "remote desktop connection has stopped working" When printing from remote desktop connection

    I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
    Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
    -I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
    diffrent machines just not the Windows 7 machine.

    Hi,
    Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
    As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections.  If you are making Connections using a single
    monitor do not use this setting. 
    So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
    path.
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
    Meanwhile sharing article with you for more information.
    Remote Session Environment
    http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
    Hope it helps!
    Thanks.

  • Remote Desktop Connection has stopped working

    Using Build 10041. Occurs on 2 separate systems I have when trying to use Remote Desktop Connection through a 2012 R2 RDS Gateway. I am able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE
    crashing. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
    Eventlog has the following:
    Log Name:      Application
    Source:        Application Error
    Date:          3/25/2015 2:50:21 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7
    Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315
    Exception code: 0xc0000005
    Fault offset: 0x000000000046d78c
    Faulting process id: 0x2164
    Faulting application start time: 0x01d06734abf028a0
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\mstscax.dll
    Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005
    Faulting package full name:
    Faulting package-relative application ID:
    JW

    Tried this with no luck.  I have the same issue as the OP.  It was failing on 10041 and is still failing with an AV on 10049.  See below event log entry after registering mstscax.dll and rebooting.  Still failing.
    Log Name:      Application
    Source:        Application Error
    Date:          4/11/2015 12:18:21
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Chuck1
    Description:
    Faulting application name: mstsc.exe, version: 10.0.10049.0, time stamp: 0x55137bff
    Faulting module name: mstscax.dll, version: 10.0.10049.0, time stamp: 0x55137d3f
    Exception code: 0xc0000005
    Fault offset: 0x000000000046d74c
    Faulting process id: 0x1870
    Faulting application start time: 0x01d0748c29e55e06
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\mstscax.dll
    Report Id: 83921b7c-e07f-11e4-960f-40f02f7ad3a4
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-11T19:18:21.000000000Z" />
        <EventRecordID>73626</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Chuck1</Computer>
        <Security />
      </System>
      <EventData>
        <Data>mstsc.exe</Data>
        <Data>10.0.10049.0</Data>
        <Data>55137bff</Data>
        <Data>mstscax.dll</Data>
        <Data>10.0.10049.0</Data>
        <Data>55137d3f</Data>
        <Data>c0000005</Data>
        <Data>000000000046d74c</Data>
        <Data>1870</Data>
        <Data>01d0748c29e55e06</Data>
        <Data>C:\WINDOWS\system32\mstsc.exe</Data>
        <Data>C:\WINDOWS\system32\mstscax.dll</Data>
        <Data>83921b7c-e07f-11e4-960f-40f02f7ad3a4</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

  • "Remote Desktop connection has stopped working." problem in Windows 8

    here is the event log.  Only happens on a few of our servers
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
    Exception code: 0xc0000005
    Fault offset: 0x0000000000002acd
    Faulting process id: 0x13c4
    Faulting application start time: 0x01cdbd0d09091fcd
    Faulting application path: C:\Windows\System32\mstsc.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 4d923a55-2900-11e2-be73-cc52af4d02a3
    Faulting package full name:

    Your Ricoh printer drivers cause the crashes:
    * Exception Analysis *
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for RC5BE130.DLL -
    FAULTING_IP:
    ntdll!memcpy+21a
    000007f8`1fed2acd f30f6f4402f0 movdqu xmm0,xmmword ptr [rdx+rax-10h]
    EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007f81fed2acd (ntdll!memcpy+0x000000000000021a)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000bd9e440c
    Attempt to read from address 00000000bd9e440c
    DEFAULT_BUCKET_ID: INVALID_POINTER_READ
    PROCESS_NAME: mstsc.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 00000000bd9e440c
    READ_ADDRESS: 00000000bd9e440c
    FOLLOWUP_IP:
    RC5BE130!PrinterProperties+2a1ea
    00000000`71c4c46a 8b442430 mov eax,dword ptr [rsp+30h]
    DETOURED_IMAGE: 1
    NTGLOBALFLAG: 0
    APPLICATION_VERIFIER_FLAGS: 0
    APP: mstsc.exe
    FAULTING_THREAD: 0000000000001198
    PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
    BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
    LAST_CONTROL_TRANSFER: from 0000000071c4c46a to 000007f81fed2acd
    STACK_TEXT:
    000000bb`ba9cf248 00000000`71c4c46a : 000000bb`00000040 000000bb`ba9cf618 000000bb`bd7a1458 00000000`00000000 : ntdll!memcpy+0x21a
    000000bb`ba9cf250 00000000`71c4bf68 : 000000bb`b45ccc40 000000bb`bae6e7c8 000000bb`bd7a1458 00000000`00000000 : RC5BE130!PrinterProperties+0x2a1ea
    000000bb`ba9cf2a0 00000000`71c4b2f9 : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`71c10000 : RC5BE130!PrinterProperties+0x29ce8
    000000bb`ba9cf380 00000000`71c2a08a : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`02000000 : RC5BE130!PrinterProperties+0x29079
    000000bb`ba9cf3d0 00000000`71c283de : 000000bb`ba9cf618 000000bb`badfb050 000000bb`00000000 00650074`00730079 : RC5BE130!PrinterProperties+0x7e0a
    000000bb`ba9cf440 00000000`71c2209d : 00000000`00000000 000000bb`ba9cf618 00007989`001a0019 000007f8`169fafa0 : RC5BE130!PrinterProperties+0x615e
    000000bb`ba9cf550 000007f8`169e5ea0 : 00000000`00000000 000000bb`ba9cf618 000000bb`bd7a1458 000000bb`bd7a1458 : RC5BE130!DrvDocumentPropertySheets+0x1d
    000000bb`ba9cf580 000007f8`169e6b9f : 000000bb`00000000 000000bb`ba9cf670 00000000`00000000 00000000`00000004 : winspool!DocumentPropertySheets+0xb0
    000000bb`ba9cf5f0 000007f8`169e6aa5 : 00000000`00000002 000007f8`ffffffff 00000000`00000000 00000000`00000000 : winspool!DocumentPropertiesWNative+0xcf
    000000bb`ba9cf680 000007ff`f4f3dc32 : 00000000`00000000 000000bb`b93f3990 00000000`000004d4 000000bb`ba9cf790 : winspool!DocumentPropertiesW+0x7d
    000000bb`ba9cf6e0 000007ff`f4f9a09b : 00000000`00000000 000000bb`ba9cf7b0 00000000`00000000 000000bb`b93c7530 : mstscax!CTSClientPrintDriver::DocumentPropertiesW+0x37e
    000000bb`ba9cf730 000007ff`f4f994d4 : 000000bb`b93c7530 000007f8`00000000 00000000`00000000 000000bb`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Invoke_DocumentPropertiesW+0x12b
    000000bb`ba9cf7e0 000007ff`f4f8ff0c : 000000bb`b93c7530 000000bb`b93f29e0 000000bb`b94060d0 00000000`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Dispatch_Invoke+0x68
    000000bb`ba9cf840 000007ff`f4f95a84 : 000000bb`b93c7530 00000000`00000000 000000bb`b93c7530 000000bb`b93cccc0 : mstscax!CStub<IMMClientNotifications>::Invoke+0x64
    000000bb`ba9cf8b0 000007ff`f4f94310 : 000000bb`b93cccc0 000000bb`b93c7530 000000bb`ba9cf930 000000bb`b693b3c0 : mstscax!CRIMStreamStub::OnDataReceived+0x98
    000000bb`ba9cf8e0 000007ff`f4f18c5a : 000000bb`b93cccc0 000000bb`b93f4cd8 000000bb`b93f4b10 000000bb`b93f4cd8 : mstscax!CRIMObjManager::OnDataReceived+0x150
    000000bb`ba9cf960 000007ff`f4f20132 : 000000bb`b93c6908 00000000`00000000 000000bb`b93c6908 00000000`00000e28 : mstscax!CDynVCChannel::HandleAsyncCall+0x12e
    000000bb`ba9cf9b0 000007ff`f4ed94e7 : 000000bb`b93f36a0 000000bb`b93c68c0 00000000`00000000 000000bb`b93f40d0 : mstscax!CDynVCThreadPoolThread::ThreadPoolEntry+0x102
    000000bb`ba9cfa00 000007ff`f4c5aba9 : 000000bb`b7ddeb58 00000000`00000000 000007ff`f4b50000 00000000`00000000 : mstscax!CTSThread::TSStaticThreadEntry+0x33b
    000000bb`ba9cfa90 000007f8`1e41167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!PAL_System_Win32_ThreadProcWrapper+0x25
    000000bb`ba9cfac0 000007f8`1fef3501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    000000bb`ba9cfaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: rc5be130!PrinterProperties+2a1ea
    FOLLOWUP_NAME: wintriag
    MODULE_NAME: RC5BE130
    IMAGE_NAME: RC5BE130.DLL
    DEBUG_FLR_IMAGE_TIMESTAMP: 4bd67428
    STACK_COMMAND: ~18s; .ecxr ; kb
    FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RC5BE130.DLL!PrinterProperties
    BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_DETOURED_rc5be130!PrinterProperties+2a1ea
    WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/ntdll_dll/6_2_9200_16420/505ab405/c0000005/00002acd.htm?Retriage=1
    Followup: wintriag
    0:018> lmvm RC5BE130
    start end module name
    00000000`71b00000 00000000`71cdd000 RC5BE130 (export symbols) RC5BE130.DLL
    Loaded symbol image file: RC5BE130.DLL
    Image path: C:\Windows\System32\spool\drivers\x64\3\RC5BE130.DLL
    Image name: RC5BE130.DLL
    Timestamp: Tue Apr 27 07:20:40 2010 (4BD67428)
    CheckSum: 001E2D52
    ImageSize: 001DD000
    File version: 0.3.0.0
    Product version: 1.0.0.0
    File flags: 1 (Mask 3F) Debug
    File OS: 40004 NT Win32
    File type: 2.1 Dll
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: RICOH CO., LTD.
    ProductName: RICOH RPCS Printer Driver
    InternalName: RC5BE130.DLL
    OriginalFilename: RC5BE130.DLL
    ProductVersion: 1.0.0
    FileVersion: 7.6.9
    FileDescription: RICOH RPCS Printer Driver
    LegalCopyright: Copyright(C) 1999-2010 RICOH CO., LTD.
    so check for a printer driver update and what you can also do is to avoid mapping your printer to the Remote Desktop. Maybe this also fixes the issue.
    "A programmer is just a tool which converts caffeine into code"

  • Remote Desktop Connection has encountered a problem and needs to close. We are sorry for the inconvenience.

    Remote Desktop Connection has encountered a problem and needs to close. We are sorry for the inconvenience.

    Hiya,
    What O/S versions(RDP) are you connecting to and from? Try and open the target machines event log and see what it throws when you try to connect.

  • Remote control fails if remote desktop connection has occurred...

    Windows 7 64 bit. ZCM 11.2.
    ZENworks Adaptive Agent Version: 11.2.0.16117
    I enabled remote desktop connections to the Windows 7 PC. I can
    remote control it through ZCM without any problems. But if someone
    makes a remote desktop connection to that PC, I can no longer remote
    control it until after the PC is restarted (haven't tested further to
    see what else will fix it). When I attempt to remote control through
    ZCM, it eventually times out with this error: "Communication error.
    It is likely that some other application is running on the specified
    port."
    Any known fix or workaround for this?
    Thanks,
    Ken

    Lindsey,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Remote Desktop Connection (RDC) No longer working - Please help!

    Ok... here we go.  I cannot RDC to my network at work.  I originally was using a PC and was able to connect a few times using RDC before it stopped working.  It would not connect either wirelessly or connected via ethernet cable no matter what I tried.  I then tried a laptop from work - same problem.  I then went and bought a new Macbook Pro - connected no problem 5 times in a row until it stopped worked again out of the blue.  
    In summary:
    - same problem exists on Macs and PCs
    - same problem exists when using Wifi or Ethernet cable
    - problem ONLY occurs at home with my FIOS router - all the same computers can RDC using any other network
    - if I connect to my neighbor's Wifi on either a Mac or PC, it's works fine
    Please help!!  I've been looking at my router settings but I'm over my head.  Any help would be greatly appreciated. 

    I am going to take an educated guess as to why, it does not work. If this does not solve the issue, please post,
    The solution was posted here by user "tns", from user BigDaddy on DSLReports:
    Login to your router normally, then click this link, which will take you to the now-hidden IGMP Proxy config page:
    192.168.1.1/index.cgi?active_page=6059
    If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

  • Remote Desktop Connection Stopped Working when Disconnecting

    Hi I have a fresh clean install of Windows 8.1. Whenever I RDP into another Windows 8 machine... upong disconnecting I get the error: "Remote Desktop Connection Stopped Working"
    I have tried not mapping to remote printers, or drives (smart cards etc.) and it still persists. When I remote to Windows Server or Win 7, it does not happen. 
    Anyone have any ideas?
    Thank you
    mi

    FYI, same issue here, Windows 8.1 on ThinkPad W520 (upgraded from Windows 8).
    Even without Fingerprint Manager, and having uninstalled ThinkVantage Password Manager as well, still crashes.  I also tried the:
    Dism /Online /Cleanup-Image /RestoreHealth
    but no luck, my mstsc.exe is still crashing when the remote session window is closed.
    Any ideas?  Happy to upload/provide more details, here's the Report.wer contents from
    C:\Users\myusername\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_fe9be6b453d387663f457b9f305ac5e3ae6f5fc2_00000000_2fb47393\Report.wer
    Version=1
    EventType=CLR20r3
    EventTime=130332895175356766
    ReportType=2
    Consent=1
    UploadTime=130332895176424161
    ReportIdentifier=1d23a02d-7507-11e3-81f8-f0def1f95c65
    Response.BucketId=c93f173301a697688e31de36235ffda6
    Response.BucketTable=5
    Response.LegacyBucketId=-439202015
    Response.type=4
    Sig[0].Name=Problem Signature 01
    Sig[0].Value=mstsc.exe
    Sig[1].Name=Problem Signature 02
    Sig[1].Value=6.3.9600.16384
    Sig[2].Name=Problem Signature 03
    Sig[2].Value=5215e2b5
    Sig[3].Name=Problem Signature 04
    Sig[3].Value=WHSOLConnector
    Sig[4].Name=Problem Signature 05
    Sig[4].Value=2.5.7.7
    Sig[5].Name=Problem Signature 06
    Sig[5].Value=4beac4d4
    Sig[6].Name=Problem Signature 07
    Sig[6].Value=70
    Sig[7].Name=Problem Signature 08
    Sig[7].Value=71
    Sig[8].Name=Problem Signature 09
    Sig[8].Value=System.NullReferenceException
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    UI[2]=C:\WINDOWS\system32\mstsc.exe
    UI[3]=Remote Desktop Connection has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\WINDOWS\system32\mstsc.exe
    LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\WINDOWS\system32\KERNEL32.DLL
    LoadedModule[3]=C:\WINDOWS\system32\KERNELBASE.dll
    LoadedModule[4]=C:\WINDOWS\system32\ADVAPI32.dll
    LoadedModule[5]=C:\WINDOWS\system32\GDI32.dll
    LoadedModule[6]=C:\WINDOWS\system32\USER32.dll
    LoadedModule[7]=C:\WINDOWS\system32\msvcrt.dll
    LoadedModule[8]=C:\WINDOWS\system32\ole32.dll
    LoadedModule[9]=C:\WINDOWS\system32\OLEAUT32.dll
    LoadedModule[10]=C:\WINDOWS\system32\SHELL32.dll
    LoadedModule[11]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.16384_none_62475f7becb72503\COMCTL32.dll
    LoadedModule[12]=C:\WINDOWS\system32\COMDLG32.dll
    LoadedModule[13]=C:\WINDOWS\system32\SHLWAPI.dll
    LoadedModule[14]=C:\WINDOWS\system32\CRYPT32.dll
    LoadedModule[15]=C:\WINDOWS\system32\WINHTTP.dll
    LoadedModule[16]=C:\WINDOWS\system32\credui.dll
    LoadedModule[17]=C:\WINDOWS\system32\Secur32.dll
    LoadedModule[18]=C:\WINDOWS\system32\CRYPTUI.dll
    LoadedModule[19]=C:\WINDOWS\system32\CFGMGR32.dll
    LoadedModule[20]=C:\WINDOWS\system32\WS2_32.dll
    LoadedModule[21]=C:\WINDOWS\system32\NETAPI32.dll
    LoadedModule[22]=C:\WINDOWS\system32\RPCRT4.dll
    LoadedModule[23]=C:\WINDOWS\system32\WINMM.dll
    LoadedModule[24]=C:\WINDOWS\system32\IPHLPAPI.DLL
    LoadedModule[25]=C:\WINDOWS\SYSTEM32\sechost.dll
    LoadedModule[26]=C:\WINDOWS\SYSTEM32\combase.dll
    LoadedModule[27]=C:\WINDOWS\system32\MSASN1.dll
    LoadedModule[28]=C:\WINDOWS\system32\NSI.dll
    LoadedModule[29]=C:\WINDOWS\system32\netutils.dll
    LoadedModule[30]=C:\WINDOWS\system32\srvcli.dll
    LoadedModule[31]=C:\WINDOWS\system32\wkscli.dll
    LoadedModule[32]=C:\WINDOWS\system32\WINMMBASE.dll
    LoadedModule[33]=C:\WINDOWS\system32\WINNSI.DLL
    LoadedModule[34]=C:\WINDOWS\system32\SHCORE.DLL
    LoadedModule[35]=C:\WINDOWS\system32\DEVOBJ.dll
    LoadedModule[36]=C:\WINDOWS\system32\SSPICLI.DLL
    LoadedModule[37]=C:\WINDOWS\system32\IMM32.DLL
    LoadedModule[38]=C:\WINDOWS\system32\MSCTF.dll
    LoadedModule[39]=C:\Windows\system32\nvinitx.dll
    LoadedModule[40]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
    LoadedModule[41]=C:\WINDOWS\system32\CRYPTBASE.dll
    LoadedModule[42]=C:\WINDOWS\system32\bcryptPrimitives.dll
    LoadedModule[43]=C:\WINDOWS\system32\uxtheme.dll
    LoadedModule[44]=C:\WINDOWS\system32\credssp.dll
    LoadedModule[45]=C:\WINDOWS\system32\NTASN1.dll
    LoadedModule[46]=C:\WINDOWS\SYSTEM32\clbcatq.dll
    LoadedModule[47]=C:\WINDOWS\system32\PROPSYS.dll
    LoadedModule[48]=C:\WINDOWS\system32\dwmapi.dll
    LoadedModule[49]=C:\WINDOWS\system32\mstscax.dll
    LoadedModule[50]=C:\WINDOWS\system32\PSAPI.DLL
    LoadedModule[51]=C:\WINDOWS\system32\d2d1.dll
    LoadedModule[52]=C:\WINDOWS\system32\d3d11.dll
    LoadedModule[53]=C:\WINDOWS\system32\MSACM32.dll
    LoadedModule[54]=C:\WINDOWS\system32\VERSION.dll
    LoadedModule[55]=C:\WINDOWS\system32\SETUPAPI.dll
    LoadedModule[56]=C:\WINDOWS\system32\DWrite.dll
    LoadedModule[57]=C:\WINDOWS\system32\bcrypt.dll
    LoadedModule[58]=C:\WINDOWS\system32\ncrypt.dll
    LoadedModule[59]=C:\WINDOWS\system32\pdh.dll
    LoadedModule[60]=C:\WINDOWS\system32\dxgi.dll
    LoadedModule[61]=C:\WINDOWS\system32\explorerframe.dll
    LoadedModule[62]=C:\WINDOWS\system32\DUser.dll
    LoadedModule[63]=C:\WINDOWS\system32\DUI70.dll
    LoadedModule[64]=C:\WINDOWS\system32\WINTRUST.dll
    LoadedModule[65]=C:\Windows\system32\WHSOLConnector.dll
    LoadedModule[66]=C:\WINDOWS\system32\mscoree.dll
    LoadedModule[67]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
    LoadedModule[69]=C:\WINDOWS\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_88dcdb0b2fb19957\MSVCR80.dll
    LoadedModule[70]=C:\WINDOWS\system32\profapi.dll
    LoadedModule[71]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\mscorlib\97d2eb053ee241db571311577790ae43\mscorlib.ni.dll
    LoadedModule[72]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
    LoadedModule[73]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System\8b12c5fec7e8912da325ee73b380e652\System.ni.dll
    LoadedModule[74]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Drawing\3eac16e6688dfec78565e3e71a26266f\System.Drawing.ni.dll
    LoadedModule[75]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\d78d7a76a56319e4bc1cbffa3a90a0e1\System.Windows.Forms.ni.dll
    LoadedModule[76]=C:\WINDOWS\System32\Essentials\VCListener.dll
    LoadedModule[77]=C:\WINDOWS\system32\MF.dll
    LoadedModule[78]=C:\WINDOWS\system32\MFCORE.DLL
    LoadedModule[79]=C:\WINDOWS\system32\ksuser.dll
    LoadedModule[80]=C:\WINDOWS\system32\MFPlat.dll
    LoadedModule[81]=C:\WINDOWS\system32\RTWorkQ.DLL
    LoadedModule[82]=C:\WINDOWS\system32\AVRT.dll
    LoadedModule[83]=C:\Windows\System32\MSAudDecMFT.dll
    LoadedModule[84]=C:\WINDOWS\System32\MMDevApi.dll
    LoadedModule[85]=C:\WINDOWS\System32\perfos.dll
    LoadedModule[86]=C:\Windows\System32\msxml6.dll
    LoadedModule[87]=C:\WINDOWS\system32\NLAapi.dll
    LoadedModule[88]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[89]=C:\WINDOWS\system32\WTSAPI32.dll
    LoadedModule[90]=C:\WINDOWS\system32\WINSTA.dll
    LoadedModule[91]=C:\WINDOWS\system32\mswsock.dll
    LoadedModule[92]=C:\WINDOWS\system32\DNSAPI.dll
    LoadedModule[93]=C:\Program Files\Bonjour\mdnsNSP.dll
    LoadedModule[94]=C:\WINDOWS\System32\fwpuclnt.dll
    LoadedModule[95]=C:\WINDOWS\system32\DPAPI.DLL
    LoadedModule[96]=C:\WINDOWS\system32\CRYPTSP.dll
    LoadedModule[97]=C:\WINDOWS\system32\rsaenh.dll
    LoadedModule[98]=C:\WINDOWS\system32\schannel.DLL
    LoadedModule[99]=C:\WINDOWS\system32\tspkg.DLL
    LoadedModule[100]=C:\WINDOWS\system32\ncryptsslp.dll
    LoadedModule[101]=C:\WINDOWS\SYSTEM32\gpapi.dll
    LoadedModule[102]=C:\WINDOWS\system32\wdmaud.drv
    LoadedModule[103]=C:\WINDOWS\system32\AUDIOSES.DLL
    LoadedModule[104]=C:\WINDOWS\SYSTEM32\powrprof.dll
    LoadedModule[105]=C:\WINDOWS\system32\msacm32.drv
    LoadedModule[106]=C:\WINDOWS\system32\midimap.dll
    LoadedModule[107]=C:\Windows\System32\msmpeg2vdec.dll
    LoadedModule[108]=C:\WINDOWS\System32\msvproc.dll
    LoadedModule[109]=C:\WINDOWS\system32\LINKINFO.dll
    LoadedModule[110]=C:\WINDOWS\system32\ntshrui.dll
    LoadedModule[111]=C:\WINDOWS\system32\cscapi.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=CLR20r3
    AppName=Remote Desktop Connection
    AppPath=C:\Windows\System32\mstsc.exe
    ReportDescription=Stopped working
    ApplicationIdentity=00000000000000000000000000000000

  • Remote Desktop Connection not working

    I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.

    thebluemamba_24 wrote:
    Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
    If you read my previous post it said:
    "I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
    I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work?

  • Remote desktop connection for iphone?

    I am currently using my mac and remote desktop connection to access my work desktop. Can we do the same thing with the iphone? it would be really usefull
    thanks
    JF

    It would be a bit tough to navigate, but quite useful. I would suspect it would not be long after the SDK is released that we would see at the least VNC software.

  • Remote Desktop Connection stopped working

    I made a change to my Verizon TV and Internet package, downgrading from Ultimate HD to Extreme HD and from 35/35 to 25/25.  This morning, when I ran a speed test it showed the new speed.  I went out for a few hours, and when I returned, my internet connection was not working at all.
    I called Verizon's support number and, after talking to two different people, one who wanted to swap out my router, and one who wanted to send a tech to check out my ONT, they finally figured out the problem was with their configuration, not any of the hardware in my house, and got me running again at the correct speed.
    During the trouble shooting process, they had me do multiple soft and hard reboots of my router, they remotely rebooted it, and had me push the recessed reset button once, restoring it to factory defaults.  This led to problems with my wireless devices, so I loaded a configuration file to the router that I had thankfully saved some time prior to this problem, and everything seemed to be working properly.
    Then, I tried to open a remote desktop connection from one of my machines to another one, both on my internal home network, a connection that had worked flawlessly up until now, and it would not work.  Moreover, trying to ping the "remote" machine from the one trying to initiate the connection gets no reply, but pings are replied to in the other direction.  And, both machines can see and access each other's shared folders and files, and both can see each other in the network map in the networking and sharing control panel app.
    I never made any configuration changes to either machine during the trouble shooting process, but to be sure, I used system restore on both machines and took them back to restore points made yesterday, when everything was working.
    I am at a loss to understand what has gone wrong, and would appreciate any constructive and helpful suggestions as to how to remedy this situation.
    ps
    I am running two different web servers on the target machine, and am running stunnel on it to provide secure nntp connections to a news client that doesn't have that capability built in, and none of these servers are available from other machines.  Nothing seems to be getting through to the target pc except windows network sharing! 

    dslr595148 wrote:
    #1 In the router go to Advanced -> Universal Plug and Play OR to Advacned -> UPnP (what ever exist in your router).
    #2 If you do not have at least two special computers that support Universal Plug and Play (UPnP) where you can not define the ports that they use, turn off UPnP.
    A perfect example. At least two game consoles. Any two (Two Xboxes, two Playstations, One Xbox and one Playstation).
    #3 If you have at least two special computers that support UPnP where you can not define the ports that they use....
    Do you only use one at time or are there times when at least two are on?
    #4 In the router go to Advanced -> IP Address Distribution Or to Advanced -> Private LAN
    #5 What is the Starting and Ending IP Address, that is listed in there?
    We have two Xboxes and a Logitech Revue.  I have Windows Media Sharing enabled on three computers, and am also running a beta of Logitech Media Server on one.   It is possible that there are times when two or more streaming clients are in operation, but that is a very rare occasion.  Two of the computers, the ones I mention in my original post, are on almost continuously.
    In Advanced -> Universal Plug and Play, both Allow Other Network Users to Control Wireless Broadband Router's Network Features and Enable Automatic Cleanup of Old Unused UPnP Services are checked, and WAN Connection Publication: is set to Publish Only the Main WAN Connection.
    In Advanced -> IP Address Distribution, under Dynamic IP Range it says192.168.1.2 - 192.168.1.254.  However, in Advanced -> IP Address Distribution -> Connection List I have set all the lease types to Static, because I was having problems using the Verizon web page to access my set top boxes, particularly the MRDVR.  The Static IP addresses for the computers, game consoles, Bluray player etc. are in the range 192.168.1.2 - 192.168.1.12, and the set top boxes are at 192.168.1.100 & 192.168.1.101.
    One thing I did not mention in my original post is that I have two unmanaged gigabit ethernet switches in my home network.  There are two computers, the ones I mention in my original post, and the Logitech Revue plugged into one switch.  That switch plugs into another switch which also has one pc, an Xbox, and a Bluray player plugged into it, and that switch then plugs into one of the ports on my Verizon supplied Actiontec MI424-WR Rev C, firmware version 4.0.16.1.56.0.10.14.4.  All of the other ethernet ports on the router are unused.  In addition, we have a laptop, a notebook, another Xbox, and a Wii that connect through the Actiontec's wireless.
    I don't know if media streaming is still working and I don't really care if it is because we use it so seldomly.  It never worked consistently or to our satisfaction.  When we want to watch or listen to media from one computer on another, we copy it over the network from shared folders.  We have a Homegroup, to which all of the computers belong.  If we want to watch or listen to media on one of the game consoles, we copy it to a flash drive.  The Bluray player is only connected to the network for firmware updates and for discs with network enabled content.
    This same setup was operating before the problem developed, and I can't figure out what has changed to create the problem.  The router configuration file that I am using is from June of 2011, and I'm pretty sure that everything was working fine then, and don't recall making any changes to the router's configuration since then.

  • Remote Desktop Connection stop working after upgrade from 10.5.8 to 10.6.1

    I too could not connect to a W2K3 server with RDC 2.0.1 after upgrading from Mac OS X, 10.5.8 to 10.6/10.6.1. I have another Mac which is on 10.5.8 and connect fine with the same version of RDC 2.0.1 as well as other PC with Terminal Service Clients.
    There is no change on the server side. I have uninstalled and reinstalled RDC 2.0.1 several time and it did not resolve the issue. To rule out firewall/network, I tested with another remote desktop application called CoRD (for Mac) on the same laptop running SL 10.6.1 and it connected to the same W2K3 server fine.
    One thing that is worth mentioning (in my case), when it does not connect, RDC totally quit (not running anymore. Not minimize, no cannot connect error message, no little dot on the Dock for RDC, nothing) right after I put in the credential in. When looking at the log entries that are related to RDC in the Console application, I see the following
    machine 10.6.1. with RDC 2.0.1 (non-working)
    9/22/09 1:17:16 PM [0x0-0x3a03a].com.microsoft.rdc[468] objc[468]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . One of the two will be used. Which one is undefined.
    On the 10.5.8 machine with RDC 2.0.1 (working), I see the following entries
    9/22/09 1:13:23 PM [0x0-0x24f24f].com.microsoft.rdc[5502] objc[5502]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . Using implementation from /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL .
    9/22/09 1:13:39 PM Remote Desktop Connection[5502] * _NSAutoreleaseNoPool(): Object 0x16a25c20 of class NSCFArray autoreleased with no pool in place - just leaking
    Stack: (0x9277af4f 0x92687432 0x93062bf5 0x926ce0fb 0x9723dff5 0x9268d52c 0x92fd447a 0x92fd4753 0x92fd4a48 0x930375da 0x530bac 0x4831a2 0x483750 0x483c0b 0x47a811 0x4796ac 0x485dad 0x47d475 0x5099dc 0x574c70 0x4ade03 0x4ae65d 0x4ae6f7 0x4ac8dd 0x53260c 0x534187 0x4ae76a 0x4ae7d0 0x4ae88e 0x493925 0x4ae13d 0x533b1a 0x53da6c 0x94a48057 0x934b3155 0x934b3012)
    Any help would be appreciated

    Doing some more troubleshooting after my post above as I saw a couple of entries referencing Stop Light keep popping up in the log of the Console. I removed Stoplight and Cocoa Gesture (for good meausre) and RDC 2.0.1 started working. I think it is Stop Light which causes RDC stop working, but I don't have to time right now to put Cocoa Gesture back to confirm that. I might if I have the time or post here if you have Stop Light installed as well and removing it resolved the RDC issue for you.

  • When I am using remote desktop connection from PC1 to PC2 and if Firefox has opened before remote connection I will see only black screen in Firefox window on PC2. Os WinXP prof Sp3. If I run FF on PC2 remotely, FF works perfectly.

    I am using an integrated feature Remote Desktop connection on WinXP without any additional software. Connection through internal LAN, so speed is very fast.

    Hi,
    You can try to toggle the various options in the '''Experience''' tab of RD.

  • Remote Desktop Connection won't work from Leopard to Windows XP

    Hi, folks:
    I'm unable to connect to my work XP computer via my home iMac (Leopard 10.5.7) using Microsoft's Remote Desktop Connection for Mac. The XP settings are correct, I'm connected on my work network VPN, and I don't believe I have any router firewalls causing the problem --- the reason I know this is because I also have an MacBook running Tiger (10.4.11) and it has been connecting to my work PC without any problems. So, this must be a Leopard firewall setting?
    As far as that goes, on my iMac I've got Screen Sharing, Remote Login and Internet Sharing turned on. Again, work network VPN is on.
    I'm getting this error from Remote Desktop Connection:
    "The Mac cannot connect to the Windows-based computer
    This problem can occur if:
    - The Windows-based computer is not set up to accept remote connections
    - The Windows-based computer is not turned on
    - The Mac, or the Windows-based computer is experiencing network problems
    Try connecting to the Windows-based computer again, or contact your administrator"
    Anyone know of a fix? I'd greatly appreciate it!
    Thanks.

    What Firewall setting do you have on your Mac? Try setting it to allow all connections. At least as an experiment.
    Do you have any Proxies set in System Preferences -> Network -> Advanced -> Proxies? If yes, then is it possible that "Bypass" list is not covering the XP system.

  • Remote Desktop Connection no longer working

    Hi, I really hope someone can please help me.   I just switched from Comcast to FIOS and I can no longer remote desktop to work - so I'm not getting paid until I can get it fixed.
    The way that I was doing it before was to connect with a regular Microsoft VPN (I have Windows XP Professional), and then I would use Remote Desktop Connection to log into the work PC.  Since I switched to FIOS it no longer works on either my laptop with wireless or my desktop which is connected to the router. 
    The VPN seems to be connecting OK; it says it is and it is sending/receiving a small bit of data.  But when I open the the RDC and try to connect using the PC name it says that the computer cannot be found.  I tried to connect to the IP address of it (after connecting through the VPN) and then it says it's found but cannot connect.
    There is another location to which I log in using a Cisco VPN and then Remote Desktop - that still works just fine.  Nothing at work has changed; everyone else can log in with no problems, including everyone else with FIOS.
    I honestly have no ideas at all; this is not my area of expertise to say the least.  If anyone could help I would REALLY appreciate it!
    Thanks much!
    Solved!
    Go to Solution.

    It is a new Actiontec router. 
    I finally got it resolved; one of my coworkers suggested checking to make sure that the IP addresses were not in conflict, and they were.  So, if anyone else has this problem, what happened was that the new router was assigning IP addresses to my PC's at home in the 192.168.1.x range, which was also the server at work's IP address.
    So the really dumbed down version (for people like me!) is to open a command prompt on your desktop, run ipconfig /all, and then it will tell you your internal IP address.  (I was getting thrown off because the ROUTER'S IP address, which is the one you can look up online, was different).  If the PC's IP is almost the same as the server IP address, then you have to change the IP range on your router to something like 192.168.114.x.  There's directions if you google the router specs; I had to change it in three places on the router software; the router IP, the begin range and the end range.
    Thank you, jumpin68ny, for starting to help me.  Hopefully now this may help someone else!

Maybe you are looking for