Windows XP Multiuser Remote Desktop

Remote Desktop ConnectionAn interesting feature, on Windows XP, is the ability to be remote controlled from a second PC: the so called “Remote Desktop Connection” can be used from a dial-up connection or in a local ethernet network.

XP (and Media Center Edition), differently than the Server versions of Windows, has a limit: a single PC can be controlled by a single “local” user (the “real” person on place), OR a single “remote” user. If someone logs into the computer security from remote, the local user is disconnected. The following procedure deactivates this block and allows multiple persons to connect and to use a single computer from remote.
Very useful, for example, if you’ve a very strong PC and you want your wife/friend/brother to use an old computer like a “terminal” to use applications on the new one, at the same time of you. Other application of the same technique: you’re at work and you want to connect to your home PC, without blocking your wife that is using the same computer to check email ;)

UPDATE: it seems that XP is limited, also after this modification, to 3 concurrent users. So don’t waste time trying to raise the maximum number of connections over three (see step 5) because, at this time, I don’t think there’s a way to use the same XP PC with more than 3 persons at the same time (e.g. a local user and 2 remote users).

This procedure is an “hack”: do it at your own risk:

STEP 1
Start your Windows in Safe Mode (tap on F8 first of the Windows Loading Splash Screen);
click on “My Computer” with right mouse button and choose “Properties”;
go to “Remote” tab and uncheck “Allow users to connect remotely to this computer” (if it’s already unchecked, just do nothing);
click OK.

STEP 2
Go to Start -> Control Panel;
open “Administrative Tools” and then “Services”;
double click “Terminal Services”, in the list;
choose “Disabled” for “Startup Type” option;
click OK.

STEP 3
Go to C:\windows\system32\dllcache;
rename the termsrv.dll file to termsrv.original or another name you like;
copy into the folder this unrestricted old version of termsrv.dll;
go to C:\windows\system32 (the upper folder of the current one);
do the same operation: rename termserv.dll also here, and put another copy of the file I linked above.

STEP 4
Click Start, then “Run…”, type “regedit” (without quotes) and press ENTER;
navigate in the Windows Registry Tree to reach this path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Licensing Core;
click with right mouse button on blank space in the right part of the registry window, choose “New” > DWORD, name the new key “EnableConcurrentSessions” (without quotes), then edit it and set its value to 1;
close the editor.

STEP 5
Click Start, then “Run…”, type “gpedit.msc” (without quotes) and press ENTER;
open Computer Configuration > Administrative Templates > Windows Components > Terminal Services;
double click “Limit number of connections”, choose “Enabled” and set the maximum number of concurrent connections you want to allow (2 or more), then Restart Windows in normal mode.

STEP 6
Go back to Remote tab of My Computer’s properties (see step 1) and activate “Allow users to connect remotely to this computer”;
Go back to “Terminal services” in “Services” (see step 2) and set its “Startup type” to “Manual”

Now restart Windows. Your operating system should be ready to accept multiple remote desktop connections ;)
Remember that you’ve to prepare different Windows Users for every “phisical” user that want to connect to your desktop, to autenticate with separate logins/passwords. User accounts configuration is reachable in the control panel, and the list of users that can connect to the PC is editable in the remote tab of My computer.

272 commenti

  1. Intrigued said:

    What exactly is this oldr version of the server dll? Does it mean older, fixed vulnerabilities will be back? Will windows update overwrite this older dll later?

  2. riccardo said:

    Maybe Windows update will overwrite it, I’m not sure.
    This is termsrv.dll version 5.1.2600.2055, from Windows XP SP2 RC1, if I remember.

  3. matt said:

    Have you come across anyway to get Remote Desktop to work on XP Home as a host?

  4. GCNaddict said:

    Is it possible to use the server 2003 version of the DLL? I would prefer using that one instead :P

  5. riccardo said:

    I can’t say anything about XP Home because I have only the pro edition, sorry! I hope someone will report information of its experience with the Home version.

  6. whispers said:

    HOME would be a nice “find”…I’ll keep my fingers crossed.

  7. David said:

    I know this may seem wierd but my C:\windows\system32\dllcache directory did not have the dll in it. the system32 did. and my terminal services did not have the “Limit number of connections” folder. Could you help me out here a little bit.

    XP SP2 build 2600

  8. tange1 said:

    This doesn’t seem to work if the machine is part of a domain.

  9. Rob Eberhardt said:

    There’s a MUCH easier way to do this. Try Sala’s Terminal Server patch: http://sala.pri.ee/?page_id=11

    I’ve done the manual way, but his patch makes it a cinch (single reboot).

  10. betbest1 said:

    Does this make it possible to use Remote Desktop with XP Home? Or does that still not work?

  11. Shawn Fairburn said:

    In re: This doesn’t seem to work if the machine is part of a domain.

    This probably wont work with a machine that is joined to a domain because after joining to a domain, fast user switching is disabled. I’m sure there is something that virtual terminal server uses that is disabled.

  12. kinkywala said:

    antiwpa.org .ru/Other/TerminalserverNoRestrPatch-1-1/

    This patch from the makers of antiwpa, works for windows xp home/pro, and windows 2003. Unlimited number of RDP sessions, and you don’t have to replace your termsrv.dll with an older version.

  13. Matt said:

    Anyone know if there is a 64-bit version available?

  14. John Q. Public said:

    Attention!

    kinkywala’s link appears to include atleast one known Trojan

  15. Natron said:

    From what I know, the old termsrv.dll is from an older build of XP. MS had considered allowing users to have this functionality but then decided against it since it goes against the “single-user” license of XP.

  16. Anonymous said:

    Can someone confirm the trojan claim especially as it applies to 2003? It seems to come with source

  17. Kat said:

    Just an fyi, this definitely does NOT work with the Win2k3 dll.

  18. Anonymous said:

    Soleiis kunnu 3 brka somu Windows XP teldu senn

    Gev gtur at hetta er eitt offisielt ‘hack’, sum man t gert upp egnu byrgd! MEN, hesin hevur funni tav hvussu man kann fa Remote Desktop at loyva fleiri brkarum somu XP teldu senn. Altso soleiis, at ein sterk Windows XP telda kann virka…

  19. Keith said:

    How much will it affect the security flaw in Windows XP?

  20. Chris Law said:

    If this is just using the file from the SP2 beta (when they were mulling over making concurrent sessions a feature), then yes, Windows Update will eventually screw it right back in place to 1 user at a time.

  21. Montanna said:

    Anonymous. I can confirm that the antiwpa.org.ru link does contain a torjan (Trojan.Win32.Agent.jh) according to message labs Scansafe.

  22. Sensoft2000 said:

    Very nice article…

  23. Timbo said:

    About kinkywala’s link. Don’t be too alarmed. It’s like saying VNC is a trojan. You can view McAfee’s page about it here: http://vil.nai.com/vil/content/v_136760.htm

    I hate how AV companies label all non-commercial remote access methods as trojans.

  24. stafari said:

    Ummm… why bother, use VNC. Seriously

  25. bill said:

    mabey cause vnc sucks? toolbag

  26. /var/log said:

    Hacking XP

    Via lifehacks.org, found a post on some site about allowing more than one terminal (RDP) connection to a Windows box!  Haven’t looked closely at it, but it sounds intriguing.

  27. drosan said:

    http://sala.pri.ee/terminal-server-patch/

    didnt scan it for virii though, just came across it

  28. bobo said:

    vnc works fine for 1 connection, the whole point of this is to be able to make multiple connections, so that’s why not to use vnc

  29. Anonymous said:

    VNC is not remote desktop, it’s remote control. There’s a difference. You don’t want another user using your desktop, you want them in their own session.

    THAT is why not to use VNC!!

  30. Mystere said:

    Please do NOT use this hack. It replaces your termserv.dll with an older version that contains at least one actively exploited vulnerability. I think you’re better off using the patchers that are out there.

  31. RedHot5 said:

    Timbo, what you stated about virus comompanies randomly labelling remote access software as trojans is not correct in this case.

    Here is a link to details about the Trojan.Win32.Agent.jh or as Sophos calls it the Troj/Dagonit-A trojan:
    http://www.sophos.com/virusinfo/analyses/trojdagonita.html

    I don’t think I would intentionally install this myself…

  32. Mike said:

    OK, OK, I have followed the guide. I went an extra step and created a new user with password on my test PC. What steps do I take next? On my main PC, what am I looking for to start the remote connection?

  33. Mike said:

    Nevermind, I was missing Remote Desktop shortcut, fixed it with http://www.5starsupport.com/xp-faq/1-29.htm

  34. frostbyte said:

    I am wondering if anyone knows of a similar hack for 2003 small business server. Microsoft has limited terminal server to remote desktop for admin purposes only. I would like to enable remote desktop for applications.

  35. Anon said:

    Just a clarification on this; my tests proved that this works but you should be aware that each connection requires a different username/password combo if you don’t want to log off the local user. This means that you cannot have someone connect to the console remotely at the same time that a local user is connected like you can do on Win2k3 Server. I’ve even tried using a Win2k3 Server termsvr.dll file but this does not change.

    And since you have to have fast switching on you will see the remote user’s icon on the logon screen each time someone logs on. Surprisingly, this is true even if you uncheck the “Use the Welcome Screen” (which disables Fast Switching) but change the Fast Switching service to Automatic and force it to start. Therefore the requirement seems to be not only that Fast Switching is on but that the Welcome Screen is on as well.

  36. John Daharsh said:

    I found this a few days ago, and opted to try Sala Source http://sala.pri.ee/terminal-server-patch/ from a suggestion in the comments (props to Rob Eberhardt) rather that follow the hack.

    Sala source is working great (for 3 days so far), I’ve upped the RAM on my machine and now two of us are sharing a workstation.

    This is a great find – whether you go through the process described in the article or you use something like Sala Source. It’s an absolute shame that this is disabled on Windows XP *Pro* – and a really great find that we can re-enable true “workstation” functionality.

    Some small obstacles I had to overcome were enabling fast user switching (Control Panel > User Accounts > Change the way users log on or off > Check “Use the welcome screen” and “Use fast user switching”.

    The final tiny obstacle is that I always log in using my Administrator account, and when you enable the welcome screen (necessary to enable fast user switching) you don’t have the option to log on as administrator. To get the Administrator login, just type ctrl-alt-delete twice when you are on the welcome screen and you can log in as Administrator if you need to.

  37. Zipper tha Seven said:

    You can’t use this patch on a machine that is a member of a domain because this hack involves editing the local group policy. On a domain, the domain group policy (as set by the domain administrator or enterprise administrator) takes precedence over *any* local policies. In effect, any changes you make to local policy are overridden by domain policy.

  38. Sharjeel said:

    Do you have a similar hack for windows 2000 server which allows more than 3 users to log on to a server

    Sharjeel
    http://www.sharjeel.net

  39. pentapenguin said:

    Thanks Ricky for that tip! I added your blog post here to my tutorial called “Accessing Your PC Remotely Part 1″ here: http://www.pentapenguin.com/forum/viewtopic.php?t=1853

  40. Mr Badger said:

    I ended with an XP Home addition kind of by accident and would really like to get to it via Remote Desktop. So this thread was an interesting tease. Has anyone tried the http://antiwpa.org.ru patch on a XP Home system?

    And any further word on whether it actually contains an infection? The McAfee link seemed to think it was harmless. The Sophos.com link didn’t seem to like it at all. But if you looked at what it was actually doing it pretty much looked like what would be necessary to enable and start Terminal Services and the Remote Desktop. Might be opening it up a bit wider then one would like – but didn’t look all that suspicious to me. But them I’m an embedded systems guy and only play with this Windows stuff out of necessity – so what do I know? :-)

    Mr Badger

  41. cc said:

    Will this work if I want to log on once using the local user and another time using a domain user?

  42. heppl said:

    :( :@

  43. Alex said:

    This thing doesn’t seem to work on winxp SP1. Has anyone a solution for this? (I know that the best way would be ’simply’ download SP2, but in my case it’s not a solution :( )

  44. Seba said:

    Very helpfull article. Solution works great for me:)

  45. dmz said:

    Hey, Im also intrested in a patch for 2003 SBS server, i need it for more than 3 users at a time :(

  46. coolkitty said:

    I have been using multiple user remote access for 3 of my offsite staff and it has worked great.
    What I need to know is, where do I go to see when / who is in session?

    Thanks

  47. Steeeve said:

    coolkitty,

    “where do I go to see when / who is in session?”

    this should show who is currently logged on, don’t know anything much about logs etc soz.

    ctrl + alt + delete to open up task manager and select the ‘Users’ tab, (either when logged on at the machine or when logged on remotely) . I’ve not actually tried this with this hack yet but I think it should work. Hope this is some kind of help ;-)

  48. me said:

    who know how to enable fast switching in a domain computer keeping the computer in the domain?
    or who can tell me other solution, because Windows XP Multiuser Remote Desktop wont work in a domain computer…

    I will be very appreciated if you help me.
    thanks

  49. Steven said:

    Its a big possiblity your right about antiwpa.org.ru combine a tojan with it my bank account was effected could be keylogger too, because I told no one my password and $500 was taken without my permission, though Paypal, just wondering if strange happen with it, it was traced to russia, althou there is no clear connection.

  50. EF said:

    Does anyone have a solution/software for a Windows XP Pro x64 multiuser remote desktop? Tried the termsrv.dll but it didn’t work?

  51. S E A N said:

    If you were wondering if this worked for Windows XP (SP1) — it does! The Sala patch listed above does not, though. Working with my clients, I’ve seen the problems with SP2 and Automatic Updates enough to know to avoid both. You are more likely to lose data and/or spend time recovering Windows due to Windows file corruption than virus/spyware/adware. Isn’t that sad!? Well, they don’t call it Microsloth Winblows for nothing. (not saying I have a better solution, but when it comes I’ll jump ship faster than a fly on crap).

    Note: You cannot use the same profile onsite at the same time as someone who is using Remote Desktop. Simply, you can use a different profile than the one being remoted to without being knocked off like before.

  52. ux said:

    Does anybody know how to patch WindowsXP 64bit to enable concurrent sessions ?
    Maybe with with dlls from Server 2003 64-bit ?

  53. Aj said:

    Hey Guys;

    I followed this hack long time ago & found it to work on only one machine. My other machine continued to kick the local user off. I’ve re-installed Windows on both of my machiens and re-applied the hack, but still neither works.

    I made sure the fast user switching & the welcom screen is checked off.

    I did a checksum on the old termsev file and found it still the ‘hack’ file, thus it hasn’t been re-patched by ms. Anyone else have similar problems.

    Any ideas?

    Also, anyone know how to avoid warning prompt on the the local machine, where the remote users is loggin in, Allow Deny button?

    TIA
    AJ

  54. shyam said:

    thanx for giving such a nice advise i appriciate all your efforts with lots of thanx ….. shyam india

  55. HooKy said:

    Thanks for the info. Works great on my end.

    Just wanted to comment on S E A N’s assinine comment that you should not update to SP2 or do any automatic updates. Clearly you are clueless. I feel sorry for any “clients” you may have, as you are not serving them at all well… Do some reading before making ridiculous posts like that…

  56. nick vaidya said:

    I am rather ignorant ….. can someone summarize the best procedure when the machine is part of a domain… step by step.. like a complete idiots guide.

    Nick

  57. raymond said:

    i have win xp sp2 ver 2550, and i install sala source patch and concurent remote session, it’s done well for unlimited rdp. But when i try with the new win xp sp2 ver 2600, it’s just work just for 3 RDP (4 with the win xp host). Did anyone find the new way?

  58. Deep Fat said:

    Probably a really obvious cock-up but for anyone that’s been having trouble with Sala’s Terminal Server patch I found I needed to follow step 1 of the manual approach first i.e. install the patch when Windows is running in safe mode. Otherwise, Windows File Protection kicks in and “mends” the “broken” file … Doh!

  59. James said:

    Great write up…something I didn’t know yet. Only problem is we’ll see if this hack (w/ the old dll) works when SP3 comes out.

  60. Lee said:

    The Sala patch is nice but this is nicer:

    http://xpunlimited.com/demo.html

    They give you unrestricted 3 user version for free. Works well and easier to install than Sala.

    Lee.

  61. BillWalter said:

    Have you found a way to inplement this functionality on VISTA RC1?

  62. keith said:

    Hey Rick,

    I attempted to use your hack for the Windows XP multi-user remote console. I followed your instructions to a tee (I think) with one exception. There is no “C:\windows\system32\dllcache;” directory as referenced in Step #3.
    After completing all other steps remote console sessions are still limited to 1.

    Any thoughts?

    many thanks,
    Keith

  63. riccardo said:

    Hello Keith,

    dllcache is a system folder: it’s probably hidden in your system, you’ve to go to tools->folder options->view and un-check “Hide protected operating system files (Recommended)” to make it appear.

  64. squirell said:

    hello,
    i have tried but it didn’t work…
    perhaps because the computer is a member of domain?
    if so, can we do something so we can still use multiuser remote desktop?

    thanks in advance,

  65. angelo smith said:

    hi,

    can any one explain me how to get the windows2003 sever accept domain users to login and use resources. I believe that with 2003 2 users can have concurrent sessions. Note i am using domain and need some of active directory users to log on to the server for some, still limited resources.

    thanks in advance

  66. angelo smith said:

    Hi kieth,

    I guess with XP there aint no dllcache. You can instead do the changes to c:windows/servicepackfiles and on c:windows/system32

    I tried it works…

  67. Ivan DSOL said:

    Hey guys…look… Im trying to fix this problem for several months…and i have found only tws olutions…well three if we hack the windows with termsrv.dll…

    One is WinConnect and the other one is XP Unlimited… This is what i want…but there is some tricky thing about XP Unlimited…

    Look… on web site of XP Unlimited there is a sentance that says something about open source of this solution…

    ***************************************************************
    Open Source

    Our Demo software will be made Open Source. One could argue that our software is somehow already “Open” because reading the Win32-API specifications on the Microsoft MSDN-site, specific the ones about desktops, will give you enough information to make your own XP Unlimited solution. Still, you want our solution, because it’s ready, available and cheap. You should not try to invent the same solution when you can already buy it for such a low price.

    ***************************************************************

    Well know…since im not a programer…i dont know what this is all about…but if there is an easy way to build this solutions and make it opensource that would be great…

    So if there is someone who can do it… and to share it with us… im ready to make some donations… ;)

    Greetz,
    Ivan DSOL.

  68. Woytaz said:

    I had a little trouble to get this “hack” working. In order to make it working the Fast User Switching option must be enabled
    (Control Panel–>User Accounts–>Change the way user log on or off –>
    And check both options Use Welcome Screen and Use Fast User Switching) and its working :)

  69. theUser said:

    This is a great tip for XP…

    How about Vista? I’m not even going to attempt to replace the DLL, as I’m sure it’s completely different by now… There has got to be a way for this to work in Vista as well, right?

    Thanks

  70. Patricia Govezensky said:

    Nice, I looked all over the internet for implementing this RDP thing

  71. Skweez said:

    I think this hack has been disabled after the release of a security upgrade. Is anyone experiencing this?

  72. Mariano said:

    The patch of sala’s is the best at the moment, but i can’t connect more than 3 users at the same time, how can i increase the number? (i increased the number in the TS configuration but it didn’t work)

  73. Mariano said:

    i found the way to connect more than 3 sessions, after install sala’s patch reboot, install this patch (first disable windows file system protection) http://www.lvllord.de/?lang=en&url=downloads#4226patch and reboot again

  74. Dansen said:

    Hi, I just applied your method to Win XP Pro 32, has anyone found a 64 Version already?

  75. Dan said:

    Will Microsoft’s Automatic Updates reverse our changes and replace the “hacked” termsrv.dll file with the original one? Is anyone experiencing changes after Windows Updates?

    Also, what are the risks we give our computer by doing this. Such as security risks and maybe the possibility of computer errors?

  76. Richard said:

    It seems that MS has already updated the flaw. I updates the system today and it won’t work again. Take care.

  77. Facundo said:

    Thanks, it just work perfectly, the only way to prevent security risks is creating secure passwords for your account

  78. Kel_Sceptic said:

    # Rob Eberhardt Says:
    April 25th, 2006 at 4:30 am

    There’s a MUCH easier way to do this. Try Sala’s Terminal Server patch: http://sala.pri.ee/?page_id=11

    I’ve done the manual way, but his patch makes it a cinch (single reboot).

    Thanks Rob and SALA for the great patch. Worked like a charm. Flawless Victory :) )

  79. MRM2006 said:

    Hi,

    Is there any solution for Win XP 64-Bit? none of xpunlimited or sala patch works!

    Please Help me!

    Thanks.

  80. rob said:

    at the university i work at, i tried to remotely connect to my office computer with my laptop but, the controls were blocked, i couldn’t tick where it says: “Allow users to connect remotely to this computer”. Do you have any idea how i can hack through without anyone noticing so that i would be able to tick that box?

    Thanks

    reply asap please

  81. Computer Reviews said:

    MRM2006 – I’m also looking for a solution for 64bit

    Have anybody found it..if so can you let us know

    Thanks
    Jim

  82. Sam said:

    Thanks, Rick.
    I tried what you said.

    In reponse to Matt, I don’t think Home Edition would work as afaik there is no option to enable remote connections in System / My Computer properties.

  83. Ryan said:

    Mr. Badger, your best solution might be to upgrade to XP Pro, and then apply the hack. You can turn an XP Home install disk into an XP Pro install. Google “Change XP Home Pro” to find out how.

    rob, you should be able to make direct Registry Edits so that you can “tick the box”, or use gpedit.msc, but I’m not 100% sure. Google “Allow users to connect remotely to this computer grayed out”. The first link I found was this:

    http://windowsxp.mvps.org/rdenable.htm

  84. Snappo said:

    i need a way to add it to xp home

    any ideas?

  85. B00 said:

    Have any of you tried any of these patches (manual, Sala, WinConnect or XP Unlimited) after Microsoft’s 12/12-2006 update?

    From WinConnect: “The latest WinConnect Server XP software does support Windows XP and Windows SBS 2003 Updates released by Microsoft on 12 December 2006.”

    And, is there a risk that Microsoft will claim that my Xp is not a valid XP after applying any of these patches?

    What differs WinConnect from the others? They claims support for up to 21 simultaneous users on XP home and XP pro! Do these guys have a deal with Microsoft or? (They do claim that you have to have one XP license per simultaneous user, but it is up tip the user to make sure…)

  86. Bob said:

    I have Windows XP Pro, and I don’t have a dllcache directory *anywhere*, nor
    a termserv.dll file?

    I’m using RDP successfully for one user, however.
    I have the latest MS updates applied…

    Any clues? I’m an XP newbie, is the “search/files” restricted to where it searches
    by default? Something I have to tweak? I told it to search for hidden and system files…

  87. Pet said:

    Any findings for XP 64bit?

  88. Techtoad said:

    I am running an upgraded version of windows xp pro, it was SP1, now its SP2, it used to be on a domain and the group policy is messed up. I do not have the option of a restore as i have software on the machine i dont want to lose which i dont have discs for… i tried running the salsa patch, but it says it has already been patched, it doest work so i assume a version conflict? the demo patch seems to work, but i lose the ability to use remote desktop externally (not via lan)

    I tried the manual way, and many other versions of the manual way, but all fail when gpedit.msc was required, i have finally hacked round the policy, i can now access it, but cannot find the LIMIT NUMBER OF CONNECTIONS.

    Does anyone have any ideas, i require seperate sessions at same times from 1 machine, my work travels around hundreds of computers and i have many users.

    I know this DEFINATLY IS POSSIBLE as i have almost completed it, but have found other problems.

    **REMINDER** when users have the option to kick the local or other remote user off, the clients dont have a choice, when multiple logons are available, this question is not asked. Hacking this version gives a MASSIVE security flaw, if u ever decide to remove it, ANY USER (even guest) can kick administrator, to fix this problem, restore the old.dll file replaced with the SAME BUILD as your OS (this can be found on the OEM CD)

    Thankyou for reading, anyone has any ideas, please let me know ;)

  89. Scorpion said:

    I tried the patch to increse more than 3 sessions. But its still not working
    what could be the problem?

  90. Harry said:

    A GUIDE FOR NON-EXPERTS

    Here is a definitive guide for this hack for people who may not be experts.

    This is a great program! Thankyou to those responsible.

    —————————–

    1. Example scenario:
    You are using your home computer (LOCAL) and you want to connect to your work computer (REMOTE) whilst someone/more than one person is already using it.

    —————————–

    2. Assumption:
    The REMOTE machine is using XP Pro, SP2 (Service Pack 2). (If unsure, go to Start | Control Panel | System, and read the information under the ‘General’ tab.)

    —————————–

    3. Setting up your LOCAL machine:
    You will need to have a User name on the LOCAL machine that is not already a User name on the REMOTE machine. (You already have one default account – probably ‘Admin’ – and you can use this User name – but if this name – e.g., ‘Admin’ – is already used on the REMOTE machine, you will need to change it.)

    To change your User name, simply follow the instructions at Start | Control Panel | User Accounts. (You might, for example, want to call yourself ‘Bill’.)

    If you decide to set up a separate User name, simply go to Start | Control Panel | User Accounts, and create an account. But bear in mind that your new user (desktop) settings will not be the same as those for your original account, so this is a second-best option.

    If there are other people who use your LOCAL machine, you might want to give yourself a password (to stop them being able to accidentally access your REMOTE machine). Otherwise, there is no need.

    —————————–

    4. Setting up the REMOTE machine:
    Log in as administrator on the REMOTE machine.

    On this REMOTE machine, go to Start | Control Panel | User Accounts and create a new account, using whatever name you gave yourself on the LOCAL machine (e.g., Bill).

    Make the account type ‘Computer administrator’.

    You will now be back at User Accounts | Pick a Task, on the REMOTE computer. Double click on the account you just created (e.g., Bill), and create a password (e.g., abc123).

    Using the Back button, return to User Accounts | Pick a Task, and click “Change the way users log on or off”. Make sure both boxes are ticked (actually, this may not really be necessary).

    Back in Control Panel, select Windows Firewall, and choose the appropriate option. (I chose “ON”; under “Exceptions”, I selected all five options. But a colleague of mine has his firewall turned off completely. You may wish to experiment a little.)

    Close control panel and go back to your desktop on the REMOTE machine.

    Download this patch onto the REMOTE machine, http://sala.pri.ee/?page_id=11, but DO NOT install it. (The download is very fast.)

    Turn off the REMOTE machine, and start it again in SAFE MODE (to do this, keep pressing F8 after the machine starts until you get to the options screen). Do not start the computer in normal mode!

    Once you are back at your desktop, run the patch you downloaded (double click it). Restart your REMOTE machine when prompted to do so in NORMAL mode. The whole process will take you only a couple of minutes.

    —————————–

    5. Accessing the REMOTE computer:
    You are now set up. (You may want to restart your LOCAL machine just to make sure everything is OK.) Now, to start Remote Desktop Connection on your LOCAL machine, go to Start | All Programs | Accessories | Communications | Remote Desktop, and click on it (you may like to make it a shortcut on your desktop if you use it frequently).

    Type in the IP address of the REMOTE computer (e.g., 211.11.111.11), and press CONNECT. The computer will ask you for your user name (which will the User name you gave yourself on the LOCAL and REMOTE computers (e.g., Bill), and your password (e.g., abc123).

    When you press OK, you will be on the REMOTE computer (make sure it is turned on!), and you will be able to work independently, even if someone else is already using it.

    —————————–

    6. Giving other people access to the REMOTE machine as well:
    Simply go to Start | Control Panel | User Accounts on the REMOTE computer and create an account for them (make sure the name they are using is different to all the other User names on the REMOTE machine; also make sure that it is the SAME name as their User name on their LOCAL machine).

    Give them a password.

    That is all! They can then connect to the REMOTE machine using Remote Desktop Connection from their LOCAL computer, in the way described above.

    —————————–

    7. Some final matters:
    a. As far as I am able to determine from the EULA (which I read carefully), this hack is not illegal.

    b. I am not sure, but I think the total number of users on the REMOTE computer at any one time is limited to three (3).

    c. When a person logs into the REMOTE computer, they will be independent to the person already using it. As such, the desktop will be different, and they will need to set up their own email accounts, etc. However, all the same files and programs will be there (i.e., exactly the same as for the original user).

    d. I am not certain, but I think the REMOTE computer needs to running Service Pack 2 (SP2).

    e. As far as I know, you can use this hack with XP Pro only (not XP home) on the REMOTE computer. However, you do not need XP Pro on the LOCAL computer (you can use Remote Desktop, for example, with Windows 2000 by downloading this program from Microsoft: http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx ).

    —————————–

    I hope this helps. Best wishes.

  91. Harry said:

    A mistake!

    Sorry, you DO NOT NEED TO SET UP ANYTHING ON YOUR LOCAL MACHINE.

    (My apologies – I was thinking of something else.)

    You only have to set up the REMOTE machine.

    Please ignore all of Point (3) in my previous post.

  92. noimp said:

    To make Vista RTM x86 support multiple connections termsrv.dll has to be patched like this:

    C:\Windows\System32>fc /b termsrv_patched.dll termsrv_rtm.dll
    Comparing files termsrv_patched.dll and TERMSRV_RTM.DLL
    000150D8: BA 3B
    000150D9: 00 91
    000150DA: 01 20
    000150DB: 00 03
    000150DD: 90 00
    000150DF: 89 0F
    000150E0: 91 84
    000150E1: 20 0C
    000150E2: 03 CA

    C:\Windows\System32>

    0100 (second and third byte) is the connection limit. In can be decreased or increased if needed.

  93. AMIT RAWAT said:

    HI
    I VERY IMPRESSED AFTER READING AND DOING SUCH TYPE OF WORK ON MY PC
    IT IS VERY FANTASTIC
    THANKS FOR THAT

  94. sunmorgus said:

    noimp…where do you get the termserv_patched.dll?

  95. MeMyself&I said:

    Thanks noimp!!! I’ve been waiting for two and a half months for this patch.

  96. qsw11 said:

    Re: the Sala patch.

    It says you cannot use if your Windows is in a domain.

    What does this mean? I have two computers at the remote site connected to a router. Does this count?

  97. seb said:

    Hello noimp,

    have vista build 6000 and would like to use the termsrv_patched.dll
    do you know where i can get hold of it?

    thank you!

  98. noimp said:

    Here is an enhanced version of the patch that adds one more byte:

    C:\Windows\System32>fc /b termsrv_patched.dll termsrv_rtm.dll
    Comparing files termsrv_patched.dll and TERMSRV_RTM.DLL
    000150D8: BA 3B
    000150D9: 00 91
    000150DA: 01 20
    000150DB: 00 03
    000150DD: 90 00
    000150DF: 89 0F
    000150E0: 91 84
    000150E1: 20 0C
    000150E2: 03 CA
    000154BF: 90 43

    C:\Windows\System32>

    with this additional byte terminal services will check the registry HKLM\System\CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser and if will reconnect to the existing user sessions if this is 1 or create a new session if this is 0.

    To patch the file you need to use some kind of hex editor. Make sure that original version and patched version differ in exactly this locations by verifying with fc. Also to overwrite termsrv.dll you need to change the file’s owner and permissions as by default the ACL allow write only for TrustedInstaller.

  99. sunmorgus said:

    Here is a link to the patched dll (the first one mentioned by noimp):

    (wrong address)

    Also, http://www.missingremote.com has a guide up now with this link to enable the concurrent sessions…

  100. sunmorgus said:

    Sorry…typo…should be:

    (wrong URL)

  101. DeOS said:

    Will the vista patch also work on the 64-bits version of the dll? I’ve got the feeling that it’s a bit different from the 32-bits version.

  102. sunmorgus said:

    Won’t work in the 64 bit version. noimp…can you give me some insight as to how you enabled this in the 32bit version? I have scrolled through some of the 64bit dll, and found some similarities, but nothing really concrete. If you would like, I can email you the 64bit dll so that you can take a look. Let me know. Thanks!

  103. noimp said:

    Here is the patch for x64 Vista RTM:

    fc /b termsrv_x64_patched.dll termsrv.dll
    Comparing files termsrv_x64_patched.dll and TERMSRV.DLL
    0005BC8F: B8 8B
    0005BC90: 00 81
    0005BC91: 01 38
    0005BC92: 00 06
    0005BC94: 90 00
    0005BC95: 89 39
    0005BC97: 38 3C
    0005BC9B: EB 75
    0006523E: 00 01

  104. DeOS said:

    Tnx noimp! You made my day!

  105. sunmorgus said:

    Thanks again noimp!

    64bit dll can be found here:

    (wrong URL)

  106. nelison said:

    (wrong URL)

    This patch from the makers of antiwpa, works for windows xp home/pro, and windows 2003. Unlimited number of RDP sessions, and you don’t have to replace your termsrv.dll with an older version.

  107. nelison said:

    and x64

    enjoy…

  108. noimp said:

    Vista Premium’s remote desktop can be enabled by adding one more byte to the patch:

    Comparing files termsrv_patched.dll and TERMSRV_RTM.DLL
    000150D8: BA 3B
    000150D9: 00 91
    000150DA: 01 20
    000150DB: 00 03
    000150DD: 90 00
    000150DF: 89 0F
    000150E0: 91 84
    000150E1: 20 0C
    000150E2: 03 CA
    000154BF: 90 43
    0004943C: EB 74

    There are also missing many registry entries so these should be added. Here is .reg file for import:
    ———————————–
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
    “fDenyTSConnections”=dword:00000000
    “StartRCM”=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Clip Redirector]
    “Type”=dword:00000003
    “Name”=”RDPClip”

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\DND Redirector]
    “Type”=dword:00000003
    “Name”=”RDPDND”

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Dynamic VC]
    “Type”=dword:00000000
    “Name”=”\\Device\\DrDynVc”

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Sound Redirector]
    “Type”=dword:00000003
    “Name”=”RDPSound”

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Terminal Server Redirector]
    “Type”=dword:00000000
    “Name”=”\\Device\\RdpDr”

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration]
    “fInheritAutoLogon”=dword:00000001
    “fInheritResetBroken”=dword:00000001
    “fInheritReconnectSame”=dword:00000001
    “fInheritInitialProgram”=dword:00000001
    “fInheritCallback”=dword:00000000
    “fInheritCallbackNumber”=dword:00000001
    “fInheritShadow”=dword:00000001
    “fInheritMaxSessionTime”=dword:00000001
    “fInheritMaxDisconnectionTime”=dword:00000001
    “fInheritMaxIdleTime”=dword:00000001
    “fInheritAutoClient”=dword:00000001
    “fInheritSecurity”=dword:00000000
    “fPromptForPassword”=dword:00000000
    “fInheritColorDepth”=dword:00000001
    “fResetBroken”=dword:00000000
    “fReconnectSame”=dword:00000000
    “fLogonDisabled”=dword:00000000
    “fAutoClientDrives”=dword:00000001
    “fAutoClientLpts”=dword:00000001
    “fForceClientLptDef”=dword:00000001
    “fDisableEncryption”=dword:00000001
    “fHomeDirectoryMapRoot”=dword:00000000
    “fUseDefaultGina”=dword:00000000
    “fDisableCpm”=dword:00000000
    “fDisableCdm”=dword:00000000
    “fDisableCcm”=dword:00000000
    “fDisableLPT”=dword:00000000
    “fDisableClip”=dword:00000000
    “fDisableExe”=dword:00000000
    “fDisableCam”=dword:00000000
    “Username”=”"
    “Domain”=”"
    “WorkDirectory”=”"
    “InitialProgram”=”"
    “CallbackNumber”=”"
    “Callback”=dword:00000000
    “Shadow”=dword:00000001
    “MaxConnectionTime”=dword:00000000
    “MaxDisconnectionTime”=dword:00000000
    “MaxIdleTime”=dword:00000000
    “KeyboardLayout”=dword:00000000
    “MinEncryptionLevel”=dword:00000001
    “ColorDepth”=dword:00000001
    “NWLogonServer”=”"
    “WFProfilePath”=”"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs]
    “rdpclip.exe”=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Utilities]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Utilities\change]
    “winsta”=hex(7):31,00,00,00,57,00,49,00,4e,00,53,00,54,00,41,00,00,00,63,00,68,\
    00,67,00,6c,00,6f,00,67,00,6f,00,6e,00,2e,00,65,00,78,00,65,00,00,00,00,00
    “port”=hex(7):30,00,00,00,31,00,00,00,50,00,4f,00,52,00,54,00,00,00,63,00,68,\
    00,67,00,70,00,6f,00,72,00,74,00,2e,00,65,00,78,00,65,00,00,00,00,00
    “logon”=hex(7):30,00,00,00,31,00,00,00,4c,00,4f,00,47,00,4f,00,4e,00,00,00,63,\
    00,68,00,67,00,6c,00,6f,00,67,00,6f,00,6e,00,2e,00,65,00,78,00,65,00,00,00,\
    00,00
    “user”=hex(7):30,00,00,00,31,00,00,00,55,00,53,00,45,00,52,00,00,00,63,00,68,\
    00,67,00,75,00,73,00,72,00,2e,00,65,00,78,00,65,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Utilities\query]
    “winsta”=hex(7):31,00,00,00,57,00,49,00,4e,00,53,00,54,00,41,00,00,00,71,00,77,\
    00,69,00,6e,00,73,00,74,00,61,00,2e,00,65,00,78,00,65,00,00,00,00,00
    “appserver”=hex(7):30,00,00,00,32,00,00,00,54,00,45,00,52,00,4d,00,53,00,45,00,\
    52,00,56,00,45,00,52,00,00,00,71,00,61,00,70,00,70,00,73,00,72,00,76,00,2e,\
    00,65,00,78,00,65,00,00,00,00,00
    “session”=hex(7):30,00,00,00,31,00,00,00,53,00,45,00,53,00,53,00,49,00,4f,00,\
    4e,00,00,00,71,00,77,00,69,00,6e,00,73,00,74,00,61,00,2e,00,65,00,78,00,65,\
    00,00,00,00,00
    “process”=hex(7):30,00,00,00,31,00,00,00,50,00,52,00,4f,00,43,00,45,00,53,00,\
    53,00,00,00,71,00,70,00,72,00,6f,00,63,00,65,00,73,00,73,00,2e,00,65,00,78,\
    00,65,00,00,00,00,00
    “user”=hex(7):30,00,00,00,31,00,00,00,55,00,53,00,45,00,52,00,00,00,71,00,75,\
    00,73,00,65,00,72,00,2e,00,65,00,78,00,65,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Utilities\reset]
    “winsta”=hex(7):31,00,00,00,57,00,49,00,4e,00,53,00,54,00,41,00,00,00,72,00,77,\
    00,69,00,6e,00,73,00,74,00,61,00,2e,00,65,00,78,00,65,00,00,00,00,00
    “session”=hex(7):30,00,00,00,31,00,00,00,53,00,45,00,53,00,53,00,49,00,4f,00,\
    4e,00,00,00,72,00,77,00,69,00,6e,00,73,00,74,00,61,00,2e,00,65,00,78,00,65,\
    00,00,00,00,00

    ————————-
    That’s all. Enjoy!

  109. Jose Luis said:

    Problme with Multiuser Remote Desktop
    I have 2 Pc conected by switch with win XPsp2.
    when I stablish conection from the Local Machine, in the Remote Machine , the process pctspk.exe begin to use 98% of CPU. It have a Modem HSP56.
    How I could to solution this problem?
    Help me Please.
    Thanks

  110. Scuffs said:

    noimp,
    Thanks a LOT for getting this working. If you have some spare time, do you think you can try getting MCE to display across RDP? If you try now it says it wont work through Remote desktop. Extenders use RDP sessions to hook up so it should be possible.

  111. RDP User said:

    Hi all, this really cool and help me to on desktop virtulization, despite Widows Terminal Server & Citrix Metaframe in a small deployment :P
    By the way, does anyone of you have try video playback using RDP? I found the sound and picture of the video is not sync?

    Thanks in advance if you have tips to overcome this issue :)

  112. Desperate Dan said:

    Can someone please re-upload the patched version of termserv.dll which allows more than 3 active connections

    thanks.

  113. JJ said:

    This hack is dangerous. I am having trouble with Windows XP several weeks after and have been attacked by someone.

  114. Chris Baker said:

    This might come in handy for some of you

    Converting Windows XP Home Edition to Windows XP Pro:

    1. go to HKEY_LOCAL_MACHINE/SYSTEM/ControlSet00X/Control/ProductOptions
    where ControlSet00X is the one with the highest number and delete
    the key “ProductSuite” completely.

    2. Create a new key named “Brand” of type “DWORD” and set it’s value to “0″.

    3. Reboot the system.

    4. After BIOS-screen, press F8 and choose “Last Known Good Configuration”.

  115. ocnsss said:

    On personal opinion, I find this very helpful.
    Guys, I have also posted some more relevant info further on this, not sure if you find it

    useful: http://www.bidmaxhost.com/forum/

  116. Matt said:

    # nelison Says:
    February 21st, 2007 at 9:46 pm

    (wrong URL)

    This patch from the makers of antiwpa, works for windows xp home/pro, and windows 2003. Unlimited number of RDP sessions, and you don’t have to replace your termsrv.dll with an older version.

    I did a test of being suspicious and scanned it with Norton Anti Virus and it saw it as a trojan. I would not advise anyone to try this out.

  117. rupanshu said:

    If any body want to do this on domain then here is the hack:—
    1. Download this. http://concurrentremotesessions.netfirms.com/Concurrent_Remote_sessions_SP2.zip
    2. Extract the zip…
    3. Double click on Install.bat.
    4. Reboot.
    That is all, you are set to go!
    if u see windows warning while installing then just ignore that
    if u r in domain as i’m then just put
    enable Concurrent Remote sessions SP2.bat
    to all users statup.
    one more thing i did was to put it on scheduled task to run every 3 min as the domain policy will update after a predefined time interval and it will also change this reg key.
    More info about the “Windows Task Scheduler” can be found here: http://www.iopus.com/guides/winscheduler.htm
    the only problem with this was whenever i closed any rdp connection without log off , all connections get lost after a few mins… but if i log off properly then log in..it worked fine for me..and i was able to connect 10 users remotrely (however i didnt try for more….)!!!!!!
    hope this will help u all…..enjoy n dnt forget to mail me at fms24@hcl.in if u get success……cheers!!!!!!!!!!!!!

  118. Daniele said:

    Tutto ok e seguendo la procedure è estremamente facile!! Ottimo per chi ha Windows XP anche con SP2 e vuole farlo “diventare” un Windows Server.

  119. SteelNerver said:

    OK, anyone got any ideas? I have a XP HOME SP2 machine here at home and I want to be able to connect to it from work, doesn’t matter if I kick a local user off(I just won’t log on if i set process’ to run before i left the house) I’m a network admin(interning at the moment since I’m still in highschool) so I know enough, just not much about individual machines. What’s the best way to do this?

  120. Netter said:

    This hack doesn’t work in a DOMAIN

    I have checked that Fast user switching is running

    enableConcurrentSessions is set to 1

    allowMultipleTSSessions is set to 1

    Yet when i try RDP as another user from another machine to my pc, i still get the message I will be kick off !!!

    Please help!!!

  121. JohnGreen said:

    i can’t get desktop remote to work at all from a client pc? i have enabled my new pc to allow remote connections and typed in my ip address from the client but it only gets to the password and user name …when i send it or clik ok it tell mer this pc cannot connect to the remote pc and to check with the remote pc administrator? i have set the ip and the dhcp and dns to static and so on for the modem the only thing i don’t get is the port forwarding? do i do this on the remote pc only? do i need to do so at all? qwest wanted to sell me a domain to set up a static ip address?$ okay so what am i missing? the modem is dsl it is an action tech gt701 thanks ahead of time

  122. Bohdan said:

    Rar archive with both 64 and 32 bit versions of the hack plus automated bat files for business, premium and ultimate versions.
    (wrong URL)

  123. Netter said:

    Hi

    Does anyone know what happened to the sig9 forum regarding concurrent RDP session on XP ? The whole website seems to be down

    Can anyone help me on how to get concurrent RDP work in a DOMAIN environment ? Tks

  124. Andrajos said:

    Just a comment to rupanshu: you can automate silently the ‘enable Concurrent Remote sessions SP2.bat’ executinon just exporting the keys to a reg file and adding the following str entry to HKLM\Software\Microsoft\Windows\CurrentVersion\Run:
    regedit /s (with full path)

  125. Andrajos said:

    To JohnGreen: perhaps you need to made the hack first with the computer not in the domain and later join to it again.

  126. Netter said:

    Hi Andrajos,

    Did you manage to get it work in a domain environment ?

    No matter if I did the hack before joining the domain, it still won’t work in a domain

    I have also checked the EnableConcurrentSessions and AllowMultipleTSSessions value and it’s set to 1. Yet I’m unable to get concurrent multi RDP connection :(

  127. Q said:

    Antivirus software detects that “TermSrvNoRestrPatch” because it contains regfile (TS_Free.reg) similar to some trojans. Most probably it’s more safe than using that old termsrv.dll file.

  128. Andrajos said:

    Hi Netter: it happens to me the same making it on a diferent computer: all registry modifications made, inluding the ‘Run’ one, but it seems not to work. What we’ve done is just unjoining computer, try the multiple RDP with administrator and a new local user (it works) and then rejoin to the domain: it works! If I have time, I’ll try to make an step to step instructions. Regards.

  129. ma said:

    Hi.. just wondering if this leaves the RDP protocol open to any exploits by using an older version of termserv.dll. I know there were some RDP exploits that were fixed in SP2.

    I leave my RDP open to the internet. Although it is on a high port and restricted by IP address, I still want to be sure I’m not opening up the system to attack.

    Thanks.
    mike

  130. Arun Goel said:

    i am using windows server 2003, i want to incrage number fo remote desktop connection pls help.

  131. Anarchist said:

    Working in a domain

    Create a folder c:\termserv
    Inside this folder create a registry key called “Concurrent Remote Sessions SP2.reg” with the following:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]
    “EnableConcurrentSessions”=dword:00000001
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
    “MaxInstanceCount”=dword:00000003
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Terminal Server\Licensing Core]
    “EnableConcurrentSessions”=dword:00000001
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    “AllowMultipleTSSessions”=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\terminal server\
    “TSenabled”=dword:00000001

    Windows will set the value “0″ in the regkey “AllowMultipleTSSessions”=dword:00000001 every time your computer starts if machine is part of a domain. So you have to set that key to “1″ after win has set it to “0″. To reset this value we create a service which runs at boot time. At the command prompt type: “c:\termserv\instsrv.exe XP3RDC c:\termserv\srvany.exe”
    (instsrv and srvany are part of the MS Resource kit)

    In the registry locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\XP3RDC

    Add a key with the following:
    Key Name: Parameters
    Class:

    Select this newly created Parameters key and add the following value:
    Value Name: Application
    Data Type: REG_SZ
    String: c:\windows\regedit.exe /s “c:\termserv\Concurrent Remote Sessions SP2.reg”

    Your machine now has a service which will reset your registry to allow concurrent remote sessions every time it boots in a domain.

  132. Santa said:

    Windows XP SP2 no user limit
    C:\WINDOWS\system32>fc /b termsrv_rtm.dll termsrv_patched.dll
    Comparing files termsrv_rtm.dll and TERMSRV_PATCHED.DLL
    00022859: 74 75
    000228DE: 7F 90
    000228DF: 16 90

  133. Netter said:

    Hi,

    Where can I get the unlimited termsrv_rtm.dll file ?

    Good to see this forum still active :) thanks to all contributors

    1. Is it possible to make the xp hack work on xp home edition

    2. Is it possible to have multiple sessions for the same user?

    tq

  134. Hoekstes said:

    This is the most informative blog i’ve read in a long time. Thanks to all the contributors!

  135. Dave said:

    A question for Anarchist regarding his help for getting this to work in a domain:

    which .dll file do we need to use? i have done all you say but still only one user allowed :-(
    The only thing i can think of now is that i’m using the incorrect .dll

  136. Juggernaut said:

    “where do I go to see when / who is in session?”

    Copy tsadmin.exe from Win2K3 Server \system32 directory and use it. If you don’t have a Win2K3 Server available, download its Service Pack 2 (x86 version) from Microsoft and extract the file manually. Works great.

  137. Juggernaut said:

    # Matt Says:
    March 30th, 2007 at 8:05 pm

    (wrong URL)

    - -

    I did a test of being suspicious and scanned it with Norton Anti Virus and it saw it as a trojan. I would not advise anyone to try this out.”

    It is recognized as a generic hacktool as it patches winlogon.exe. I installed it first on Virtual PC for the sake of safety. Works fine and scanning the whole virtual hard disk mounted on another virtual machine with multiple online (Panda, TrendMicro, Bitdefender) as well as local (Avast, AVG, Kaspersky, Norton) antivirus scans results no infections. AVG Anti-rootkit finds no rootkits and Spybot Search & Destroy as well as AVG Anti-spyware say that the computer is clean.

    It also works perfectly. With tsadmin.exe from Win2k3 Server I can control multiple simultaneous sessions:

    http://img407.imageshack.us/img407/1647/05gn5.png

    Tsadmin works just like in real Windows Server with remote control option:

    (this image has been removed)

    and finally, I can log on with the same account both in the console and with the Remote Desktop Connection simultaneously:

    http://img210.imageshack.us/img210/2010/sameaccountmultiplesessyr5.png

    For reasons unknown, the text on the left side of classic Start Menu reads “Windows Terminal Server”, not “Windows XP Professional”.

  138. Jamie M. said:

    Hey Folks. I got the termsrv.dll hacked to allow “unlimited” users (really it is set to 99) to log into XP!!

    http://www.likestuff.com/termsrv.dll

    I did some big tests with some thin clients. Here are my results:

    5 thin clients on 512mb ram, no problem. If you close the connection instead of logging off, when you try and log back in you get booted with TCP/IP error 4226. Download the 4226 patch at http://www.likestuff.com/EvID4226Patch.exe and set the connections to at least 50.

    10 thin clients got some resource errors on 512mb ram. On 1 gig, no problem. Opened lots of copies of word, excel, etc. Had my 4226 patch set at 100 connections.

    20 thin clients needed 2 gigs of ram to have each one open both word and excel. I had my 4226 patch set to 500.

    When the 21st user tried to login, I got an out of virtual memory and a BSOD (invalid page fault in module svchost.exe). I didn’t have more then 2gigs of ram to try, so not sure if that woulda helped.

    Anyway folks, enjoy!

    (this image was removed from the remote server)

    And video:
    (this video was removed from the remote server)

    Sweeeeet.

    -Jamie M.

  139. Naresh Prajapati said:

    hi

    i have do as per ur solution but still i have to suffre this problem in xp
    i m not able to multiple remote login
    i have changes in registry $ group policy but still working same

    please be need full

    Regards,

    Naresh prajapati

  140. Snix said:

    is there any solution making the remote desktop connection server to try to connect to the client, because my server(home computer) is behind a router and I cannot setup the port mapping for local.

    Thanks

  141. Coello said:

    Jamie: It really works thats greate !
    But the “users” tab in the task manager is gone, is there any way to get it back ?

  142. Coello said:

    Hi, Try open the port 3389 in your router and configure windows firewall to admite remote desktop connections

  143. As said:

    Is there a solution for x64 Home Premium? looking over at the missingremote site a number of people have said the 64bit dll doesnt work for home premium. I have had the 32bit dll working fine for 32bit Home Premium, but in Home Premium x64 the 64bit dll wont allow any connection, with the client machine seeing no error message.

  144. Mike said:

    I’m having a hard time understanding this. I recently had a laptop set up on my TV so I could play movies and the like, controlled from my desktop. I have since given the laptop to my parents and am now trying to configure a desktop for the same thing. The thing I don’t get is the laptop obviously wasn’t logged off, or I wouldn’t get output on the TV. I never messed with the registry or policies or anything like that. But now I can’t configure the desktop to do the same. I don’t want to modify it, because it belongs to my roommate. I just don’t understand how I had it work before with no issues and now everybody says it’s impossible without extensive modification/patching of system files…

  145. DP said:

    Be very careful – We setup this for a home user in our small office and there is a serious vulnerability in the above suggestions. Our server was working vry slowly for a couple of days & we found a hidden user a/c. When we logged into this account there was email software sending out thousands of spam from our server. The software that was installed had a “network aware” virus and it is 11pm and we are in the office reinstalling xp/office/etc on every PC !! I advise to look at commercial thin client software – being hacked is not worth the $100 saved. D

  146. Netter said:

    Hi DP,

    Which hack version did you use ? Was your firewall running ?

    If you are going the commercial route, you might wanna check out ThinServer XP at :-

    http://www.aikotech.com/thinserver.htm

  147. Kamran said:

    hi can someone tell me that i dont have remote desktop connection in my start menu how can i get it back ……… someone deleted it from my computer.

    thnkz

  148. Netter said:

    What’s going on with this website ?

    Looks like being spammed :(

  149. Bill Gates said:

    Please remove this website.

  150. darkman said:

    bill gates 0wnz :D

  151. Steve Jobs said:

    If all fails you can always go for Winconnect or ThinServer

    ThinServer is having a sales now

    http://www.aikotech.com/thinserver.htm

  152. me said:

    start/run/
    %SystemRoot%\system32\mstsc.exe

    for remote desktop connection

  153. Quantum Networks said:

    quote: Kamran Says:

    November 22nd, 2007 at 9:11 pm
    hi can someone tell me that i dont have remote desktop connection in my start menu how can i get it back ??? someone deleted it from my computer.

    thnkz

    start
    run
    mstsc

    or even faster is ms logo + r , then type mstsc.

  154. Yanwz said:

    Has some one made Multiuser Remote Desktop successfully under Windows XP x64 Edition? Does x64 dll file works?

  155. zarraza said:

    has a definitive resolution been achieved for SBS2003? i have read this page a couple times and see XP, and Vista now, but no definitive answer for SBS

    would a termsrv.dll from a non SBS 2003 server cure those ails? and i’m assuming a couple registry hacks! :-)

    any help would be appreciated

  156. Netter said:

    hi zarraza,

    For Win2003 SBS, you can try Winconnect at :-

    http://www.thinsoftinc.com

    You can try to rip their termsrv.dll off and see if it works on the regular hack :)

    As for regular XP, you can try ThinServer at :- http://www.aikotech.com/thinserver.htm

    They offer free software now as part of their promotion

  157. web_knows said:

    for those who couldn’t download the dll linked on this post, here is a version that works with win xp pro sp2:

    http://members.lycos.nl/nessyh/files/termsrv.dll

  158. MouthpiecePC said:

    Ok, I read 3/4 of this thread. I am running XP Pro. My mother whom lives 2000 miles away, “U.S.”, is running Windows XP Home SP2. I need to connect to her coomputor and resolve some issues she is having. I noticed on her PC, “WinXP Home”, there is no option to enable other users to connect in the system properties option. Can someone please give me advice on how I can connect to her PC using RDC from my computor that is running XP Pro. Thankyou in advance for the help.

  159. Jarko said:

    I have been successed connecting 10 concurrent remote desktop clients using patched version of termsrv.dll. But randomly in time the network performs slowed connection between clients and server and eventually ALL client connections drop. This can happen once a day and sometime more. Where does this problem reside? Anyone ever experience this? Pls help.

  160. Jarko said:

    Sorry, I am using winxp pro sp 2, core 2 duo proc, 1 GB ram, gygabit ethernet running 100 MBps full duplex as server machine.

  161. edd said:

    Just installed Vista SP1 and unfortunatly the tervserv.dll has been updated, noimp: can you tell us how to patch this new version ? I can send you the file if you like

  162. edd said:

    by the way, I also tried with the previous version of termserv.dll but that didn’t work

  163. edd said:

    just tried patching the file searching for the hex codes comparing with the old version, but there seems to be a small difference, this is what’s in the new version:

    3B 91 20 03 00 00 5E 0F 84 31 EF

    here’s where it differs from the RTM version of termserv.dll, the 2 last bits are different (31 EF) so I’m not able to patch the file …

  164. man said:

    MouthpeicePC
    I have used the windows messenger remote desktop feature to connect to my mother’s pc (xp home). You just have to both have a messenger account.

  165. GarberFC said:

    I’m planning on applying the hack to my XP 64 SP2 PC. I find two different flavors of the dll on this page. One is 126,960 bytes bytes, the other that is inside the termsrv.rar file is 499,202 bytes?

    The file in my C:\WINDOWS\system32\termsrv.dll is 364,032 bytes!

    How can I tell which file may be for XP64 vs. all the flavors of Vista?

    Please let me know…

  166. GarberFC said:

    Then there’s web_knows version here: http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-multiuser-remote-desktop/#comment-85601 . He states it’s for XP Pro SP2, but doesn’t say weather it’s for 32 or 64 bit. That file size is 215,552 bytes.

  167. Usarryglalley said:

    I am necessary wish to find

  168. Netter said:

    Anyone got it running on win xp pro 64 bit ? Heard Thinserver is coming out wth a 64 bit version …

    http://www.aikotech.com/thinserver.htm

  169. josego said:

    I have it working inside a domain!!

    Simply follow instructions included in:
    http://concurrentremotesessions.netfirms.com/Concurrent_Remote_sessions_SP2.zip
    Thank you rupanshu!
    rupanshu’s comment: http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-multiuser-remote-desktop/#comment-43400
    (I don’t know why but download failed with firefox and worked with IE)

    I also followed the complicated instructions from Anarchist without success, but thank yoy anyway, I have learned how to manually create a service
    Anarchist’s comment: http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-multiuser-remote-desktop/#comment-56153

    Thank you

  170. 888 said:

    NETMEETING includes Remote Desktop Sharing.
    On a Windows 2000 or XP machine fire up Netmeeting, set it up, activate RDS and leave RDS on, turning off NetMeeting itself.
    All you need is an Administrator (or other account with admin priviledges).

    With NetMeeting’s RDS you can control any Windows machine (starting from Windows 95) from any other Windows (i.e. you can log on to Windows 2000 from a Windows XP, or even from a Win95/98/ME machine).

    Windows XP have NetMeeting hidden. Start->Run, type “conf.exe” and press enter to start NetMeeting on XP.
    Or.
    Right-click on the desktop anywhere, create new shortcut, type “conf.exe” there (no quot. of course), name it “NetMeeting” and voila, you have your NetMeeting shortcut on the desktop from now on.

    If the machine you want to connect to (and control it remotely) is other than Windows XP, you can do it with NetMeeting’s RDS.
    If you want to connect to XP from other machine, just use Remote Desktop Client obviously (since it is better on XP than NM’s RDS).

  171. na1.4 said:

    Has anyone got a dll or suggestion on which one to use for windows xp sp2 64-bit?

  172. Vincent BOURDEAU said:

    edd : I have a similar problem like you on Microsoft Windows Vista Service Pack One (MS Windows Vista SP1) x86 (32-bit) french builtin.
    The RDP has changed, so the previous version doesn’t work. Where can I find the MS Windosw Vista (not SP1) termsvr.dll genuine (not patched) to see changes ?
    Where and what are the digits to change ?
    Sorry for my english level, but I’m french ;)

    Has anyone got a dll or suggestion on which one to use for Microsoft Windows Vista SP1 x86 ?
    Thank you very much.

  173. Netter said:

    na1.4,

    Looks like a lot of people is looking for the 64 bit version. Heard some time ago Aikotech is coming out with a 64 bit version but no time frame yet. Anyone found anything? Anyway they have a new version out ( 2.2 )

    http://www.aikotech.com/thinserver.htm

  174. John Avgeros said:

    Just posting my experience with XPUnlimited:

    The software is good as long as you don’t have to call them! I spoke to a guy who just didn’t want to help!!! I never received the License Code and although i sent them several emails through the registered email address they claimed they never got them… When i asked for an alternate way to get the License Code (ie: by faxing them the invoice etc…) they said it can’t be done. Bottom line when i asked them about the money they said they automatically refund the money if the License Code (which i never got) isn’t activated within 30 days… As for me… I’ll try Thinstuff….

  175. Netter said:

    John Avgeros,

    Sorry to hear abt your experience. From their website, you can tell that they are not professional. You may want to consider ThinServer XP ( http://www.aikotech.com/thinserver.htm ). The software is very easy to install, just key in the included passcode and you are good to go :)

  176. Kevin K said:

    I am having a weird problem. When I set up remote desktop to run a program on my server, when I exit the program the remote desktop hangs during the log off sequence. This started when I installed XP SP2 on the server. When I did not have SP2 and exited the program the RDP session closed fine. Anyone see this problem? I installed XP SP2 so I could set up the multi-user terminal server on my xp server PC. I got that working using Sala’s Terminal Server patch: http://sala.pri.ee/?page_id=11. His patch only works with SP2.

    Got multi user working and broke the ability to run a program….

  177. Daniel Jarrett said:

    Thank you very much. I followed your instructions and everything worked great on Vista Home Premium.

    Has SP1 interfeared with this fix at all? I tryed to remote in today after installing SP1 last night and I’m having problems.

    PLease, Please, Please advise.

    Thanks again,
    Daniel S. Jarrett
    jarrett001@comcast.net

  178. Phantasm4489 said:

    Windows XP SP3 RTM no user limit
    E:\WINDOWS\system32>fc/b termsrv.bak termsrv.dll
    Comparing files termsrv.bak and TERMSRV.DLL
    00022A17: 74 75
    00022A69: 7F 90
    00022A6A: 16 90

    use this alongside these registry changes and all will be fine:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]
    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    “AllowMultipleTSSessions”=dword:00000001

    Tested against the termsrv.dll 5.1.2600.5512 RTM version released on MSDN today.

  179. Grapevine said:

    Remote desktop rules

  180. emir said:

    Hi All,

    How about windows server 2003 ? How that i can remote for multiuser? Please help me and give me the way step by step. Thank you very much.

    Regards,
    EN

  181. mike said:

    okay, had this working in xp sp2, just upgrade to sp3 and won’t work. How do I fix it??

  182. Mark said:

    Thanks to Phantasm4489. It works great on XP SP3.

  183. bob said:

    Windows XP SP3 RTM no user limit
    E:\WINDOWS\system32>fc/b termsrv.bak termsrv.dll
    Comparing files termsrv.bak and TERMSRV.DLL
    00022A17: 74 75
    00022A69: 7F 90
    00022A6A: 16 90

    would anyone like to explain this step more?

  184. Mark said:

    Those are the places you need to use a hex editor to modify termsrv.dll.

  185. nobodyespecial said:

    Can anyone please explain how to ger this working on SP3 more detailed please.

  186. affinity said:

    For the following, you will need a hex editor to adjust the file:

    E:\WINDOWS\system32>fc/b termsrv.bak termsrv.dll
    Comparing files termsrv.bak and TERMSRV.DLL
    00022A17: 74 75
    00022A69: 7F 90
    00022A6A: 16 90

    At Hex position 22A17 you will find the hexadecimal value of 74, this needs to be changed to 75 and so on for the other address location values.

  187. affinity said:

    Thanks Phantasm4489 for the tips.

    Very happy that I can use a current termsrv.dll file for this.

    I used winhex (found via google) to edit a copy of the newer termsrv.dll file as required.

    I also used split to break my copy of termsrv.dll into smaller parts so that I could edit it without buying winhex at this time.

    cd \windows\system32
    copy termsrv.dll termsrv.dlx
    spilt -b 150k termsrv.dlx

    Edited the first file (xaa) using your fc/b reference data, then rejoined the two split pieces fine as follows:
    copy/b xaa+xab termsrv.xac

    Kind Regards
    AndrewM

  188. mike said:

    anyone want to post a modified termserv.DLL for donwload? That’d be great!

  189. Mark said:

    Another good hex editor is Notepad++ with Hex-Editor plugin. It is free and can open big files without splitting.

  190. Music2030 said:

    Thanks Phantasm4489. I’ve just applied your solution and it works great !

    Modified version of termsrv.dll can be found there :
    http://www.orbitfiles.com/download/id2784635793.html

    Reg file for the registry changes are there :
    http://www.orbitfiles.com/download/id2784636447.html

    Do it at your own risk, no warranty about these files but it worked for me.

    To do it yourself, you can use this “Hex Editor” :
    http://www.hhdsoftware.com/Family/hex-editor.html

    Music2030

  191. PiousMinion said:

    Ok, I changed the following value in a copy of termserv.dll

    00022A17: 74 75
    00022A69: 7F 90
    00022A6A: 16 90

    and I added these registry values:

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]
    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    “AllowMultipleTSSessions”=dword:00000001

    but no matter what I do when I go to connect to the computer via a terminal services client it tells me that the current logged in user has to be logged off and then it asks the current logged in user if it’s ok to do so.

    I’ve double checked the termsev.dll and the registry values and everything looks A-ok, but doesn’t function as such. :(

  192. Kostas said:

    Can anyone upload somewhere the corrected file please? Pretty please???

  193. SBM said:

    I can verify that the hack works wonderfully. Thanks very much Phantasm4489.

  194. Anonymous said:

    http://rapidshare.com/files/115602684/termsrv.dll.html

  195. Fishlord said:

    Nope, sp3 hack just doesn’t work, changed over to posted dll, changed registry, doesn’t work!

  196. NoName said:

    The hacked SP3 dll works for me. You need to overwrite both system32 and system\dllcache under safe mode. Many thanks to Phantasm4489.

  197. Somebody else said:

    Works for me. Thanks Phantasm

  198. wil said:

    Thanks everyone contributed here. My setting is XP SP3, and it works.

    Just want to confirm, with two concurrent sessions, one login locally and one remotely, the two sessions have to be different users. Is this correct? I tried logging in with the same username, then one session will be terminated if the other one session starts.

  199. Rober RDP said:

    Greetings guys. Its working for me. But I have a problem. All the solution permit only 3 remote users . . .

    . . . someone know how to fix it?

  200. John said:

    Patched termsrv.dll for SP3 can be downloaded here:

    http://alonbilu.wordpress.com/2008/05/17/enabling-multiple-concurrent-remote-sessions-on-windows-xp-sp3-patched-file-included/

  201. replier said:

    sala’s terminal patch worked great. i have replaced the original with the hacked termsrv.dll file for sp3. i have copied the registry entries to notepad and applied the changes through a .reg file. (make sure the formatting is maintained, the ” gets changed to something else in my computer). i have not been able to simultaneously log on remotely and locally.

    we need a sala’s patch for sp3!

  202. VR said:

    Looks like this thread has a fix for XP SP3 but not yet a fix for Vista SP1 (i’m looking for one for ultimate x64)

  203. trackbacker said:

    this patch does NOT allow you to control a remote session while the session host is active unlike sala’s patch. i’m looking for a fix for that. this thread one to do concurrent sessions but not simultaneous logged on concurrent sessions. there’s a clear difference in that.

  204. Mark said:

    One way to do it on SP3 is running sala’s patch first then replacing the termsrv.dll with the patched SP3 one under safe mode. That way you don’t need to mess with other things manually.

  205. Mike said:

    I can’t get any of this stuff to work :( .

    WinXP PRO SP3.

    Can someone plz create a one-click solution for SP3?

  206. trackbacker said:

    mark, have u tried running sala’s patch on sp3? i get an error message saying this patch is for sp2 only…

  207. Mark said:

    Sorry. I ran sala’s patch on sp2. After sp3 upgrade, I just replaced the termsrv.dll with the patched one. Never tried to run sala’s patch on sp3.

  208. Netter said:

    Just replace the SP3 termsrv.dll with the hacked version then cross your fingers :)

  209. Marky Sparky said:

    Don’t you think it is time to edit the article where it says:

    UPDATE: it seems that XP is limited, also after this modification, to 3 concurrent users. So don’t waste time trying to raise the maximum number of connections over three…

    As we now know that it *is* possible.

  210. zorro said:

    OK, i have read a lot of this but it is impossible to go thru and figure out exactly what all the steps are to get XP remoted desktop able to connect into another computer and use another account from the one logged in (without kicking the one logged in off). is there a complete listing of ALL the steps to follow using all the latest links and files and “whatever”? or do i have to read from the beginning (2006)?

  211. trackbacker said:

    zorro, what you are looking for is currently not available through these patches. you will get kicked for sure because the patch does not address the functionality you’re looking for. i am also interested in concurrent remote and local rdp sessions.

  212. PigAlien said:

    Hey everyone! This thread is great and I’m so happy now to be able to boot into multiple desktops on my remote machine!!! The reason this was so important to me is that I’m using my old laptop as a Media Center PC and I had to set the main display to be the television, and since I want to also use the Media Center PC as an always-on server for bittorrent and MIRO and other programs, I needed a way to be able to administer the other programs without interfering with the Media Center while its playing shows…

    Anyhow, this now works great, and I’m just wondering, is there a way to automaticall start multiple users on boot-up, each running different programs? For instance, I want the main user to boot into Media Center, and I want another user to automatically start Azureus and Miro and Orb, etc…

    Do you know how to do this?

    Thanks again for this awesome thread!

  213. PigAlien said:

    Following on to my previous post, it occurs to me:

    Can I use a script or batch file solution to switch users automatically at startup?

    For example:

    1) computer boots up
    2) xp auto-logon to account A
    3) batch file runs at account A startup
    3a) batch file does user switch (fast user switching) to account B without logging out account A

    Could I do something like this?

    Thanks!

    PA :)

  214. majster said:

    How about Windows XP 64-bit with Service Pack 2?
    My version of termsrv.dll is srv03_sp2_rtm.070216-1710
    Size: 364 032 bytes
    I’ve found very similar to mine, but it was from xp64sp1.

  215. Netter said:

    Mike,

    The one click multiple RDP solution for XP SP3 can be found at :-

    http://www.aikotech.com/thinserver.htm

  216. Carlos said:

    Does anyone know if it still works? I just cannot make a 2nd connection without kicking out the first one.

    Thanks

  217. Jim said:

    Hi All:

    I really learned a lot from this post. Thanks for all the contributions from everywhere.

    Can any of you guys give me an answer for WinXP Pro 64-bit system? Many thanks.

  218. Rafael said:

    Hi! I’m also looking for a solution for the Windons XP Profession 64-bit Edition? Anyone can help?

  219. Mike M said:

    I want to thank Anarchist for his detailed instructions. Thanks to that post and a little tweaking I have a WinXP SP3 PC that can host multiple RDP sessions on a Domain without having to login the system. The PC boots and sits at the “Welcome To Windows” prompt while RDP sessions work away in the background.

    For those of you who have followed his intructions and are having trouble making it work, here are a few tips:

    - Have the newly created service login as a local admin.
    - Don’t forget to replace the termsrv.dll in the ServicePackFiles\I386 directory.
    - Remove the formatted quotes from Anarchist’s intructions.
    - Don’t forget to download a WinXP TCP Connections patcher.
    - Adjust concurrent sessions as needed (his file is set to 3, I used 8) along with a patched SP3 termsrv.dll.
    - Don’ forget to add users to the allowed RDP users (since I always login as an admin I initially forgot to add Domain Users).

    Good Luck!!

  220. Yanwz said:

    Solution for Windons XP Profession 64-bit Edition?

  221. Netter said:

    ThinServer XP is currently having a special price promotion. If can’t get multi RDP to work, check out their solutions

    http://www.aikotech.com/thinserver.htm

  222. Guillaume said:

    Somehow, rdpclip.exe (needed for clipboard sharing) is not started on my system. Does that have anything to do with the patch?

  223. Vikram said:

    Hi,

    For all the guys out there who couldn’t get this to work. Trust me I understand , suffered through it too. Have detailed it out here what finally worked for me …

    http://piglings.blogspot.com/2008/08/multiple-remote-desktop-connections-rdc.html

    All the best !!

  224. sweetsinse said:

    —WORKS WITH DOMAIN—

    Done with WinXP SP2. not sure results on others.

    I recommend reading the whole post before beginning.

    A user can only log in once, i.e. same user cannot have multiple sessions.

    I have pulled information from 3 sites, including this one to make this possible. Much info was taken from user responses and i will try to document where I can.

    —LINK 1—(mostly informative only)
    http://www.mydigitallife.info/2008/06/13/enable-multiple-concurrent-remote-desktop-connections-or-sessions-in-windows-xp/

    —LINK 2—(how to work in domain/REG file)
    http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-multiuser-remote-desktop/#comment-56153

    —LINK 3—(the DLL file I used)
    http://riccardo.raneri.it/blog/eng/index.php/2006/04/24/windows-xp-multiuser-remote-desktop/#comment-57567

    —LINK 4—(informative, info about gpedit.msc)
    (this link has stopped working)

    If you have problems refer to those sites (specifically those posts in the the link) and don’t be afraid to read. There may be another procedure that works but this is how i got it going. I had 5+ people logged in concurrently thru a domain. bomb.

    DIRECTIONS

    1) In windows explorer go to Tools > Folder Options > View…
    —–CHECK show hidden files and folders
    —–UNCHECK hide extensions of known files
    —–UNCHECK hide protected op. sys. files
    NOTE: those of you that CAN’T see a ‘dllcache’ folder (later) DO NOT have the op .sys. files viewable. there are about 200 things in that folder.

    NOTE: i did the whole thing in one step by killing all ’svchost.exe’ thru task manager. sometime a few will respawn but as long as they have no ‘User Name’, especially your own, this should work. after doing this however, some aspects of the WIN OS do not behave correctly, i.e drag/drop + copy/paste. if your not comfortable with that, try the safe mode approach in the original post.

    2) go to start > run and type ‘cmd’ without quotes to open a terminal/command prompt. then open task manager and go to processes. sort the processes by name and start killing svchost.exe everywhere. (i have read you only need to kill the ones with your user name, i.e. NOT local system OR network service, but i waxed them all :) )

    this will begin a forced shutdown. go to the terminal and type ’shutdown -a’ without quotes to abort the running shutdown. kill the remaining ’svchost.exe’ if necessary and abort the shutdown as necessary.

    3) get the DLL from LINK 3 or:

    (May not always be available so mirror!!)
    tony.brokerbin.com:8008/LINKED/termsrv.dll

    backup termsrv.dll in ‘c:/windows/system32′ AND ‘c:/windows/system32/dllcache’. place your new copy in both folders.

    4) download this registry file i’ve wrote (auto-adds necessary keys)

    (mirror this!!!)
    tony.brokerbin.com:8008/LINKED/multiTS.reg

    save the file as a ‘.reg’ (without quotes of course…). when you double click this file it should ask to ‘merge’ with the registry. click yes. if you like refer to LINK 2 and LINK 1 for manual directions.

    NOTE: at this point you should be good to go for NON-DOMAIN uses. *simply* reboot and test (if it doesnt work try the steps involving gpedit.msc in the original post, not sure if its necessary, then reboot again) domain access requires a few more steps, refer to LINK 2 and LINK 1 for the reason.

    5) create a folder – ‘c:/termsrv’ – and put the multiTS.reg file from earlier in there.

    6) download this from MS resource kit (instsrv.exe AND srvany.exe) they allow running apps as a boot service:

    tony.brokerbin.com:8008/LINKED/srvany.zip

    that zip has both files, else find them elsewhere. put both files in ‘c:/termsrv’

    7) open a terminal and run:

    c:\termsrv\instsrv.exe XP3RDC c:\termsrv\srvany.exe

    that will install a service and setup the registry key. all that remains is to configure that key/service….

    8) this could probably be done with a REG file, refer to the other one for syntax. open start > run and run ‘regedit’ (no quotes…)

    navigate to ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\XP3RDC’

    Add a KEY (folder) with the following:
    Key Name: Parameters

    Select this newly created Parameters key and add the following STRING value:
    Value Name: Application
    Data Type: REG_SZ
    Value data: c:\windows\regedit.exe /s “c:\termsrv\multiTS.reg”

    9) reboot your computer

    10) rejoice and bask in your own self-satisfaction when you login with 5+ domain users like i did. if this sadly is not the case, refer the the links i provided and try again. i ASSURE you this does work!!

    peace

  225. sweetsinse said:

    just as a quick update to my above post:

    i followed what i wrote but SKIPPED step 2 (killing svchost.exe). i was able to get this working again in less than 10 minutes on another machine.

    HOWEVER. I think it only worked BECAUSE of steps 5-9. These steps create a service that automatically set the correct registry entries at boot time.

  226. HyperActive said:

    AMAZING walkthrough! Hats off to you Ricky and to whomever helped you figure this out!

  227. nynexn1nja said:

    why dont you just setup winconnect or setup VMWare ESXi with a windows XP Virtual cluster? With ESXi being free, a pre-existing copy of windows xp, vmware converter (free) and a little time, you can create a slew of XP remote desktop machines. Assign a clustered address, and use a service redirect via clustering services, and you have 3x however many licenses of XP you have on hand, at no additional overhead.

  228. Netter said:

    nynexn1nja,

    Won’t each VM suck resources as oppose to solution such as our hack here or winconnect or thinserver ?

    Check them out at :-

    http://www.aikotech.com/thinserver.htm
    thinsoftince.com

  229. peter.fernados said:

    If your like to use RDP over internet using microsoft windows teredo service(peer to peer connectivity) you can check this soft http://www.lanoninternet.com
    Now RDP can work behind NAT/firewall

  230. allan said:

    i seem to have followed procedures regarding how to set up multiple remote desktop sessions but it is not working any ideas thanks

  231. Saidul Islam Talukder said:

    I did everything but can not access multiple user at a time with win-xp professional. any one can help be regarding the issue. i want to access at a time multiple user from referent location.

  232. Chris said:

    I followed sweetsinse’s instructions, and it worked great on my SP3 domain system. I booted into safe mode rather than killing off all of the svchost processes. The only difficulty was getting one of my programs to work: it relies on MSSQL, and would not work because it couldn’t read the date correctly. I’ve previously had dozens of problems with this program so that was unsurprising. All I had to do was run this program as the user that was locally logged on and that seems to have cured the problem.

  233. Jack said:

    does it work on sp3? where do I get the dll ?

  234. Nick The Greek Geek! said:

    I just tried the http://sala.pri.ee/?page_id=11 patch and so far
    works like a dream, 3 clients are connected with the server and
    everything seems to work fine.

    The system ive patched is: Windows XP Pro SP3 English

  235. just_me said:

    anyone has got windows xp 64bit patched version of termsrv.dll ? or anyone can explain how get to know which bytes should be modificated?

  236. Michael said:

    Nice article.. I will use it as a tutorial:D

  237. Netter said:

    Hmmm Thinserver XP is having a Christmas sale now. Those still unable to enable RDP might wanna check out their site at :-

    http://www.aikotech.com/thinserver.htm

  238. fernando said:

    I am using Windows 64 bit s system since the computer that wee arranges use of 8 gb of RAM and I need use all of the memory. We are many users and wee want to use it all of us at the same time.

    have any got a program like Termiserv_XPSP2_i386_1.0 patch for windows xp 64 bit system? or other solution for xp 64 bits?
    Thank you very much

  239. sweetsinse said:

    That link I posted for the registry file (multiTS.reg) is down, as a got a little wrist slap for using that domain for that post :-( … so I will post it here.

    —–>STARTFILE

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]

    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

    “EnableConcurrentSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

    “AllowMultipleTSSessions”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]

    “MaxInstanceCount”=dword:00000009

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server]

    “TSenabled”=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Terminal Server\Licensing Core]

    “EnableConcurrentSessions”=dword:00000001

    —–>ENDFILE

    Save everything between the markers as “multiTS.reg”, and you can follow the instructions I’ve written above. Srvany can be found in several places including MSDN I believe; it is free.

    NOTE: “MaxInstanceCount” is set to NINE above. Change that to the max users that need to login… note however that the system will bluescreen when it runs out of resources for all users… one person managed to get 21 people logged in before that happened, although mileage will vary with respect to RAM, etc.

    H@ppY H@ckz0r1ng H0l1d@ys!!!

  240. sweetsinse said:

    The large gaps in above post i think are due to text justification or something along that line… they should only be spaces.

  241. sweetsinse said:

    ….also beware copy and pasting as those are not standard double quotes (” “) … looks like the blog engine changed them to something “prettier”… replace them with real double quotes before running.

  242. fernando said:

    Sweetsinse:
    can you explain how get to know which bytes should be modificated in windows xp 64bit or other solution to get concurrent users in this system?

  243. fernando said:

    if you know any of this send my an e-mail to fbuezas@gmail.com

  244. chp said:

    For vista x64 SP1

    http://s.ly.lv/tc/chp/attachment/4995274865.dll

    rename to termsrv.dll then
    copy to system32

    thanks to noimp :D

  245. Abe said:

    Hi Everyone,
    Got it working for xp 64 bit with instructions.
    http://popcopy.blogspot.com/2008/12/enable-multi-user-concurrent-logon-for.html

  246. monicagalindo said:

    this is for win 7 beta build 7000
    Comparing files termsrv.dll and TERMSRV.PATCH.DLL
    0001BC2F: 3B B8
    0001BC30: 86 00
    0001BC31: 20 01
    0001BC32: 03 00
    0001BC34: 00 90
    0001BC35: 0F 89
    0001BC36: 84 86
    0001BC37: F3 20
    0001BC38: 28 03
    0001BC39: 01 00
    0001C367: 43 90
    00063ABD: 74 E9
    00063ABE: 2F 2C
    00063ABF: 68 00
    00063AC0: 60 00
    00063AC1: 43 00

  247. ckoplay said:

    Don’t forget to enable “fast user switching” otherwise this method doesn’t work.

  248. fernando said:

    Abe:

    The method work very well.
    Thank you very much, you saved many headaches to me

  249. seviyeli chat said:

    thanks for the info..

  250. pepe said:

    check this out
    http://www.remkoweijnen.nl/blog/2008/12/19/windows-xp-x64-terminal-server-patch-part-1-mandatory/

  251. GarberFC said:

    I just did an install of XP sp1, then installed sp3 plus all the fine MS updates. When I followed the procedures I got stuck! The step for updateing the “Limit number of connections” couldn’t be done b/c there wasn’t a “Terminal Services” component.

    I did perform all the other steps and believe it or not it still works! Maybe MS did something were the “Limit number…” step no longer has to be performed…

  252. dofus kamas said:

    I tried logging in with the same username, then one session will be terminated if the other one session starts.

  253. Tania said:

    Greatings,
    this is very useful to us.

    Thank you
    Tania

  254. Ali said:

    Dear friend,
    Many thanks in advanced for your all explaination and advising. I have the following problem which about 2 month I could’nt find any solution for that.
    1- I have done your instruction in a computer with Win XP-SP2 already
    2- Everything is OK
    3- When a client with any Windows connects to the server, its connection will disconnect after some times(1,2,3 or 4 hours) and after disconnecting its not possible to connect again untill we restart the server.

    Please advise me a solution.
    Thanks and regards,
    Ali

  255. MC (Athens, GA) said:

    Riccardo: This is a great blog, the best I’ve ever read. Thanks for getting the ball rolling.

    sweetsinse: Thanks for consolidating the latest information.

    For those who are having trouble following sweetsinse’s instructions on a domain, you may want to try limiting your directory name (i.e. termsrv) to 8 characters with no spaces, and your registry file (i.e. multiTS.reg) to 8.3 with no spaces. I originally called the directory “Terminal Services” and the regedit command was not running after a reboot. When I changed the directory name to “TermServ”, it worked.

  256. ana said:

    Thank you very much

    I have found everything very helpfull

  257. Eugene said:

    Hi, guys! What about termsrv.dll version 5.1.2600.5733 (preSP4)?

  258. Eugene said:

    anyone can answer me?

  259. Eugene said:

    If nobody wants ;-) I answer the question:

    Windows XP SP3 with latest updates (Pre-SP4) no user limit
    termsrv.dll version 5.1.2600.5733
    E:\WINDOWS\system32>fc/b termsrv.bak termsrv.dll
    Comparing files termsrv.bak and TERMSRV.DLL
    00022D47: 74 75
    00022DC2: 7F 90
    00022DC3: 16 90

  260. James Lawson said:

    This situation with remote access for multiple concurrent users has troubled many people. So many, that they have decided to create a lot of thired party software. There are big, expansive, but very functional programs from Citrix, for example. But there are other programs, less complicated, but still very efficient, like ThinPoint.It all depends on how you are planing to use concurrent connection to your machine really.

  261. tonmi said:

    I need

  262. NetGeek said:

    There are also software like ThinServer which is cheaper and easier to work with and can work on XP Professional as well as Windows Server 2003

  263. Ashish said:

    Thank you very much

  264. chp said:

    For vista sp2 x64

    http://noricube.pe.kr/tc/chp/attachment/3631389456.dll

    thanks, noimp ;)

  265. REggie said:

    Was wondering if anybody has run into a problem with Vista Business like mine. I downloaded and ran the batch file (below) and now I can’t RDP to my machine. In services.msc, I see the following error for the service TermService: . Also, I had previously changed RDP to listen on port 918 and it was working (before I ran the batch file)

    I downloaded the hacked .dll from remotedesktoprdp.com and ran the batch file for Vista Business. I’m a linux guy and feel pretty helpless here.

    Here are the contents of the batch file I ran. How can I reverse these changes? I’d be fine with getting it back to allowing only 1 concurrent session.

    Thanks much for any thoughts.

    :START
    @echo off
    cls

    :D ETECTARGUMENTS
    SET SINGLESESSION=1
    SET BLANK=1
    IF /I *%1 == *MULTI SET SINGLESESSION=0
    IF /I *%2 == *MULTI SET SINGLESESSION=0
    IF /I *%1 == *BLANK SET BLANK=0
    IF /I *%2 == *BLANK SET BLANK=0

    :SETSOURCEFOLDER
    REM This will get the folder the batch file was launched from since the current
    REM directory will change if launched from a network share
    SET SOURCEFOLDER=%~dp0
    ECHO Source Folder is %SOURCEFOLDER%

    :TAKEOWNERSHIP
    echo Taking ownership of %SystemRoot%\System32\termsrv.dll
    takeown /a /f %SystemRoot%\System32\termsrv.dll
    echo Granting Administrators rights
    icacls %SystemRoot%\System32\termsrv.dll /Grant Administrators:F

    :STOPTERMINALSERVICES
    echo Stopping Terminal Services
    net stop “Terminal Services”

    :BACKUPTERMSRVDLL
    copy %SystemRoot%\System32\termsrv.dll %SystemRoot%\System32\*.*.bak

    :COPYTERMSRVDLL
    echo Copying %SOURCEFOLDER%termsrv.dll to %SystemRoot%\System32\
    copy /y “%SOURCEFOLDER%termsrv.dll” %SystemRoot%\System32\

    :IMPORTREGKEYS
    echo Enabling RDP
    REG ADD “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server” /v fDenyTSConnections /t REG_DWORD /d 0 /f

    :SETSINGLESESSIONSETTING
    ECHO Setting fSingleSessionPerUser to %SINGLESESSION%
    REG ADD “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server” /v fSingleSessionPerUser /t REG_DWORD /d %SINGLESESSION% /f

    :SETBLANKPASSWORDPOLICY
    ECHO Setting LimitBlankPasswordUser to %BLANK%
    REG ADD “HKLM\SYSTEM\CurrentControlSet\Control\Lsa” /v LimitBlankPasswordUse /t REG_DWORD /d %BLANK% /f

    :CONFIGUREFIREWALL
    ECHO Configuring Remote Desktop in Windows Firewall
    netsh firewall set service remotedesktop enable

    :STARTTERMINALSERVICES
    echo Starting Terminal Services
    net start “Terminal Services”

    :P AUSE5SECONDS
    ECHO Pausing 5 seconds to give service time to start listening
    choice /n /c y /d y /t 5 > nul

    :CHECKIFSERVICELISTENING
    echo Checking if Service is listening on port 3389
    SUBST
    netstat -a | find /i “3389″
    if ERRORLEVEL 1 goto SERVICENOTLISTENING

    :SERVICEISLISTENING
    echo Service is listening
    goto CONTINUE

    :SERVICENOTLISTENING
    echo Service is not listening

    :CONTINUE
    echo Done
    Pause

  266. REggie said:

    Looks like the forum pulled out the error. The error said – Failed to Read Description error code 2

    Thanks.

  267. champions online resources said:

    i couldn’t tick where it says: “Allow users to connect remotely to this computer”. Do you have any idea how i can hack through without anyone noticing so that i would be able to tick that box?

  268. abovocipher said:

    for all of you guys looking for concurrent users for xp 64bit SP2, this does work:
    http://popcopy.blogspot.com/2008/12/enable-multi-user-concurrent-logon-for.html

    its alittle extra work, but i dont mind doing it as long as it works and it does.

  269. azam patel said:

    Very helpfull article. Solution works great for me:)

  270. azam patel said:

    It is possible in Win7 and Win Vista

  271. Remote desktop said:

    I have had every version of Windows since XP releases..yes, even Millennium Edition, and despite putting in many hours of effort, I have never been able to make these connections work using just Windows. What is odd is that within five minutes I was able to establish a connection with third party software. I wonder why the Windows offering is so very hard for the layman to operate?

  272. gonewild said:

    Thanks you, the post of Anarchist is functioning on a domain computer.

Leave a comment