Right click goes to verisign befor action

I would greatly appreciate help on this. When I right click on a file and bring up the menu my computer tries to go to verisign (I blocked it in the firewall). Each different type of file does it. It doesn't do it a second time unless it has been 10 or 15 minutes between choosing the same file type. For instance: Right click an exe file an it calls verisign, right click another exe file it doesn't call out but right click a jpg and it calls out wait 15 minutes and right click an exe again and it calls out. It seems to have started after installing a new HD (Maxtor). After right clicking it takes about 20 seconds befor getting control back which usually unhilites the option I have chosen then I have to choose it again and it works. Extreeeeeemly irratating. I can't even think of where to begin. Thanks in advance. Running XP SP1 up to date.

jaccod

To those technicaly inclined: I just captured this from my firewall.....

C:\WINDOWS\explorer.exe
File Version : 6.00.2800.1221 (xpsp2.030511-1403)
File Description : Windows Explorer
File Path : C:\WINDOWS\explorer.exe
Process ID : 0x278 (Heximal) 632 (Decimal)

Connection origin : local initiated
Protocol : TCP
Local Address : 192.168.2.101
Local Port : 1089
Remote Name : crl.verisign.com
Remote Address : 12.158.80.10
Remote Port : 80 (HTTP - World Wide Web)

Ethernet packet details:
Ethernet II (Packet Length: 76)
Destination: 00-03-2f-06-2c-c7
Source: 00-0b-db-27-17-b2
Type: IP (0x0800)
Internet Protocol
Version: 4
Header Length: 20 bytes
Flags:
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset:0
Time to live: 128
Protocol: 0x6 (TCP - Transmission Control Protocol)
Header checksum: 0x95d8 (Correct)
Source: 192.168.2.101
Destination: 12.158.80.10
Transmission Control Protocol (TCP)
Source port: 1089
Destination port: 80
Sequence number: 956432387
Acknowledgment number: 0
Header length: 28
Flags:
0... .... = Congestion Window Reduce (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...0 .... = Acknowledgment: Not set
.... 0... = Push: Not set
.... .0.. = Reset: Not set
.... ..1. = Syn: Set
.... ...0 = Fin: Not set
Checksum: 0xd3e5 (Correct)
Data (0 Bytes)

Binary dump of the packet:
0000: 00 03 2F 06 2C C7 00 0B : DB 27 17 B2 08 00 45 00 | ../.,....'....E.
0010: 00 30 02 7D 40 00 80 06 : D8 95 C0 A8 02 65 0C 9E | .0.}@........e..
0020: 50 0A 04 41 00 50 39 02 : 00 03 00 00 00 00 70 02 | P..A.P9.......p.
0030: 40 00 E5 D3 00 00 02 04 : 05 B4 01 01 04 02 00 B6 | @...............
0040: 78 33 62 75 74 74 6F 6E : 73 2F 77 32 | x3buttons/w2

crl.verisign.com is the repository for certificate revocation lists. Whatever file or software you are using has an expired certificate, and it is trying to contact verisign for an update. I think you're ok to go ahead and allow it. Once it gets the update, it should stop trying to connect.

hudsonsmith thanks for the reply. I allowed explorer to go to verisign then waited about 15 minutes and retried on the same file. It still wanted to go back to verisign. Still hoping for a solution. VERY FRUSTRATING.

Jaccod

There was a similiar problem casued by Norton Antivirus recently. The fix was to go into Internet Explorer-Internet Options-Advanced and uncheck "check for publishers certificate revocation
Might work for you too

Then they produced an update so you did not have to turn off this important security aspect of explorer. Do you have Norton jaccod?

@ techs, that was the ticket. Turned it off and problem disappeared. Thanks alot.

@ Master NooNoo. I have read many of you most excelent posts. Yes I do use Nortons. Is there a fix so as to keep this feature on?

jaccod

My bad, it was versigns problem... it just affected norton badly.

I assume you are uptodate with scan engine and virus definitions and you run live update?

Yes to "I assume you are uptodate with scan engine and virus definitions and you run live update?", and thanks for your input.

jaccod

This explains the prior problem. You could try downloading the problematic crl and installing it locally (this would stop applications from trying to contact verisign). If it is the one listed, it is available here. Otherwise, you will have to check your logs and see if you can determine which crl is causing the problem.

@ hudsonsmith The problem happened on all programs that had access to the internet. I went to Nortons and did an update and it fixed the problem. I can now check mark the cirtificate revocation flag with no problems. Before if I either let it access the verisign site or not it would take about 20 seconds to receive a response from a right click. Co-incidently, Nortons was set to update on April 13 2004 probably fixing the problem and making me scratch my head all the more. Thanks to all for the help especially techs and NooNoo.

jaccod
PS This just started about 2 weeks ago.