-2147467259 - [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation

Question

Post reply

-2147467259 - [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation

Viewing 8 posts - 31 through 37 (of 37 total)

You must be logged in to reply to this topic. Login to reply

monkeyjr SSC Journeyman Points: 98 More actions · Answer 1

finally we solved the problem by upgrade the network from FE to GE

network bandwidth not enough for the system

Brandon-904064 SSC Enthusiast Points: 165 More actions · Answer 2

I can also confirm a prior post's solution fixed our problem...disabling TCP Offload (TCP Chimney) fixed the issue for us. Here is a good link that describes, for all different OS's, how to turn off TCP Offloading.

Hope this helps!

Brandon-904064 SSC Enthusiast Points: 165 More actions · Answer 3

Oops...here's the link: http://www.alacritech.com/Support/FAQs/DisableOffload.aspx

NJ-DBA SSChampion Points: 13834 More actions · Answer 4

NJ-DBA

SSChampion

Points: 13834

March 10, 2009 at 3:00 pm

#957104

Nevermind.

Manu Kapoor SSC Journeyman Points: 88 More actions · Answer 5

This looks to be case of denial-of-service attack feature:

This might help:

Solution:

You have to make registry entry to disable the feature:

1. http://support.microsoft.com/?id=899599

Knowledge:

1. http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx

2. http://support.microsoft.com/?id=899599

I am benefitted out of it, so please check with it thoroughly.

Regards

Manu Kapoor

Irish Hall of Fame Points: 3958 More actions · Answer 6

Hey everyone,

This thread has a long and storied history. I want to add this little tidbit of information.

One of the suggested changes is to disable the TCP Offload in Windows, but what I found out today is that this is also a setting on HP NICs, particularly those that are teamed.

The long and short of it is that the setting must be modified on the NIC itself. Here's a link to the discussion thread on HP's site (There are alot of posts in this thread! You were warned :w00t: )

http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?

admit=109447626+1246034730325+28353475&threadId=1153566

Regards, Irish

Mark-527630 SSC Enthusiast Points: 160 More actions · Answer 7

I'm getting this error on a small Microsoft Access ADP application:

SQL Server 2008 Express on a Windows XP Pro SP2 box

client PC is Win XP Pro too

the error occurs when trying to open an ADO connection using the ADP's current connection.

I am going to try the TCP Chimney fix

Mark-527630 SSC Enthusiast Points: 160 More actions · Answer 8

don't have that command on Win XP.

I have created the SynAttackProtect registry key so will see if that helps after rebooting tonight.