Help!!! Could not establish secure channel for SSL/TLS intermittent error -- dotnet remoting

PromisedOyster
8/4/2005 8:24:47 PM

Our C#/.NET Remoting application has been running successfully for a
number of months on a number of different networks.

However, there is one client using HTTPS that is getting the following
error message intermittently:

The underlying connection was closed. Could not establish secure
channel for SSL/TLS.

Note that the same server is used by a number of clients (over the
Internet using HTTPS).

Our suspicion is their network, but to be honest, I am not sure where
to start looking.

They have replaced their modem/router. They are using a wireless
netork.

Clients are running XP Professional, NET Framework 1.1 SP1

Erick Sgarbi
8/5/2005 11:27:09 AM

I had a similar problem but slightly different exception here is what I
did:

http://support.microsoft.com/default.aspx?scid=kb;en-us;823177

Anyway, that sounds like a server certificate validation.

HTH
Erick Sgarbi
www.blog.csharpbox.com

[quoted text, click to view]

Bill
11/2/2005 1:34:02 PM

If that doesn't solve it, you may want to check if FIPS complicancy is
checked in your local security policy. If it is, uncheck it and you should be
able to connect. If FIPS is required, then .NET Framework 2.0 is suppoed to
support TLS which is a FIPS compliant protocol.
--
Bill Larson

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet remoting

dotnet remoting : Help!!! Could not establish secure channel for SSL/TLS intermittent error