Re: Symantec Common Client update prevents OE retrieving mail

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Larry Suddarth" <suddarth@xxxxxxxxxx> wrote in message news:%23ZDXMUHPFHA.4064@xxxxxxxxxxxxxxxxxxxxxxx
HOT DOG!!!!!!!!!!!!!!!!!!!!!!!!! It fixed the problem of having to turn off email scanning in Norton Antivirus. That little file, ISRIRstr.exe cleaned the Application Rules folder. I turned email scanning back on and tried sending and receiving in OE. I little box popped up on the lower right stating that rules for OE were being automatically created. Worked great!!!!!!!!!

"Larry Suddarth" <suddarth@xxxxxxxxxx> wrote in message news:eOetHOHPFHA.3076@xxxxxxxxxxxxxxxxxxxxxxx
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.


While Symantec might provide a quick tool for wiping the application rules, that will probably wipe them all. Last version I used for NIS was 2003 and it has a configuration panel to let you add, delete, or modify application rules. That's why I mentioned deleting just those app rules applicable to your situation. You could delete them all there, too. I assumed that NIS 2005 also provides an app rule config panel.

Glad you got it working. I ran into that before (and not just within Norton's firewall) where I had to delete the old app rule based on an old version of a program to get the firewall to permit connections by a new version of the program.

--
____________________________________________________________
** Post your replies to the newsgroup - Share with others **
For e-mail Reply: remove "NIXTHIS", add "#VS811" to Subject.
____________________________________________________________

.

Relevant Pages

  • Re: FYI: Security Problems Plague XP SP2 via Symantec/McAfee
    ... Because eTrust & your Firewall are complimentary programs, ... the same company what happened isn't a violation of Firewall rules. ... >> Norton System Security, Norton Utilities, etc. are another thing ... >> Symantec has definitely lost their reputation in the past 5 years or so. ...
    (microsoft.public.windowsxp.general)
  • Re: Windows Security Center Shows non exisitng Symantec firewall
    ... After several hours of chatroom discussion with Symantec suport people, ... I still see the same info about Norton Internet Security ... being ON in the firewall section if I turn off Windows firewall. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Symantec Common Client update prevents OE retrieving mail
    ... I turned email scanning back on and tried ... > them after disabling Norton Personal Firewall. ... >>> If I accept the Symantec Common Client update from Live update in NIS ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Virus Protection Problem?
    ... Symantec can still be an acceptable choice. ... locking step with Norton, investigate other vendors. ... is that I still cannot use and recommend McAfee. ... That's where Norton Firewall is a better choice. ...
    (microsoft.public.windowsxp.general)
  • Re: Outlook Express 6 (sp2 installed) slow to check pop3 accounts
    ... >> I have Norton Internet Security 2005. ... >> I also tried disabling the firewall, also indicated by a red 'X' over ... >> Tured off ALL email scanning, restarted, opened OE, same response. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)