Web services are hot. To make them workable in practice, however, is not easy. Often, successful implementations of Web services warrant that various applications on heterogeneous platforms participating in a service communicate correctly and effectively. But achieving seamless interoperability among participating entities in a Web service can be tricky. Despite the advances made by standards bodies like Web Services Interoperability Organization, many architectural and implementation level mismatches remain to be tackled. These mismatches stem mainly from the differences in the way various commercial and open-source Web services toolkits implement the core Web services protocols. In this paper, we look at the problems arising for accessing enterprise Java beans exposed through open source Apache SOAP server from Microsoft clients and suggest workarounds to achieve end-to-end interoperability. We demonstrate our approach through a toy application.