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".
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
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.
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.
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.
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.