Re: Timeout value in new RDP 6.0 client
- From: "Charles Babbage" <CharlesBabbage_at_lineone_dot_net>
- Date: Wed, 13 Dec 2006 19:06:40 -0000
Thanks for the reply Josh - I got fed up at about 3 minutes and manually
cancelled the connection. The server I was trying to connect to was under
severe load which is why it was failing to connect. Under the same load, the
5.0 client would timeout pretty consistently after 30 seconds.
"Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:efRJ7ytHHHA.3268@xxxxxxxxxxxxxxxxxxxxxxx
There is still a timeout built in to the client, at least in every case
I've seen. Is it possible the connection is just progressing slower than
people are used to? How long have you allowed a connection to sit before
cancelling it?
--
Josh Rosenberg [MSFT]
SDE - Terminal Services
"Charles Babbage" <CharlesBabbage_at_lineone_dot_net> wrote in message
news:etxrWLsHHHA.3424@xxxxxxxxxxxxxxxxxxxxxxx
With the 5.0 client, it would timeout after 30 seconds if it couldn't
connect to a server. The 6.0 client doesn't seem to do this in that it
just waits and waits. Is this something that is configurable somewhere -
I'd like to be able to have my attempted sessions timeout and error if
they can't connect? A quick regmon (process monitor?) suggested it
wasn't.
.
- Follow-Ups:
- Re: Timeout value in new RDP 6.0 client
- From: Josh Rosenberg [MSFT]
- Re: Timeout value in new RDP 6.0 client
- References:
- Timeout value in new RDP 6.0 client
- From: Charles Babbage
- Re: Timeout value in new RDP 6.0 client
- From: Josh Rosenberg [MSFT]
- Timeout value in new RDP 6.0 client
- Prev by Date: Newly installed App showing on all servers
- Next by Date: Re: Deciding weather to go for terminal server?
- Previous by thread: Re: Timeout value in new RDP 6.0 client
- Next by thread: Re: Timeout value in new RDP 6.0 client
- Index(es):
Relevant Pages
|