Re: Symantec Common Client update prevents OE retrieving mail
- From: "Larry Suddarth" <suddarth@xxxxxxxxxx>
- Date: Fri, 8 Apr 2005 14:45:24 -0500
Just did a live update and IE stopped accessing web pages . I could access
them after disabling Norton Personal Firewall. I did not check to see if OE
was still working. But after some research, I followed the instructions for
"To restore the default General and Trojan Horse firewall rules." I have
version 2005 and downloaded ISRIRstr.exe This is on the Symantec web page.
Double-clicked the file and it cleaned out the Application Rules folder. Now
as I access programs, New rules are created fresh automatically.
I don't know what version you have, but there are different files to
download for different versions. Also, different directories for different
versions. Wish I had checked OE to see if it has stopped working. I am going
to check to see if it fixed the necessity to disable email scanning also.
Good luck.
<Vanguard> wrote in message news:gvidnS3KYtSrUsvfRVn-3w@xxxxxxxxxxxxxx
> "kgjunk_1" <kgjunk_1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C05961A7-6A0E-4B6F-AE42-6683AA02880F@xxxxxxxxxxxxxxxx
>> If I accept the Symantec Common Client update from Live update in NIS
>> 2004, I
>> cannot download any mail. OExpress connects to the server but the status
>> just
>> shows as "executing" and eventually times out.
>>
>> Restoring the PC to prior to the update and all works fine again.
>> I'm running XP home, SP2.
>>
>> Any ideas ?
>
>
> Go into the applications rules and delete those for Symantec or Norton.
> Then when you are prompted to allow those applications to make a
> connections, do so. Sometimes an upgrade results in an old rule refusing
> to work because the hash code recorded is for the old version and not the
> new version. This isn't just with Symantec components trying to make a
> network connection but with any program that gets updated. Normally the
> firewall should see the upgraded component as a whole new component to
> then prompt you if you want to let it connect or not, and if you let it
> then a new hash code gets stored for that component. It doesn't always
> work (because the trigger to prompt you for the "new" upgraded component
> doesn't appear). So delete the application rule for that component and
> recreate it.
>
> --
> ____________________________________________________________
> ** Post your replies to the newsgroup - Share with others **
> For e-mail Reply: remove "NIXTHIS", add "#VS811" to Subject.
> ____________________________________________________________
>
.
- Follow-Ups:
- Re: Symantec Common Client update prevents OE retrieving mail
- From: Larry Suddarth
- Re: Symantec Common Client update prevents OE retrieving mail
- References:
- Symantec Common Client update prevents OE retrieving mail
- From: kgjunk_1
- Re: Symantec Common Client update prevents OE retrieving mail
- From: Vanguard
- Symantec Common Client update prevents OE retrieving mail
- Prev by Date: MAJIK!! I survived!!
- Next by Date: Re: Symantec Common Client update prevents OE retrieving mail
- Previous by thread: Re: Symantec Common Client update prevents OE retrieving mail
- Next by thread: Re: Symantec Common Client update prevents OE retrieving mail
- Index(es):
Relevant Pages
|