Thoughts from your friendly neighborhood technologist.

Symantec Endpoint Protection SVA Network Connectivity Issues

This afternoon while deploying the Symantec Virtual Appliance for vShield for a customer I ran into an issue after the initial deployment where the appliance could not connect to the configured network in the configuration file.

For whatever reason, the appliance is configured for the default route of the private vmservice-vshield-pg network instead of the specified  Network in the config file.

In order to get the appliance talking correctly to the Symantec Endpoint Protection Manager I had to remove the gateway for ETH1.

Login to the console of the appliance with the username admin and the password you specified during deployment.

Then type sudo su – and press enter, enter your admin password again and now you’re root.

Edit the ETH1 config by typing the following command.
vi /etc/sysconfig/network-scripts/ifcfg-eth1

Cursor down to the GATEWAY= and press your D key, and then D key again.

Write out the file by pressing the following keys in order…  : w q ENTER

Now it’s time to restart the networking service… enter the following command service network restart

Attempt to ping your Symantec Endpoint Protection Manager IP now and if you get a reply you’re all good.

This is only going to be an issue in the event that your SEP SVA is on a different network than your SEP Manager Server.


Let me know if this worked or didn’t for you, and I’ll be happy to research a little more.


  1. This was exactly what was keeping the SVA’s from talking to our SEPM. I greatly thank you for this!! Just wish I would have found it sooner.

  2. Dang, glad it’s working for you now!

Leave a Reply

© 2019

Theme by Anders NorenUp ↑