Question : Transport Level Error(Connection forcibly closed)

Application .NET 3.5
SQL Server 2008


The application connects to the SQL server over  a VPN.(Two offices connected over VPN, with the server in the head office.)

Frequently users from the branch office get this error in the application:
Transport-level error / (provider: TCP Provider, error: 0 - An existing  connection was forcibly  closed by the remote host.)

Now, the internet connection used to connect to the VPN is a dedicated line only for the VPN. Its a cheap internet line which I guess is one of the problems.

The error occurs frequently only at the branch office and never at the Head office.
Spooling is on by default.

Will getting a Private link line between the two offices help in getting rid of the error.
My guess is that its the internet connection which is unstable that is causing the error.

Is there any other cause for this?
What is the possible solution?

Attachments:

ES-Error.jpg (52 KB) (File Type Details) 

Transport level error.

Answer : Transport Level Error(Connection forcibly closed)

>> (provider: TCP Provider, error: 0 - An existing  connection was forcibly  closed by the remote host

Definitely related to VPN connectivity issues. TCP connection using VPN drops off frequently causing this error. check with your VPN admin or Network administrator to get it resolved.

More possible reasons listed here:

http://www.redmountainsw.com/wordpress/archives/tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host