Symantec Messaging Gateway 9.5 (SMG) or later servers are undetected while attempting a manual or Product Discovery integration into Symantec Protection Center 2 (SPC)

Article:TECH175999  |  Created: 2011-12-01  |  Updated: 2012-02-02  |  Article URL http://www.symantec.com/docs/TECH175999
Article Type
Technical Solution


Subject

Issue



No Symantec Messaging Gateway 9.5 (SMG) or later servers are detected while attempting a manual or Product Discovery integration into Symantec Protection Center 2 (SPC). During the add product integration an error relating to the failed integration attempt may be displayed.


Environment



SPC 2 / SMG 9.5


Cause



The SPC  Product discovery process is unable to detect or interact with the SMG discovery web services. This can be caused by firewall rules blocking traffic over port 8443, or it can be caused by a configuration setting on the SMG server that restricts management access to specific hosts.


Solution



Check the SMG  9.5 server configuration for the presence of Host Access Control settings. If this feature is enabled, you must add the IP address of the SMG server into the allowed hosts, or you may need to disable this feature and allow ALL HOSTS. The steps to check this are below:

  1. Log on to the SMG web console and navigate to Administration > Settings > Control Center
  2. On the Access tab verify that the SPC 2 appliances IP address and/or Fully Qualified Domain Name (FQDN) has been added to the Hosts area, if you are using this security feature of SMG.
  3. Save the settings


     
  4. Log on to the SPC 2 web console and re-attempt the integration.

Note: If you continue to have difficulty activating your SMG application consider changing the access level to "ALL HOSTS" in the SMG Control Center.

If integration is now successful you can continue to troubleshoot this issue, or keep the configuration in this state.

Please notify SPC and/or SMG support about the Host Access Control setting issue so they can perform tracking of this issue, and investigate further. 




Article URL http://www.symantec.com/docs/TECH175999


Terms of use for this information are found in Legal Notices