Unable to connect error when using WSDL.EXE

I have setup a web service and need to generate the source code from the proxy.  I can access the web service just fine from the browser (set up in IIS), but get an error through WSDL.EXE.  The error I get is:

C:\Documents and Settings\Stew>wsdl http://localhost/Service/Service.asmx?WSDL
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: There was an error processing 'http://localhost/Service/Service.asmx?WSDL'.
  - There was an error downloading 'http://localhost/Service/Service.asmx?WSDL'.
  - Unable to connect to the remote server
  - No connection could be made because the target machine actively refused it

As I mentioned, I can access the same URL above on the same machine just fine.

Any ideas?
StewartMeyersAsked:
Who is Participating?
 
drichardsCommented:
The only other thing I can think of would be to try back on the server machine where things weren't working and substitute the machine's name or address for localhost:

    http://<machine name>/Service/Service.asmx?WSDL
or
    http://<ip address>/Service/Service.asmx?WSDL

You'll have to put in the correct values.

Also, do you have a local firewall enabled?  A lot of them allow certain apps through (like the browser) and block others.  Though they usually ask if you want to allow the new app to access the network.  I don't have any trouble running the wsdl utiity against web services on my local box.  Very odd.
0
 
drichardsCommented:
The error is saying that there is no server listening on port 80.  To be clear, you say you can see the WSDL by entering the URL "http://localhost/Service/Service.asmx?WSDL" in your browser on the same machine on which you are running the WSDL utility?
0
 
StewartMeyersAuthor Commented:
Yes, I can see the WSDL by entering http://localhost/Service/Service.asmx?WSDL in the URL in the browser; exactly the same URL I am trying to access from the WSDL utility.  I can also access the web service fine from the browser without the WSDL parameter.  IIS is setup to listen on port 80 for the default web site.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
drichardsCommented:
Have you tried the WSDL utility from another machine (not the one with the server)?  That way you could 1) see if it is a local problem and 2) monitor the network traffc and see what request is being made.
0
 
StewartMeyersAuthor Commented:
Wow, what a great thought!  I executed the WSDL utility from another machine and it worked!  So what's the deal with that?  I tried rebooting but to no avail
0
 
StewartMeyersAuthor Commented:
The firewall was the problem.  I use ZoneAlarm and as soon as I disabled it, everything was fine.  This was actually not the first time I've had trouble with ZoneAlarm interference.

Thanks very much for your help!
0
 
drichardsCommented:
You're welcome.  And happy coding...
0
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.

All Courses

From novice to tech pro — start learning today.