Thomas Bork
2011-Sep-10 01:22 UTC
[Samba] Samba 3.5.11 shares and downloads with IE9 on Windows 7
Hi @all, Internet Explorer 9 on Windows 7 cannot save files on shares from Samba 3.5.11, but Firefox can do this. With IE9 there is only a 0-Byte-file on the share. -- der tom
Thomas Bork
2011-Sep-10 15:13 UTC
[Samba] Samba 3.5.11 shares and downloads with IE9 on Windows 7
Am 10.09.2011 03:22, schrieb ich:> Internet Explorer 9 on Windows 7 cannot save files on shares from Samba > 3.5.11, but Firefox can do this. > With IE9 there is only a 0-Byte-file on the share.Maybe this is a problem with delete on close on the temporary file xxx.partial, which will be created from IE9? The new file without '.partial' cannot be created and the xxx.partial-file is only 0 Byte. I have a log with debug level 10, if anybody is interested in. The downloaded file doesn't matter - tried it for example with http://samba.org/samba/patches/patches-3.0.37/0001-s3-schannel-client-Push-the-domain-and-netbios-name-.patch The share has 0777 nobody.nogroup, the share definition is [downloads] comment = public directory on eis2161 path = /downloads force create mode = 0777 force directory mode= 0777 browseable = yes writeable = yes -- der tom
Linda Walsh
2011-Sep-11 02:44 UTC
[Samba] Samba 3.5.11 shares and downloads with IE9 on Windows 7
Thomas Bork wrote:> On 11.09.2011 01:41, Linda W wrote: > >> This sounds like https://bugzilla.samba.org/show_bug.cgi?id=8412. >> > > I don't think, it's the same problem. I already tried without oplocks > and smb2 isn't activated here. > Anyway - I could test a patch for 3.5.11. >---- Don't know if there is one -- and there was no SMB2 in 3.5.11... But I misread this one... It doesn't say it affects 3.5 or before... Dang...now which one was it!...remember reading one recently that hit 3.6 ... that I thought had to do with file access problems. .. Just your symptom sounded very similar.. I would see a file with the real name created in the target dir, then see a tmp file created and grow to the size of the file, then would get a message that the file couldn't be saved due to an access problem. In the save dir, I'd find the initial file it created @ 0 bytes. The 'tmp' file I'd find in my server's "recycle" dir for that dir -- and it would be the full file. (I have the vfs recycle2 option turned on for many of my shares... so the tmp files ended up in there; if you don't have that option turned on, then the files would just get deleted)...