Folks, strange issue... We have a web service installed in our dev
environment and it works fine.  Installed it on 2 servers for testing
and again fine.  Now on production it works on 1 server and fails on
an other one!

The URL http://server/service/service.asmx works fine, it lists the
functions and you can click on them to fill in parameters to execute
the functions.
Executing the function itself doesn't work.  Then the return is a 404
for the URL http://server/service/service.asmx/function

After quite a lot of digging on the net, it ain't the utility URLScan
from Ms because that is not installed.
It ain't a problem with POST or GET as both are defined in the
web.config of the service.

I'm sort of desperate on this...
I'm assuming there is nothing wrong with the installation of the
webservice as we don't have to change anything after running the
installer and it works on all other servers.
I'm assuming the .net runtime is installed correctly for the IIS
because it can list the functions when you go to the .asmx page

I am guessing that the IIS is not passing the URL to the aspnet
process but how can this be checked?
Any other insights or things to try are more than welcome.

tia