Adding UsernameToken To An Old .NET 1.1 WS VB Client HTTP 401 Authorisation Required?

This question is about using VB for writing a web services client, so I hope it will be suitable for this forum.I've been asked to add a username/pwd token to the SOAP/HTTP request headers sent by an old WS client developed years ago with the .NET framework 1.1. I believe I have done everything it is needed, but I get consistently an HTPP error 401 (Authorisation Required). I hope some experienced WSE user may help me in solving this problem, without forcing me to upgrade everything.I have downloaded WSE 2.0 SP3 and updated the WebReferences in my VisualStudio 2k3 project: a new client service class myServiceWse has appeared aside the old myService.I have followed thoroughly the example "How to: Add Security Credentials to a SOAP Message" (http://msdn.microsoft.com/en-us/library/ms819938.aspx) using the new service class and adding instructions to my old code. I have added lines to my web.config according to the sample WSE.config provided. I am enclosing the relevant lines at the end of this post.The only glitch is that the section <httpHandlers> in WSE.config mentions a class Microsoft.Web.Services2.Routing.RoutingHandler, which is actually not present in the Microsoft.web.Services2.dll file. Anyhow I'd say WS-Routing is not the issue here. I left that section out of web.config altogether.

I have tried all sorts of experiments with duration of the token, form of password sending (plaintext, hashed, none), etc. I enclose the lines of code and hope to get some useful hint.

Last details:

- the client code has worked fine beforehand, as long as authorisation wasn't required at the server. The problem is strictly related to my botched addition of WSE functionalities

- if I approach the server from another client (e.g. SoapUI) and provide the same credentials, the request is accepted no problem. So again the trouble is either in the code or in the configuration I presented in this post.

[Code]...