UNSOLVED

czqcq9

updated

19 years ago

C

czqcq9

2 Posts

0

6631

July 18th, 2007 17:00

Remote Desktop on Vista Home close with DEP error

Trying to connect to my office PC running XP SP2 with Remote desktop from Vista Home Primium. I am able to login, but after a while, it was closed with a DEP error - DATA Execution Prevention. The the Remote Desktop was never be able to get up again until the system was reboot, then crashed again..
 
Thanks
Alex
  • mombodog

    2 Intern

    12735 Posts

    178

    0

    Posted July 18th, 2007 23:00

    Change the DEP settings in Vista, in the second window I posted, change the setting to the second radio button, reboot, then add the remote desktop program to the list with the "add" button, you may have to add other programs you use to the list as well, if you get the same error message for them. The only other solution is to turn DEP off in the bios, not suggested to do this.
     
     
     
     
     
     
     


    Message Edited by mombodog on 07-18-2007 07:50 PM

    Message Edited by mombodog on 07-18-2007 07:53 PM
  • mombodog

    2 Intern

    12735 Posts

    178

    0

    Posted July 19th, 2007 00:00

    I may have another solution  http://blogs.msdn.com/ts/archive/2006/11/29/remote-desktop-connection-terminal-services-client-6-0-for-windows-xp-and-windows-server-2003-english-only-released.aspx   scroll down to almost the bottom and read the Post by Bart van de Beek , he shows how to use a batch to get around this error.
     
     
    "people connecting to 2000/2003/XP should use RDC5, NOT 6. If you have 6, revert back to 5. There's not much benefit using RDC6 to connect to 2000/2003/XP anyway. Problem is just with people on Vista, they cant revert to 5. So connecting Vista to 2003 will give you these problems. To get rid of it once and for all, I've written a batch. Copy/paste this into a textfile, name it rdc.cmd, put it in windows-folder, then create a shortcut having this as commandline:"
     
     
    "To get rid of it once and for all, I've written a batch. Copy/paste this into a textfile, name it rdc.cmd, put it in windows-folder, then create a shortcut having this as commandline:

    cmd /c rdc

    This batch simply strips whatever it otherwise prepends to the username. I admit, it's just a workaround, but at least it works until microsoft releases the next version which probably will have more logic added to detect better what the client is connecting to, and which also fixes the USernameHint-bug (which really is a bug in the 6.0 client). Hope this will help most people having this issue here.

    This batch leaves all other options and features intact, so saving credentials, choosing not to save them, etc. all still works. This batch only strips every time you use it to logon, nothing more. Be advised that in a multi TS environment this batch can lead to other problems, be aware of this!

    The batch:

    @echo off

    if %1x==x goto help

    for /f "usebackq tokens=2 delims=: " %%i in ('echo %1') do set a=%%i

    for /F "usebackq delims=" %%i IN (`reg query "HKCU\Software\Microsoft\Terminal Server Client\UsernameHint" /v %a%`) do set t=%%i

    for %%i in (%t%) do set n=%%i

    set name=%n%

    if %n%==REG_SZ set name=

    if %n%==UsernameHint set name=

    if not %name%x==x for /f "usebackq tokens=2 delims=\" %%i in ('echo %name%') do set name=%%i

    reg add "HKCU\Software\Microsoft\Terminal Server Client\UsernameHint" /v %a% /d "%name%" /f

    start mstsc /f /v:%1

    exit

    :help

    echo RDC FQDN/IP/DOMAIN to connect to

    echo RDC replaces the annoying crediantial dialog of Remote Desktop Connection 6.0

    echo     asking and setting FQDN\Username as default

    echo     It does this by stripping the FQDN/IP/DOMAIN-part,leaving only the username

    pause



    Message Edited by mombodog on 07-18-2007 08:06 PM

    Message Edited by mombodog on 07-18-2007 08:06 PM