405 method not allowed when calling ASP web service

I have an application that runs fine on my development machine locally that consists of a web service and a client application calling the web service.

When I move the client portion to another machine and use my dev machine (Windows XP Pro SP2, IIS 5.1) for the web service I get an error on the client app stating
"405 method not allowed" when attempting to call the web service.

I can pull up the web service web page and test it fine from the client machine, but when I run the client application I get this error.

I've searched for many fixes and already added POST and GET configs to the web.config file.  Also, I've re-installed ASP .Net on my dev machine through the aspnet_regiis -i.  My persmission are set to allow anonymous access and scripts are allowed to run.  I'm not sure what other security setting I can change.

Thanks for any help.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

have you done the WSDL file for the client again - check that it is not pointing to localhost or the lopback address. you can see the end point towards the end of ther WSDL file.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Valdar729Author Commented:
WSDL file?

I'm not sure where I would find that.

The web services are referenced through my dev machines name so when deploying the client it should be calling it by name and not ip or loopback.  I can ping my dev machine and run it through the test page fine, using the machine name.

Also, I would get a 404 error if I didn't have it set correctly, right?
Valdar729Author Commented:
I'm an idiot, I had the client app referencing the web app correctly, but there is a class that I didn't have set correctly to reference the web service.  Thanks for the help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.