Login with RDP, without bumping current session.

Ragzarok said:

SquonkSC said:

Ragzarok said:

Hello,
It looks like the tool does not work any more. Can some one confirm this on their system for me?

Nope, still works.

Have you downloaded the right one for your Win7 build?

There are different versions for different builds.

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.

Sorry Ragzarok, but you're wrong.

I don't know why it's not working in your case.

But in my entire network I can logon remotely with client A's credentials, while client A is logged on.
That is the whole purpose of the script.

Again, why it's not working for you, is hard to tell, cause it can be multiple causes.
In many cases permissions and users have been messed with.

Make sure you download the right version.
Mind the build number, and if it's 32bit or 64bit.

I assure you the problem isn't the script.
I've tested it on more than 30 different systems.

Greetings.

Ragzarok said:

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.

Dear Ragzarok,

if the mod is done correctly, when A is logged in let's say from remote, another user can login as A from the console or from another remote location (this I couldn't test yet because I don't have 3 computers here). Pity that skype won't work on both sessions

Of course if you want to do this you must run the script with the parameter "multi", or set your registry "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" fSingleSessionPerUser=0

You can verify this from the image that I attached.

Ciao!

SquonkSC said:

(...)
Make sure you download the right version.
Mind the build number, and if it's 32bit or 64bit.

I assure you the problem isn't the script.
I've tested it on more than 30 different systems.
(...)

...well, I am surprised about this because in my case I experienced a different behavior of the script on two systems that were identical. Anyway it was not so difficult to figure out and copy the dll files manually.

But it is very strange. I will do a test on the next 7system I have in my hands.

Yeah, it looks like you're right on this. I reinstalled and applied the hack again, and it is now working as it should. Thanks.

Now only one thing remains, how to disable that prompt that RDC always gives when you disconnect from the server?

Ragzarok said:

(...)

Now only one thing remains, how to disable that prompt that RDC always gives when you disconnect from the server?

can you please be a little bit more precise about the prompt? From your information I am guessing right now that you are leaving the session open instead of real disconnecting (...and consuming unnecessarily huge amount of memory)

MaX

freesbee said:

Ragzarok said:

(...)

Now only one thing remains, how to disable that prompt that RDC always gives when you disconnect from the server?

can you please be a little bit more precise about the prompt? From your information I am guessing right now that you are leaving the session open instead of real disconnecting (...and consuming unnecessarily huge amount of memory)

MaX

\
This is the prompt when you close the remote session.
Edit: Leaving the session open really only takes up about 38MB of RAM so it's not that bad. Although I do close the connections whenever possible b/c I have a few machines that I constantly work on, thus, the aforementioned prompt does consume a little more time. I mean...really...but still better to be efficient if possible.

Dear Ragzarok,

normally I get this message when I close the remote session by the "x" button in the top-right of the window.

I don't get it if I do "Start / Logoff" ("Win7button / logoff" on Win7)

MaX

Kari said:

Please guys, correct me if you think this is wrong: If I configure my firewall so that RDP can use alternative ports, could I have two RDP sessions simultaneously from two different computers?

Please don't call me an idiot when answering, that name is reserved to be used exclusively only by my ex-wives.

Kari

I have set this up at home to work, allowing me to RDP to all of the machines at home. Just map various external ports to port 3389 of each of the internal machines, so that perhaps:

55555 = 192.168.1.100:3389
55556 = 192.168.1.101:3389

works like a charm

Hi there

RDP'ing to the SAME machine concurrently with different users is normally a problem unless its a SERVER.

There is a problem with this -- usually on THE ROUTER apart from the OS itself.

You need to port forward the port to a specific address on your lan so you'll have to enable your router to forward say prt XXXX and YYYY to IP 192.X.X.X as the previous post says - but this will normally be for a single user.

RDP'ing to DIFFERENT machines isn't a problem so long as you know the internal LAN address and set the port forwarding OK - even then only 1 session per (non server) machine will work without all sorts of tricks which I've never tried.


(Tunnelling might be a partial solution).

I doubt also if having two users with the same ID logged on is a good idea - even if it is possible (I don't know) as what happens with simultaneous data updates.

I'm sure a retail home version of an OS DOES NOT HAVE the same robust locking mechanism as a commercial database system.


If you need 2 users to simulatneously be able to change data on a remote machine that's NOT a server ithen IMO a method would be to RDP to a virtual machine running on the actual machine you want to connect to --and then use "bog standard" networking to make your changes on the HOST disks (easy to share disks between a VM and its host).

(You wont be able to RDP to the HOST from a Virtual machine if both of these are running on the same physical host -- you wont have a console --crash --its not a Linux system that can run with a virtual console or even none at all).

Cheers
jimbo