I'm seeing this WebException pop up randomly when connecting to an ASP.NET 1.1 Web Service using integrated authentication:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse (WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse (WebRequest request) <etc, etc> I've seen others squawking about this one in various support newsgroups, and I've seen work-arounds that relate to disabling HTTP keep-alives. While this appears to work for anonymous access, it definitely does not work for integrated authentication as integrated authentication requires keep-alives to function properly. Has anyone else come across a way to prevent this exception from occurring? Is there a server-side fix or a client-side work-around that supports integrated authentication? Many thanks! -Andy Hopper =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
