Workaround for Norton AV debacle

[kurttrail]

1. First, disconnect from your network, or internet for those with
broadband, otherwise this process will be very slow.
2. Go to your Norton Antivirus, and disable the automatic LiveUpdate.
3. Go to C:\Program Files\Common Files\Symantec Shared.
4. Rename the file called CommonClient.dat to something else like
CommonClient.dat.bad.
5. Rename the file called CommonClient_old.dat to CommonClient.dat.
6. Reconnect your network.
7. Until theres a new fix for this, use LiveUpdate.
8. Put these in your hosts file [C:\Windows\System32\Drivers\etc] with
notepad:
127.0.0.1 sitefinder-idn.verisign.com
127.0.0.1 crl.verisign.com1 crl.verisign.com


--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei!"

 

[Carey Frisch [MVP]]

The above post is the "hard way".... this is the "easy way":

Right-click on your IE desktop icon and select:
Properties > Advanced and scroll down to the
Security heading. Uncheck the box next to
"Check for publisher's certificate revocation"
and click "apply" and reboot.

It appears that all the NAV files are signed with a certificate
that expired 1/7/2004. Every time it tries to use a file, it's going
out to VeriSign to see if it's really expired and if there's a new
certificate available.

Hopefully Symantec will correct this issue soon.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

------------------------------------------------------------------------------------------------


| 1. First, disconnect from your network, or internet for those with
| broadband, otherwise this process will be very slow.
| 2. Go to your Norton Antivirus, and disable the automatic LiveUpdate.
| 3. Go to C:\Program Files\Common Files\Symantec Shared.
| 4. Rename the file called CommonClient.dat to something else like
| CommonClient.dat.bad.
| 5. Rename the file called CommonClient_old.dat to CommonClient.dat.
| 6. Reconnect your network.
| 7. Until theres a new fix for this, use LiveUpdate.
| 8. Put these in your hosts file [C:\Windows\System32\Drivers\etc] with
| notepad:
| 127.0.0.1 sitefinder-idn.verisign.com
| 127.0.0.1 crl.verisign.com1 crl.verisign.com
| --
| Peace!
| Kurt

 

[Mickey Segal]

1. First, disconnect from your network, or internet for those with
broadband, otherwise this process will be very slow.
2. Go to your Norton Antivirus, and disable the automatic LiveUpdate.
3. Go to C:\Program Files\Common Files\Symantec Shared.
4. Rename the file called CommonClient.dat to something else like
CommonClient.dat.bad.
5. Rename the file called CommonClient_old.dat to CommonClient.dat.
6. Reconnect your network.
7. Until theres a new fix for this, use LiveUpdate.
8. Put these in your hosts file [C:\Windows\System32\Drivers\etc] with
notepad:
127.0.0.1 sitefinder-idn.verisign.com
127.0.0.1 crl.verisign.com1 crl.verisign.com

Is there some URL at Symantec that owns up to this problem and suggests
actions? A quick visit to their site revealed no obvious admission of the
problem, though Symantec is not known for being forthcoming about its
screw-ups.

 

[kurttrail]

"By the act of scrolling this post on your computer, and/or printing or
replying to this post, you agree that I am your everlasting Lord & Saviour.
Breach of this term will result in you burning in hell for ever and ever!
Amen!"

The above post is the "hard way".... this is the "easy way":

Right-click on your IE desktop icon and select:
Properties > Advanced and scroll down to the
Security heading. Uncheck the box next to
"Check for publisher's certificate revocation"
and click "apply" and reboot.

It appears that all the NAV files are signed with a certificate
that expired 1/7/2004. Every time it tries to use a file, it's going
out to VeriSign to see if it's really expired and if there's a new
certificate available.

Hopefully Symantec will correct this issue soon.

Agreed. But between their putting this crap on the net, that even a
simplest-minded tester should have caught, and their Product Activation
scheme, I won't be buying anymore of their products. Off to go download AVG
for free.

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei!"

 

[kurttrail]

"By the act of scrolling this post on your computer, and/or printing or
replying to this post, you agree that I am your everlasting Lord & Saviour.
Breach of this term will result in you burning in hell for ever and ever!
Amen!"

1. First, disconnect from your network, or internet for those with
broadband, otherwise this process will be very slow.
2. Go to your Norton Antivirus, and disable the automatic LiveUpdate.
3. Go to C:\Program Files\Common Files\Symantec Shared.
4. Rename the file called CommonClient.dat to something else like
CommonClient.dat.bad.
5. Rename the file called CommonClient_old.dat to CommonClient.dat.
6. Reconnect your network.
7. Until theres a new fix for this, use LiveUpdate.
8. Put these in your hosts file [C:\Windows\System32\Drivers\etc]
with notepad:
127.0.0.1 sitefinder-idn.verisign.com
127.0.0.1 crl.verisign.com1 crl.verisign.com

Is there some URL at Symantec that owns up to this problem and
suggests actions? A quick visit to their site revealed no obvious
admission of the problem, though Symantec is not known for being
forthcoming about its screw-ups.

Would you admit it, when you charge people nearly the price of the software
for phone support?

--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei!"

 

[Richard Urban]

What is the actual problem we are discussing here? I have 3 computers with
Norton A.V. on them and I have not, as of yet, seen anything strange.

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard

 

[Malke]

"By the act of scrolling this post on your computer, and/or printing
or replying to this post, you agree that I am your everlasting Lord &
Saviour. Breach of this term will result in you burning in hell for
ever and ever! Amen!"


Agreed. But between their putting this crap on the net, that even a
simplest-minded tester should have caught, and their Product
Activation
scheme, I won't be buying anymore of their products. Off to go
download AVG for free.

Richard - the problem is that all of a sudden right-clicking brings
nothing but the "working and waiting" hourglass on clean XP systems.
Apparently this is connected to a problem with the latest NAV updates.
I started seeing posts about it yesterday and actually experienced it
on two clients' machines today.

Cheers,

Malke

 

[Greg]

Seems that any right click menu "contextmenu" that includes "Scan with
Norton" will be slow to react. This includes most things you can right
click on.