I think I've found the problem. There are a number of
VeriSign certificates on the system that expired on
1/7/2004 (even one for 1/6/2004). You can view them all
under the IE config options/Content/Certificates. The
one I see trying to get downloaded is the Class 3
certificate. Apparently there isn't a newer one
available or it is failing to get updated properly if it
does come down ok.
Whose responsibility is it to provide updated versions,
VeriSign or MS? I would have thought they would come
down with all these cumulative IE updates always on
Windows Update.
Jeff
>-----Original Message-----
>I've got machines that are running a much older version
[quoted text clipped - 130 lines]
>>
>.
Harry Jones - 10 Jan 2004 16:34 GMT
Thanks for the sleuthing Jeff. I'm glad I've found out
the reason for the problem I've been having, but am
perturbed for a few reasons:
a) how and when will the problem be resolved?
b) I installed ZoneAlarm and sure enough both Word and
Excel were trying to get out to the Internet. I blocked
them, but somehow they are still managing to get around
ZoneAlarm and packets are coming and going as the app is
loading. Not sure how they are evading ZoneAlarm.
c) I can't believe all the certificates in IE. Who are
these people? Should I be worried about SecureNet or
Thawte?
Perhaps I should go back to Netscape. Maybe that would
help.
>-----Original Message-----
>I think I've found the problem. There are a number of
[quoted text clipped - 75 lines]
>>>>to download the file
>>>>http://crl.verisign.com/Class3SoftwarePublishers.crl.
>>>>This file is a 'certificate revocation list' that I
>can
[quoted text clipped - 73 lines]
>>>>
>>>>This needs to be fixed by Microsoft ASAP.
Harry Jones - 10 Jan 2004 19:21 GMT
Thanks for the sleuthing Jeff. I'm glad I've found out
the reason for the problem I've been having, but am
perturbed for a few reasons:
a) how and when will the problem be resolved?
b) I installed ZoneAlarm and sure enough both Word and
Excel were trying to get out to the Internet. I blocked
them, but somehow they are still managing to get around
ZoneAlarm and packets are coming and going as the app is
loading. Not sure how they are evading ZoneAlarm.
c) I can't believe all the certificates in IE. Who are
these people? Should I be worried about SecureNet or
Thawte?
Perhaps I should go back to Netscape. Maybe that would
help.
>-----Original Message-----
>I think I've found the problem. There are a number of
[quoted text clipped - 75 lines]
>>>>to download the file
>>>>http://crl.verisign.com/Class3SoftwarePublishers.crl.
>>>>This file is a 'certificate revocation list' that I
>can
[quoted text clipped - 81 lines]
>>
>.
Peter - 12 Jan 2004 03:15 GMT
Thanks for the inputs Jeff. I'll keep looking to see if
I can find anything else showing a correction to the
problem. I also found some information on the Symantec
web site that might be of interest to you at the link
below.
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/
2004010810205113
>-----Original Message-----
>I think I've found the problem. There are a number of
[quoted text clipped - 75 lines]
>>>>to download the file
>>>>http://crl.verisign.com/Class3SoftwarePublishers.crl.
>>>>This file is a 'certificate revocation list' that I
>can
[quoted text clipped - 81 lines]
>>
>.
Mike Lenz - 27 Jan 2004 22:18 GMT
In regards to Jeff's comment:
>Some core Windows component is trying to access
>crl.verisign.com (the first thing you'll see is a DNS
>lookup to resolve the IP for this domain). It then
tries
>to download the file
>http://crl.verisign.com/Class3SoftwarePublishers.crl.
>To compound the problem,
>apparently now even if the file is successfully
>downloaded, the control seems to keep downloading the
>file every time it initializes (actually, according to
>the network trace, it downloads it twice starting MS
Word).
I'm interested in more details here since our own testing
shows that once the file (Class3SoftwarePublishers.crl) is
downloaded and stored in the IE cache, it is not
subsequently fetched from the network.
Do you still see the same behavior if you sniff the
network traffic today? Do you know that NAV was the
source of the crl file request? Have you installed a
later NAV update that changed the behavior?
Please email me or post any further details of your system
environment and answers to the above if you have seen the
behavior Jeff describes.
Thanks,
Mike Lenz
VeriSign