2.0 app talking to 1.1 webservice via SSL......

[charry]

Just migrated our public website to .NET 2.0. Everything went OK,
except for a couple secure webservices that are not under our control.

Basically everytime I try to call any functions associated with them, I
get the following message (after a long delay):

System.Net.Sockets.SocketException: A connection attempt failed because
the connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond

I had gotten this with webservices that ARE under my control, I
realized that the Web References directory needed to be re-copied to
the server after recompiling the projects for .NET 2.0 (looks like the
reference map files changed slightly). Once I recopied the directory,
everything worked OK with those. I did the same for the services that
I dont have control of, but Im still getting the above error. Note
that I can go on the webserver and directly access the URL of the
webservice.

Any ideas? Is it possible that our .NET 2.0 site isnt talking nicely
to the .NET 1.1 webservice? I didnt think that would matter (its just
SOAP and XML), but Im at a loss as to why I cant contact an external
service anymore. This all used to work before, but obviously our app
was 1.1 along with the webservice we're trying to connect to.

Thanks!
-Chris

[RYoung]

For the .NET 2.0 clients who have web references to the 1.1 services, did
you update the web reference? I know you said you recompiled the client, but
I'm not sure if that updates the web reference.

Have you tried creating a 2.0 test project from scratch and adding a web
reference to the 1.1 service to see if that works?

Ron

<ch****@gmail.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...

Just migrated our public website to .NET 2.0. Everything went OK,
except for a couple secure webservices that are not under our control.

Basically everytime I try to call any functions associated with them, I
get the following message (after a long delay):

System.Net.Sockets.SocketException: A connection attempt failed because
the connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond

I had gotten this with webservices that ARE under my control, I
realized that the Web References directory needed to be re-copied to
the server after recompiling the projects for .NET 2.0 (looks like the
reference map files changed slightly). Once I recopied the directory,
everything worked OK with those. I did the same for the services that
I dont have control of, but Im still getting the above error. Note
that I can go on the webserver and directly access the URL of the
webservice.

Any ideas? Is it possible that our .NET 2.0 site isnt talking nicely
to the .NET 1.1 webservice? I didnt think that would matter (its just
SOAP and XML), but Im at a loss as to why I cant contact an external
service anymore. This all used to work before, but obviously our app
was 1.1 along with the webservice we're trying to connect to.

Thanks!
-Chris