Vista Remote Desktop disconnects after about 20 minutes

Hi
I am connecting to a Vista desktop from a Windows XP 64 bit laptop. The RDP
Client appears to be version 6. After a period of time (guessing 20 mins)
the remote desktop connection disconnects. NB: A second RDP connection to a
separate Windows XP SP3 computer does not. When I try to reconnect, I get
the login screen, then when I try to login - the screen starts the login
process, then hangs. It makes no difference whether I try to login using RDP
or actually login from the console - the same thing happens.
I then have to cold reset the computer. The whole process kinda defeats the
purpose of remote desktop.
Does anyone have any ideas where I can start to diagnose the problem. Is
this a known issue?
Thanks
George

Is the RDC session idle when the disconnect happens? Is this in a standalone
work group environment or a domain environment? There are group policies that
control idle sessions. Perhaps that is the problem.

My problem is similar except in my case the disconnect isn't a timeout. I
clicked the disconnect button. When trying to log back on later, I receive a
message saying the host was busy processing a logoff, delete, etc. When I
return home, the host is still hung and I have to hit the reset button to
reboot. If I try to login at the local console, I can enter my password but
it hangs at the welcome screen.

My host is Vista Ultimate and the remote is XP Pro.

I have similar problems. Remote connection to Vista Ultimate x64 from
XP Pro computer drops after about 20 minutes. If you try to
reconnect, you get a "busy processing a disconnect, connect etc.
error". This error lasts for about 20 minutes, at which time you can
remote in again. If you attempt to log in locally after remote
session dropped (e.g. when I get home from work), it hangs for about
10 minutes.

Finally, if the first logon to the Ultimate x64 is a remote logon,
many programs such as steam, thunderbird etc do not work. They show
up in process when I attempt to execute them but getting the gui up is
impossible. Thus, before I leave for work, I have to turn on my
Ultimate x64 pc, log on locally, or my programs won't work when I
remote in from work.

I have been looking for a solution to this for some time. It is quite
annoying.

On Apr 7, 11:16*am, HerbD <He...@discussions.microsoft.com> wrote:
> My problem is similar except in my case the disconnect isn't a timeout. I
> clicked the disconnect button. When trying to log back on later, I receive a
> message saying the host was busy processing a logoff, delete, etc. When I
> return home, the host is still hung and I have to hit the reset button to
> reboot. If I try to login at the local console, I can enter my password but
> it hangs at the welcome screen.
>
> My host is Vista Ultimate and the remote is XP Pro.
>
> "Sooner Al [MVP]" wrote:
> > Is the RDC session idle when the disconnect happens? Is this in a standalone
> > work group environment or a domain environment? There are group policies that
> > control idle sessions. Perhaps that is the problem.
>
> > --
>
> > * * Al Jarvi (MS-MVP Windows – Desktop User Experience)
>
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights...
> > The MS-MVP Program -http://mvp.support.microsoft.com
>
> > "George" wrote:
>
> > > Hi
> > > I am connecting to a Vista desktop from a Windows XP 64 bit laptop. *The RDP
> > > Client appears to be version 6. *After a period of time (guessing 20 mins)
> > > the remote desktop connection disconnects. *NB: A second RDP connection to a
> > > separate Windows XP SP3 computer does not. *When I try to reconnect, I get
> > > the login screen, then when I try to login - the screen starts the login
> > > process, then hangs. *It makes no difference whether I try to loginusing RDP
> > > or actually login from the console - the same thing happens.
> > > I then have to cold reset the computer. *The whole process kinda defeats the
> > > purpose of remote desktop.
> > > Does anyone have any ideas where I can start to diagnose the problem.*Is
> > > this a known issue?
> > > Thanks
> > > George