By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,760 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,760 IT Pros & Developers. It's quick & easy.

Web Service using SSL on a new port

P: n/a
Hi,

I have created a web service which is using SSL. I already have another web
service running on the same server using SSL therefore I have to use another
port.

But I get the following error when I try to call my web service. Is there
any way to avoid this error?

The underlying connection was closed: Could not establish trust relationship
for the SSL/TLS secure channel.

Regards

Henrik Skak Pedersen
Feb 1 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Henrik,

Welcome to the MSDN newsgroup.

From your description, you have deployed an ASP.NET webservice on your
server and the webservice is protected through SSL protocol. Since there is
another existing IIS site using SSL, you have configured the new IIS site
(in which your webservice is deployed) to use a new SSL port. However, when
you try calling the new webservice(through SSL/https), you're getting the
"the underlying connection is closed..." error , correct?

Please feel free to let me know if there is anything I misunderstand.
Generally speaking "the underlying connection is closed..." is a common
error message when the client side fail to establish network connection
(ususally http connection) with the server. I think first we can check the
server's SSL configuration to ensure it works correctly. To do this, we can
put some simple aspx pages in the IIS server's application virtual
directory(or just the application virtual directory your webservice
deployed). Then, try visting them through https address from client
machine's IE browser to see whether the page can be displayed without any
error or warning. When there is something incorrect with the SSL/https
setting of the server, the browser will popup a dialog to display the
problem. For example, the server certificate is not following a trusted
path at clientside or the server certificate's servername dosn't match the
servername in the url client application request, etc... Such error or
warning can be handled or ingored when we visit the SSL protected pages in
IE browser, however, when we programmatically request those pages, this
will lead to the "the underlying connection is closed...." error.

Please have a test on the above things. BTW, the server's IIS log is
another useful information we can check.

Hope this helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Feb 2 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.