weird issue with dot net

default webservice doesnt accept get requests on one server only

[realmofillusions]

Best way to start is with a play by play.
I have (2)web servers in seperate locations each with a SQL connection at that location. Am using round robin for load balancing and failover, and the idea is to replicate the SQL data via the Web Servers, over 443 using a webservice. Since the remote server is at an ISP, the idea is to push and pull the data with the webservice on the remote, and a windows service on the local server(sounds simple, right?). (2) tables are to be synched, giving (4) web methods. A push, and a pull for each table, and each was written in vb.net.
Everything is right with the world on the local machine, but they refuse to show up on the remote machine. Not the methods themselves, they show as available, but they will only accept SOAP headers.
Not any remote machine, just that one.

I have gone so far as to create a default "hello world" project on that machine, and it will not accept a GET request.

The same default project will accept GET requests when created on the development machine or another remote server.
Method as follows.

<WebMethod()> Public Function HelloWorld() as string
Dim HelloWorld as string
HelloWorld = "Hello World"
Return HelloWorld
End Function

Ive double checked, and any method without arguments (which should accept a GET), will not, but only on that machine

Ive uninstalled and re-installed the .dot net platform , doesnt seem to produce any real change

I've thought through any thing that might be specific to the machine itself, permissions, evil spirits, but any thing should have been set to default when reinstalling.

Im going to end it here, if this seems to be a common problem, someone else will have encountered it and know exactly what im talking about. If not, please reply with any requests for details.

Thanks In Advance

VLG

[Ocean10000]

Update your Web.config. Depending on the servers Service pack level/Dot.Net and Version, the Protocals section of the System.Web config might have the httpPost & httpGet methods commented out. The following should fix your problem with the HttpGet operation for the webservice not working.

<?xml version="1.0"?>

<configuration>
<system.web>
<webServices>
<protocols>
<add name="HttpSoap1.2"/>
<add name="HttpSoap"/>
<add name="HttpPost"/>
<add name="HttpGet"/>
<add name="HttpPostLocalhost"/>
<add name="Documentation"/>
</protocols>
</webServices>
</system.web>
</configuration>

[realmofillusions]

your a genius

the machines in question were all built at the same time, are running the same version of .net and have identical service pack installations, so...im sticking with my 'evil spirits' theory as to why it wasnt working.

but that fixed it

Thanks

VLG