![]() However this is obviously not the preferred solution. This tool is a lightweight, standalone tool designed to be run directly on the Symantec Endpoint Protection Manager (SEPM) server, and should return a graphical display of the content distribution status. It's getting to the point where I'm considering setting up LiveUpdate to run once a day and to allow all traffic out to the internet for a 10 min widow while it does. The Content Distribution Monitor helps monitor Group Update Provider (GUP) health and status as well as general content deployment. Should these CNAMEs be added to the policy as allowed or should the firewall be able to deal with them? I've done some packet tracing when all traffic is allowed and it looks like LiveUpdate has multiple CNAMEs returned from the DNS. The tech article in question can be found here: However, when I block internet traffic, allow DNS lookup to pass through as LiveUpdate uses FQDNs and follow the Symantec tech article to allow it through the firewall, it fails every time. ![]() The updates work when I allow all traffic from DMZ -> WAN, so I know the Symantec software is installed fine. Troubleshooting when a client does not update content. I'm running 6.0.4 on a 200E and need to allow Symantec LiveUpdate to run through the F/W. The internal LiveUpdate server has connectivity to Symantec LiveUpdate. I'm hoping someone here has successfully been able to set this up and can give me some pointers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |