Forum Discussion

JasonNall_44907's avatar
JasonNall_44907
Icon for Nimbostratus rankNimbostratus
Jun 11, 2008

SMB File Share Balancing Event ID error

I have what I would consider a pretty simple setup with attempting to configure SMB file share load balancing. I have posted on this several times over the last few months, and I have still not been able to roll this out to production

 

 

I currently have the rules configured correctly, and the forwarding appears to be working as well. The problem I am not having is that when I "enable" the SMB virtual servers, and point the traffic to the address, I am getting the following error over and over in the Windows 2003 server log.

 

 

Event Type:Warning

 

Event Source:Srv

 

Event Category:None

 

Event ID:2012

 

Date:6/11/2008

 

Time:12:07:15 PM

 

User:N/A

 

Computer:OPSDATA1

 

Description:

 

While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.

 

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Data:

 

0000: 00 00 04 00 01 00 54 00 ......T.

 

0008: 00 00 00 00 dc 07 00 80 ....Ü..€

 

0010: 00 00 00 00 84 01 00 c0 ....„..À

 

0018: 00 00 00 00 00 00 00 00 ........

 

0020: 00 00 00 00 00 00 00 00 ........

 

0028: 7a 09 00 00 z...

 

 

 

I have of course looked this up, and it appears as though the network card is being over run with traffic. The question then becomes, why would this only happen when the traffic is hitting the server via the F5, and not when the clients connect directly? Any help would be greatly appreciated!
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Sorry to hear you still haven't been able to get this working... I think it would help to have a clear idea of what the server is seeing before looking to fix it on the LTM. Have you found any MS-related articles (Click here) which might explain why the error is being generated? Can you capture a tcpdump while the error is generated?

     

     

    Aaron
  • Thanks for checking in Aaron. I have actually tried this on several different machines, and the event error follows wherever the F5 is pointing. I actually opened a case today with F5 Support, and we are looking through tcp dump files as we speak. I will keep you all posted.

     

     

    I have indeed looked at all of the articles you included. I feel like it is specifically related to the F5 though in so much as the problem follows whatever physical server I point it at. Thanks again!