14 DAY TRIAL // Microsoft is pointing customers running Windows Server in combination with older releases of Symantec Endpoint Protection and Symantec Antivirus to solution made available by the security outfit. Robert Paige, senior program manager Windows Partner Application Ecosystem Team, recommended that all the upgrades be applied as soon as possible in the context in which Symantec security products on top of Windows Server generate network connectivity problems.
“When a Windows Server is running older versions of Symantec Endpoint Protection 11 or Symantec Antivirus 10.2, they may experience performance issues for network shares, or intermittent loss of connectivity to SMB shares. We’re hoping we can help you avoid a costly and time consuming support incident by making this issue more visible to help you plan your deployments,” Paige stated.
One of the most common issues reported by end users is related to the “Network Path Not Found” error message. However, according to Microsoft, there are additional bugs dealt with in the solution provided for older versions of Symantec Endpoint Protection 11 and Symantec Antivirus 10.2.
“Symantec confirms that this is a known issue and there are updates to resolve the problem. For more information, please see the Symantec Knowledge Base article about this issue. For information about Symantec support for Endpoint Protection 11, visit the Symantec Support site,” Paige noted.
Customers that for various reasons are unable to upgrade, or if they are stuck using the security products affected by networking issues should contact Symantec technical support. The security company will labor in order to help customers deploy workarounds instead of the resolves provided.
Paige enumerated the error messages encountered by customers and dealt with by the solution provided by Symantec:
“• 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).”