locked
An existing connection was forcibly closed by the remote host

    Question

  • Hi

    I would like some assistance with this. I have a distributed application that uses TCP .NET Remoting for communication between the server and client computers. 

    I am pretty sure the issue is network related because the application is currently running at multiple clients, it is running in instances where the UI on the client connects to the server over a TCP port over the internet. In this client's case, they have two sites in two different cities. The main site (where the server is located), the users connecting to the server are working fine. Even I can connect from my office if I connect via a VPN connection to their network. However, the other users from the other town, get the error "An existing connection was forcibly closed by the remote host" and their IT cannot seem to fix this.

    Any ideas on how to fix this?

    They've already done the following tests:
    • They can ping the server from the other site's computers
    • They can get an open connection when attempting a Telnet session
    • When using a sniffer to monitor the connection, they can see traffic flowing back and forth from the user machine to the server
    • On the firewall they have a rule allowing the entire site's DHCP IP range connection to the entire server IP range at the main site on all ports
    • We've tried connecting via a different port and via Singleton & SingleCall  (it is configurable in the application)
    Wednesday, April 06, 2011 12:19 PM

Answers

  • For anyone else who has this issue.  They did a full investigation from their side and eventually found the problem.  In this instance, they said the following:
    "We did find that the network configuration on the MDD side in Durban was not correct. The MDD distribution switch need to have the routing enabled from the user IP range to the server in order to establish a successful connection. This was added and the user could connect."
    I have no idea what that means, but if you give this to the IT / Network people, they could perhaps figure out how to solve.
    • Marked as answer by Viper Tuesday, April 19, 2011 10:37 AM
    Tuesday, April 19, 2011 10:37 AM

All replies

  • Simplify the reproduction of the issue.  Create a bare minimum .NET Remoting application that will reproduce the issue.  If the issue goes away, then there is an issue in the original application.  If the issue persists, it is a network connectivity setup issue.
    • Proposed as answer by Myron Walker Sunday, April 17, 2011 7:37 PM
    • Unproposed as answer by Viper Tuesday, April 19, 2011 10:38 AM
    Sunday, April 17, 2011 7:37 PM
  • For anyone else who has this issue.  They did a full investigation from their side and eventually found the problem.  In this instance, they said the following:
    "We did find that the network configuration on the MDD side in Durban was not correct. The MDD distribution switch need to have the routing enabled from the user IP range to the server in order to establish a successful connection. This was added and the user could connect."
    I have no idea what that means, but if you give this to the IT / Network people, they could perhaps figure out how to solve.
    • Marked as answer by Viper Tuesday, April 19, 2011 10:37 AM
    Tuesday, April 19, 2011 10:37 AM
  • Make ensureSecurity argument to false in RemotingConfiguration.Configure method. Like

    RemotingConfiguration.Configure(path, false);

    Wednesday, December 14, 2011 12:00 PM