|
|
|
This text is based on the text from here:
http://forum.osnn.net/showthread.php?t=39878&page=1
Unlimited concurrent
remote desktop
You should only use this dll on WIN XP SP2. (Not the 64-bit version).
One thing I am very annoyed about with SP2 is why they have added (in build 2055) and then taken away in the final Build (2180) Concurrent remote desktop and a physical user logged into the same machine....
So if you are now running the SP2 final, and would like too use this feature. Here is what you must do..
Attached is a zip with 4 files
1. termsrv.dll - a cracked dll with no concurrent desktops limit.
2. Install.bat - an install script for the dll
3. enable Concurrent Remote sessions SP2.bat – a registry changing code.
4. uninstall.bat – if you want to cancel the changes – run this script.
Ok, so here what to do
2. Extract the zip...
3. Double click on Install.bat.
4. Reboot.
That is all, you are set to go!
If you get this screen:

don’t worry – it is ok – it is a windows warning because you are replacing a
system dll.
I can’t believe MS removed this feature from the final build of SP2
The termserv here is the same as the one that comes with the final version of SP2 but there is no limit to the number of concurrent remote desktops you can have.
Limitations –
More info about the “Windows Task Scheduler” can be found here:
http://www.iopus.com/guides/winscheduler.htm
termsrv.dll is not the original file from SP2, it is a patched file and I don’t know how legal is it to use is – but I think it will be very hard to catch you – you don’t really install a software, only a dll, and you only “unlock” a hidden property of windows xp.
In order to check if you succeeded - connect to your own
computer, do this like that:
The limitation of Windows's XP Remote Desktop client is that it refuses any connection from the
localhost (127.0.0.1) to the localhost with the following error message: "The client could not
connect. You are already connected to the console of this computer. A new console session cannot
be established". In order to be able to tunnel this through SSH, this limitation must be broken.
The first idea was to hack the client executable and remove the limitation but it's simpler than
that. I noticed that if you run the executable mstsc.exe from another operating system than XP,
the limitation does not exist. Drilling a bit into that, it is possible to run mstsc.exe on
Windows XP to the localhost by using application compatibility with older windows 9x.
Procedure:
1. Create a folder (For example c:\TSclient) on your XP box
2. Copy mstsc.exe and mstscax.dll from your XP's %systemroot%\system32 to this folder.
3. Right click mstsc.exe and go to the properties of it.
4. Select the Compatibility tab
5. Check "Run this program in compatibility mode for"
6. Select "Windows 98/ Windows Me"
7. Click on OK
8. Now connect execute “mstsc.exe”.
9. Connect to “localhost” computer name.
10. Login as a user different from your own – so you won’t be logged out….
Notes:
- It doesn't work with the USIntl keyboard layout.
Other name for search engines:
Free terminal server
Use Windows XP as a terminal server
termsrv.dll patch
Unlimited termsrv.dll
Unlimited terminal server
Unlimited remote desktop users