Hey Eddie,

Please check the WSDL you added the reference from.  When you look at the
WSDL, at the bottom there is a <port> element and within that a
<soap:address> element that lists the Access Point location.  Is that by any
chance set to LOCALHOST or an unreachable address?

For example, in the WSDL for the XWebEmailValidation Web Service
(http://ws.xwebservices.com/XWebEmailValidation/V2/XWebEmailValidation.wsdl)
the Access Point in the <soap:address> is a URI that you should be able to
hit with anything:
http://ws.xwebservices.com/XWebEmailValidation/V2/EmailValidation.asmx.

If you get the error when adding a reference off the WSDL above, let me
know.  It's probably something else, like a firewall that is blocking POSTs
to the Access Point location.


Cristian Sturek
Principal SOA Architect
http://www.xwebservices.com
http://www.soahub.com

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Eddie Lascu
Sent: Thursday, July 10, 2008 11:01 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Web Service generates "Unable to connect to the
remote server" exception

I have this Web Service that was made available on the Internet. Using its
WSDL file I created a Web Reference in my VS.NET 2005 project. The problem
is that every time I try to invoke any of its web methods I get the same
exception: "Unable to connect to the remote server!". Hitting the same ws
with XML Spy returns the expected SOAP responses so I am thinking that I
have something wrong in my IDE. Can anyone make a suggestion where to look
and what else to try?

Any suggestion will be highly appreciated.

Thanks in advance,
Eddie

===================================
This list is hosted by DevelopMentorR  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to