Microsoft Knowledge Base Email Alertz

A file sharing connection to a Windows Server 2008-based server drops unexpectedly if the server has Symantec Antivirus installed

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 961654 - Last Review: May 28, 2009 - Revision: 2.1

A file sharing connection to a Windows Server 2008-based server drops unexpectedly if the server has Symantec Endpoint Protection prior to 11.0.4202 (MR4-MP2) or Symantec Antivirus 10.2 installed

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center

SYMPTOMS

Assume that you try to access a network file share that resides on a server that is running Windows Server 2003, 2008, or 2008 R2. However, in this situation, the file sharing connection drops intermittently after a while, and then the network share becomes unresponsive.

When this problem occurs, the following events are logged in the event log:

Event ID: 4226
Source: Tcpip
Message:TCP/IP has reached the security limit imposed on the number of concurrent (incomplete) TCP connect attempts.

Event ID: 2022
Source: server
Message: The server was unable to find a free connection number times in the last number seconds.


Note Event 2022 may occur every 20 to 30 seconds.

CAUSE

This problem occurs when Windows Server is running certain versions of Endpoint Protection 11 or Symantec Antivirus 10.2. Some file filter drivers, such as Srtsp.sys or Srtsp64.sys, may cause this problem.

RESOLUTION

To resolve this issue, follow the instructions that are provided by Symantec to upgrade the software to the latest version of Symantec Endpoint Protection 11.0.4202.75 (MR4 MP2) or Symantec Antivirus. For more information, visit the following Symantec Knowledge Base article:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102613484948 (http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102613484948)
For more information, visit the following Symantec Web site:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121216494948 (http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121216494948)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

REFERENCES

For more information about intermittent file sharing connectivity from various clients to a Windows Server 2008 server, visit the following Microsoft Web site:
http://blogs.technet.com/networking/archive/2008/07/10/intermittent-file-sharing-connectivity-from-various-clients-to-a-windows-server-2008-server.aspx (http://blogs.technet.com/networking/archive/2008/07/10/intermittent-file-sharing-connectivity-from-various-clients-to-a-windows-server-2008-server.aspx)


For more information see the following Microsoft Knowledge base articles:

961293 Unable to access Shares "The specified network name is no longer available" when Symantec Endpoint Protection prior to 11.0.4202 (MR4-MP2) or Symantec Antivirus 10.2 are installed on a Windows 2003, 2008 or 2008 R2 Server

http://kbalertz.com/Feedback.aspx?kbNumber=961293 (http://kbalertz.com/Feedback.aspx?kbNumber=961293)

961654 A file sharing connection to a Windows Server 2008-based server drops unexpectedly if the server has Symantec Endpoint Protection prior to 11.0.4202 (MR4-MP2) or Symantec Antivirus 10.2 installed

http://kbalertz.com/Feedback.aspx?kbNumber=961654 (http://kbalertz.com/Feedback.aspx?kbNumber=961654)

953615 Clients cannot get IP address from a Windows Server 2003 based DHCP server with Symantec Endpoint Protection 11.0 installed

http://kbalertz.com/Feedback.aspx?kbNumber=953615 (http://kbalertz.com/Feedback.aspx?kbNumber=953615)

923360 You may experience various problems when you work with files over the network on a Windows Server 2003-based or Windows 2000 Server-based computer

http://kbalertz.com/923360 (http://support.microsoft.com/default.aspx?scid=kb;en-us;923360)

822219 Your system stops responding, you experience slow file server performance, or delays occur when you work with files that are located on a file server


http://kbalertz.com/822219 (http://support.microsoft.com/default.aspx?scid=kb;en-us;822219)

APPLIES TO
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Server
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Standard without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Web Server 2008
Keywords: 
kbtshoot kbexpertiseadvanced kbsurveynew kbprb KB961654
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate