How to: enable remote desktop on Windows Vista Home Premium SP1 (x64 & x86) Edition

Update 6.8.09:
In light of Vista SP2, some files have changed. Please see this post.

For the impatient:
Don’t wanna read a lot of babble? Download the file, read the readme.txt file, and you’re done.


I just got a new Dell Dimension XPS M1330, but I was really bummed to find that the Version of Vista it had—Windows Vista Home Premium SP1 (x64)—didn’t allow incoming remote desktop connections. Lame! Fortunately, there’s an easy fix. Read on….

What to do:
Download this zip file and extract it wherever you want; then choose either the x64 or the x86 folder depending on if your version of Vista is 32-bit or 64-bit. Then, you will notice there are three batch files; simply run the one that corresponds to your version of Vista (there are batch files for Business and Ultimate as well). When you run the batch file, be sure to right-click and choose “Run as Administrator” or it won’t work.

Note: If you do not have Vista SP1 installed on your machine, I’m not sure if this will work or not. I doubt it.

Helpful tip
If you have two or more computers on your network accepting remote desktop connections, and you have a hardware firewall that is forwarding ports, you’ll need to change the listening port(s) on the additional machine(s) and then forward them appropriately.

Legal Disclaimer added 1.11.09
If you use this tool, you should have a paid license for a version of Windows Vista that contains remote desktop officially; and you’re not currently using it. Otherwise this hack might be illegal (i.e., you’re getting features you didn’t pay for). I’m not really sure—just throwing this out there in case (for example, I have a paid version of Vista Ultimate x64 that I don’t have installed on anything right now).

Update added 2.09.08
John Wolf left a comment addressing something a lot of people have been asking about—the issue of taking over an existing session vs. creating a new session each time. He said:

I’ve been fishing to solve the issue of it creating a new session when you RDP to a Vista box. After digging through the thread on the green button, I found a registry setting that remedies this issue. There’s a key HKLM\System\CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser, that defaults to 0 which means create multiple sessions per user. Simply setting this to 1 will give you what you want. I just verified this and it works like a charm!

His comment is #36 below. Thanks John for finding this fix—I think it answers a lot of questions!

By the way, did you find this article through Google? I also encourage you to come back to my home page regularly; I’m constantly adding new tech tips to this site. Thanks for stopping by.

Andrew Block

I (Andrew Block) am the Director of Analytics and Insights for MSP-C, an awesome brand journalism company in Minneapolis, MN. Insights are everywhere - and this blog explores that premise. One part geek and one part analyst, I like to blog about techy and insightful things. Or insightful techy things...or....

Andrew Block wrote 121 posts

Post navigation

  • Ray

    I used the Premium batch file on a Vista HomeP SP2 without making any change between the SP1 and SP2 folders —- worked great the first install…very slick! Thanks Andrew Block!!!

  • Steve

    http://www.ammyy.com/ is something you would need for remote connection. Simple and quick tool.

  • diyd2013

    My Medion, Vista Home P, Laptop has very dodgy graphics (display and any output refuses to work at all for long periods) so remote acccess is a life saver. SP2 version didn’t work but SP1 version is fine. Problem is I have several users on the laptop and I can only remote in to the account I ran the hack from. Other accounts give a “Not in Remote Desktop User Group” error and I can find no way add users this because, of course, there is no Remote Desktop dialogue under Computer Management. Is there a way to do this directly in the registry? Or will it be OK to run the hack from within every user account?
    Any ideas folks?

  • Raed

    solution for home premium 32 bit is that we use the sp1 termsrv.dll and paste it in the folder of sp2, run as administrator and it works perfectly.

    solution for home premium 32 bit is that we use the sp1 termsrv.dll and paste it in the folder of sp2, run as administrator and it works perfectly.

    The fault I had was that windows asks me username and password and the window disappeared.

    the solution is in the comments you have written above

  • http://gravatar.com/diyd2013 diyd2013

    For the record and to possibly save others hours (if not days!) of time, I found it necessary to revert to the SP1 version to get this to work on my HP AMD based 32bit machine with Vista Home Premium. The SP2 version installs fine, listens as it should and appears to logon but no desktop screen appears and nothing I could find or do could resolve it. (Just like mac back in jan 2007!) The SP1 version not only works but requires no logon password (just a username) unless there is already one associated with the user account… and allows multiple logons, including those to the same account where remote and local screens operate simultaneously and independently of each other. (Haven’t checked same file locking issues however.)
    Ican remote in from XP-PRO, Vista Home P and Win 7 Home P.
    Regards,
    diyd

  • Sunil Battu

    awesome, worked like.
    thanks Adrew!!

  • debmalya

    This is documented here “http://support.microsoft.com/kb/954369″ but need a work around for home premium.

  • debmalya

    Why do I keep getting this “the requested session access is denied” ?
    When I connect as an administrator it works okay.

  • http://abbottnet.com Chris Abbott

    Flawless thanks

  • Stan

    I ran as admin, tried the hacks for sp1 and sp2 and both together and one after the other. Cant get it to work. Only remote assistance shows up on system properties

  • Stan

    I know this thread is really old but I am still trying to get some help. I resurrected an old vista lappie and want to be able to use RDP. I am somewhat of an amateur but I followed all the instructions with my machine running vista home premium sp1 with no luck. I then upgraded to sp2 hoping that would help but no luck. The command prompt listens for the port and all and I have added it to the firewall but no matter what I do I cant get the remote desktop option to appear. I really need help please

  • http://andrewblock.net Andrew Block

    glxyds – I am pretty sure this stuff all needs elevated access. If there is an admin account somewhere on the machine, you could SHIFT-RIGHT CLICK on the batch file and choose “Run as different user” and enter the admin creds. That’s just a guess as I am not 100% sure.

  • http://gravatar.com/glxyds glxyds

    Andrew, do you know of anyway to get this working with a standard user account?

  • http://andrewblock.net Andrew Block

    Hi Ada – glad it worked for you.

  • Ada

    thanks very very much i am working as consultant and this guys set me up with a vista home edition and i need to administrate remote pcs!! thanks again

  • Kyle

    Hey Andrew, Thanks for the hack.

    I am new to remote desktop, I just bought a Windows Virtual Dedicated Server so I could access it remotely like a second computer to run programs to save RAM on my PC.

    Anyway then I find out that Visa Home does not have remote access enabled, so I have been going crazy trying to find a solution.

    I found your hack, I did what you said in the instructions, but I have no idea if I did it right or if it’s working, or if it is working how to I start using it?

    This is what I get:

    Source Folder is C:\Users\Kyle\Downloads\remotedesktop_vista_sp1\rdp_vista_sp1\R
    DP Vista x86 SP1\
    Taking ownership of C:\Windows\System32\termsrv.dll

    SUCCESS: The file (or folder): “C:\Windows\System32\termsrv.dll” now owned by th
    e administrators group.
    Granting Administrators rights
    processed file: C:\Windows\System32\termsrv.dll
    Successfully processed 1 files; Failed processing 0 files
    Stopping Terminal Services
    The Terminal Services service is stopping.
    The Terminal Services service was stopped successfully.

    1 file(s) copied.
    Copying C:\Users\Kyle\Downloads\remotedesktop_vista_sp1\rdp_vista_sp1\RDP Vista
    x86 SP1\termsrv.dll to C:\Windows\System32\
    1 file(s) copied.
    Copying C:\Users\Kyle\Downloads\remotedesktop_vista_sp1\rdp_vista_sp1\RDP Vista
    x86 SP1\rdpclip.exe to C:\Windows\System32\
    1 file(s) copied.
    Importing Registry Keys
    Enabling RDP
    The operation completed successfully.
    Setting fSingleSessionPerUser to 0
    The operation completed successfully.
    Setting LimitBlankPasswordUser to 0
    The operation completed successfully.
    Configuring Remote Desktop in Windows Firewall
    Ok.

    Starting Terminal Services
    The Terminal Services service is starting.
    The Terminal Services service was started successfully.

    Pausing 5 seconds to give service time to start listening
    Checking if Service is listening on port 3389
    TCP 0.0.0.0:3389 Kyle-PC:0 LISTENING
    TCP [::]:3389 Kyle-PC:0 LISTENING
    Service is listening
    Done
    Press any key to continue . . .

    I press any key to continue, the screen goes away and nothing else happens, what am I suppose to do now?

    Thanks in advance for your help.

  • http://www.motorcyclenotebook.com Don

    Andrew, thanks very much! March 2012 and I’m finally getting around to converting an old box to a home network depository (we’ve got three other computers in the house, and it’ll be nice to be able to access stuff without having to turn one on and blah blah blah) I successfully remoted into this ol’ computer on a newer W7 computer. Thanks very much!

  • Asbjorn

    Hi first if all thanks very much for this Hack looks like it working, on my windows vista home premium, however when im trying to connect from my windows 7 pr, it comes up asking me for login details user name and password, i made an ekstra administrator user on the vista machine have tried ot login via remote desktop using these details, however all that heppes it that i get a message that the certificate is not approved, i then clik ignore and connect to remote computer, however noting happens after this any suggestions?

  • Rick

    Awesome! I’m migrating off a Vista machine (finally!) to a new Win 7 system. Not having RDP access to my old system was like Vista’s last way of screwing me. This worked perfectly, Thanks!

  • ning

    Great job! Thank you very much!

  • Tom N

    Running Vista Premium x86 SP2 (All Updates)..connect reports
    Failed to connect when trying from Vista Home Basic box or Windows 7 Ultimate box. RDP from a “Vista Premium” box works fine, Have never got it to work going to a Vista box of any flavor…Any Thoughts…I’m a Computer/Network Specialist. Been doing this stuff for 25yrs.

  • http://www.techfactor.org/ Set Out of Office Outlook 2010

    A person essentially assist to make severely articles I might state. This is the very first time I frequented your website page and to this point? I surprised with the research you made to make this particular post amazing. Wonderful job!

  • http://belkinrouterip.org Belkin Router Ip

    Hi there, just wanted to say, I liked this post. It was inspiring. Keep on posting!

  • http://andrewblock.net Andrew Block

    I’ve not seen a fix to the sound problem, although I have not looked into it in a while.

  • Arnor Baldvinsson

    Hi,

    I tried this on my Vista 32bit Home Premium laptop and my Vista 64bit Home Premium cannot see it. Do I need to reboot either or both machines before this takes effect? The zip went through without problems and tells it is listening on the port. I don’t have FW on the computers, but I do have a router – do I need to set up port forwarding on it (I’m only using this on my LAN for now)

    Best regards,

  • Spamme

    Somebody has solved the problem of the sound? When I remote desktop my laptop (vista 32bit home premium) I get always the same message “No audio output device is installed” on the volume icon in the task bar.

  • http://andrewblock.net Andrew Block

    Thanks, Gene. Happy computing. :)

  • http://andrewblock.net Andrew Block

    Hey BubbaRay,

    Thanks for the comment. Microsoft really needs to cool it on the different flavors of windows. They need to go back to home and pro, like the good old days.

  • BubbaRay

    Well I’ll be, after 6 hours of screwing around with this problem, endlessly editing other site’s .BAT files, this one came alive right out of the box! Kudos to you. And a big thumbs down to greedy Bill Gates and MS for removing this functionality that was free in XP. Their attempt to squeeze another dollar out of Vista Home Premium owners for an upgrade is unconscionable. Yessir, Vista — the shining vision of endless zero day bug fixes out there on the horizon.

    Now please make sure your site is listed #1 in Google searches. :-)

  • Gene Loriot

    HEY!!! YOU ROCK. This is simply perfect. I have an HP Slimline, which is unfortunately very proprietary. The upgrade to Ultra, or whatever Microsoft’s solution just is unusable. BUT your solution got me where I needed, with any issues. PERFECT…. Did I mention that you rock???

    Thanks again
    Gene Loriot

  • jshah

    Hi,
    I have vista home premimum SP2 and i tried your solution but it won’t work for me. Are these files specifically for SP1? how can i make it work to SP2? i really need Remote Desktop connection from my home laptop (Vista Home Premium) to my work PC (Window 7).
    Please some one help me..and guide me..i really appreciate it.

  • http://andrewblock.net Andrew Block

    Josh – thanks for posting.

  • Josh

    I just wanted to thank you for posting all of this information. Your hard work was well received when I found your site and finally got RDP working on Vista. In case anyone else needs this info, I am running Vista Home Premium SP2 x64. I extracted the x64 folder from the SP2 zip file and ran the Business.bat. I then took other posters’ advice and did the same steps for SP1 overwriting the SP2 and now it works great. (I also changed the fSingleSessionPerUser to 1.) I can now access my PC from other PC’s and my iPhone and iPad!

  • Samy

    Hi Andrew,

    I have been trying to work with RDP from my vista home premium to my office XP professional.

    I installed the hack as you described and changed the port and everything but final command “port is not listening” keeps on coming back. i checked it via netstat -a, the port is not listening. I tried all the solutions given in here. Please help me.

  • http://andrewblock.net Andrew Block

    Bobby – clarify please. You’re not giving me much to work with. :)

  • Bobby

    doesnt work for sp2 home premium. help!

  • http://andrewblock.net Andrew Block

    @Brendan,

    Mac & PC, together at last…LOL.

  • http://andrewblock.net Andrew Block

    @travis,

    Not 100% sure, but see my comment to Charlie.

  • http://andrewblock.net Andrew Block

    @charlie,

    I saw you forwarded the port, but did you open 3389 in the windows firewall? Also – any chance antivirus software is messing with things?

  • Brendan

    Hey Andrew, just wanted to say thanks for this – now remoting into my vista-pc from my new OSX Mac, great! (no sound is the only issue)… Cheers.

  • travis

    i have the same problem as Charlie. Host has closed the session, almost immediately after it negotiates the connection.
    this is on a windows 7 Home premium box and accessing with iphone.
    when trying to access with xp box, it acts like i didnt even hit connect, it grays out then comes back and ready to be hit again.
    please help.

  • charlie

    Sorry, forgot to mention this was with Vista Premium SP2 running the SP2 service pack.

    Wrong area, I know.

  • charlie

    Installed and ran just fine, was “Listening”. Port forwarded 3389. Verified open port. Tried connecting with RDP on my iPhone. No luck. “Host has closed the session”.

    Tried local IP, public IP, and DNS server. Same message for all.

  • HARRY EVANS

    you are a star mate worked a treat

  • http://andrewblock.net Andrew Block

    @zort,

    That’s a good point–thanks for bringing that up. So if the hack fails, it’s good to check the permissions on termsrv.dll. Good call!

  • http://andrewblock.net Andrew Block

    @Chris,

    What do you mean by “reverse the process”? Do you mean remove the hack?

    For your second question, this should work over the Internet if you have port forwarding properly set up on your router.

  • http://www.weblogic.pl zort

    I’ve got it solved…
    First of all sorry for my english :)
    I couldn’t run RD on my Vista HP SP2 64bit using your solution. I couldn’t because administrators had no rights to replace termsrv.dll. I had to grant administrators full control over this file (they could only read and use the file), and then replace it (using the one from SP1 of course). After that it works perfectly :)

  • Chris

    How does one reverse the process? And does this only work among one’s own network or does it work over the internet?

  • http://economic-forecast.blogspot.com Patrick Salbaing

    Thank you so much Andrew … was a breeze to install on Vita home premium SP2

  • http://andrewblock.net Andrew Block

    @riley,

    Awesome!

  • riley

    I installed SP1 over SP2 and now it works.

  • riley

    I’ve got the exact same problem as neel. I get a certificate back from my Vista box if I tell it to warn me, but when the connection goes through it seems to just end instantly. And I’m back to the login prompt.

  • neel

    I followed these instructions word for word. but this is where I am stuck now: Trying to access Vista 32bit home premium from XP in a home network. When I netstat -a:find “3389” on Vista I see two entries like:
    [0.0.0.0]:3389
    [..]:3389

    I can, telnet from xp box to these ports.

    But when I use the rdp client from xp box, it never connects, the connect button goes grey for a while and come back, but I never get the vista screen. No error is thrown anywhere either. What can I do now?

  • http://andrewblock.net Andrew Block

    @Edwin G,

    Sweet. That sounds like you went through quite a process. Great troubleshooting!

  • http://andrewblock.net Andrew Block

    @VP,

    Did you change the port # from the default of 3389? If so, are you including it when you type the IP address into remote desktop? Like -> xx.xx.xx.xxx:3391

  • Edwin G

    WINDOWS VISTA HOME PREMIUM X86
    I had the same problem, i was unable to get terminal service to replace the file because it was already running, after reading how (TOM) got his to work, i tried looking for that software whoslockingit, but no luck finding it. I then rebooted my computer in safe mode (NO NETWORKING). I then ran the patch as administrator, noticed that the service was now started but it was unable to test because i was on safe mode, reboot the pc in normal mode and that was it. success
    Thanks for all comments

  • VP

    Thanks Andrew for such nice article. it helped me a lot to setup my RDP on vista home premium. Though i have some issues accessing this hacked RDP from outside of home network. I did have proper port forwarding in my router & i am accessing using my public ip address. In fact i can access RDP for my other machine with vista business on it. but when i changed the port forwarding to my vista home machine the RDP errors out with not able to connect to remote system. Any help will be appreciated.

  • http://andrewblock.net Andrew Block

    @Howie,

    That’s great! Aaah, the wonders of copy+paste. :)

  • http://andrewblock.net Andrew Block

    I am not completely sure, so someone can maybe help me answer this question: does port forwarding have to be enabled on the router on a local network for remote desktop to work? I wouldn’t think so, but I’m not 100% sure either.

  • Chris

    private home network to start with. Once i can get that working then I will set up my router port forwarding.

  • http://andrewblock.net Andrew Block

    Hey Chris…maybe a stupid question, but are you trying to connect over the Internet or over your private, home network?

  • Chris

    Andrew,
    I’m running Vista x64 Premium on my laptop. I ran the proper batch file with no error messages, netstat says that terminal services is listening on port 3389, but i cannot connect from my XP laptop (or any other pc for that matter). It consistently gives me the typical network error it gave when terminal services was not running. I have disabled all firewalls and the two laptops can definitely ‘see’ each other on the network. Do you have any ideas?

  • Howie

    Andrew, you’re a genius, I tried CRTL+C and am currently copying my file! :-)

  • http://andrewblock.net Andrew Block

    @ Dave M,

    Cool.

    @Mike,

    Sorry but I’m not so sure on this one. I think if you browse through the comments some other people have already discussed this issue.

  • http://andrewblock.net Andrew Block

    @Howie,

    Did you try CTRL+C on a file on the host machine, and CTRL+V in a directory on the target computer? I am not sure if the clipboard is shared by default or not.

    There is a registry DWORD value located at HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp called ‘fDisableClip’. Make sure that is set to ‘0’ and then just try copying and pasting between computers (this needs to be set on the computer you are connecting FROM).

  • Howie

    Update, I got RDP working after trying a few more things from this page, but I can’t seem to see my local drives/resources no matter what I try… how can I copy files off the computer I’m remoted into?

  • Howie

    Hi Andrew, thanks for taking the time to put this site together… I would love your advice on this, I just bought a Vista Home Premium SP1 64-bit machine, and I used your packages near the top of the page, which appeared to work at the command prompt, but I still can’t successfully RDP to this new machine… I know port 3389 is open, I know terminal services are running, and I ran your batch file as an admin. I’m not sure why your zips don’t seem to include termsrv64.dll in the x64 folders, and I found a link from another site to download termsrv64.dll from rapidshare, but I guess I’m not quite sure how to use it, which folder to put it in, what permissions needed to be changed, or if I even need it since your zips don’t include it. If you could give me a link to the current x64 files for Vista Home Premium SP1, I would be so thankful.

  • Dave M

    Thanks worked a treat

  • Mike

    Does anyone know how to allow a non administrator to connect?Obviously since there is no Remote Desktop Users group in Vista HP, I can’t just add the non-admin account to the RDU group. Any other ideas?

  • DB

    Many thanks! You saved me no end of hassle.

    I ran it first time and it didn’t work, but then realized that it was my own fault because I hadn’t run it as administrator (as your instructions said to) … anyway, worked fine for me as soon as I ran it second time on Vista Home Premium 64 bit.

  • http://andrewblock.net Andrew Block

    Jose,

    You definitely need to port forward. What is the make & model of your router?

  • Jose

    I need help … i have read this posts like 20 times so far… and can’t find the answer, I applied the hack in vista home premium 64 bits and the RD works internally, I use the IP provided by the router (192.168.2.2) but i can’t figure out how to connect from the internet in another location, I disabled the antivirus (kaspersky) and added the port to the windows firewall … but dont know what they talk about when they say forward the ports in the router, do i need to do that if I am planning to apply the RD in only one computer ? please help me out with this…
    thanks

  • Howard

    Thanks to Andrew and all those that have commented. I have Vista Home Premium x64 with SP2. I tried using the SP2 package as is, and it seemed to connect as it asked for authentication, but then it mmediately stopped. As Mike suggesed on 6/1, I copied the termserv.dll fom the SP1 package and overwrote the SP2 version, and then reran the BAT file. Everything just orks now. I can remote desktop in without an issue.

    You have made my day. I have been very nhappy since I got this machine, and now I can use it as intended.

  • Tony_wh

    Thank you, thank you, thank you.

  • http://andrewblock.net Andrew Block

    Hey Jake,

    Not sure on your remote desktop audio bug, but I would suggest using something besides remote desktop to share files over the Web. Maybe give something like Weezo a try? http://itmanagement.earthweb.com/netsys/article.php/3845281/Share-Files-Over-the-Web-with-Weezo.htm

    Keep in mind you have to open up port 80 on a machine, so that opens up a security risk.

  • Jake

    I’ve got myself a pc with Vista Home Premium on it. I was able to use the patch here to open up the remote desktop feature, but one of the reasons I wanted it enabled was so i could play music from my home pc over on to my work pc. But when I try to play any kind of audio device windows gives an error, “no audio device detected”. For some reason when I open up the remote desktop and ask for the audio to be sent to the pc connecting to my Vista machine, it disables the audio drivers on the Vista machine.

    the audio drivers work fine on the vista machine when I log in directly to it, they only get disabled when I RDP into the Vista machine.

    Does anyone have any work around to get the audio to work?

  • http://andrewblock.net Andrew Block

    Bruce,

    The machine accepting the request gets the hack. So in your case, that would be the Vista 32 bit machine.

  • Bruce

    I understand what is going on here but It is unclear what machine gets this “patch”?

    I have a Vista 64 bit machine that I am trying to use RD to connect to a Vista 32 bit machine. So which machine gets this patch?

    Thanks in advance

  • http://andrewblock.net Andrew Block

    Darren,

    System restore? System Properties > System Protection > System Restore. Choose a date before you applied the hack.

  • Darren

    So I tried to install this fix in Windows 7 home premium and it jacked it all up. Is there anyway to reverse the damage that was done? Specifically to the registry? I have purchased the Win 7 Pro upgrade and it still doesn’t work after I put the old termsrv.dll back in place. Help!

  • angela

    i put credentials on it. nothing happen?please help

  • angela

    help! whats is credentials that i need to input i really don’t have idea. help will be greatly appreciated. thanks ahead

  • patrick

    I used the SP1 32bit on a sp2 32bit home premium system, and it worked great. Thanks for your efforts.

  • bg

    I was able to enable this on my premium 64 bit, by 1st disabling the terminal services ( via control panel) … and restarting the OS and then runing the premium.bat file provided in the download and then restarting the teminal services( to automatic).

  • http://andrewblock.net Andrew Block

    Stephen,

    Since you have three PCs, you will need to change the listening port on two of them. Microsoft has an article on how to do this: http://support.microsoft.com/kb/306759. Make sure the ports are different on each PC that you change.

    Then you need to forward port 3389 (the original listening port for remote desktop) to the PC you didn’t change the port on. And then, you need to forward the other two ports (let’s say for example 3390 & 3391) to the other two PCs. You would need to handle this forwarding using your router. You also need to know the IP address of each of your PCs so that you can forward the appropriate ports to them. You may need to set up a static ip address on each PC; are you familiar with how to do that under Vista?

    Oh also, the protocol for remote desktop is TCP.

    What is the make & model of your router?

  • Stephen Blair

    I noticed that at least one individual listed above mentioned port 3389. I haven’t changed mine. How do you do that.

    My router is not setup for port forwarding. I lists the following fields to be filled in:

    Application
    Start
    End
    Protocol (Currently set to “Both” but TCP and UDP are options.)
    IP Address (Lists my router’s address with the last octet set to “0”, but it is able to be modified.)
    And Last but not least, the “Enable” Check Box.

    Sorry to be asking for such (probably simple and annoying help, but that’s where I’m at) basic help. Your help is greatly appreciated.

    Thank you…

  • http://andrewblock.net Andrew Block

    @Stephen Blair,

    Did you change the listening ports on two of the computers? Did you configure port forwarding on the router?

  • Stephen Blair

    I don’t have a Domain Server. I just have three PC’s running through a router and I cannot get connected. I am running Vista 64-bit with thye 64-bit patch in place and everything seems to be listening. Any help?

  • http://andrewblock.net Andrew Block

    @Martyn, you’re welcome.

  • http://www.martynwalker.com Martyn

    Thanks Andrew, like a lot of folk you’ve already helped this has been frustrating me for a long time.

  • http://andrewblock.net Andrew Block

    @Patrick,

    Cool! Would you mind detailing how you accomplished this, in case someone else is having the same problem? Did you go to services.msc?

  • http://andrewblock.net Andrew Block

    Hey Dustin,

    For the registry tweak to allow all versions of Remote Desktop, navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp. Look for the DWORD key called “UserAuthentication”. To allow all versions, I believe it needs to be set to “0”. If the value doesn’t exist, try creating it and see if it works.

  • http://andrewblock.net Andrew Block

    @Dustin,

    The only thing that fixed those types of problems was installing the app to the phone’s main memory instead of the flash memory. Tried that?

  • Patrick

    Quote: 107. Chinh Says:

    July 20th, 2009 at 11:30 pm
    To people who might have the same issue with Scott
    “System error 1079 has occurred.

    The account specified for this service is different from the account specified f
    or other services running in the same process.”

    => Changing the account for starting “Terminal Services” to Network Service with blank password has solved the problem on my machine (Vista Home Premium x86)

    Just wanted to say that this was the thing that I needed to know to get mine to work after hours of banging hy head against the wall

  • Dustin

    i found out i need a registry tweak. what tweak would i need to do to let my vista home premium PC allow all versions of Remote Desktop
    im sure its in terminal services somewhere.

  • Dustin

    OK… first let me say that this hack save me a few years of my life. I have been pulling my hair out for the past 8 days trying to figure out why i couldnt connect to my desktop using RDC. Only to find out that Vista home premium wont do it out of the box… i was online with my router support, on the phone with my router support, HP live chat, HP phone support, Microsoft answers, PPC geeks, you name it i was trying it.

    So just let me say BIG THANKS.

    However… i have still not solved my main issue.

    I am trying to get my Touch Pro 2 to Remote connect to my desktop.
    This hack fixed every other connection. I can now use my internal ip, my external ip, and even my DYNDNS to connect from my laptop all perfectly.
    but when i use windows remote desktop connection on my phone to connect to my desktop it will not work still… i get an error that says,

    “The Connection was ended because
    of a network error. Please try connecting
    to the remote computer again.”

    this had been a new error since installing this hack. I use to get errors that said the remote machine not set up, or cant locate machine, yada yada..

    but now its getting through to the computer at least.

    Is this hack maybe not set up to allow this type of connection from a phone? (even if the phone has windows on it and the phone came with RDC)

    Any ideas please

  • http://andrewblock.net Andrew Block

    @Josh,

    Running as administrator? Double-checked that you’re using the proper 64-bit version? McAfee blocking the file thinking it’s a virus?

  • Josh

    I am fairly new to this, but I think I have covered all the bases and still am having trouble.

    Bat file runs smoothly untill terminal services trys to start and this is what I get.

    The Terminal Services service could not be started.
    A system error has occurred.
    System error 193 has occurred.
    *** is not a valid Win32 application.

    And obviously service is not listening…

    Thanks in advance for any input/suggestions.

    home premium sp1 64 bit

  • http://andrewblock.net Andrew Block

    Hey aaron what if you try creating a new administrator account, and try running the batch file from that account? Maybe something with your account is screwy? Just a thought.

  • aaron

    yea, i run command prompt as admin and run the batch with no luck. thats the message i received.

  • http://andrewblock.net Andrew Block

    @aaron,

    Did you try running the batch file as Administrator?

  • aaron

    forgot to say that im running home premium sp1 64 bit and thanks for any assistance

  • aaron

    ok, so im new to this and learning as i go. i have attempted what seems to be every possible solution on this forum and all others i have came across. i still have the same result. i know its my error but i dont have enough experience to resolve it. here is what i am receiving:

    Source Folder is C:\Users\KRISHNA\Desktop\NewFolder\
    Taking ownership of C:\Windows\System32\termsrv.dll

    SUCCESS: The file (or folder): “C:\Windows\System32\termsrv.dll” now owned by th
    e administrators group.
    Granting Administrators rights
    processed file: C:\Windows\System32\termsrv.dll
    Successfully processed 1 files; Failed processing 0 files
    Stopping Terminal Services
    The Terminal Services service is not started.

    More help is available by typing NET HELPMSG 3521.

    1 file(s) copied.
    Copying C:\Users\KRISHNA\Desktop\NewFolder\termsrv.dll to C:\Windows\System32\
    1 file(s) copied.
    Copying C:\Users\KRISHNA\Desktop\NewFolder\rdpclip.exe to C:\Windows\System32\
    1 file(s) copied.
    Importing Registry Keys
    Enabling RDP
    The operation completed successfully.
    Setting fSingleSessionPerUser to 0
    The operation completed successfully.
    Setting LimitBlankPasswordUser to 0
    The operation completed successfully.
    Configuring Remote Desktop in Windows Firewall
    Ok.

    Starting Terminal Services
    System error 1079 has occurred.

    The account specified for this service is different from the account specified f
    or other services running in the same process.

    Pausing 5 seconds to give service time to start listening
    Checking if Service is listening on port 3389
    Service is not listening
    Done

  • Pingback: HeadWing | No Terminal Server function in Vista Home

  • docdee

    @Andrew Block – the 3 causes listed are:
    1. Remote connections might not be enabled at the remote computer
    2. The maximum number of connections was exceeded at the remote computer
    3. A network error occurred while establishing the connection

    FYI – under the my system properties I only have a checkbox for “Remote Assistance” which from what I read above is expected on Home Premium even after using the hack.

  • http://andrewblock.net Andrew Block

    @John P. — thanks for the tip.

    Another general tip for everyone: It’s also important to note that (I think) checking Remote Desktop won’t work if you use a custom port for RD to listen on. I think you’d have to manually create an entry for that port then (for example, port 3391).

  • http://andrewblock.net Andrew Block

    @docdee — what three likely causes did it list?

  • docdee

    I have Vista Home Premium with SP2. I use a LinkSys WRT545GS router, with Commodo Firewall and AVG AntiVirus. I downloaded the latest hack that was added by James on 8.14.09. I followed the instructions verbatim running as Administrator and the console output showed sucess. The hack was able to stop terminal services (and media center), it was able to copy the file to System32 and set the admin privs on it, update the registry and restart the service. I rebooted just for giggles and I can see TS service listening:

    C:\Windows\system32>netstat -a -n -o | find “3389”
    TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1192
    TCP [::]:3389 [::]:0 LISTENING 1192

    I have windows firewall and defender disabled since I use commodo and avg as stated above. I created a rule in my firewall to allow TCP in/out on port 3389. So everything looks good, and when I try to connect via RDC from a XP Pro machine I can even see my firewall rule firing and it says the connection was accepted. But RDP won’t connect. The error I get says “The client could not establish a connection to the remote computer” and list the 3 likely causes. HELP!

  • John P.

    I re-ran the SP1 batch file after I installed SP2 on my Vista x-64 version and it seemed to work just fine for starting the remote service connection but I could not connect through the remote desktop.

    Apparently when I upgraded to Vista SP2 my Windows Firewall was updated to block all incoming connections. When I unchecked the box I was able to connect remotely again.

    Control Panel -> Security -> Windows Firewall -> Change Settings -> Uncheck “Block all incoming connections” -> Exceptions tab -> Make sure remotedesktop is checked

  • http://allzoom.ru.ru Zashkaser

    Ya put a smile in my face.

  • http://andrewblock.net Andrew Block

    @ Håvard,

    I am really glad you got it working. And stop kicking yourself in the head — you might get brain damage if you keep it up! :-p

    I have to note that I cannot take credit for writing the batch file. I don’t know the author; I found it a while back and now I can’t find the original site again. I just made some mods to include an x64 version and stuff. Just making sure I am not taking credit where it isn’t due.

  • Håvard

    Hi.

    First of all I would like to thank Andrew for a brilliant solution to a frustrating problem! Then i want to kick myself in the head for wasting the whole day going back and forth disabling/enabling firewalls and different versions of this patch.

    After pulling all of my hair out, I found out that it was the SP1 version that works for me, even if I’m running Vista home Premium SP2.
    I can’t explain why. But here is a compressed history of today’s work:

    1. Trying different Solutions before stumbling over this brilliant site.
    2. Installed the SP1 version of the patch. But the problem was that I had to disable the firewall on my client PC to be able to connect.
    3. Installed the SP2 version, and had the same problem.
    4. Then I did something(can’t remember what…) and I’m not able to remote in.
    – I could enter a password, but was thrown back to the first dialog again.
    – I could enter a wrong password and get a warning…
    5. Some hours later, I re-installed the SP1 version of the patch, and everytning works as expected! (Even with active windows firewall on both client and server).

    BTW, my client is a laptop running Vista Business SP2, and the server is a Home Premium SP2.

    As I said in the beginning; BIG thanks to Andrew, and egually big kick in the head to me for wasting my day:)

  • http://andrewblock.net Andrew Block

    @ Chinh,

    Thanks for posting your tip – that’s a good idea to try.

  • Chinh

    To people who might have the same issue with Scott
    “System error 1079 has occurred.

    The account specified for this service is different from the account specified f
    or other services running in the same process.”

    => Changing the account for starting “Terminal Services” to Network Service with blank password has solved the problem on my machine (Vista Home Premium x86)

  • http://andrewblock.net Andrew Block

    @Todd,

    Glad it helped. Thanks for reading!

  • Todd

    Nothing is better than searching for an answer and have a site like yours be uncomplicated to the point and the answer work without alot of if’s and’s or’s

    Thanks please keep up the very good work

    Todd

  • http://andrewblock.net Andrew Block

    @James, thanks for posting the DLL — MUCH appreciated.

    @Sam, I am really glad it has helped you out. Thanks for reading.

  • Sam

    OK..here is an update….I uninstalled a few of those updates and downloaded your copy of the termsvr.dll (what i had before was from greenbutton)….i updated the registry keys etc. but was not able to copy the dll file because it was locked..I simply booted my machine in safe mode and copied it over…when i rebooted it..BANG! 3389 was listening when i did a netstat -a and even better, with your copy of the dll, the copy paste etc were also working properly !!! thanks for your life saver…i would have had to run back and forth to the basement if not for your version….

  • Sam

    Everything was working fine until last week when the windows update (security or so)…(windows vista still says sp1) installed in my home premium…I have tried everything after that and nothing can get remote desktop back to working like it was….wish someone could help in getting back to running.

  • James

    Here’s an unhacked Vista x86 SP2 termsrv.dll for those who want it:
    http://rapidshare.com/files/247347791/termsrv.dll.html

  • http://andrewblock.net Andrew Block

    @Araqnid78,

    You can change the Terminal Services port on one of the computers via the registry: http://support.microsoft.com/kb/306759.

    You will also need to open whatever port you choose in the Windows Firewall. Simply checking “Remote Desktop” won’t work, because that only opens 3389. You’ll need to create a custom entry for your new port (for example, I chose 3390 for my second PC on my LAN).

    Then of course, on your hardware firewall/gateway, you’ll need to forward the port to the PC’s internal IP address.

    Also — when trying to connect to the PC with the custom port, be sure to add :[portnumber] to the end, like this: 192.168.1.2:3390.

    Hope this helps.

  • Araqnid78

    Any ideas on enabling RD on two compters within the same LAN? The termsrv batch file assumes port 3389. What about adding another computer? Another port say, 3390, would have to be used, right? And termsrv.zip does not support that – I assume.

  • http://andrewblock.net Andrew Block

    If you’re looking for a version of this with files from SP2, check out this post: http://andrewblock.net/?p=411 (currently I only have the x64 version of the files; trying to figure out where to get 32-bit ones).

  • http://andrewblock.net Andrew Block

    @Dreballer – no problem dude! Glad it helped you out. :)

    @Chuck – I really do need to update it with SP2-compatible files. The problem is, I am not sure where I will find a 32-bit DLL, as all my OS’s / systems are 64-bit. If anyone has a 32 version of the SP2 DLL, lemme know…I’ll start with the 64-bit one for sure. It is my goal to update it tonight.

    @Yash – if you’re doing it over the Internet, you could point a Dynamic DNS service to your ISP-assigned IP address, and then use that URL to access your remote desktop. 192.168.xx.xx won’t work over the Internet. For example, you could use DynDNS: http://www.dyndns.com/.

  • Yash

    I can easily remotely log into my laptop at home through mobile, but can’t from outside over internet. I can guess that I am not able to do correct set up in port forward on the web page of my Belkin wireless router. Would you check whats wrong-

    Server Name – anyname
    External Port Start – 3389
    External Port End – 3389
    Protocol – TCP
    Internal Port Start- 3389
    Internal Port End – 3389
    Server IP Address – 192.168.2.1 (IP address of my laptop to which I am trying to login from my HTC Touch mobile on windows mobile 6.1)

    Already tried various permutations and combinations but no success.
    Thanks in advance!

  • Chuck

    Interestingly enough trying again and again w/ some playing managed to change my connection error to:

    Remote Desktop Disconnected:
    The client could not establish a connection to the remote computer

    The most likely causes for this error are:
    1)Remote connections might not be enabled at the remote computer.
    2)The maximum number of connections was exceeded at the remote computer.
    3) A network error occurred while establishing the connection.

  • Chuck

    Any update on SP2. I had this working perfectly connecting from my laptop (winxp) to my x64 vista desktop. I applied SP2 last week and RDP immediately quit working. I have tried reapplying the patch, but after I still can not connect. Now when attempting to connect I get an instant failure on the connecting side with the error: “The connection was ended because of a network error. Please try connecting to the remote computer again” I’m not sure where to go next at this point and I haven’t found any information on it. Your help would be appreciated.

  • Dreballer

    Thanks man. works great for x86 and x64 home premium. Just needed to have home premium for it has builtin Media center.(cheaper than ultimate)

  • http://andrewblock.net Andrew Block

    @Gerald, I think what I’ll do is compare termsrv.dll from sp1 and sp2 and see if the files have changed. It may be that users will just have to reapply this hack after installing sp2. hopefully that’s the case. :)

  • Gerald

    I ran this hack for the first time and i have sp2. Works perfectly. Andrew I dont think you have to recreate anything.

  • Gerald

    Great I just installed SP2. Ive read somewhere that you just gotta replace the dll file again and it will work.

  • http://andrewblock.net Andrew Block

    @RB, I probably need to make an updated package for those that have SP2, as I’m sure the SP1 DLL won’t work with SP2. I will try and do that sometime this week.

  • RB

    Might be something else.. but this seems to have stopped working since installing Vista64 SP2

  • santino

    Does anyone have fixed this sound, clipboard and shared disk problem … or it works for someone? Especially I care about my disk resources.

  • Jeremy

    Thanks very much for this! You just saved me from having to lug my laptop home from the office every time I want to WFH. Much appreciated.

  • http://andrewblock.net Andrew Block

    MARK- Is the Mac reporting the error? Have you successfully connected from another Windows-based PC?

  • MARK

    Hi, I installed this hack, and i’m trying to connect to my windows vista SP1 32 bit system from my MAC laptop running OS X 10.4.11 using remote desktop connection from windows and it says i’m having network problems? I guess my laptop is seeing my CPU buts its not working? I also can’t see the cpu on my regular network??? what do you think the problem is??

  • http://andrewblock.net Andrew Block

    Are you running the Command Prompt as administrator?

  • claud

    i get the black DOS screen window saying. Connecting to 71.63.44.
    104 (which is my ISP ip address) for few seconds and then the whole window vanishes as if nothing happened??

  • http://andrewblock.net Andrew Block

    Claude,

    Pretty sure Windows Defender doesn’t block any ports.

    But I’ve got something you can try. On the computer that’s having issues, go to a command prompt type this:

    1. Telnet name_of_your_computer 3389
    2. If it goes to a screen with a blank cursor, it connected successfully and the computer is configured correctly. Here we know the problem is with the hardware firewall.
    3. If it errors out, then the problem is with the PC, and…well then it could be lots of problems. :(

    I think localhost may work for the computer name as well. Full article on this -> http://support.microsoft.com/kb/187628

  • claud

    3389 is already added to the windows firewall. But what about the windows defender do i have to do anything with it?

  • http://andrewblock.net Andrew Block

    Hey claude,

    Sorry I don’t think I’m being much help, but I have never used PCTools’ Spyware Doctor and antivirus…I tried Googling how to add port exceptions in that program but nothing came up. I am not sure if that program even blocks ports or not.

    Did you create an exception for port 3389 in the Windows Firewall itself? http://windowshelp.microsoft.com/Windows/en-US/help/4da18300-9044-47b6-9038-595c78db81ab1033.mspx

  • claude

    by the way so many thanks for your time and prompt response and knowledge

  • claude

    Antivirus: Spyware Doctor and antivirus by PCTools.
    Registry: I have 3389 set up for port number under Decimal

  • http://andrewblock.net Andrew Block

    @One BigScam, Johnny: Thanks for dropping a note guys. Glad this has helped you out. Please keep in mind I am not the coder of this hack; I just bundled some things together. :) (don’t want it to seem like I’m trying to steal credit)

    @Catherine, I really don’t know. Is everything working as it should? I am assuming if you went and did the 32-bit version that it would just overwrite the 64-bit DLL and everything would be fine. I guess if it’s working then you’re good to go.

    @claude, unfortunately this hack does not add the Remote Desktop functionality back into the Windows GUI. Any tweaks/modifications have to be done through the registry. For the issue with connecting, what antivirus app do you have? You may need to create an exception there as well. Hard to say if I don’t know which app you have though.

  • claude

    Hi Andrew,
    you are the greatest. Pinpoint and efficacious answers. I downloaded the patch from the updated file you have posted above for my Vista 64 Home Premium, and everything said to be done and listenning to 3389. But i still can’t connect to my desktop. i have a router that is already set up for triggering and Fwding to 3389 and to the right ip address of the desktop. do you think i am missing some boxes not checked. I have the port allowed in my firewall. i have pctools malware detective and antivirus , but i don’t know if it has anything to do with the issue. Could you please help. PS. after i ran your patch i still don’t have any mentioning of RDP under Computer Properties/Remote tab…. i only see the Remote assistance thing. is that the way it should be?

  • Johnny

    Thanks Andrew! Works great. Spent 3 days looking for something that worked. all the others failed me but yours works like a charm on my vista 64 prem. Thanks for spending the time to release this, much appreciated.

  • Catherine

    I installed x64 for my 32-bit vista home premium by mistake, then I installed x86 but did not unistall the x64, is there any problem?

  • One BigScam

    First off this rocks! Secondly, it seems you can just edit the batch file and change SET SINGLESESSION=0 from 0 to 1. That seemed to solve the multiple sessions problem for me in one step.

  • http://andrewblock.net Andrew Block

    Aaron, sweet! This is great information to have as part of this comment thread. I am sure somebody else out there is having the exact same problem, so thanks for taking the time to explain how you fixed it.

  • Aaron

    @ Andrew -> yes I was adding the 3390 to the end of the IP address when trying to remote in. I finally figured out the problem. Even though I had went into the registry and changed the default rdp-tcp port from 3389 to 3390 it was still listening on port 3389 and I found this out by opening a command prompt and typing NETSTAT -A and scrolling through looking for the corresponding port number which was still on 3389. So all I had to do at that point was open up the servies under administrative tools and restart the terminal services. After I restarted the terminal services I open back up the command prompt and did the NETSTAT -A again and it had finally switched from 3389 to 3390 and now works great. Thank you!

  • http://andrewblock.net Andrew Block

    @RicJim –> You are welcome. Glad it helped you out.

    @Aaron –> in the remote desktop connection dialog, did you specify port 3390 at the end of the IP address/computer name you want to connect to? For example, if you were trying to connect to 192.168.1.2 on port 3390, you’d need to enter 192.168.1.2:3390. If you leave the “:3390″ part off, it assumes 3389. Did you try that?

  • http://andrewblock.net Andrew Block

    @PK – thanks, and please keep me posted if you find anything. I’m willing to add it to the main post if it’ll help other people out, too.

  • Aaron

    I have two computers that I am trying to set up to use remote desktop connection. Everything works fine as long as I use the default port 3389 but I edited the registry on one of the comptuers since they both can’t use the default 3389 and I changed it to 3390 and it will not let me connect. They both work if they use 3389 but I need to assign one of them and different port. I have everything set up corretly as far as setting up my router to forward the ports properly but I can’t seem to get the other computer to work unless it uses the default port. Any suggestions or ideas?

  • RicJim

    Just wanted to let you know how thankful I am for your script. Also thanks to @John Wolf for finding the multiple sessions per user fix. Thanks!!!!!

  • PK

    Yes I am sure, since it is the Batch file that automatically picks up the DLL from the x86 folder and copirs it to the system32 folder. I have manually copied the DLL from the x 86 folder and still it does not work ?!?!

    It is frustrating that everything looks good and it still does not work. Wireshark shows that the remote computer is trying to make a connection but something somewhere is messing up.

    Thanks anyway. If I find a solution, I will definitely post it here.

  • http://andrewblock.net Andrew Block

    PK — are you sure you’re using the appropriate x64 or x86 DLL? That’s the only thing I could think of. I’ve never really heard of the issue you’re having before.

  • PK

    Hello, My RDP (Vista Home Premium) use to work before with a hacked file such as yours. Then a few months ago, I noticed that my termserv.dll was replaced by one of the Microsoft updates and that caused my RDP to not work. After that, I upgraded to SP1 and just a couple of days ago decided to go back to try and get the SP1 hacked file on your site and use it to get the RDP going. I can telnet to the computer on port 3389, but I get an error “The connection was ended because of a network error. Please try connecting to the remote computer again.”

    I can connect to my desktop with logmein.com account and see that the port connection is “ESTABLISHED” when I telnet on 3389.

    Is it some registry setting ? or the dll that is not working out for me. All the registry settings look fine (according to the batch file) when I check in my settings.

    Any Help would be appreciated !!

  • Nikke

    Works great, except the sounds. Got the no device installed, no matter what I do.
    Anyone have a solution for this?

  • http://andrewblock.net Andrew Block

    @Lester — awesome! I’m glad it worked for you. As you can see, a lot of people were disappointed to find that MS had crippled Home Premium.

    @Lisa — you do not have to use port 3389; you can change remote desktop to listen on any port you want via the registry. Check out http://support.microsoft.com/kb/306759. Also, if you have a hardware firewall, you need to forward appropriately. Let me know if you need help on this, as I have done it several times. :)

  • Lisa Brown

    Do you have to use port 3389 or can you change the registry to reflect a different port?

  • Lester Bestertester

    I just had to say this solved my problems. I too assumed remote desktop would work and I frantically tried to find out how to enable it in WinVistaHP. This worked first try. Brilliant!

  • http://andrewblock.net Andrew Block

    Tim,

    Yes, you can access a machine over the Internet.

    As you’re connecting to remote desktop, simply enter your domain name…let’s say it was tim.no-ip.org. You’d just enter that into remote desktop, and then you’d have to provide your Windows logon credentials.

    Of course, you need to set up port forwarding on your router/gateway. The default remote desktop port is 3389, so you’d need to internally forward that port to the appropriate machine (mac-vistapc’s internal IP address) in your case. You’d do this via your router’s web interface.

    Does this help?

  • Tim

    Hi,

    This site is excellent. I have a question relating to the remote desktop. I can access mac-vistapc on an internal home network. Like Dil I downloaded no-ip and I want to be able to use the remote desktop from outside of my home network. Os this possible? If so could you provide any guidance.

    Many thanks

    T.

  • Dil

    Hi Andrew,
    I have a bigger issue now. Where the remote laptop is located, apparently port 80 is blocked. I wonder if there is a workaround for this.

    Dil

  • Jordan

    @ John Wolf / Mac / Andrew:
    Just stopped by again, and changed the key HKLM\System\CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser to 1.
    Worked perfectly.
    Thanks for keeping up with this!

  • Dil

    Thanks for taking the time.
    The remote machine is running 64bit Vista and I have installed the 64bit file. It is a new laptop and sound works fine on that machine. The issue is that it will not bring sound to the local machine. I had to forward port 80 to test the RDC connection using my neighbours LAN. Now the remote machine is in another part of the world and I am still to test the RDC. In addition to RDC patch, I have installed a no-ip update client so I should be able to find it without much drama. Will keep you updated.

    All good things take time.

  • E

    Andrew,
    I’ll try the “control userpasswords2″ when I get home. I figured out why creating the “Remote Desktop Users” group didn’t help me. It is normally a BUILTIN group with a well-known SID. So, the group I created is useless because it isn’t recognized as “BUILTIN\Remote Desktop Users”. I wonder if there is anyway to create a group with a specific SID.

  • http://andrewblock.net Andrew Block

    E~

    Out of curiosity, do Start->Run, and then enter “control userpasswords2″. Does that do anything for you?

    I’m on an XP box right now and it works for me but it might not work right in Vista Home Premium.

  • E

    Unfortunately, there is no Local Users and Groups snap-in on Vista Home Premium. The only choice is the command-line tools. Also, the “Remote Desktop Users” group didn’t even exist (like it normally does once RDP has been enabled). So, I had to create it and add the normal users. I’m surprised that I’m the first to ask about this. Perhaps, most people use administrator accounts?

  • http://andrewblock.net Andrew Block

    @TechDude–you are very welcome.

    @Scott–Just guessing here, but maybe try this from another administrative account? I Googled your error but didn’t really come up with anything good.

  • http://andrewblock.net Andrew Block

    @Dil,

    I am not really sure, but does the host machine have a sound card/drivers properly installed? Is the volume un-muted and turned up? Is the connection laggy, maybe preventing the sounds from being “streamed” to your PC? Again I am really just taking a stab in the dark, as I don’t really know. Sorry I can’t be more help to you.

  • http://andrewblock.net Andrew Block

    E~

    Not really sure…did you try using Administrative Tools -> Computer Management -> Local Users and Groups and adding users to the Remote Desktop Users Group that way?

  • E

    Well, I figured out how to create and add users to the “Remote Desktop Users” group using the “net localgroup” command, but I still cannot RDP in as a regular user. Help!

  • E

    OK, using this hack I am now able to RDP into my Vista x64 Home Premium machine from all my other PCs. However, only as Administrator, since that is the only user in the “Remote Desktop Users” group. Normally, I would just add the other users to that group, but I don’t know how to do that in Vista Home. Any ideas?

  • Dil

    My sound issue still exists. I do nt get sound from host at the remote computer. I have already installed all the latest updates.
    Thanks

  • Scott

    I have followed your steps and everything is fine until the script tries to start Terminal Services. Here is my output. Can yuo tell me what the error 1079 means?

    Peace,
    Scott

    Source Folder is C:\Users\scott\Documents\rdp_vista_sp1\RDP Vista x64 SP1\
    Taking ownership of C:\Windows\System32\termsrv.dll

    SUCCESS: The file (or folder): “C:\Windows\System32\termsrv.dll” now owned by th
    e administrators group.
    Granting Administrators rights
    processed file: C:\Windows\System32\termsrv.dll
    Successfully processed 1 files; Failed processing 0 files
    Stopping Terminal Services
    The Terminal Services service is not started.

    More help is available by typing NET HELPMSG 3521.

    1 file(s) copied.
    Copying C:\Users\scott\Documents\rdp_vista_sp1\RDP Vista x64 SP1\termsrv.dll to
    C:\Windows\System32\
    1 file(s) copied.
    Copying C:\Users\scott\Documents\rdp_vista_sp1\RDP Vista x64 SP1\rdpclip.exe to
    C:\Windows\System32\
    1 file(s) copied.
    Importing Registry Keys
    Enabling RDP
    The operation completed successfully.
    Setting fSingleSessionPerUser to 0
    The operation completed successfully.
    Setting LimitBlankPasswordUser to 0
    The operation completed successfully.
    Configuring Remote Desktop in Windows Firewall
    Ok.

    Starting Terminal Services
    System error 1079 has occurred.

    The account specified for this service is different from the account specified f
    or other services running in the same process.

    Pausing 5 seconds to give service time to start listening
    Checking if Service is listening on port 3389
    Service is not listening
    Done
    Press any key to continue . . .

  • Techdude49

    Thank you for sharing this information. I was going to install VNC until I read your blog and I am very appreciative for the working hack. Thank you!!!

  • http://andrewblock.net Andrew Block

    @Dil from #36 — did you get your sound issue figured out?

  • mac

    Perfect! :) After changing the registry key as posted by John the RDP does not create a new session any more.

    Thank you very much gentlemen! :)

  • Mark S

    There is a bug for user with spaces in their names. Fix is:
    SET SOURCEFOLDER=”%~dp0″
    If copy fails for some reason If it does not work, copy the termsrv.dll and rdpclip.exe to Windows/System32. Stop the Terminal Service first in services.msc
    Thank you for this. it works well for me.

  • Steve N

    Thank you very much. This worked well for me.

  • http://andrewblock.net Andrew Block

    @John–that’s great! A lot of people have been asking me about this. If it’s OK with you, I am going to add your comment as an addendum to my post. I’ll give you credit, of course.

  • John Wolf

    Also….

    The thread is here:

    http://thegreenbutton.com/forums/1/156341/ShowThread.aspx

    The post with the above info is here:

    http://thegreenbutton.com/forums/permalink/156341/169698/ShowThread.aspx#169698

    You may need the hack linked in the thread, I’m not sure if it’s different than the one posted here.

  • John Wolf

    Hey Jordan/Mac/Andrew,

    I’ve been fishing to solve the issue of it creating a new session when you RDP to a Vista box. After digging through the thread on the green button, I found a registry setting that remedies this issue. There’s a key HKLM\System\CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser, that defaults to 0 which means create multiple sessions per user. Simply setting this to 1 will give you what you want. I just verified this and it works like a charm!

    Good luck,

    -John

  • Dil

    Bring to this computer.
    am not able to connect from outside of my LAN to this computer. I have already enabled exeptions in firewall for RDC and forwarded port 3389.

    Thanks

  • http://andrewblock.net Andrew Block

    @Dil,

    If you click Options, and then go to the Local Resources tab, what setting do you have chosen for Remote Computer Sound?

  • Dil

    This hack works within my lan. However sound does not work. I get the following message “No audio devices are installed”. What could be the issue any ideas how to get it working.

    Thanks

  • http://andrewblock.net Andrew Block

    Sorry Jordan — I don’t know what else to say! :) I am out of ideas on this one.

  • Jordan

    I checked my registry: fDenyTSConnections was already set to 0, and UserAuthentication was set to 0 as well. I tried switching it to 1, but no luck.
    -sigh-
    I don’t think home premium likes trying to do stuff that was designed for ultimate.This may be more complicated than I had hoped.

    Thanks for trying to help, though.

  • http://andrewblock.net Andrew Block

    Hey Jordan,

    I found this at http://www.mydigitallife.info/2007/01/26/turn-on-or-enable-remote-desktop-on-windows-vista (#s 3, 4, and 5 seem most pertinent).

    Enable Remote Desktop on Windows Vista via the registry

    1. Open registry editor.
    2. Navigate or browse to the following key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server
    3. Locate the fDenyTSConnections subkey, and change the DWORD value to 0.
    4. To enforce the use of RDP 6.0 and NLA, navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp
    5. Locate the UserAuthentication subkey, and change the DWORD value to 1. Comment: In our case, I believe we would set this to 0?
    6. Exit registry editor and restart the computer to make the changes effective.
  • Jordan

    @ Andrew & mac,

    I am beginning to suspect that this /admin issue may be caused by this hack. I’ve tried several tricks, including configuring my xp mce sp3 machine to support network level authentication (NLA) (see link below if curious)
    http://vidmar.net/weblog/archive/2007/05/27/The-remote-computer-requires-Network-Level-Authentication-which-your-computer.aspx

    On that same page, I noticed that when Vista Ultimate users go to Remote Settings under System Properties they can select ‘Allow connections from computer running any version of Remote Desktop (less secure)’
    I don’t even have that option (or the other two surrounding it). Maybe that’s part of the problem – checking that box disables the need for the client to have NLA. Perhaps if we could get a registry key or something to disable the need for NLA (effectively check that box) then it could solve our problem.

    Or maybe I should just buy Vista Ultimate : (

  • Pingback: Content Unbound » Windows Vista and Remote Desktop

  • http://andrewblock.net Andrew Block

    @ Jordan & Mac,

    Good luck, guys. I’m afraid what you’re discussing is probably way over my head at this point, but I hope the two of you can figure it out! :) Sorry I’m not more help on this one….

  • mac

    ups … last sentence … meant of course “ideas” and not “days”! Sometimes one should go to sleep and try to fix the computer! ;)

  • mac

    @Jordan: I find some more info with Google and came across this article:

    http://social.technet.microsoft.com/Forums/en-US/itproxpsp/thread/e92f126d-caf6-4bdb-a45f-a0b99082f627/

    I tried to change the .rdp file as described post at the very bottom of the first page, but it didn’t help.

    I also looked into my WINDOWS\PolicyDefinitions folder, but can’t find any policies there that would allow the change in the GPO as described in the post by QEDeh (Posted on May-09-08 8:04:03 AM).

    Maybe you have some days based on what I just wrote.

  • Jordan

    Yeah, mac, it sounds like we’re getting the same problem.

    I installed SP3 on my laptop, and the versions of RDP are now the exact same on both computers (ver. 6.0.6001.18000). I still get the same behavior as before – I can use my desktop (Vista x64 with your hack) to take over the current session on my laptop (XP-MCE SP3), but I cannot do that the other way around. When attempting to log on to my desktop with mstsc /console or mstsc /admin, it creates a new session : (

    I’ll try play around with it some more, but I’m running out of ideas (it’s not a huge deal, but I’ll do what I can to get it working).

  • mac

    @Jordan: I think that’s exactly the problem I tried to address in my earlier posts. I open the remote connection and another session is created with the same username instead of taking control of the existing one.

    So now I have two sessions running, both with the same username. So I tried to run taskmgr.exe and go to the users tab. I see two users, one has “Console” in the session column, the other RDP-Tcp#0.

    I then thought to try to take over the console session with my remote session, by right-clicking the console session and choosing “Remote Control”. But after I press “ok” on the next screen, for a moment I see the message “Please wait while Terminal Services establishes the remote control session …” and then it says that “Session (Id 1) remote control failed”

    I would really appreciate some ideas how to fix this.

  • http://andrewblock.net Andrew Block

    @Jordan,

    OK, cool, just let me know–I’m curious to see if you’re able to get it figured out.

    @Ricky,

    Is it a permissions issue maybe? Beyond that I’m not so sure. You can check out this post: http://andrewblock.net/?p=70. Some of the comments appear to touch on your issue.

  • Ricky

    Great Hack!! I can connect to my Vista X64 Home Premium laptop with your hack from my xp laptop with no problems.

    However, I wasn’t really planning on connecting from my laptop. I had hoped I could connect from my phone (running Windows Mobile 6.1). My phone comes with a mobile version of the RDP client that allows me to connect to other windows machines that have remote desktop enabled.

    On my phone I get a connection status window with the message “The connection was ended because of a network error. Please try connecting to the remote computer again.”

    My phone is connected to my home network via wifi just like the xp laptop so I know I’m not trying to connect from outside my home network.

    Any thoughts?

  • Jordan

    Actually, that’s not the problem (but was good advice). I can type ‘mstsc /console’ or ‘mstsc /admin’ on my desktop (Vista x64 SP1), and it lets me take over a session on my laptop (XP-MCE).
    However, my laptop rejects ‘mstsc /admin’, and ‘mstsc /console’ works, but won’t take over the current session on my desktop (which is my main goal).
    My laptop is still XP-MCE SP2. It sounds like the new version of RDP comes with SP3. Installing that may fix this issue.
    I’ll play around with it. It’s probably not an issue with your hack.
    Thanks

  • http://andrewblock.net Andrew Block
  • Jordan

    Brilliant!
    One question: I usually run “mstsc /console” (typed into the run box) from my xp-mce laptop so I can take over an active session. When I tried to use this to take over an active session on my desktop (with home premium and your hack), it didn’t take over the active session, but rather, it created a new session (the /console didn’t work).
    Is there a way to get /console to work?
    (If not, that’s okay – I’m just glad I can use rdp now)

    Thanks

  • http://andrewblock.net Andrew Block

    @John,

    Why not just use a non-admin (i.e., standard user) account, but use administrator credentials when running the batch file?

  • John

    I want to use remote desktop on home premium without my account being in the administrators group. Has anyone done this.

    I used ntrights.exe to add SeRemoteInteractiveLogonRight to the Users group but did not allowe a member of users group to login remotely.

    Thanks in advance.

  • Tom

    It was svchost that was locking termsrv.dll. But I had to reboot after terminating the processes and coping the new termsrv.dll file to system32 because I lost network and internet access but after I did that, everything worked fine. I’m really hoping this will help all the other people that might be having problems with this. Now that I’ve experienced it, I can definitely say that this hack works! :)

  • http://andrewblock.net Andrew Block

    @Tom,

    Nice investigation, and great suggestion. I bet it will help out a lot of people; I’m sure you’re not the only one experiencing difficulties!

    But I’m curious: what program/process–according to WhosLockingIt–was locking termsrv.dll?

  • Tom

    Hey Andrew! Well, to answer your question, I do run the batch file as an administrator, I’m the owner of the computers in question so I have admin status for my user account. However, after very careful investigation, I found out why it wasn’t working. Yes, I do have it working finally! Here’s what happened. The termserv.dll file wasn’t getting replaced like it was suppose to, I think it might have even been the original Vista termserv.dll file that was still there. So, I thought I’d just copy and paste the patched termserv.dll file into the system32 directory, but there were processes locking it, so I used a program called WhosLockingIt to unlock the file and as soon as I stopped all the processes. After that I was able to copy and paste the file and I rebooted and as soon as I fired up remote desktop on my laptop and tried to connect to my desktop, bang, success!! So, my suggestion to anyone who might have problems with this hack is to check and see if your termserv.dll file is being replaced by the installer, if not, you may need to manually copy and paste it into the system32 directory. After I did that and I ran the installer again, it finally said the service was listening. ^_^

    Hope this helps!

  • http://andrewblock.net Andrew Block

    Hey Tom–it looks like the problem is that the Terminal Service can’t be stopped. Are you running the batch file as an administrative user? The terminal service not stopping sounds like a permissions deal. Does the user account you’re currently in have admin rights?

    Oh and have you tried rebooting your PC? Can’t hurt….

  • Tom

    Wow, thanks for such a quick reply! To start with, I double checked and I did install the x86 version (I have a 32-bit copy of Vista). I reinstalled it using your method and this is what I got.

    Source Folder is F:\RDP Vista x86 SP1\
    Taking ownership of C:\Windows\System32\termsrv.dll

    SUCCESS: The file (or folder): “C:\Windows\System32\termsrv.dll” now owned by th
    e administrators group.
    Granting Administrators rights
    processed file: C:\Windows\System32\termsrv.dll
    Successfully processed 1 files; Failed processing 0 files
    Stopping Terminal Services
    The Terminal Services service is stopping..
    The Terminal Services service could not be stopped.

    1 file(s) copied.
    Copying F:\RDP Vista x86 SP1\termsrv.dll to C:\Windows\System32\
    The process cannot access the file because it is being used by another process.
    0 file(s) copied.
    Copying F:\RDP Vista x86 SP1\rdpclip.exe to C:\Windows\System32\
    1 file(s) copied.
    Importing Registry Keys
    Enabling RDP
    The operation completed successfully.
    Setting fSingleSessionPerUser to 0
    The operation completed successfully.
    Setting LimitBlankPasswordUser to 0
    The operation completed successfully.
    Configuring Remote Desktop in Windows Firewall
    Ok.

    Starting Terminal Services
    The requested service has already been started.

    More help is available by typing NET HELPMSG 2182.

    Pausing 5 seconds to give service time to start listening
    Checking if Service is listening on port 3389
    Service is not listening
    Done
    Press any key to continue . . .

    The only firewall I have is the Vista firewall and the other protection I have is AVG 8.0 Free Edition. I check the terminal services and it is started and running. I have manually added port 3389 to my firewall but still to no avail. Any other ideas? Again, I appreciate such a quick reply. ^_^

  • http://andrewblock.net Andrew Block

    @Tom,

    Hey thanks for your comment. I’m sure you checked this, but you made sure to install the proper bit-strength (x86 or x64) on the desktop right? You didn’t accidentally run the wrong version? Also, you ran the proper batch file for your Vista version? Did you make sure to use “Run as Administrator”?

    Beyond the simple stuff, here’s some stuff to check.

    • Go to services.msc (Start->Run->services.msc->OK; if “Run” is not available, press Window Key + r). Is Terminal Services started?
    • Go to the Windows Firewall and make sure that Remote Desktop is allowed, OR manually allow port 3389.
    • If you have a third-party firewall (or security suite that includes a firewall), you might need to make an exception for port 3389 as well.

    Those are my initial thoughts. Let me know if you get it working. If not, maybe I can brainstorm some more ideas. Good luck! :)

  • Tom

    I’ve tried this hack and I got it to work on my laptop, but not my desktop. Both are running Windows Vista Home Premium with Service Pack 1 on them. On the laptop it installed with absolutely no problems as all, but when I installed it on the desktop, it went through everything but at the end, it said the Service was not listening. The desktop gets all the updates since it is the one that I really only use online so it’s all up to date. Is there anyway to fix this before I chuck this computer out the window? I want to connect to my desktop from my laptop just to make things clear. Thanks.

  • http://andrewblock.net Andrew Block

    @mac–sorry for the typo. I made the corrections to the file and re-posted. :)

    @Invader–it’s nice when products work like they should, isn’t it?

    @Mirek–very smart call on renaming the service. Is that terminology specific to the Czech version of Vista x64?

    @Ferry–thanks for the comment. I am glad it solved your problem. Please note I can’t take credit for the batch files or the registry entries. I just updated the DLL to 64-bit. The originals are found at:

    –http://www.unet.fi/fransblog/2007/08/30/enable-remote-desktop-connection-on-vista-home-premium/
    –http://portal.tonychan.org/Default.aspx?tabid=58&EntryID=123

  • Ferry

    Thanks! Your script is a live saver! I have Vista Home Premium with SP1 installed (x86) and with your script I can now remote desktop to it from other machine

  • Mirek

    Great, it works! I have Vista Home Premium x64 (Czech language) – I must change Buisness.bat before: on lines “net stop…” and “net start…” – I change “Teminal Services” to “TermService”. Now it fully works.

  • Invader

    Great Patch, I searched around and found the x86 patch, but the X64 patch didn’t seem to work from another webpage. Yours works flawlesly! Very Cool, Glad my new laptop will allow me to connect via Remote Desktop from my other locations.

  • mac

    great! Now it works :) Thanks a lot!

    Maybe you can answer another question that I have about RD: I would like to log into the PC with the same username over RD as “normally”. When I log in over RD, I would like to see the same work state as I left the computer when I logged out “normally”. With RD in WinXP this was not a problem, in Vista I seem to be opening a completely new (blank) login session …

    And a small thing: You named the file Buisness.bat, instead of Business.bat But I assume it will still work ;)

  • http://andrewblock.net Andrew Block

    Hey Tim,

    Great–I’m very glad this post helped you out.

    I too was annoyed when I found out I couldn’t remote into my new laptop from my other PCs. I am very glad this hack works. :)

    Thanks for reading.

  • Tim

    THANK YOU. Worked like a charm.

    When my computer arrived the other day with Vista Home Premium, I thought it went without saying that I could use Remote Desktop. My whole plan for the use of the darn thing required Remote Desktop. I was shocked when I realized it wouldn’t work out of the box like I wanted it to. This post solved my problem.

  • http://andrewblock.net Andrew Block

    @mac,

    Hi thanks for your comment. I am very sorry–my original zip file was missing one component. Please try the updated file. Tested and verified working on my Vista Home Premium SP1 x64 laptop.

  • mac

    Great Hack! :) Thank you Andrew for the 64-bit version. I installed it, and the service is running properly.

    I can connect from my laptop to the PC where RD is set up successfully. After I press the connect button, I am asked for credentials. When I enter wrong ones, I’m asked again (fine so far).

    But when I enter correct credentials, nothing happens! I get back to the screen and the connect button is re-enabled. Any ideas?