· Symantec Endpoint Protection versions prior to 11.0.4202 (MR4-MP2). Older versions of Symantec Symantec Antivirus (prior to 10.2) can also cause this problem. The problem occurs when you have the Autoprotect feature enabled in the applications.
· The problem can affect 32-bit and 64-bit versions of Windows Server 2003, 2008 and 2008 R2.
· The problem is intermittent, can affect client connectivity within hours to up to a week after installing the applications. Usually a server reboot will restore connectivity for a short period before the problem happens again. You generally are able to ping and RDP to the server when the issue occurs, but shares are inaccessible using either \\IPADDRESS or \\ServerName\Share operations.
· The problem results from a deadlock in SRTSP.SYS or SRTSP64.SYS in a push lock operation, which then causes blocked kernel mode server threads handling SMB negotiation requests. Network traces will show the server not responding to the SMB dialect packet.
· Error message: “The network path was not found” or “The specified network name is no longer available” when attempting to open shares, map a drive, run DCDIAG to the to the affected server, use netdom to reset secure channel
· Error message: “RPC Server is unavailable” when trying to connect via Active Directory Users and Computers
· Error message: “RPC Server is too busy to process the request” when attempting to join the Windows server domain
· Error message: “No network provider accepted the given network path” or “File or network path no longer exists” when copying a file over the network to affected servers
· Printing issues (cannot update printer IP address via DNS)
· AD replication failures
· Cluster service fails to start, or inability to access existing File Share resources even if they are online according to the Cluster Administrator snap-in
· Event log Event ID 4226 and or 2022 may occur frequently (up to every 20 to 30 seconds)