Bug 1411039

Summary: XP can't access SAMBA shares from F25
Product: [Fedora] Fedora Reporter: Joshua Rosen <bjrosen>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: abokovoy, anoopcs, asn, bjrosen, gdeschner, jarrpa, lists, lmohanty, madam, sbose, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:11:37 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 Flags
smb.conf none

Description Joshua Rosen 2017-01-07 19:23:27 UTC
Description of problem: XP can't access SAMBA shares from Fedora 25. Win10 has no problem. The Fedora systems was just upgraded from F22 to F25. SAMBA worked fine on F22. 


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Export SAMBA shares from F25
2. Try to access them from an XP VM
3.

Actual results: Won't allow the user to log in


Expected results: should allow the user to log in


Additional info:

Comment 1 Andreas Schneider 2017-02-10 16:21:55 UTC
Can you please provide more information? See

https://www.samba.org/~asn/reporting_samba_bugs.txt

Comment 2 Joshua Rosen 2017-02-10 16:36:05 UTC
Created attachment 1249090 [details]
smb.conf

This is the SMB configuration file that I'm using. Win10 can mount these shares fine, XP can't. Used the same configuration file for F22 and XP didn't have any problem accessing the SMB shares. I'm assuming that the authorization protocol has changed and that the newer version isn't supported by XP, is there away to drop the authorization mechanism back to the older protocol.

Comment 3 Fedora End Of Life 2017-11-16 19:52:12 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:11:37 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.