Re: RDP session logs off after disconnect

  • Thread starter Thread starter Shenan Stanley
  • Start date Start date
S

Shenan Stanley

Christian said:
since a couple of weeks I'm facing a strange behavior when working
overRDP. Normally I used remote pc's to run time talking jobs like
compiling stuff.
This is as it worked before:
- Log on
- start the work
- Disconnect and let the compiler / batch run
- Connect next day and look at the desktop you left last day

This is like it behaves now:
- Log on
- start the work
- Disconnect and let the compiler / batch run
- The session logs off after 4 minutes
- all apps get closed
- no work is done
- I'm mad

This is what I checked.
- No relevant GPO settings were changed (Terminal Services)
- It works on not updated XP computers (SP 2 only)

This is what i guess
- Someone accidentially or intentionally messed up RDP with a patch

Is this behaviour known at MS?
Which patch messed it up and can I restore the old behaviour?

Thanks in advance and excuse the bad English
Click to expand...

Sounds like some setting (screensaver, etc) has been changed.

I have many customers with Windows XP (SP3 + Post-SP3 Patches) that work
remotely all the time. Log in, work, disconnect without logging off and
connect later (sometimes minutes, hours; sometimes days) to continue where
they left off. Some remote in using other Windows XP machines, Windows
Vista machines, Windows 7 machines and Macintosh OS X machines. None
experience what you are describing.

Assuming - by your choice of words - you are in an active directory
(AD)/domain situation with Group Policy Objects (GPs) applied from the
domain to the workstations...

- Do you have AD GP control? Are you the only one?
- What screensaver is in use on said machine? (Name)
- Does it do it for your user account only?
 
Sounds like some setting (screensaver, etc) has been changed.

I have many customers with Windows XP (SP3 + Post-SP3 Patches) that
work remotely all the time. Log in, work, disconnect without logging
off and connect later (sometimes minutes, hours; sometimes days) to
continue where they left off. Some remote in using other Windows XP
machines, Windows Vista machines, Windows 7 machines and Macintosh OS
X machines. None experience what you are describing.

Assuming - by your choice of words - you are in an active directory
(AD)/domain situation with Group Policy Objects (GPs) applied from the
domain to the workstations...

- Do you have AD GP control? Are you the only one?
- What screensaver is in use on said machine? (Name)
- Does it do it for your user account only?
Click to expand...

Instead of checking what the poster asked about (a patch/update that
screwed up the RD), you start blaming screensavers, etc...
Well I have seen multitudes of people complaining about this in the last
month or so. Some update screwed up disconnecting from an RD session.
When you do, after a certain amount of time, it logs off the user that
was logged in (via RD). This has screwed up programs that are left
running. As an MS-MVP, I'd hope you please check further into this
instead of supplying the canned answers.
 
<snipped>
(No worries - the Google Groups Archived version is linked in my response.)
Instead of checking what the poster asked about (a patch/update that
screwed up the RD), you start blaming screensavers, etc...
Well I have seen multitudes of people complaining about this in the
last month or so. Some update screwed up disconnecting from an RD
session. When you do, after a certain amount of time, it logs off
the user that was logged in (via RD). This has screwed up programs
that are left running. As an MS-MVP, I'd hope you please check
further into this instead of supplying the canned answers.
Click to expand...

Welcome to End of May/beginning of June 2010.

As you can see from the Google Groups Archive - the last response to this
conversation was November 2, 2009.
http://groups.google.com/group/micr...k_remotely/browse_frm/thread/9cc314ba18c06998

You added nothing to a conversation you had nothing to do with when it was
actually occurring... Yay. Glad to have you around. ;-)

Do you think your problem even after you state, "... multitudes of people
complaining about this in the last month or so ..." now knowing when this
posting was originally made? (More than "in the last month or so" would
usually cover by 5 or so months... ;-) )

Maybe your problem *was* caused by a patch. If so - maybe you should
investigate wjhat patches were applied to said machines displaying the
symptons in the last couple of months or so (still outside the range of the
original conversation here) and post the list of patches applied to said
machines here. After all - no one here knows the answer to any of the
original questions I asked (all relevant) or even what patches were applied
to your machines....

Sure - one could assume *all* of them were applied each month (doubtful) -
but since in your case we do not even know "Windows XP ______ Edition,
Service Pack _ __-bit" - it's all still guesswork. ;-)
 
Do you think your problem even after you state, "... multitudes of
people complaining about this in the last month or so ..." now knowing
when this posting was originally made? (More than "in the last month
or so" would usually cover by 5 or so months... ;-) )

Maybe your problem *was* caused by a patch. If so - maybe you should
investigate wjhat patches were applied to said machines displaying the
symptons in the last couple of months or so (still outside the range
of the original conversation here) and post the list of patches
applied to said machines here. After all - no one here knows the
answer to any of the original questions I asked (all relevant) or even
what patches were applied to your machines....

Sure - one could assume *all* of them were applied each month
(doubtful) - but since in your case we do not even know "Windows XP
______ Edition, Service Pack _ __-bit" - it's all still guesswork.
;-)
Click to expand...

Sorry to jump down your throat, but this is a big problem for me.
It only started about two months ago. At first, I thought it was my PC that
was crashing after disconnecting, then I realized it was logging off.

I googled it and found recent inquiries about this but all the same answer.
Somebody has to know if a MS update did something that effects this,
hopefully how to fix it.

Thanks
 
<snip>
Sorry to jump down your throat, but this is a big problem for me.
It only started about two months ago. At first, I thought it was my
PC that was crashing after disconnecting, then I realized it was
logging off.

I googled it and found recent inquiries about this but all the same
answer. Somebody has to know if a MS update did something that
effects this, hopefully how to fix it.
Click to expand...

If it *was* a patch, then it is a patch in combination with some other
software application of software device driver - because in the many
machines I help manage - it does not happen. When someone remotes in,
disconnects (not clicking Log Off - but perhaps just clicking the X on the
connection drop down or by choosing disconnect from the remote start menu) -
they can later remote in or walk up to the machine (if they traveled) and
log in to resume where they left off.

So the questions remain ("-" denotes the query, "*" denotes the methodology
you could take to obtain the answer to the query or just make sure things
are 'as they should be')...

- What specific operating system for BOTH system - remote and local? (Given
where you posted: Windows XP ______ Edition with Service Pack _, __-bit for
at least the remote... I would assume.)

* assistance on answering this question:
Start button --> RUN
(no "RUN"? Press the "Windows Key" + R on your keyboard)
--> type in:
winver
--> Click OK.

The picture at the top of the window that opens will give you the general
(Operating System name and edition) while the line starting with the word
"version" will give you the rest of the story. Post _both_ in response
to this message verbatim. No paraphrasing - instead - ensure
character-for-character copying.

How to determine whether a computer is running a 32-bit version or
64-bit version of the Windows operating system
http://support.microsoft.com/kb/827218


- Are your remote desktop components updated?

* Assuming you are running a 32-bit version of Windows XP Professional (the
machine you remote into - or superset version of Professional), here is what
I suggest:

Download and install this update:
http://www.microsoft.com/downloads/details.aspx?FamilyId=72158b4e-b527-45e4-af24-d02938a95683

Reboot.

Follow the instructions in the "How to turn on CredSSP" section of this KB
Article:
http://support.microsoft.com/kb/951608/

Reboot.


- Do you have the latest versions of the device driver software for your
video card and network card for your remote computer?

* Download and install (from the hardware device manufacturer's web page
support/drivers download section) the latest driver for the video card you
have installed in the remote system (one you are remoting into - you should
be local to that machine when doing this.). Most likely a ATI, nVidia or
Intel video device. Do *not* get the one that *may be* offered by Microsoft
on their Windows Update web page/automatic updates.

Reboot.

Download and install (from the hardware device manufacturer's web page
support/drivers download section) the latest driver for the network card you
have installed in the remote system (one you are remoting into - you should
be local to that machine when doing this.). Do *not* get the one that *may
be* offered by Microsoft on their Windows Update web page/automatic updates.

Reboot.


After all that - I would try your remote connection again - and be sure you
are just disconnecting and you have no auto-logoff set/etc.
 
Back
Top