You can choose between the following approaches, as far as I know:
1) A command line tool called svcutil.
2) In VisualStudio 2008, go to the Project menu and locate the Add Service Reference menu item.
Both the above alternatives work with WSIT web services developed in Java (Metro web service stack), but I don't know if it works with Axis 2.
This looks like an issue with the client, so switching to a different server stack (like WSIT) won't do much good.
I'd start by using a tool like SOAPUI or tcpmon to examine what does get sent to the service. Does the SOAP include the same (or functionally equivalent) WS-Security information as the one sent by the Java client? That should provide a starting point for further investigation.
My thought was that if you switch to Metro, for the client, you get:
- Tooling support in NetBeans which simplifies development.
- A web service stack that has been tested to be compatible with .NET web services.
Of course, you can hand-tweek the client requests, as mr Dittmer suggests, but I'd rather learn something that I can use and rely on in the future.
My 5 cents.