WCF EndpointNotFoundException while dialing

Question

WCF EndpointNotFoundException while dialing

shreyansh raj 0

System.ServiceModel.EndpointNotFoundException: Could not connect to the remote endpoint 1888 3199479

Server stack trace:

  at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

  at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

  at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
```   Exception rethrown at [0]:

```powershell
  at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
```Inner Exception: 

System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party 1888 3199479 did not respond 

   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

   --- End of inner exception stack trace ---

Starry Night 600 Reputation points

2025-09-01T13:30:34.6266667+00:00

From document EndpointNotFoundException, we can find that The endpoint may not be found or reachable because the remote endpoint is down, the remote endpoint is unreachable, or because the remote network is unreachable. It is necessary to determine where the problem specifically lies based on your actual usage scenario. So, could you please explain in detail what functionality you are trying to implement when this issue occurs?

1 answer

Your answer

Starry Night 600 Reputation points

2025-09-01T13:30:34.6266667+00:00

From document EndpointNotFoundException, we can find that The endpoint may not be found or reachable because the remote endpoint is down, the remote endpoint is unreachable, or because the remote network is unreachable. It is necessary to determine where the problem specifically lies based on your actual usage scenario. So, could you please explain in detail what functionality you are trying to implement when this issue occurs?

Answer 1

Thank you for reaching out. Please find the answer below.

The System.ServiceModel.EndpointNotFoundException with an inner SocketException (10060) typically occurs in WCF applications when the client cannot establish a connection to the remote service. This is a network-level failure, meaning the client tried to reach the server but got no response within the allowed time. The most common reason is that the endpoint (the address and port where the service is hosted) is either incorrect, unreachable, or not actively listening.

Even if the service is running, the error can still occur due to several other factors. For example, the service might not be listening on the expected port, or the endpoint address might be misconfigured. Firewalls or network restrictions could block the connection. Additionally, mismatched WCF bindings between client and server, or infrastructure components like load balancers not routing traffic correctly, can also cause this issue. Timeouts due to server overload or slow responses are another possibility.

Comprehensive Troubleshooting Steps

Here’s a checklist that covers all the major areas:

Verify the Endpoint Address

Ensure the URI in your client configuration is correct.
It should be a valid format like http://hostname:port/ServiceName or net.tcp://hostname:port/ServiceName.
Avoid placeholders or malformed values like 1888 3199479.

Confirm the Service is Running

Check that the WCF service is deployed and actively running.
If hosted in IIS, ensure the application pool is started.
If self-hosted, verify the host application is running.

Check if the Port is Listening

Use tools like netstat -an or PowerShell to confirm the service is listening on the expected port.
- Example: netstat -an | findstr :8080

Test Network Connectivity

From the client machine, try: ping hostname
If these fail, there may be a network or DNS issue.

Review Firewall and Security Settings

Ensure firewalls on both client and server allow traffic on the service port.
Check antivirus or endpoint protection software that might block connections.

Validate WCF Configuration

Ensure the client and server use compatible bindings (basicHttpBinding, netTcpBinding, etc.).
Mismatched bindings will prevent communication even if the endpoint is correct.

Check for Timeouts and Server Load

If the server is under heavy load or slow to respond, increase timeout settings in the client config.
- Example: <binding openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" />

Consider Load Balancers or Reverse Proxies

If your service is behind a load balancer or proxy, ensure it routes traffic correctly.
Check for sticky sessions, health checks, and port forwarding rules.

Enable Logging and Diagnostics

Turn on WCF tracing and message logging to capture detailed error information.
This helps identify whether the issue is on the client, network, or server side.

Let us know if you need further help with this. We'll be happy to assist.

If the issue is resolved, Kindly mark this as answered.

Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-02T11:05:32.5966667+00:00

Hope you're doing well. We're following up on the ticket. Please let us know whether the issue persists or has been resolved. If the issue has been resolved, kindly mark the response as answered.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-05T08:52:50.5733333+00:00

Hope you're doing well. We're following up on the ticket. Please let us know whether the issue persists or has been resolved. If the issue has been resolved, kindly mark the response as answered.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-09T09:16:13.46+00:00

Hope you're doing well. We're following up on the ticket. Please let us know whether the issue persists or has been resolved. If the issue has been resolved, kindly mark the response as answered.
Varsha Dundigalla(INFOSYS LIMITED) 2,700 Reputation points Microsoft External Staff

2025-09-12T08:53:26.3833333+00:00

As we haven’t received any further updates or follow-up on this thread, it has now been closed. If you need additional assistance or have new information to share, please feel free to post a new thread. We’ll be happy to support you further as needed.

Share via

WCF EndpointNotFoundException while dialing

1 answer

Your answer