Bug 1016620

Summary: Samba shared point cannot be accessed from a Windows XP machine
Product: [Fedora] Fedora Reporter: Milan Crha <mcrha>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: abokovoy, asn, gdeschner, rmainz, sbose, ssorce, steved
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: 2015-02-17 17:33:58 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
tpcdump linux access log
none
tcpdump accessing with Windows XP none

Description Milan Crha 2013-10-08 12:27:05 UTC
I'm lazy, thus I used a system-config-samba to setup one share point, to which I did "Give access to everyone". I can access the share point from a linux machine (the same and neighbour's as well), but my Windows XP machine, which I run in gnome-boxes, cannot open the computer in the group, it asks me for a password. I would expect the "Given access to everyone" will not require a password at all. Both the linux and the windows machine are in the same workgroup, named "SKUPINA".

Comment 1 Milan Crha 2013-10-08 12:27:46 UTC
Oops, I forgot to add samba packages:

samba-4.0.6-3.fc19.x86_64
samba-client-4.0.6-3.fc19.x86_64
samba-common-4.0.6-3.fc19.x86_64
samba-devel-4.0.6-3.fc19.x86_64
samba-libs-4.0.6-3.fc19.x86_64
samba-pidl-4.0.6-3.fc19.x86_64
samba-winbind-4.0.6-3.fc19.x86_64
samba-winbind-clients-4.0.6-3.fc19.x86_64
samba-winbind-krb5-locator-4.0.6-3.fc19.x86_64
system-config-samba-1.2.100-1.fc19.noarch

Comment 2 Milan Crha 2013-10-08 12:30:14 UTC
Created attachment 809246 [details]
tpcdump linux access log

  $ tcpdump -p -s 0 -w FILENAME -i 8 port 445 or port 139

This is when accessing the share point from a (local - the same as the "server") linux machine, which succeeded.

Comment 3 Milan Crha 2013-10-08 12:34:00 UTC
Created attachment 809248 [details]
tcpdump accessing with Windows XP

   $ tcpdump -p -s 0 -w FILENAME -i 8 port 445 or port 139

The tcpdump log when accessing the same share point from a Windows XP instance running in the gnome-boxes. The machine sees the computer, but cannot give me list of share points. Even when I enter direct URI (//zyxpad/ms), then I'm asked to enter a password, which is odd.

Comment 4 Fedora End Of Life 2015-01-09 20:09:39 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 5 Fedora End Of Life 2015-02-17 17:33:58 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.