Home All Groups Group Topic Archive Search About
Author
29 Mar 2006 2:10 PM
Arne Garvander
What 'period of time' are we talking about for a WebException in .net 2.0?

System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to respond
--
Arne Garvander
Certified Geek

Author
29 Mar 2006 5:18 PM
Kevin Spencer
Hi Arne,

The timeout is determined by the WebRequest.Timeout property, for which the
default is determined by the descendant of WebRequest used. You can also set
it to whatever amount of milliseconds you wish, including Infinite (not
recommended).

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

Show quote
"Arne Garvander" <ArneGarvan***@discussions.microsoft.com> wrote in message
news:79A2D37B-1B54-4745-BBB4-44B9A2F711E5@microsoft.com...
> What 'period of time' are we talking about for a WebException in .net 2.0?
>
> System.Net.WebException: Unable to connect to the remote server --->
> System.Net.Sockets.SocketException: A connection attempt failed because
> the
> connected party did not properly respond after a period of time, or
> established connection failed because connected host has failed to respond
> --
> Arne Garvander
> Certified Geek
>

AddThis Social Bookmark Button