You do need a server certificate. This is different than Certificate
Server ...
Dan
--------------------
>Thread-Topic: ASP.NET SSL problem
>thread-index: AcTW5m1y0C2kHOF3TNyWjUZfN2+oLQ==
>X-WBNR-Posting-Host: 62.101.92.181
>From: "=?Utf-8?B?amFjaw==?=" <jack@discussions.microsoft.com>
>References: <#2T8sDl1EHA.3236@TK2MSFTNGP15.phx.gbl>
<qVll8bl1EHA.3388@cpmsftngxa10.phx.gbl>
>Subject: RE: ASP.NET SSL problem
>Date: Tue, 30 Nov 2004 06:11:04 -0800
[quoted text clipped - 12 lines]
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:26890
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 34 lines]
>> >NNTP-Posting-Host: 170.252.72.1
>> >Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
>> .phx.gbl!TK2MSFTNGP15.phx.gbl
>> >Xref: cpmsftngxa10.phx.gbl
[quoted text clipped - 13 lines]
>> >
>> >thx