New
#11
I'll give Team Viewer a go in a VM to see if it meets my needs, thanks for the suggestion.zihzag3143 said:
I'll post my question in the forums on missing remote, see how i got on there.squonksc said:
It'd be really handy if i can get it to work with XP. Thanks for the heads up on this one squonksc :)
Squonksc & Ken,or anybody, any ideas of how to configure ports; I want to test this stupid idea of mine to make remote sessions from two different machines simultaneously to one Win7 system.
Kari
Yes! I know how to, and I do it anytime. I'm not talking about VNC or similar stuff: I know really how to do the same that works perfectly on Win7 after following this guide.
There was a file termsrv.dll in WindowsXP RC3 that allowed this .
Then, when publishing final release of WindowsXP the file was modified and multiple/concurrent TS sessions were possible only on Terminal Server OS (MUCH more expensive ).
BUT
some wise guy kept the RC dll and searched for the 2 registry keys that were changed. So if you substitute the dll and change the registry keys back to the original, then you will have a TS on WinXP Pro (I tested up to SP3 x86).
Guess who was that guy!!!
NOW
it's not a problem for me to post the file (or write a tutorial), but I'm afraid that would violate MS Licencing policies because of the old release of file termsrv.dll
Please, administrator, tell me what I should do
Hello,
It looks like the tool does not work any more. Can some one confirm this on their system for me?
Dear Ragzarok,
I have experienced a malfunctioning on another Win7 7600 x64 system. I cannot tell you the reason why I had two different behaviors on two systems that were apparently identical, but I could figure out what was happening.
The script was setting all the registry keys correctly, but it was not copying the dll files in the proper path. So just try to run the script with the options that you need, then stop the RDP service(s) and manually copy the files
32_termsrv.dll -> %WINDIR%\system32\termsrv.dll
64_termsrv.dll -> %WINDIR%\SysWOW64\termsrv.dll
Start the RDP service(s) and in my case everything was fine.
Now I'm going to verify the argument of following post, because it seems to me that when I tested I could logon multiple cuncurrent users (I'm not sure, it was couple of weeks ago).
Hope this have helped
Last edited by freesbee; 03 Nov 2009 at 10:26. Reason: probably found malfunctionig Ragzarok was experiencing
Well here is the situation:
If the server has 2 users A and B and if A is logged in, the client can only log on with B's credentials without interrupting A's session. This has worked fine since the RC, I just thought the hack was supposed to allow the client system to log on using A's credentials as well. This is, however, not the case. Just wanted to clarify what it is that the hack does.