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

[Dacosta]

Dear all friends,

The database is running on VMWare ESXi 5.0, the physical server is IBM System x3850 X5  with:

OS: Windows Server 2008 R2 Standard

SQL Server 2008 R2

I have checked the network is ok, I use the robocopy 10 GB file from  client to database server with no error. No firewall from clients and  database server.

The error is: [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation, the error show often but sometime 30 minuses, sometime 1 hour or 2 hours.

I have tried:

Click Start, click Run, type regedit, and then click OK.
    Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    On the Edit menu, point to New, and then click DWORD Value.
    Type SynAttackProtect, and then press ENTER.
    On the Edit menu, click Modify.
    In the Value data box, type 00000000. Click OK.
    Quit Registry Editor.

and:

netsh int tcp set global chimney=disabled

also I disabled the chimney on the NIC card configuration.

I also changed:

Change the following key in Windows (2000, XP, 2003, Vista, 2008, 2008 R2, Windows 7):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

Value Name:  TcpMaxDataRetransmissions
Data Type:   REG_DWORD - Number
Valid Range: 0 - 0xFFFFFFFF (I changed to 120)
Default:     5
                         

Change the following key in Windows (2000, XP, 2003, Vista, 2008, 2008 R2, Windows 7):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ID for Adapter

Value Name:  TCPInitialRtt
Data Type:   REG_DWORD
Valid Range: 300-65535 (milliseconds in decimal) (I changed to 60000)
Default:     0xBB8 (3000 milliseconds expressed in hexadecimal)

I also test with http://communities.vmware.com/thread/329241?start=15&tstart=0
 

But all no success.

Please help me!

Thanks

[BrianDVS]

Were you ever able to resolve this?  I have one on esxi4.1 with the same issue.

2008r2 serves, one with sql and one terminal server both on the same box same virt card...

they were just both windows patched after not being touched for almost 1.5 years and now this...