Timeout value in new RDP 6.0 client

Tech-Archive recommends: Fix windows errors by optimizing your registry

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.



.

Relevant Pages

  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Timeout value in new RDP 6.0 client
    ... I would suspect the problem is not so much the timeout as the severely overloaded server. ... Most likely you completed the first few stages of the connection, leading the client to believe everything was okay, but the server wasn't establishing the connection in the time you expected due to the load. ...
    (microsoft.public.windows.terminal_services)
  • Re: web serivce: client side timeout?
    ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ... John Saunders | MVP - Windows Server System - Connected System ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: detecting the (brute) disconnection of a client
    ... crashed, and if an exception occurs, then the client is deconnected. ... You can either use the timeout itself as an indication of connection failure, or you can attempt to send data after the timeout. ... The server has no way to know if the connection has failed due to a client-side crash, or simply due to a temporary problem with the network. ... IMHO, it would be better to simply let the server continue to assume that the connection is valid unless there is some explicit, non-arbitrary verification that it's not. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: web serivce: client side timeout?
    ... I have a windows forms application that makes calls to a web service. ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ...
    (microsoft.public.dotnet.framework.webservices)