I am unable thus far to get SOAP requests to be answered at my server hosting them. The web services are hosted on Windows 7 Starter (using appcmd.exe to configure) and Windows 7 Home Premium (in order to test IIS Manager ad validate appcmd settings).
The web service is active (Application created with appcmd.exe) and the service's asmx page returns the descriptions of all the web methods. I can invoke any web method successfully and see the results as expected when I test on via the localhost URL. I added <protocol><add name="HttpGet"/><add name="HttpPost"/></protocol> to my web.config file to allow HTTP-based testing outside of the network. This all works fine.
However, when the web service methods are called via SOAP client, the request times out, with no record (as of yet I cannot find anything in logs, despite enabling logging at all levels I could find so far for my application) of failure at the web method host server. Temporarily dropping firewalls: same result.
SOAP requests previously worked fine when the web service was hosted on Windows Vista with IIS7. Web service was initially written with .Net 2.0 and running just fine (both HttpGet and HttpPost as well as SOAP calls) previously on the Vista implementation. I tried adding <add name="HttpSoap"/> as well to the web.config file on the Win 7 deployments, but the same results.
Code is C#.Net.
Any suggestions or insights into what has changed with Win 7 / IIS7?
Thanks very much.