October 24, 2012 at 6:21 am
Hi,
We are trying to connect a java application hosted on a Windows Server 2008 R2 machine hosted in Amazon Cloud, to a SQL 2005 server in our own internal network. The server in amazon cloud is connected to our network via VPN.
When attempting to connect the application to SQL Server, we are receiving the following ‘Severity 020’ error below in the SQL Server Error Log –
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.55.245]
We have googled this extensively, and it generally comes back with people trying to track down who might be attempting to connect to the SQL Server. In our case, we know who is trying to connect (our application hosted in Amazon), but we can’t get the connection to work…
Does anyone have any ideas?
October 24, 2012 at 6:29 am
a post here on SSC says one person thinks that error is related to this:
http://www.sqlservercentral.com/Forums/FindPost1168084.aspx
The first error message actually looks a lot like the dynamic packet sizing (autotuning) in Windows 7 and what it did to places like Pandora.com (i.e. disconnect every few seconds).
link to speedguide.net to check/modify:
http://www.speedguide.net/articles/windows-7-vista-2008-tweaks-2574
maybe that helps?
Lowell
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply