Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > Underlying Connection Was Closed

Reply
Thread Tools

Underlying Connection Was Closed

 
 
Rajeev Tipnis
Guest
Posts: n/a
 
      08-19-2004

http://support.microsoft.com/default.aspx?scid=kb;en-
us;819450

Questions:
1) Is this patch (fix) applicable to the .NET 1.1
Framework as well? That is, if we have Framework 1.1 (On
Win2K3/IIS6.0), do we still need this patch?

2) Does it specifically solve only this error:
The underlying connection was closed. An unexpected error
occured on send.
and not these (which is what we are seeing):

- The underlying connection was closed. Unable to connect
to the remote server. OR
- The underlying connection was closed. The proxy name
could not be resolved, verify correct proxy configuration.

3) Would this not happen when the webservices client is
not an ASP.NET client?

Thanks
Rajeev

 
Reply With Quote
 
 
 
 
Guest
Guest
Posts: n/a
 
      05-05-2005


> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;819450
>
> Questions:
> 1) Is this patch (fix) applicable to the .NET 1.1
> Framework as well? That is, if we have Framework 1.1 (On
> Win2K3/IIS6.0), do we still need this patch?
>
> 2) Does it specifically solve only this error:
> The underlying connection was closed. An unexpected error
> occured on send.
> and not these (which is what we are seeing):
>
> - The underlying connection was closed. Unable to connect
> to the remote server. OR
> - The underlying connection was closed. The proxy name
> could not be resolved, verify correct proxy configuration.
>
> 3) Would this not happen when the webservices client is
> not an ASP.NET client?
>
> Thanks
> Rajeev
>


User submitted from AEWNET (http://www.aewnet.com/)
 
Reply With Quote
 
 
 
 
Guest
Guest
Posts: n/a
 
      05-05-2005

> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;819450
>
> Questions:
> 1) Is this patch (fix) applicable to the .NET 1.1
> Framework as well? That is, if we have Framework 1.1 (On
> Win2K3/IIS6.0), do we still need this patch?
>
> 2) Does it specifically solve only this error:
> The underlying connection was closed. An unexpected error
> occured on send.
> and not these (which is what we are seeing):
>
> - The underlying connection was closed. Unable to connect
> to the remote server. OR
> - The underlying connection was closed. The proxy name
> could not be resolved, verify correct proxy configuration.
>
> 3) Would this not happen when the webservices client is
> not an ASP.NET client?
>
> Thanks
> Rajeev
>


User submitted from AEWNET (http://www.aewnet.com/)
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Established connection aborted and underlying connection closed Apu Nahasapeemapetilon ASP .Net Web Services 0 11-06-2006 04:24 PM
The underlying connection was closed (Windows2003, .net 1.1 sp1) Jack Wright ASP .Net 3 12-06-2004 04:37 AM
Problems migrating applicacion from Intranet to Internet. Underlying connection was closed. Luis Esteban Valencia ASP .Net 0 10-26-2004 01:01 PM
RE: System.Net.WebException: The underlying connection was closed: Steven Cheng[MSFT] ASP .Net 4 04-08-2004 08:07 AM
Underlying connection was closed sumit ASP .Net 0 11-01-2003 11:28 AM



Advertisments