NIS corruption

[ChrisX]

I use Norton Internet Security 2002 and I was having problems with it yesterday.

It all started on Thursday with the updates from Symantec. The new downloaded version of LiveUpdate won't work and the NAV timed out on shutdown as it gets so slow to load as well.

The new version of LiveUpdate maybe incompatible with the previous installation or the NIS became corrupted. The firewall may be blocking access and it just hanged.

The only way to fix was to uninstall NIS/NAV and then re-install and re-download everything.

This is the second time I have to re-install everything after uninstall, however in another computer on a different fault.

I suspect the OEM disk I am using isn't any good and this maybe causing the problems.

I got everything back to normal and another thing the OEM disk is too old and this maybe the root of the problem.

I had a good look and noticed WinXP is missing on the disk, it says Win9.x, WinME and Win2k.

I noticed that one computer wasn't affected as a downloaded file of LiveUpdate was used, not from the original disk and the website. Live Reg is also available to download as a file too.

Check out: http://www.symantec.com/techsupp/files/lu/lu.html

Just remember don’t use a too old disk and try to update first by downloading the standalone install files above. This would be useful in a network of computers.

I don’t think Norton is as good as it used to be. Did anyone experience this problem on using with NIS/NAV 2002?

[au7usa]

I had a problem similar to what your describing. I didn't really fix it, but i came up with an acceptable work-around.

I noticed that Live Update was the cause of the whole problem.

Live Update i discovered, had to download a security certificate before it could download it's updates. If it couldn't find the Security Certificate (http://crl.verisign.com/Class3CodeSigning2001.crl), it would hang.

What i did is to ping: http://crl.verisign.com, repeatedly to determine what the IP address was. I noticed that it was responding from two destinctly different IP addresses; one that would respond immediately, and one that would only occasionally respond (but ususally not at all).

My work-around was to use NIS to block the bad IP address in "Personal Firewall / Home Networking", so that if the first attempt is made to the "bad" IP address, it would immediately fail, and NIS would try the "good" IP address.

I decided that what was happening was that when NIS sent out a request to the "bad" IP address it would get NO-REPLY!, but if it was blocked, it got an instant reply. (This is why they tell us to Stealth our ports isn't it)

[ChrisX]

I noticed that Live Update was the cause of the whole problem.

Yes, the new updated LiveUpdate was the cause of all the problems and now ok. You must be luckly to be able correct the problem manually.

Check out my other post on this issue in reply: https://www.videohelp.com/forum/viewtopic.php?t=195636&highlight=verisign

This is to confirm on what you said on Verisign: http://www.zdnet.com.au/news/security/0,2000061744,20282575,00.htm

[au7usa]

Does this mean i'm famous now?

[ChrisX]

Does this mean i'm famous now?

Yes, you must be now. au for Australia, 7 for Channel 7 and USA for the States.

[au7usa]

au7usa is from the serial number of my first modem:
Multitech 28.8 external