jmartine
Thu May 08 10:02:03 CDT 2008
"David Wang" wrote:
> On May 7, 8:22 am, jmartine <jmart...@discussions.microsoft.com>
> wrote:
> > "David Wang" wrote:
> > > On May 6, 10:27 am, jmartine <jmart...@discussions.microsoft.com>
> > > wrote:
> > > > We have windows 2003 sp2 with iis 6 and when ever a large file download is
> > > > attempted via http the following error happens.
> >
> > > > "Connection_Dropped DefaultAppPool" found in the httperr.log no event in the
> > > > event log and the browser shows:
> >
> > > > The connection was reset
> > > > The connection to the server was reset while the page was loading.
> >
> > > > The file is 92 megs. A file of 32megs downloads just fine.
> >
> > > My download of 272MB from IIS6 and WS03SP2 downloads just fine.
> >
> > > Connection_Dropped means exactly what it says. Perhaps something in
> > > the network between your browser and server is throttling connection
> > > time.
> >
> > > //David
> > >
http://w3-4u.blogspot.com
> > >
http://blogs.msdn.com/David.Wang
> > > //
> >
> > I have already checked with the networking guys. There is not QOS and the
> > port setting and the nics are configured correctly. The issue is that as soon
> > as I hit the 32 meg file.
> >
> >
http://website.com/fileit starts to download till done fine. When I try the
> > 92 meg
> > file
http://website.com/largerfileit fails withing about 5 seconds.
> >
> > I have not found any good information to help me point to a possible
> > solution. Any help apprieciated.- Hide quoted text -
> >
> > - Show quoted text -
>
>
>
http://support.microsoft.com/kb/937692
>
> Since I have no problems downloading 272MB from IIS6 and WS03SP2, your
> issue looks to be either:
> 1. The person who deployed and configured the WS03SP2 server made some
> configuration change that you'll have to figure out
> 2. Your download is handled by a custom ISAPI DLL which has bugs
> 3. The networking between the client and server is dropping the
> connection within 5 seconds
>
>
> //David
>
http://w3-4u.blogspot.com
>
http://blogs.msdn.com/David.Wang
> //
>
Thanks for the suggestions.
After looking deeper into the IIS config I noticed we had ASP.NET 1.x and
ASP.NET 2.x both installed and was using 1.x. I changed it to 2.x and our
issue went away.