I too have been seeing this error but no where near the level you are.  I have seen it on less than 10% of our clients.  Oddly around the same time I began to see a 4319 error about duplicate names on the network.  I have not found any duplicate names nor have I solved either error.

Ok I found some more info.  In the task manager the page file is huge.  When I add the VM Size column view under the process tab, Rtvscan.exe is using 812 MB for virtual memory.  Also the Rtvscan.exe process is always using CPU of around 4% or greater.  I attemted to rename the computer to elminate the 4319 error and I receive an error stating:

The following error occurred attempting to rename the computer to "[computername]":

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.  Disconnect all previous connections to the server or shared resource and try again..

So I am unable to rename the computer either.  The connections lead me to a Microsoft KB884020 which deals with TCP IP connections.

Are you able to rename a computer?  Does your Rtvscan.exe uses a lot of virtual memory?  Please let me know.

Glen

Disabled my Firewall Policies and this error went away. Perhaps there is something wrong with EndPoints Teefer2 network driver.

Thanks for the tip Cary.  I have noticed that any computer that doesn't have the firewall installed such as servers and selected workstations are not receiving this error.  Also I have found that it has something to do with NetBT over TCP/IP and SEP 11.  We never had this problem until SEP 11 was installed and NetBT over TCP/IP has always been running.  Upon disabling NetBT over TCP/IP from DHCP the error has been eliminated on any DHCP configured computers.  Any static IP computer that has the firewall installed (a few workstations) are still recording the 6004 error.  I will manually turn off NetBT over TCP/IP on those and watch the next few days for the 6004 error.

OK, I have confirmed it.  NetBIOS over TCP/IP (NetBT over TCP/IP) and SEP11 do not get along.  I enabled NetBT on a computer with the SEP11 firewall active and bingo, 6004 errors started appearing in the event viewer.  I am really disappointed with this product from Symantec.  It is very buggy even after several maintenance releases.

Almost all of my XP SP3 machines are experiencing this 6004 issue as well.

The same thing is happening to me as Clint said in this thread:

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=243&view=by_date_ascending&page=1

>>

Same problem, MR3 clients.  Any other solution other than disabling the firewall?

Actually, I've withdrawn the firewall policy and I still get 6004's, so "disabling" the firewall isn't working.  I put that in quotes because from what I've read, withdrawing the policy simply opens up all the ports and doesn't actually stop it from running on the client.

I've not found out how to stop it from running on the client once it's been installed.

You may have to actually uninstall the firewall using the Change option in Add/Remove programs, or you might get away with unchecking it at the Network Connection Properties.

Right click on Local Area Connection, go to properties, you'll see the Client for Microsoft Networks, QoS Packet Scheduler...etc...the Teefer2 can be unchecked, click OK, and it should be truly disabled at that point.