August 24, 2010 at 7:29 pm
OK- I've repeated this 20 times or so. When SQL Server is running- even if just the database engine, and I attempt to copy a large file (30GB) from another server using unc name, 10 - 15 minutes into the file copy, the server "Goes haywire".... now, usually I would use much more specific descriptions, but this is like nothing I have ever seen. First the file copy terminates with the message "the specified network name is no longer available". I'm connected to the server via RDP, and my connection does not drop. However, other servers on the domain, and my own PC, are unable to ping to the server. Any RPC connections to the server fail. The server is also unable to connect to other servers. SQL Agent, or anything else using domain credentials stops working and a message "unable to bind to the domain" appears in the event logs. At first, I suggested this was somethign to do with the NICs, but the hosting guy says he checked on everything, and I can confirm it doesnt happen with SQL Server Service stopped...
any help?
August 24, 2010 at 7:31 pm
forgot to mention- also get this in event logs to the two nics:
Event Type:Warning
Event Source:l2nd
Event Category:None
Event ID:4
Date:8/24/2010
Time:8:09:42 PM
User:N/A
Computer:omitted
Description:
HP NC382i: The network link is down. Check to make sure the network cable is properly connected.
Data:
0000: 00 00 00 00 02 00 4e 00 ......N.
0008: 00 00 00 00 04 00 05 80 .......?
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
August 24, 2010 at 9:51 pm
Make sure the switch you are attached to is set to the same Duplex level as your NIC. If your switch is set to 1000Mb/s FULL DUPLEX and your server NIC is set different, you may be getting dropped packets or other network anomalies. Contact your switch admin to monitor your port and confirm duplex settings match to your NIC.
EDIT:
Also, if you haven't already, disable Windows 2003 denial of service detection.
http://msdn.microsoft.com/en-us/library/cc296620%28BTS.10%29.aspx
I ran into this issue on Virtual Windows 2003 servers.
August 26, 2010 at 5:47 am
Did not change the DoS registry key as I was not getting the tell-tale messages in the event logs.
Strange enough- I applied CU 11 and the problem has not recurred.
October 6, 2010 at 6:17 am
This problem ended up coming back after CU 11.... this was the final fix: http://support.microsoft.com/?id=948496
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply