Not Reporting Status
Updated: 21 May 2010 | 14 comments
Hi friends,
recently i installed SEP client on 11 windows 2003 servers. all thease servers are showing in not reporting status in the front page. and this servers are not taking updates from my SEPM. and if we click on the client nothing is showing.
Last Scan = " Not Scanned"
Antivirus Status = "Not Reporting Status"
Firewall Starus = "Not Reporting Status"
discussion Filed Under:
Comments
What version of the SEP
What version of the SEP client did you deploy?
SEP 11 MR2
SEP 11 MR2
Try to use MR4 MP2 should
Try to use MR4 MP2 should help you.
If you dont want to do that then make sure that your SEPM it self is updated.
And are you using Embedded database or SQL database?
it's sql Database. and i dont
it's sql Database.
and i dont think it is the issue with MP1.......
Is the policies apllied??
Is the policies apllied?? Check the server name it is communicating to??
Regards'
Ajit Jha
Technical Consultant
STS
Policies are applied. the
Policies are applied. the clients communating with the server also.
Did u manually tried to
Did u manually tried to generate a log??If not please try it
Regards'
Ajit Jha
Technical Consultant
STS
How to generate log
How to generate log manually??
You may try this. It can be problem with live update
@ Satish_venturi
try to clear currupted live update files or if a reinstallation of SEP and Live Update is possible you may try this:
Uninstall SEP
Uninstall Live update
it will ask for restart
delete live update folder from program files
delete live update folder from C:\Documents and Settings\All Users\Application Data\Symantec
reinstall SEP
server and client
server and client communication problem,
hi mark, we run the clean
hi mark,
we run the clean wipe and re installed. same problem..............
i think kajal is right.. but
i think kajal is right..
but kajal i am getting green dot on my client PC's.
This images for the problem
This images for the problem clearence.....
DNS?
We had a similar problem with our clients. Every client we added after a particular date showed up as "not reporting status" with 0 MB of free memory and 0 GB free hard drive space. We were also unable to push out client install packages. We were able to trace the problem back to a DNS change. Someone had created a new DNS entry using the name of our Symantec Managment Console with a different IP address. Apparently some of the communication occurs by IP, and some occurs by name. After we removed the offending DNS entry and rebooted the server, things returned to normal.
Would you like to reply?
Login or Register to post your comment.