Network status: At Risk but 360 status: Secure

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

Hello,

 

I'm using the latest version of Norton 360 with all the applied updates on 3 of my machines.

 

Under the network view it shows every single one of my machines as insecure, although on each machine itself, all the machines are secure (green tick on all norton 360 status'), which implies that they are all reporting incorrectly in the network status.

 

Looking at it closer if I run a diagnostic report on each machine, it shows:

 

PC Tuneup Disabled

 

However, pc tuneup is definately enabled on all machines, as they are scheduling and running tasks.

 

So I assume that each of my machines is reporting its tuneup status incorrectly accross the network.

 

Is this a known issue? I'd really like a fix for this as otherwise the entire network functionality is useless if secure computers are listed as insecure.

 

Thanks in advance,

 

Louis wu

Message Edited by louiswu on 07-13-2008 06:57 AM
Message Edited by louiswu on 07-13-2008 06:57 AM

I have read about this many times in this forum. It is a known problem, and I do not believe it is fixed as yet.

 

Please see the following thread, whcih seems to be the same issue you're seeing:

 

http://community.norton.com/norton/board/message?board.id=Norton_360&message.id=491#M491