My Web Service hosts windows 2003 applied WSE3. The Client run fine in
WindowsXP.But it throws some exception at windows 2k.
The web service use usernameForCertificateSecurity and custom
securityTokenManager.

<outputMessage utc="2006-5-23 15:37:21"
messageId="urn:uuid:afe83caa-291a-4ffd-878c-4304341b68fc">
   <processingStep description="Unprocessed message">
     <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
       <soap:Body>
         <soap:Fault>
           <faultcode
xmlns:q0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d">q0:UnsupportedAlgorithm</faultcode>
           <faultstring>An unsupported signature or encryption algorithm
was used ---> WSE3002: The receiver is expecting the key wrapping algorithm
to be http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p, but the incoming
message used http://www.w3.org/2001/04/xmlenc#rsa-1_5.  You can change the
key wrapping algorithm through configuring security token
manager.</faultstring>
           <faultactor>http://59.36.96.139/TYDMExService.asmx</faultactor>
         </soap:Fault>
       </soap:Body>
     </soap:Envelope>
   </processingStep>
   <processingStep description="Entering SOAP filter
Microsoft.Web.Services3.Design.UsernameForCertificateAssertion+ServiceOutputFilter" />
   <processingStep description="Exception thrown: Send security filter on
the server could not retrieve the operation protection requirements from the
operation state.">   at
Microsoft.Web.Services3.Security.SecureConversationServiceSendSecurityFilter.SecureMessage(SoapEnvelope envelope, Security security)
  at
Microsoft.Web.Services3.Security.SendSecurityFilter.ProcessMessage(SoapEnvelope envelope)
  at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope
envelope)</processingStep>
 </outputMessage>

How to correct the signature or encryption algorithm ?
How to modify the client app.config?

Your answer is welcome.