similar to: alternate data streams problem

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

Hello, I just had something strange happen and could not find explanations in the documentation, FAQs or mailing list. The server is a Debian installation running Samba 2.2.3 (kernel 2.4.18 if interested). It has been recently upgraded from 2.0.x (I think x=6). My smb.conf is at the bottom; the directory used is on the [public] share. The client runs Win2k (probably SP2). I copied some files in

I am trying to copy some digital images to a directory on my Redhat 7.3 Samba 2.2.3a-6 server and am getting extra files in the directory. I have included my SMB.Conf file contents below in case that is relevant. The files being copied reside on a Windows 2000 workstation and were created by Jasc Image robot. These files would have been accessed by both a Windows 2000 machine as well as a Windows

Recently I setup samba 2.23 on a Red Hat 7.3 machine to be the Primary Domain controller, my win2k machine logs in just fine with username and password I setup sees the shares it should, however the problem I have is if I try to copy something to one of the shares it copies hte file 3 times, one is the origianl one is blank, one is coded and is the same file. And I can't seem to figure this

Hello, I'm relatively new to Samba, but have it set up on my RedHat 7.3 system, and it's running great. Except for one thing, and I'm not sure if this is a Samba problem or a problem with my machines. What the problems appears is that when I'm copying or moving images (jpegs, bmps are the only two I've tried so far) from both my laptop and my desktop (both Win2k mahcines),

Hello, Last evening I did this recursive rsync: rsync -avz data /mnt/RICEX0/DWT/Daredevil/1071865403/ ..where data is a regular ext3 soft-RAID1 volume ...where /mnt/RICEX0/ is an NTFS hard-RAID10 volume mounted across VPN using SMB. And received errors that look to be generated by smb while trying to recreate(?) the illegal characters. Dec 20 04:30:55 daredevil kernel: smb_create:

Hi all, I was just looking into what was causing the lag when I open my samba (3.0.27a) shares from windows (XP, SP2). strace showed that directories were being opened and closed a lot, in sequence. Playing with Process Monitor suggests windows is trying to create alternate data streams on for the directory entires: it does a CreateFile with :{4c8cc155-6c1e-11d1-8e41-00c04fb9386d} appended to

I was looking into what was causing the lag when I open my samba (3.0.27a) shares from windows (XP, SP2). I see a lot of consecutive directory opening. Process Monitor seems to suggests that windows is being stupid about alternate data streams: it tries to create directoryname:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}, fails, and tries another sixty-ish times before failing and doing the same with

Dear all, My question is described as follows. Server: Linux Samba-3.3.1 Client: Windows XP with SP3 Step1: connect to the samba server. Step2: select a directory name ?test?. (The directory is created before testing.) The client will send a lot of QUERY_FILE_INFO requests. According to data captured by Wireshark, I find the following phenomenon: The client repeats exactly the same

Hi folks I hope someone might be able to shed some light on a problem that I am experiencing with a Samba server. I installed this server about 2 and a half years ago on a client's site. The server has been running fine. We are now experiencing two problems which according to the client occured overnight. The first problem started about a week and a half ago when they found that when trying

When sending a PUT request, the http header may be sent in the first packet when calling con.endheaders(). When we send the first chunk, the kernel may delay the send because the header packet was not acked yet. We have seen PUT requests delayed by 40 milliseconds on the server side during virt-v2v upload to ovirt. Here is example log from current RHEL virt-v2v version, uploading to RHV 4.2.3: