Thanks for your response Andreas,

Yes, I think this is a DNS or webserver(IIS)'s IP address related problem
because when creating the asp.net webservice, the address location we view
in the generated asmx file in browser is identical to the address of the
IIS website's ip address(or mapped dns name....).  You can test this with a
web page application also (view some webpages in the server from
browser...). And vs 2005 has no idea of whether the iis site or local
machine has a public IP to external internet or not.....

Also, based on my local test, the expected behavior should be, the address
location in the asmx WSDL document should be the same with the address we
typed in browser...   e.g:

when I navigate to the asmx view through

http://localhost/WebServices/MyWebService/Service1.asmx?WSDL

then, the WSDL's service endpoint shows

<wsdl:port name="Service1HttpPost" binding="tns:Service1HttpPost">
 <http:address
location="http://localhost/WebServices/MyWebService/Service1.asmx" />
 </wsdl:port>
 </wsdl:service>

while if I navigate it through public servername:

http://servername/WebServices/MyWebService/Service1.asmx?WSDL

the wsdl document's endpoint address should be:

<wsdl:port name="Service1HttpPost" binding="tns:Service1HttpPost">
 <http:address
location="http://servername/WebServices/MyWebService/Service1.asmx" />
 </wsdl:port>
 </wsdl:service>

Anyway, the clientside proxy can flexibly change the address to the new
value or updated value since they may create the proxy from a local copy of
the WSDL document rather than through the asmx address...

Thanks,

Steven Cheng
Microsoft Online Support

--------------------
From: "andreas.w.h.k. :-\)" <awhk@newsgroup.nospam>
References: <#08hFCdEGHA.3100@tk2msftngp13.phx.gbl>
<OMf94seEGHA.208@tk2msftngp13.phx.gbl>
<VWx4Q8mEGHA.1236@TK2MSFTNGXA02.phx.gbl>
Subject: Re: Continued: How to change address location
Date: Fri, 6 Jan 2006 09:42:27 +0100
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-RFC2646: Format=Flowed; Original
Message-ID: <#3MKk0pEGHA.3200@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: www.kf.no 195.18.146.10
Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.webservices:13262
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Thank you very much for your reply, Steven!

My problem is that the address:location (in the WSDL) differs from the url
in which I use when I surf to my webservice. When I try to Invoke my method
(via the webform) the result pops up in a new window with the url of the
address:location. And that is the wrong url. That is not the URL which I
use
when I surfed to my webservice.

Could it be an DNS issue? Because the address in the address:location is
only accessable from the intranet. And the address I use to access the
webservice is a public address accessable from the internet. Two DNS
pointing at the same service.

Andreas :-)