[Samba] uploading files to Samba server using Windows XP

[Jeremy Allison]

On Mon, Jun 17, 2002 at 11:45:35AM -0700, Jason Fayre wrote:
> When I try to copy a directory of files from Windows XP to my samba 
> server, I get additional files on the samba server that look like Windows 
> registry class IDs.  Here is a sample:
> 
> 
> 
> -rw-r--r--    1 jfayre   jfayre          0 Mar 17 06:31 IMG_0470.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre     461574 Mar 24 07:15 IMG_0478.JPG
> -rw-r--r--    1 jfayre   jfayre          0 Mar 24 07:15 IMG_0478.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre       7256 Mar 24 07:15 IMG_0478.JPG:Q30lsldxJoudresxAaaqpcawXc:$DATA
> -rw-r--r--    1 jfayre   jfayre     473360 Mar 24 08:02 IMG_0479.JPG
> -rw-r--r--    1 jfayre   jfayre          0 Mar 24 08:02 IMG_0479.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre       7668 Mar 24 08:02 IMG_0479.JPG:Q30lsldxJoudresxAaaqpcawXc:$DATA
> -rw-r--r--    1 jfayre   jfayre     349776 Mar 31 06:27 IMG_0480.JPG
> -rw-r--r--    1 jfayre   jfayre          0 Mar 31 06:27 IMG_0480.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre       4808 Mar 31 06:27 IMG_0480.JPG:Q30lsldxJoudresxAaaqpcawXc:$DATA
> -rw-r--r--    1 jfayre   jfayre     308626 Mar 31 06:27 IMG_0481.JPG
> -rw-r--r--    1 jfayre   jfayre          0 Mar 31 06:27 IMG_0481.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre       3748 Mar 31 06:27 IMG_0481.JPG:Q30lsldxJoudresxAaaqpcawXc:$DATA
> -rw-r--r--    1 jfayre   jfayre     427649 Mar 31 06:27 IMG_0482.JPG
> -rw-r--r--    1 jfayre   jfayre          0 Mar 31 06:27 IMG_0482.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
> -rw-r--r--    1 jfayre   jfayre       4956 Mar 31 06:27 IMG_0482.JPG:Q30lsldxJoudresxAaaqpcawXc:$DATA
> 
> These extra files also show up in Windows explorer.  I am using RedHat 
> 7.3.  Samba version is 2.2.3a.
> Any ideas what this might be?

Known bug we've fixed for 2.2.5, sorry.

Jeremy.