We have a WCF service deployed on a Windows 2003 server that is exhibiting some problems. The configuration is using `wsHttpBinding` and we are specifying the IP address. The services is being hosted by a Windows Service.

When we start the service up, most of the time it grabs the wrong IP address. A few times it bound to the correct address only to drop that binding and go to the other address (there are 2) bound to the NIC after processing for a short while.

It is currently using port 80 (we've configured IIS to bind to only 1 address via `httpcfg`) although we have tried it using different ports with the same results.

When the Windows Service starts hosting the WCF service, the properties show that it is being bound to the correct address; however, tcpview shows that it is indeed listening on the incorrect address.

Here is the portion of the config that sets up tehe baseAddress. The one that gets bound to ends up being .4 instead of .9

```
<services>
    <service name="Service.MyService"
             behaviorConfiguration="serviceBehavior">
        <host>
            <baseAddresses>
                <add baseAddress="http://xx.xx.xx.9:80/" />
            </baseAddresses>
        </host>
        <endpoint address="MyService"
                  binding="wsHttpBinding"
                  bindingConfiguration="WSHttpBinding_IMyService"
                  contract="Service.IMyService" />
        <endpoint address="mex"
                  binding="mexHttpBinding"
                  contract="IMetadataExchange" />
    </service>
</services>

```

* Is there some other configuration that needs to be set?
* Is there a tool that can help track down where this is getting bound to the wrong address?