We're building out a network of machines that exchange SOAP traffic, and we're seeing an issue not seen in development or QA.

We have a WSE3-compliant server App and a WSE3-compliant client app. Typically, the clients call web-service methods on the server. There is a use case where the server actually calls the client. The client applications add a new 'EndpointReference' to the SoapReceiver during their startup; the server knows the client addresses, and the server is able to call out to the SOAP endpoint on the clients.

For one particular machine, however, we are unable to call from the server [let's call that MachineX for this discussion]. We get a WSE101 error. We've established that MachineX is not running Windows Firewall and that nbstat -a shows 'something' listening on port 8081 .

We have a 'test client-client' that calls the Web Service that our clients have Endpoints for. From MachineX, we can run the 'test client-client' to talk to itself and that works. From MachineX, we can also run the 'test client-client' to talk to a 2nd machine -- which also works. However, from the 2nd machine (and all others that we've tried), we cannot use either our production server application or our 'test client-client' to talk to MachineX -- we get the WSE101 error.

Any suggestions on how to proceed debugging wise I'm posting on behalf of a colleague in the field, where we don't have good public internet access.

Thanks in advance,

Howard Hoffman

Oops, this is probably a DNS issue.

We've found that if we substitute the IP of MachineX for its name when trying to call it remotely, all works fine.