I am a DBA, not a developer, so forgive me if this is a silly question. But we are having issues with a SQL Server 2005 Web Service end point. On the local network I am able to add the reference in Visual Studio 2010 with out any issues. It uses digest as the authentication scheme.
However, when anyone tries to add the web reference on another network, such as a developer in New Zeland (we are in Dayton, OH USA) he receives this error:
There was an error downloading 'http://server.domain.net:1280/release-single-address?wsdl'. The request failed with HTTP status 505: HTTP Version not supported. Metadata contains a reference that cannot be resolved: 'http://server.domain.net:1280/release-single-address?wsdl'. The remote server returned an unexpected response: (505) HTTP Version not supported. The remote server returned an error: (505) Http Version Not Supported. If the service is defined in the current solution, try building the solution and adding the service reference again.
Again, this works in Visual Studio as Right Click add Reference -> Advanced -> Add Web Reference when done on the local subnet as the server.
When done on any other network the service does not impoort. We have tried it w/o any proxy. There is a cross domain trust involved but that does not seem to be the issue as the error occurs using accounts from either domain. When I download the raw XML to my hdd I can use that to create the web reference. I believe firmly this is some sort of transport layer issue, such as a proxy, but captures when the proxy server settings are disabled are not conclusive.