Using WCF in an environment where DNS resolution doesn't work.

The Situation:

We've got a WCF webservice using basicHttpBinding deployed to a WinXP
server in a WORKGROUP on a different subnet from our client. Name
resolution doesn't work from the client box to the server, while IP
addressing does.

I can address obtain the main WSDL file by addressing it through the
IP address, as in:

http://<ipaddress>/<path>/MyService.svc?wsdl

The problem is that this service references other WSDL files. These
WSDL files use the box name in the link. Is there a way to force the
system to use the IP address instead when generating these links??

Hello, kiltsarebreezy@hotmail.com!

Does WCF service uses IP addresses in the endpoint addresses?

You wrote on 1 Mar 2007 22:40:08 -0800:

k> We've got a WCF webservice using basicHttpBinding deployed to a WinXP
k> server in a WORKGROUP on a different subnet from our client. Name
k> resolution doesn't work from the client box to the server, while IP
k> addressing does.

k> I can address obtain the main WSDL file by addressing it through the
k> IP address, as in:

k> http://<ipaddress>/<path>/MyService.svc?wsdl


With best regards, Vadym Stetsyak.
Blog: http://vadmyst.blogspot.com

If the problem is with WSDL, you could create your own WSDL Exporter and plug
it in WCF. Just rename the URI's to the IP addresses needed.

HTH

"kiltsarebreezy@hotmail.com" wrote:

> The Situation:
>
> We've got a WCF webservice using basicHttpBinding deployed to a WinXP
> server in a WORKGROUP on a different subnet from our client. Name
> resolution doesn't work from the client box to the server, while IP
> addressing does.
>
> I can address obtain the main WSDL file by addressing it through the
> IP address, as in:
>
> http://<ipaddress>/<path>/MyService.svc?wsdl
>
> The problem is that this service references other WSDL files. These
> WSDL files use the box name in the link. Is there a way to force the
> system to use the IP address instead when generating these links??
>
>