Control alt delete from remote desktop connection through virtual pc windows xp on windows 7 professional

Ok this is an odd one but I am connecting to a server through a vpn which only works on windows xp so I ran a virtual pc instance to connect, and then did a remote desktop connection to the server (Windows server 2008). I need to be able to activate the
control-alt-delete combination on the server however, to change a password. ctrl + alt + del obviously goes back to my actual machine, and ctrl + alt + end acts on my virtual pc. Is there any way to push the command through to the remote server?

Hi Cooljoe,
Based on my understanding, local machine control-alt-delete key combination is control-alt-delete.
Virtual PC's control-alt-delete key combination is Right Alt - Delete.
Remote Destop session's control-alt-delete key combination is ctrl + alt +
end.
There should be no conflicts between them.
Regards,
Wilson Jia 
This posting is provided "AS IS" with no warranties, and confers no rights. 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. ”

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." 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 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.

  • Unable to start remote desktop connection broker

    somehow I could no longer start remote desktop connection broker service. I noticed that Windows image acquisition (WIA) service could be started manually and then it stopped by itself. I am not sure if they are related or not. From event viewer, I see some
    errors as follows (may be related):
    event 485 ESENT
    tssdis (2916) An attempt to delete the file "C:\windows\system32\edbtmp.log" filed with system error 5 (0x00000005):"Access is denied." The delete file operation will fail with error- 1032 (0xfffffbf8).
    Any clue or suggestion where I can look into?
    Thank you very much!!!!!

    Hi,
    Thank you for your posting in Windows Server Forum.
    register the below files using regsvr32
    regsvr32 %systemroot%\system32\wuapi.dll 
    regsvr32 %systemroot%\system32\wuaueng.dll 
    regsvr32 %systemroot%\system32\wuaueng1.dll 
    regsvr32 %systemroot%\system32\wucltui.dll 
    regsvr32 %systemroot%\system32\wups.dll 
    regsvr32 %systemroot%\system32\wups2.dll 
    regsvr32 %systemroot%\system32\wuweb.dll 
    regsvr32 %systemroot%\system32\softpub.dll
    In addition, also Try to disable UAC for your account and reboot, this might help to resolve your issue.
    Source:
    esent 485 event wuaueng.dll
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/27cd64d0-7ec7-4732-a2ac-4c36a0513690/esent-485-event-wuauengdll?forum=winservergen
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • 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 manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

    remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
    does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
    or what's the problem,
    Mahmoud Sabry IT System Engineer

    this issue maybe will be fix by latest version, we still waiting for it
    maybe your issue can be fix using this methods
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
    http://shawn.meunier.com/?p=1#comment-43

  • Remote Desktop Connection with WRT54G from Novice

    Well, I’m usually pretty good at using Google and forums to eventually figure out how to fix my problem but this one absolutely has me stumped and I’m hoping someone out there has an answer for me. For the record, I have probably a beginner/intermediate knowledge of computers so if you know the answer to my problem, try to explain it simply! ****TO ANYONE WHO TAKES THE TIME TO READ THIS THING AND CAN OFFER SOME ADVICE-THANK YOU!!!!***
    THE PROBLEM
    I would like to be able to use Remote Desktop to log into either of my home computers from basically any computer on the internet.
    THE SETUP
    I have two computers, whose names are LAPTOP and DESKTOP that are both running Windows Vista Ultimate. Both of the computers are connected to a Linksys WRt54G Router ; one wired, the other wirelessly. The Linksys router is then connected to a Westell DSL Modem that connects to AT&T’s internet service.
    SETTINGS
    My DSL service only provides me with a dynamic IP address so I signed up with no-ip.com. Through that site, I bought a domain name and downloaded their small program that runs in the background of my desktop computer. The program checks what my IP address is every couple of seconds and if it changes, it notifies their server so that anyone who types in my domain name is directed to the new IP address.
    ROUTER (Firmware 4.20.6)
    Basic Setup Page: The Router Name is just the model number, the Server Name is my DSL provider and the Domain Name is the name I chose and registered with No-IP.com. (www.mydomainname.com, for example.) DHCP Server is ENABLED. DDNS Service is DISABLED. Under Advanced  Routing, it is set in GATEWAY mode.
    Security Page: Firewall Protection is ENABLED. Block Anonymous Internet Requests is NOT checked. Filter Multicast, Filter Internet NAT Redirection and Filter IDENT ARE checked.
    Applications and Gaming Page: I chose two port numbers, one for each computer that I want to connect to. On the first line, I have Application: RDP, Port Range: 49200 to 49200, Protocol: Both, IP Address (The IP address of the computer I want to connect to) and the Enable box IS checked. [I did the same thing with the second line for the other computer, but with a different port number and that computer’s IP address)
    Administration Page: Access Server is HTTP, Wireless Access Web is ENABLED, Remote Management is ENABLED through Port 8080, and UPnP is ENABLED.
    WINDOWS VISTA SETTINGS
    First, I went to the Remote Desktop Settings of the target computer and ENABLED Remote Desktop Connection and allowed computers running any version of Windows. I also confirmed that the box labeled “Allow This Computer To Be Controlled Remotely” WAS checked. I then made sure that I had a user name, it had a password associated and that it had Administrator priveledges. I went back to the Remote Connections screen and added the user name as being allowed to connect. (I think this is redundant since it’s both the owner of the computer and has Administrator Status.)
    Next, per Randomly Googled Internet Advice, I went into the registry and changed the port number that Remote Desktop listens for incoming connections to Port 49200 to match the router settings. [Registry Entry that I modified was: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
    Finally, I went to the Windows Firewall and Added (opened) port 49200 for use as a Remote Connection. I kept the protocol as TCP and confirmed the scope was set for Any Computer.
    CURRENT STATUS
    If I go to Explorer and enter my IP address with a colon and the specify port 8080, I can get the login screen for the router. Same thing happens if I just enter my domain name and port 8080. However, if I switch the 8080 port and use one of the ports I chose (49200), it cannot connect, either using the Public IP address or the domain name. (I’m trying to connect using a wireless card and not connected to my local network so I know it’s the same as if I was anywhere else.)
    I’m not sure why it won’t let me connect; it feels like the router will not allow the connection to pass through it to the port I’m asking it to forward to. I’m guessing someone out there who took the time to read it is shaking their head at all the information I provided and knows the one dumb thing I missed!
    Thanks again!

    I'm attempting to do the same thing with my home network. the only differences are that i have cable internet from comcast and i'm running vista business. my router is the wrt54gs. i'm assuming that the web page is similar for adjustmants. To be honest i cannot figure out how to do a remote destop too. so i went to www.logmein.com and installed the program. once installed to to every computer you want to have access too and log into the website. then click on the add computer icom. full control app sharing etc... even better when you connect you have the option to deactivate the local host mouse and screen to prevent anyone seeing what your doing.
    If you resolve the router issue would you let me know. plz thanks
    Forest

  • Problem Establishing Remote Desktop Connection from Win 7 64Bit

    I just got a new Lenovo laptop running Windows 7 Pro 64 Bit with Service Pack 1. I have installed all Win 7 Updates.
    When I try to connect to other Windows 7 Ultimate (32 bit) desktops through Remote Desktop Connection over my LAN, I get the following error:
    "An authentication error has occurred. The requested security package does not exist"
    I can connect to a Windows Small Business Server 2003 32 bit server from the laptop without problem.
    All machines are members of the same Windows domain.
    The Windows 7 machines I am trying to connect to can connect to each other without issue. NLA is set as not required on each of the desktops, though I have tried turning the NLA setting on, and received the same error.
    I have even tried running the 32 bit version of mstsc.exe and disabling the 64 bit version as discussed here:
    http://www.davidmoore.info/2009/12/02/running-32-bit-remote-desktop-connection-on-windows-64-bit/
    This had no effect either.

    Hi,
    Based on my research, please check whether the value of HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages is
    kerberos
    msv1_0
    schannel
    wdigest
    tspkg
    pku2u
    If not, please correct it and see how it works.
    Note: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For
    more information about how to back up and restore the registry, please refer to
    How to back up and restore the registry in Windows.
    Hope this helps.
    Jeremy Wu
    TechNet Community Support

  • Remote desktop connection from windows computer to TC

    hi all,
    what I have: I have a TC 2TB, bought it three months ago.
    what I did: I have set it up at home. Using as base station for all my devices, iphone 4, ipad 2, macbook air and also other laptop. My TC is connected to ADSL modem with an ethernet cable (as expected). with port forwarding option of ADSL modem (in NAT Properties), I managed to forward any connection to TC. I have a static IP by the way.
    what I can do: from work or anywhere else other than my home network, I can connect to my static IP (via "Connect to Server" option in any mac device), it pops up a user name and password window, I login with my TC user name and decive password. In an instant my TC disk is mounted on my desktop, and I can reach all my files in it as if it is an external hard disk.
    what I cannot do: from a windows computer outside my network, I cannot connect to TC. I try to do this through "Remote Desktop Connection". Is this possible? If so how? Is this a problem related to network connection or TC settings?
    aakibar

    You cannot remote desktop into a TC..
    In fact you cannot remote access a TC from windows.. sorry.. but SMB protocol is blocked on the internet.. there are work arounds but no security.. don't do it.
    The only other protocol the TC offers is AFP.. there is no AFP file access software available for windows. You need to use a Mac.
    The best alternative is vpn.. replace your current adsl modem router with a vpn one.. eg draytek.. then you can access your home network. Since I presume when you say you have static ip you mean public IP then vpn is easy (well once setup it is).. reliable and secure.

  • The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

    When I try to install Connection Broker on a Windows 2012 R2 Server in a Windows 2003 domain I get this error:
    The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
    Pooled virtual desktop collection name: NULL
    Error: Logon to the database failed.
    I have added both the Connection Broker server and the 2 remote desktop servers (also Windows 2012 R2 Servers) to the "Windows Authorization Access Group" in the domain according to this: http://support.microsoft.com/kb/331951
    But it still does not work :-(
    I keep getting same error....
    Any idea what I might be missing ?

    Hi,
    Thank you for posting in Windows Server Forum.
    Firstly please let us know by which method you have setup RDS role. You can have more advantage and feature when you will install with Standard deployment instead of Quick start deployment. So if you have setup with quick start option then you can try installing
    with standard type and check the result.
    In addition, please check SQL server database is properly configured for RDS server. Also check that domain controller properly communicates. Kindly go through below thread for more information.
    Server 2012 RDS - Remote
    Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • 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 to Windows 8 PC from other computers crashing

    Hi all.
    Was hoping someone would be able to help me with an issue I'm having.
    I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
    never will. The computer has a single user profile that has full administrator rights.
    I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me. 
    The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
    crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
    the connection or do anything. I have to restart the computer from then to be able to use it again.
    I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
    Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
    I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
    to continue using it. Dead end there, it seems.
    The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
    done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck. 
    If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
    you think I can provide anything.
    Thanks in advance!
    rugbyreff

    The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
    in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
    Brandon
    Windows Outreach Team- IT Pro
    The Springboard Series on TechNet
    Hi Brandon
    Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
    this still hasn't helped.
    If you have any other ideas I'd be very glad to hear them!
    rrugbyreff
    "If it's worth doing, it's worth overdoing" -- MythBusters

  • Remote Desktop Connection Times Out With "Can't Connect" From One Specific Computer Only

    This is an odd one... I manage several servers from this computer. This particular server, 2012 Essentials, won't allow for remote desktop connections to either the server or attached workstations. I can get into the server's remote web page but when I
    attempt a remote desktop connection, it hangs on "Initiating remote connection..." and then times out with the error response that remote desktop can't connect. But... if I attempt the same connections from any other computer, I am able to get in
    and utilize remote desktop. Does this mean that there is a certificate issue with the computer unable to connect and if so, how does one remedy this? Or is it some other issue? I've attempted everything within my technical ability to no avail. Any suggestions
    are greatly appreciated.

    Hi,
    Before going further, would you please let me know the RDC version that used in the problematic computer? Was it the same with other computers?
    Please temporarily disable firewall and then check if this issue can be solved. Based on your current description, it’s hard to say the root reason of this issue.
    So, I suggest that you should check relevant log files and get some clues. It will help us to narrow down and solve your issue.
    Hope this helps.
    Best regards,
    Justin Gu

  • 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.

Maybe you are looking for