For best results: this site requires
that cookies be enabled for proper operation - see Legal Page for more info
Select Any of These
Norton and Symantec Bugs
LAST UPDATED:
Wednesday, 11 March 2009 14:38:29 -0600
Changes to this page are IN PROGRESS
NAV 2001 VERSUS WINDOWS ME
The viral detection process in Norton AntiVirus 2001
can be bypassed if the infected file is placed in the C:\_Restore
folder in Windows ME. During a Full System Scan, Norton AntiVirus will
fail to recognize the presence of viruses and Trojans in the \_Restore
folder. If the \_Restore folder is manually scanned, Norton AntiVirus
will alert you of the virus's presence, but can't take any further
action (that is, Delete, Repair, Quarantine).This could lead to the
malicious placement of viruses and Trojans that Antivirus can't
sanitize. There are currently no fixes or workarounds for this bug.
Users are urged to contact Symantec for further information.
Users of Symantec's Norton AntiVirus have reported
numerous problems with versions 4.0 and later, the first of which are
unexplained system hangs. In such cases, pressing Ctrl-Alt-Delete
merely causes an error in msgsrv32.exe. Second, Scandisk creates
innumerable temp subdirectories which you can't easily remove. Other
problems have been reported when using NAV in conjunction with the
Netscape Messenger mail client. Messenger may take a long time to
start or may not start at all.
Symantec has confirmed that the June 16 and 19 virus definition
updates are responsible for these problems. Users should update their
virus definitions. Use the LiveUpdate feature included with NAV or
download the update manually from
Performing a TCP SYN scan on a host running Symantec
pcAnywhere will cause the program to crash. You must restart the
application to regain normal functionality. This bug affects all
versions of pcAnywhere after 8.0.1 for all versions of Windows. As
yet, there are no known fixes or workarounds for this bug. Although
not all forms of support are available for pcAnywhere 8.0.x, users can
still review articles in the Knowledgebase or contact Symantec for
more information at
Norton Antivirus for Microsoft Exchange contains a bug
that can cause the program to crash. The unzip engine improperly
handles zip files attached to e-mails. If NAV tries to scan a zip
archive containing files with long file names, it will crash. It will
not scan any further e-mails until the service restarts. There are
currently no fixes for this bug. Concerned users are urged to contact
Norton and/or Microsoft Support for more information.
Symantec's Norton AntiVirus for MS Exchange versions
1.5 and 2.0 are susceptible to (as yet undetermined) circumstances,
which could allow viruses to slip by undetected. When you call upon
the NavExchange service to scan an e-mail message for viruses, it can
enter a state in which it will not respond to system calls. When NAV
is in the "fail-open" state, it transmits virus-laden messages right
through to the intended recipients while leaving the system completely
unprotected. The Event Log records the failure, but the virus remains
undetected.
Once NAV has entered the fail-open state, it will remain so until
restarted. Symantec is aware of this problem and claims that version
2.1 of the program fixes it. Users should use the LiveUpdate feature
to upgrade or contact Symantec at
When attempting to extract CAB files in an
installation or Microsoft update, Symantec Norton AntiVirus 2000
Auto-Protect may detect the virus WM.NiceDay. Scanning the CAB files
manually or scanning the extracted contents finds no viruses. To solve
this problem, run LiveUpdate and download the latest program files for
NAV.
NAV 2000 VERSUS MICROSOFT OUTLOOK EXPRESS
If you use Norton Antivirus 2000 and Microsoft Outlook
Express, you may get the following error message: "XIMS: Outlook
Express POP3, Error 0x800ccc0e, Socket Error 10061". However, Symantec
(maker of Norton software products) assures us this stems from a
simple misconfiguration in the ports on the Microsoft Exchange Server.
If you use these two programs on the same system and are experiencing
the error, search the Knowledge Base for instructions on how to
reconfigure MS Exchange Server ports: