WAAM, your link is failing to 404 page not found. Can you provide current link for ?
https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-security/sescloud/Getting-Started/urls-to-****-for-v129099891-d4155e9710.html
Original Message:
Sent: May 29, 2023 06:30 AM
From: WAAM
Subject: How do you **** symantec liveupdate ip in your firewall
URLs to **** can be found here :
https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-security/sescloud/Getting-Started/urls-to-****-for-v129099891-d4155e9710.html
Symantec LiveUpdate servers Used for SEP to connect to for definition engine and content updates. | https://liveupdate.symantec.com https://liveupdate.symantecliveupdate.com If you use a proxy server and default LiveUpdate servers on SEPM, allow the following URLs with port 80 (no longer required in 14.3 RU1): http://liveupdate.symantec.com http://liveupdate.symantecliveupdate.com | |
------------------------------
Wahid Amer
Strategic Support Engineer | Symantec Enterprise Division
Broadcom
Original Message:
Sent: Mar 11, 2015 06:30 AM
From: Migration User
Subject: How do you **** symantec liveupdate ip in your firewall
How do I **** liveupdate in our firewall. I have seen from this post http://www.symantec.com/connect/forums/liveupdate-behind-firewall that Symantec does not provide a list of IP addresses for the LiveUpdate. But suggest to ****. Is the FQDN always going to be correct and is it liveupdate.symantecliveupdate.com In our firewall logs we had a FTP connection from 77.67.22.169 and file livetri.zip
The ip does not have a reverse lookup name but liveupdate.symantecliveupdate.com has ip 83.148.190.96 and ping -a 83.148.190.96 gives cache.akamai.com
Did 77.67.22.169 have a short lived rDNS and DNS?