Re:Indy 9.0 & Socket Error # 10061 Under Win2K
All other connectivity is fine, the routes all work, I can even hit the
target with IE from the same machine.
I was rather pinning my hopes on an WINSOCK parameter that under NT is
defaulted, but needs specifying under Win2K.
I moved from TNMHTTP to avoid the memory leaks and blocking problems
experienced when compiling in Delphi5 and above.
Simon
"Patrick Van Laake" <patrick.vanla...@powersurfr.com> wrote in message
news:3c72a26e$1_2@dnews...
Quote
> "Simon Hubbard" <si...@hu66ard.freeserve.co.uk> wrote in message
> news:3c729ad6_2@dnews...
> > Anyone...
> > We've got Delphi5/6 componentry happily working with TIdHTTP all is fine
> it
> > never crashes, doesn't leak.. bah blah.
> > Problem is run the component under Win2K and we always get "Socket Error
#
> > 10061" returned when we issue a POST.
> > Anyone seen similar, I'm guessing it's WINSOCK under Win2K but what do I
> do
> > about it ?
> Hi Simon,
> It would help to specify some more details on the error and the server bah
> blah.
> Error 10061 (WSAECONNREFUSED) stands for an Connection Refused on the
remote
> machine. From my own experience I know that this need not be the case,
> however. Your first recourse would be to make sure that you can reach the
> host using HTTP with an ordinary browser. Secondly, do you connect through
a
> proxy or a firewall?
> If it turns out to be a WinSock error, I have little hope to offer. In my
> case, the problem was so deeply buried in the OS I couldn't even find it
> using the de{*word*81}. My solution was to go from using the NMfast suite of
> components to Indy 8.0, but I guess that won't really help you, other than
> knowing that it might be some obscure component setting...
> Patrick
