Remote Desktop hangs after inactivity

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

WindowsXP --Remote--> Windows 2003

Remote Desktop hangs anytime there is a period of long (60
seconds?)inactivity. If you wait (60 seconds or so?) then it un-hangs and
all is well. When it un-hangs there is a brief flash of the blue large
reconnect icon in the upper right of the client screen.

Any ideas appretiated -- thanks.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

GRT <no@spam.com> wrote:

> Remote Desktop hangs anytime there is a period of long (60
> seconds?)inactivity. If you wait (60 seconds or so?) then it un-hangs
> and all is well. When it un-hangs there is a brief flash of the blue
> large reconnect icon in the upper right of the client screen.

That reconnect icon signifies that your network conenction was broken, and
is being re-made. So you need to look for reasons why your network
connectivity goes down after a period of inactivity. This is not a Remote
Desktop issue as such.

What is the nature of the network connection between client and server?

--
Robin Walker [MVP Networking]
rdhw@cam.ac.uk
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Network connection is to a remote site.
Network (ping test) is up during this problem and Firewall logs show no net
down during problem. Problem is very reporduceable (just dont do any client
activity for 60 seconds and it will hang. Very odd problem.
Thanks for any ideas.

"Robin Walker [MVP]" <rdhw@cam.ac.uk> wrote in message
news:dcss0e$e47$1@gemini.csx.cam.ac.uk...
> GRT <no@spam.com> wrote:
>
>> Remote Desktop hangs anytime there is a period of long (60
>> seconds?)inactivity. If you wait (60 seconds or so?) then it un-hangs
>> and all is well. When it un-hangs there is a brief flash of the blue
>> large reconnect icon in the upper right of the client screen.
>
> That reconnect icon signifies that your network conenction was broken, and
> is being re-made. So you need to look for reasons why your network
> connectivity goes down after a period of inactivity. This is not a Remote
> Desktop issue as such.
>
> What is the nature of the network connection between client and server?
>
> --
> Robin Walker [MVP Networking]
> rdhw@cam.ac.uk
>
 

snafder

Commendable
May 25, 2016
1
0
1,510
I note this issue too. Our server is 2008 R2.
Happens no matter where I connect from outside of the network and using various OS varieties (Win7 to Win10).
The server lives internally on our network and I get the same issue when connected to the local network as when I connect remotely.
It sits behind layers of firewalls and TMG - but only for outside access.

It's a VM hosted on ESX infra that is suitably resourced.
I connect to various remote desktops on the same network (internally), hosted on the same ESX hosts, and using the same vSwitches and physical connections back to the core network, and same VLAN as the others, and don't experience the same issue with those servers.

Doesn't seem to be any different when there's a large number of users on the server or nobody else. Proc/Memory look fine.

My issue isn't specifically 60 seconds though - I've not timed it but it can be fine if I have the window open on another monitor and continue doing stuff locally on the other monitor. If I minimise the window or place things in front of the window (full screen things), or lock the local PC for a short while - then it seems to hang like the OP experiences. Same with the whole reconnecting thing.

I wonder if there's a Windows setting deep in the reg that's responsible?
Any advice or avenues for further analysis would be greatly appreciated, it is very frustrating having to wait when you come back to it.