Viper
Member
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:
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