Bug 919405
Summary: | Samba4 impossible to read/copy if accessing from Android devices | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Salvatore La Bua <slabua> | ||||||||||||
Component: | samba | Assignee: | Guenther Deschner <gdeschner> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 18 | CC: | abokovoy, asn, gdeschner, jlayton, mike_parlett, sbose, ssorce | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | Unspecified | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-03-25 22:53:28 UTC | Type: | Bug | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Salvatore La Bua
2013-03-08 11:38:02 UTC
Could you please share: 1. smb.conf 2. debug log of level 10 (log level = 10) when performing steps that lead to a problem. Specifically, we want to see what client-server exchange between each other in such case. Thanks for taking the time to report an issue. Every major SMB/CIFS client is correctly working with Samba 4.0. We don't know about any issues in this area. I would say it is a bug in the jCIFS client used by ES File Explorer. However you could try to set: max protocol = LANMAN1 in your smb.conf. (In reply to comment #1) > 1. smb.conf http://pastebin.com/3HmpSRXw > 2. debug log of level 10 (log level = 10) when performing steps that lead to > a problem. > > Specifically, we want to see what client-server exchange between each other > in such case. I'm not sure what exactly I should grep from the logs, or should I report all of them? I got log files for smbd, the phone ip and jcifs0_1_d0. (In reply to comment #2) > I would say it is a bug in the jCIFS client used by ES File Explorer. It was working, though, with a previous version of samba. Meanwhile, I'll check other clients and see if they work fine. > However you could try to set: > > max protocol = LANMAN1 > > in your smb.conf. If I use the line above I can't access to the server in any way, neither from a windows machine. Hi I can confirm this problem. reading a file from Sammaba 4.0.3-2 (FC18 x64) with Android ICS ES File explorer Browse share OK Delete file on share Ok Copy File Share to Same Share FAIL Read file on Share FAIL Copy file to Share OK I have tried this from homes share Addin a Samba share for my home and explitily mapping it No clues found yet.. Sorry Mike (In reply to comment #4) > Hi > > I can confirm this problem. [...] > Mike Thank you Mike. I also tried different android samba clients, such as AndSMB and Solid Explorer, and I get the same unsuccessful result. -- Salvatore We need log files, config file and a network trace. Please read https://www.samba.org/~asn/reporting_samba_bugs.txt Created attachment 708351 [details]
smb.conf
Created attachment 708352 [details]
tcpdump between the two machines
Created attachment 708353 [details]
log.smbd
Created attachment 708354 [details]
log.jcifs
Created attachment 708355 [details]
log.192.168.1.100
(In reply to comment #6) > We need log files, config file and a network trace. > > Please read https://www.samba.org/~asn/reporting_samba_bugs.txt All the requested log files are attached. Cloudshark version of the tcpdump: http://www.cloudshark.org/captures/a9497b4e1d92 A bug for jCIFS should be reported too. samba-4.0.4-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/samba-4.0.4-3.fc18 Package samba-4.0.4-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing samba-4.0.4-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4247/samba-4.0.4-3.fc18 then log in and leave karma (feedback). samba-4.0.4-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Loaded testing version it would all appear to work as expected well done all and thank you mike MikeP: If you have time please report a bug to jCIFS or the Android app using jCIFS. They have a bug in what they send to the server. We just handle the wrong flags they send more gracefully. The details can be found in this thread: https://lists.samba.org/archive/samba-technical/2013-March/090922.html |