Remote Desktop doesn't maintain session on remote computer!

[Steve]

Has anyone experienced this?
You log into your workstation from a laptop (or any other remote
computer) on the same network, interact with the remote machine, run
programs, etc., then end the session. You then remotely connect a
little later, and all programs are still running just as they were; no
problem. But THEN, you return to your locked workstation and login,
expecting the same programs to still be running, but at that very
instant, it LOGS YOU OUT, quits all your programs, and logs you back
in!

Why is it doing this?! If I use my same login either local or remote,
seems like it should never logout my session! This is so frustrating
that I'm about to use TightVNC or something with better functionality.

 

[GwD]

That's how remote desktop works.

Try NETOP.

 

[Phil]

No it doesn't. I use remote desktop everyday(using it right now to post
this). When you go back to the computer you were remotely connected to, it
does not log you off. You simply unlock the workstation and your in with all
programs still running.

 

[Phil]

I really don't have a solution for you as I've never seen this and I use
remote desktop everyday(using right now to post this), but I can say that
this is not the way it's supposed to work. When you connect remotely the
computer you connect to locks the workstation and displays the welcome
screen. Then when you try to log onto that machine locally you should be
able to just simply type in your password and the station unlocks and your
in. It should keep all programs running that you started in the remote
desktop session and should not log you off. I've never seen that one before,
but clearly something is wrong. Just wanted to let you know it should not
work as you describe. Maybe a sfc /scannow at the run line will fix it up,
or more drastic would be a repair install.

 

[Steve]

I should say that it does exhibit the correct functionality sometimes,
but only if I go back to the first workstation in a "short period of
time". After some unknown period, it seems to 'forget me' and rather
than unlocking, I get a logOUT. I should also mention that we're on a
domain, rather than a workgroup.

 

[Phil]

Hmmm.... I've never used it on a domain network so maybe something it set to
"time out" and logs the user off. I'm really not sure, I just know it
shouldn't do that in a normal setup. But I still think it's on that machine
locally. I'd start with sfc /scannow and see if it helps.