"John" wrote:

> Thanks for the info... Still no luck tho :-(
>
>
> "blackpope" wrote:
>
> > proxies maybe? I had the same problem a while back and solution was using a
> > webproxy class and authenticating with it first. preauthenticate i think it
> > is...
> >
> > "John" wrote:
> >
> > > Calling a .net 2.0 web service, get "The underlying connection was closed: An
> > > unexpected error occurred on a receive."
> > >
> > > I have tried everything I have found on the web. The httpRequest override,
> > > disabling keep alives, increasing timeout etc, etc..
> > >
> > > I have a client app that calls the web service. If I make multiple calls in
> > > a for loop then all is well. If I create worker threads (using
> > > queueuserworkitem) I get this error after several calls. The problem seems
> > > related to the length of time the calls take, shorter ops get thru more calls
> > > than longer ones.
> > >
> > > Can anyone help?
> > >
> > > Thanks
> > >
> > > -j