Re: need help desperately. The underlying connection was closed:

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


microsoft support helped me solve this problem. The problem in essence
was the maker of the server code , did not specify which SSL protocol
they were using, and with dotnet 2.0 the dfeault is TLS, while the
server was actually using SSL3..

so basically what i had to do, is before creating any of the
communication objects run this line of code
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;

which in essence specifies the security protocol at a low level
(sockets) level, so it works no matter whether tie client object you
are using is a httpwebrequest, webclient , or webservice proxy class
generated by visual studio , or web services security extention 3
(WSE3) as is in my case.
I hope that putting this post out there, may help some other frustrated
coder in the future.

.

Relevant Pages

  • Re: 78K0 programming
    ... You did not specify a problem. ... Your original message says, in essence, ... Maybe AVR. ...
    (comp.arch.embedded)
  • Re: 78K0 programming
    ... You did not specify a problem. ... Your original message says, in essence, ... Maybe AVR. ...
    (comp.arch.embedded)