Network error occurred, Connect failed; operation now in progress (7), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
 Network error occurred, Connect failed; operation now in progress (7), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
Error code: 12034
Error text: <time><severity><host><type>  Network error occurred, Connect failed; Operation now in progress (7), check your network connection settings, check your proxy settings (if applicable), and check to ensure that port 443 (HTTPS) is open through any relevant firewalls.
Affected module: conduit
Product version: Symantec Brightmail Gateway 9.0
Cause: At specific intervals, your Symantec Brightmail appliance needs to refresh ruleset data from the Symantec Brightmail rules servers. Any interruption in connectivity between the individual appliance and the rules server can lead to this error. The following are possible causes:
DNS is not properly resolving the Symantec Brightmail rules server address
The proxy settings specified for the appliance are incorrect.
A configured proxy server is down or otherwise unresponsive.
Firewall/Routing changes are blocking connectivity between your appliance and the Symantec Brightmail rules servers.
A networking problem anywhere upstream between your appliance and the Symantec Brightmail rules servers is interrupting a valid connection.
A temporary outage may be affecting the Symantec Brightmail ruleset server farm.
Ruleset Information is not updated
Error message in Scanner logs
Conditions: There is an interruption in network connectivity between the scanner host in question and the Symantec Brightmail rules server.
Resolution: The first question to ask is whether this is a one time occurrence, a regularly recurring issue, or if it has never worked.
In the case of a one time occurrence, a communication failure can usually be safely ignored. The server will reattempt download of any rulesets. Such transient failures can occur if new settings are applied to DNS or proxy servers; or if firewall and router configurations have changed. See the table below for other possible resolutions.
Confirm manual connectivity to the Brightmail Rules Server from the affected appliance
Log on to the admin command line interface and enter: ping aztec.brightmail.com
Use the table below to determine further action to take.
Table: Results and Actions
If you get a return value of:
ping: unknown host aztec.brightmail.com
The problem is most likely rooted in your DNS configuration.
Confirm or correct your DNS configuration for the host in question and/or resolve any issues with DNS server configuration.
If you get a valid, unsuccessful ping response, such as:
Firewall rules in your deployment network may be blocking ping responses, or there may be a routing misconfiguration.
Confirm the settings for your default gateway on the affected host, and any optional routing you may have set up to ensure that your settings do not interfere with function.
You should get a valid response such as:
PING aztec.brightmail.com (220.127.116.11) 56(84) bytes of data. 64 bytes from 18.104.22.168: icmp_seq=1 ttl=244 time=373 ms 64 bytes from 22.214.171.124: icmp_seq=2 ttl=244 time=360 ms --- aztec.brightmail.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 360.669/367.142/373.616/6.501 ms 126.96.36.199) 56(84) bytes of data.
If you get a valid, successful ping response, and have configured your appliance to use a proxy server.
Confirm your proxy settings and the functionality of your proxy server.
If your proxy is up and functioning correctly, confirm that firewall rules for your deployment network allow access to port 443 on aztec.brightmail.com and that firewalls are up and functioning properly.
Imported Document ID: HOWTO65700
Subscribing will provide email updates when this Article is updated. Login is required.