[Samba] Lots of NT_STATUS_OBJECT_NAME_COLLISION errors, harmless?

Paul Elliott paul.elliott at ynic.york.ac.uk
Thu May 24 10:16:43 MDT 2012


Hello all,

I'm attempting to setup a small Windows network using Samba as the PDC 
(and the only server involved). Clients are running Windows 7 (x86_64) 
and the server is running Debian Squeeze with samba 3.5.6. For now I'm 
just using tdmsam as the passwd backend.

The problem I have is that I see lots of errors involving 
NT_STATUS_OBJECT_NAME_COLLISION, here's an example at login time for 
user pre500 with roaming profiles enabled:

[2012/05/24 15:36:15.038884,  3] smbd/dosmode.c:166(unix_mode)
   unix_mode(pre500.V2) returning 0700
[2012/05/24 15:36:15.038902,  2] smbd/open.c:2505(open_directory)
   open_directory: unable to create pre500.V2. Error was 
NT_STATUS_OBJECT_NAME_COLLISION
[2012/05/24 15:36:15.038925,  3] smbd/error.c:80(error_packet_set)
   error packet at smbd/error.c(153) cmd=162 (SMBntcreateX) 
NT_STATUS_OBJECT_NAME_COLLISION

And similar errors at logout for every directory within the profile:

[2012/05/24 15:36:15.975852,  3] smbd/dosmode.c:166(unix_mode)
   unix_mode(pre500.V2/AppData/Roaming/Microsoft/Windows/Start Menu) 
returning 0700
[2012/05/24 15:36:15.975870,  2] smbd/open.c:2505(open_directory)
   open_directory: unable to create 
pre500.V2/AppData/Roaming/Microsoft/Windows/Start Menu. Error was 
NT_STATUS_OBJECT_NAME_COLLISION
[2012/05/24 15:36:15.975888,  3] smbd/error.c:80(error_packet_set)
   error packet at smbd/error.c(153) cmd=162 (SMBntcreateX) 
NT_STATUS_OBJECT_NAME_COLLISION

The unix user can access, create and delete files/directories within the 
profiles directory without issue directly on the samba server itself and 
the directories quoted in the error messages already exist with the 
correct owner.

Here's my global and profile share config in case it shows any obvious 
errors:

[global]
     security = user
     workgroup = YNIC
     netbios name = SAMBA
     os level = 99
     preferred master = yes
     domain master = yes
     domain logons = Yes
     wins support = yes
     name resolve order = wins hosts bcast
     interfaces = 144.32.169.120
     bind interfaces only = true
     encrypt passwords = yes
     username map = /etc/samba/smbusers
     # management scripts pruned
     passdb backend = tdbsam
     logon path = \\%L\profiles\%U
     log level = 4
[profiles]
     path = /srv/samba/profiles
     comment = roaming profiles
     read only = no
     store dos attributes = yes
     create mask = 0600
     directory mask = 0700
     browseable = no
     guest ok = no
     printable = no
     profile acls = yes
     csc policy = disable

So far, even with these errors, I haven't observed any failures from the 
client although my testing so far has been severely limited. Would 
anyone be able to confirm if these errors are something I should be 
concerned about or if they are purely cosmetic and can be safely ignored?

Much appreciated, Paul.

-- 
Paul Elliott, UNIX Systems Administrator
York Neuroimaging Centre, University of York


More information about the samba mailing list