Symantec LiveUpdate blocked by ISA2004

I have an SBS2003 SP2 Premium install with ISA2004 that is running Symantec Endpoint Protection v11.0.4. My LiveUpdates have stopped working. When I monitor ISA2004 for denied connections, I see requests from Symantec servers denied with unidentified IP traffic.

I am not sure what has changed. This was working.

Anyone have any ideas?

Who is Participating?
dcadlerConnect With a Mentor Author Commented:
It turned out that I needed to reinstall LiveUpdate from the CD1 disk of SEP 11.0.4000 MR4. Once I did this, everything started working as expected. The process involved deleting all references to LiveUpdate in several folders before reinstalling. This problem was finally identified by a Symantec Engineer who remotely connected to the server and ran several tests. I believe that if LiveUpdate is in progress and you have a server crash or (in my case) the user power cycles the server, it can corrupt the process and require a complete re-installation of the LiveUpdate software.

I appreciate all of your feedback.

Raj-GTConnect With a Mentor Systems EngineerCommented:
I can't guess what might have changed, but this is what I would recommend.

1. Create a new domain name set with * entry.
2. Create a new firewall policy and allow FTP, HTTP, HTTPS for All Users from internal to the new domain name set above.
3. Move this rule above your standard internet access rule.

This should allow LiveUpdate working again through ISA.

dcadlerAuthor Commented:
I set up the domain and rule with no luck. I have another server that is still using ISA2000. It is running the same version of Symantec and it updates just fine. I have the proxy parameters set the same, relative to the site specifics.

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Raj-GTSystems EngineerCommented:
Since ISA is saying unidentified IP traffic, can you change the rule to allow all outbound protocols and try again? I would also like to see the ISA logs for these attempts.
dcadlerAuthor Commented:
Raj-GT, I opened up the rule to allow all outbound protocols and runing LiveUpdate from within SEPM still failed.

I beloieve now that the issue is not ISA2004 because...

From the SBS 2003 Server I was able to browse to and download the most recent SEPM .jdb file

From the SBS 2003 Server, I was able to point my browser at and also download the latest SEPM .jdb file.

I was able to do this with and without the specific Symantec firewall access rule enabled.

I am pointing the proxy to the LAN IP of the SBS2003 server and referencing ports 8080 for HTTP and 21 for FTP. This is similar to what I have configured for another client who is running SBS2003 with ISA2000.

To me, this seems to be an issue with Symantec. In SEPM rather than ISA.


On your SEPM Server , check the liveupdate log file

C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Log.LiveUpdate

does it give any errors in here ?

Do you have SEP Firewall installed ? In version MR4 MP1 there are known issues with the Network Access Control component. That version was pulled from distribution just after release ( not acknowledged by Symantec to the general public though =p) ..

try MR4 MP1a from file.connect ( if you have a support agreement )
Raj-GTSystems EngineerCommented:
When you launch the browser and access the update url, the browser will pass your credentials to ISA; this may not be the case with an autoupdate process. The rule should allow "All outbound protocols" to "All Users" and not "All Authenticated Users"; can you confirm this?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.