Crockett
01-09-2004, 09:27 AM
This is a verisign failure, but a problem for our customers, which is why we're involved with trying to find a solution. These certificates are not hosted, maintained, or installed by Symantec.
Verisign basically got hit with loads of people (not just those with Symantec products, btw) who had expired certificates which overburdened their servers. Verisign's servers have been up and down all day, resulting in intermittent results that people are seeing. The system is designed to automatically update these certs (thus the connections to crl.verisign.com), but if the back end servers are down, it obviously isn't able to complete the process.
I don't argue with the contention that Symantec should have a more public response up to save people the time of digging through support looking for an answer. We'll work on that.
--
Brendon Woirhaye
Sr. SQA Engineering Manager
Client Security Technologies
Symantec Corporation
http://www.dslreports.com/forum/remark,8983896~mode=flat~start=373
This fix has worked for many people:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2004010810205113
Verisign basically got hit with loads of people (not just those with Symantec products, btw) who had expired certificates which overburdened their servers. Verisign's servers have been up and down all day, resulting in intermittent results that people are seeing. The system is designed to automatically update these certs (thus the connections to crl.verisign.com), but if the back end servers are down, it obviously isn't able to complete the process.
I don't argue with the contention that Symantec should have a more public response up to save people the time of digging through support looking for an answer. We'll work on that.
--
Brendon Woirhaye
Sr. SQA Engineering Manager
Client Security Technologies
Symantec Corporation
http://www.dslreports.com/forum/remark,8983896~mode=flat~start=373
This fix has worked for many people:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2004010810205113