HP,Altiris Group

Symantec AV client is connecting to the parent server but it is being told or is reporting it's antivirus definition files are current, eventhough, they are not.  The Client log file shows it connected but it also shows av definitions are current.

 

Anyone know what or why the client is reporting current when it is not.  Example.  My client  was installed fresh with a def date of 1/15/09.  My client connected to the server to update but then does not as it thinks it's current.  The .xdb file on the server is 11 Mar 09.

 

Why would this be? 

Yes, I have the same problem, Attached is the screenshot. Any idea from anyone appriciated.

I'm having the same problem with PTP signatures. The other two seemed to be OK.

I got this error.

I have deleted all my manager updates, but the error still happen in some machines.

I have set the clients to use Symantec LiveUpdate also to download the definitions fro internet. After that, I have disable this option and now my clients done the PTP update from my manager.

I don't know why this is happening, but every time I install a new client, I have to leave the Symantec internet update about 24h to disable it later.

@samiron7567 Actually I think that your problem and Dan's problem are slightly different. There is a difference between showing the wrong date, and "wating for updates". Also obviously dan's problem is for antivirus not PTP. The solutions might end up being the same, I just think it is important to point out these differences.

However I want you guys both to take a look at this forum we have going already to see if anything helps you. The link for that is here:
https://www-secure.symantec.com/connect/forums/antivirus-and-antispyware-definitions-are-upto-date-showing-out-date-sep-client

A couple of the important links to check out from that forum are:
http://service1.symantec.com/support/ent-security....

http://service1.symantec.com/support/ent-security....

Cheers,
Grant

PTP doesn't have that much updates. They don't release it often.

Mon makes a good  point. We had a user post about PTP not updating, but as it turned out it was updated but just had a earlier date than its antivirus counterparts. However this would still report the date, it would just be earlier than the other two. So I don't think this is what samiron is experiencing. If you look at his screenshot it is obvious that something is wrong with PTP.

PTP may not have constant updates, but It would be nice if Symantec has a webpage that lists all the latest version of AV, PTP and IPS.

Nice bjohn, I was also looking for PTP and NTP update list from Symantec Site but cannot find it. Hi Dan, our PTP update for today is April 24, 2009 r16, can you see your PTP update?

LOL, you are way behind then.

All of my machines have 2009-05-15 rev. 019. (i'm only testing on about 50 machines)

One of my laptops that update from the Internet (rather than SEPM) has 2009-05-18 rev. 018. I have no idea how this machine gets the latest PTP. Even when I run liveupdate manually, I don't get 2009-5-18.

This is why it is very important to have a page that lists the latest  AV, PTP, IPS signature dates for SEP.

I know that Paul from Symantec says the dates really don't matter, because the engine runs anyway, but that's besides the point.

Instead of having irregular update dates. Why can't Symantec just change the date stamp of the file weekly just for the sake of updating. I know it could be a waste of their time, at least we'll have the assurance that we're getting updates and the update engine works.

As for samiron7567's problem. Is it solved yet?

Are you using a push or pull method for your clients to communicate with the manaement server?

Either way...  Do you know what the default port numbers are for both the "server conection" updates and the "definitions"?

I believe they are ports 3389 and 8014

Have you tried, from the client that is experiencing problems:

telnet [server name] 3389
telnet [server name] 8014

There may be something blocking on the server side if you are using pull method or something blocking on the client for a push method.

Also, I did not read the linked article, so forgive me, but have you ensured that the "Liveupdate policy" is configured to use an internal server: "Use the default management server (recommended)" and this value was not changed?

Hmm I agree with all of you on the topic of posting the version numbers. I am submitting a product enhancement on it, and I suggest you guys do the same. I also will mention it to my superiors and see what can be done.

Cheers
Grant

Thanks grant. I submitted a product request.

P.S. Looks like the latest PTP signatures are 2009-05-19

Hey bjohn, your PTP def update is 5-15-09? Mine is only 4-26-2009 but I have a check mark? Hmmm, wat could have happened?

i don't know, but I have the same problem.
My PTP signatures never seemed to update automatically. When I run liveupdate manually from the SEPM console, it updates.
All my other signatures have no issues.

P.S. the latest PTP is 2009-05-19 rev. 018

With Paul's case, could it be possible that PTP checks tha latest updates only from the local SEP server and not the internet. It could mean the the server only has that update as the latest.

Just an update, my PTP defs are still the same but it has a green check icon.

Check the defs on the server.