Bug 3332 - Conflict between Samba 3.0 and Symantec Antivirus Corporate Ed. 10.0
Summary: Conflict between Samba 3.0 and Symantec Antivirus Corporate Ed. 10.0
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.20b
Hardware: x86 Windows 2000
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2005-12-15 06:44 UTC by Michele Ficara
Modified: 2018-03-17 23:29 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Michele Ficara 2005-12-15 06:44:35 UTC
After some googling I came to this page:
I have 4 Ms Windows 2000 SP4 machines joining an NT Domain created by Samba 3.0.20b
I set up roaming profiles and everything works perfectly, BUT when I install Symantec Antivirus CE 10.0, doesn't matter if client or server mode, on these clients, strange behavior occurs:
a)existing common profiles aren't loaded on session logon
b)new profiles aren't created on the server on user logoff (even if the profile Dir is created immediately after user logon)
c)after logoff it takes several minutes to turn back to logon screen
d)in the local profile Dir on Windows machine every time a user logon a new small file (8 KB) is created and 8 KB is the size of NtUser.POL file I put in netlogon share on the SMB server.
If I remove the Symantec product from the client machine everything turns OK again.
I do appreciate any suggestion. Greetings
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-12-15 08:24:36 UTC
Can you test this against a Windows server?  If there 
is no problem against Windows, then it is definitely
our bug.  Bug past experience makes me suspicious of
the virus software itself and not the file server.
Comment 2 Michele Ficara 2005-12-19 01:58:03 UTC
Some additional informations:
1) Symantec AV CE 10.0 works perfectly in a Ms Windows Server 200x environment
2) Only Symantec AV CE 10.0 cause this issue; installing version 9.0 caused no conflict with Samba:
a) correct roaming profiles operation was restored
b) temporary files "Prfxx.tmp" on local Windows Profile cache (which I could verify to be effectively the policies file NTConfig.POL) weren't generated anymore and Domain policies restarted to work
c) logoff procedure only takes a couple of seconds
Comment 3 Simo Sorce 2018-03-17 23:29:48 UTC
Samba 3.0 has been EOLed ages ago.