samba - Jan 2009 - Chronic Problems with "File system does not support long filenames"

When trying to create a file or folder on a samba share (3.0.28-0.el4.9)
from a Windows 2003 R2 server, I occasionally receive an error message
stating that the target filesystem does not support long filenames. This

happens even if object name follows 8.3 naming conventions. It 
does not *always* happen. Also, I have another samba 3.0.28-0.el4.9
server 
where this does not happen at all.

What the heck causes this?

Here's the smb.conf from the "bad" server. It's pretty much
the same as
the "good" server.

[global]
   unix charset = LOCALE
   workgroup = MYWG
   netbios name = APP2
   realm = MYWG.MD
   server string = Linux Server
   security = ADS
   allow trusted domains = No
   username map = /etc/samba/smbusers
   log level = 2
   syslog = 0
   log file = /var/log/samba/%m.log
   max log size = 50
   printcap name = /etc/printcap
   ldap ssl = no
   idmap backend = idmap_rid:MYWG=500-100000000
   idmap uid = 500-100000000
   idmap gid = 500-100000000
   template shell = /bin/false
   template homedir = /alley/%U
   winbind use default domain = no
   winbind nested groups = Yes
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   dns proxy = no
   hosts allow = 192.168.5. 192.168.10. 192.168.15. 172.16. 127. 10.
   load printers = yes
   cups options = raw
   hide dot files = yes
   short preserve case = no
   client schannel = no

--
Eric Robinson



Disclaimer - January 17, 2009 
This email and any files transmitted with it are confidential and intended
solely for Robinson, Eric,samba@lists.samba.org. If you are not the named
addressee you should not disseminate, distribute, copy or alter this email. Any
views or opinions presented in this email are solely those of the author and
might not represent those of . Warning: Although  has taken reasonable
precautions to ensure no viruses are present in this email, the company cannot
accept responsibility for any loss or damage arising from the use of this email
or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/