Unable to ping or connect to Symantec Encryption Management Server (formerly PGP Universal Server) with multiple network interface cards installed after a PUP update
|Article:TECH206123|||||Created: 2013-05-10|||||Updated: 2013-07-27|||||Article URL http://www.symantec.com/docs/TECH206123|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
There is a known issue that can occur sometimes when updating the Symantec Encryption Management Server (SEMS) or PGP Universal Server. This problem occurs when updating from one major release version to another that requires a kernel update and/or an update of various other packages on the system. If you have several network interfaces cards installed in the system. An update to a newer version may change around which interface is detect as Interface 1 verses Interface 2 and so on.
Some examples of where this has occured is when updating from version 3.2.0 to 3.3.0 or 3.2.1 to 3.3.0.
Symantec Encryption Mangement Server (SEMS) or PGP Universal Server with multiple onboard network interface cards and (possibly) additional add-on Network Interface Cards installed
PUP update which requires a kernel and/or Network Interface Card driver update
Sometimes the PUP update release versions of the server require a kernel update or an update of network interface card drivers. This can sometimes change the behavior of how the underlying operating system that we use for the server detects the hardware. Restarting the server will most likely not fix the problem in this case.
Try swapping ethernet cables connected to the server around.
If you have problems after attempting to swap the cables around please contact Symantec Technical Support.
Article URL http://www.symantec.com/docs/TECH206123