Comment # 5
on bug 11196
from chirrindulari
Dear Jeff. Thank you for your support. I appreciate your help.
There aren't any non ASCII characters on the path or filename. The file is at
the top level of the share.
I have compared the samba log files trying to double-clicking on a file called
fishero.pcap from tho different computers.
# On a WinVISTAx32 (where I can open the file from the samba share)
# On a Win7x64 (where I connot open it)
The main difference I see (I am not an expert on SMB protocols) is...
WinVISTA...
gsa opened file fishero.pcap read=Yes write=No (numopen=3)
linux_set_kernel_oplock: got kernel oplock on file fishero.pcap, dev = fd0e,
inode = 45, file_id = 11
Win 7......
gsa opened file fishero.pcap read=No write=No (numopen=3)
gsa closed file fishero.pcap (numopen=2) NT_STATUS_OK
As you can see Win7 tries to open as read=NO and a bit later, it closes the
file.
I don't know why the OS or WIRESHARK does not open the file as read=Yes, like
in WinVISTA. Maybe this is not the true reason (as with dumpcap.exe)
I have added the samba logs of every test (I have deleted lines before the
first occurrence of fishero.pcap)
Best regards.
You are receiving this mail because:
- You are watching all bug changes.
