Hello, a report a bug from a Mageia users from MLO (Original in French) [quote]PC with samba : If the first PC (PC1) is open before the second PC (PC2), the second PC (PC2 cannot access samba shared file from the first PC (PC1) with Dolphin when opening with "Network->Samba Shares" Dolphin give the error : "No work group found in the local network. It can be a working firewall who block it." (Original message in french : «Aucun groupe de travail n'a été trouvé dans votre réseau local. Ceci peut être dû à la présence d'un pare-feu activé.») If the first PC (PC1 is start after the second PC (PC2), samba can access file. Bug reproduction : [table] [row] [head colspan="3"]Various test done result[/head] [/row] [row] [col][b]First computer who Boot[/b][/col] [col][b]Second computer who Boot[/b][/col] [col][b]Résult of access of samba file sharing from the second PC (PC2) to the First PC (PC1)[/b][/col] [/row] [row] [col]PC1 On Mageia 1[/col] [col]PC2 On Mageia 1 and accessed from dolphin : Network->Samba Shares[/col] [col]"No work group found in the local network. It can be a working firewall who block it." (ERROR)[/col] [/row] [row] [col]PC1 On Mageia 1[/col] [col]PC2 On Mageia 1 and accessed from dolphin : Network->Samba Shares + Firewall disactivated[/col] [col]OK (WORK)[/col] [/row] [row] [col]PC2 On Mageia 1[/col] [col]PC1 On Mageia 1 and accessed from dolphin : Network->Samba Shares[/col] [col]OK (WORK)[/col] [/row] [row] [col]PC1 On Mageia 1[/col] [col]PC2 On OpenSuse 11.4[/col] [col]OK (WORK)[/col] [/row] [row] [col]PC1 On Mageia 1[/col] [col]PC2 On Mageia 1 and accessed when use [url=smb://192.168.1.12]smb://192.168.1.12[/url] like an URL[/col] [col]OK (WORK)[/col] [/row] [row] [col]PC1 On Mageia 1[/col] [col]PC2 On Mageia 1 and accessed with Gigolo[/col] [col]Ok (WORK)[/col] [/row] [row] [col]PC1 On Mandriva 2010.2[/col] [col]PC2 On Mageia 1 and accessed with dolphin : Network->Samba Shares[/col] [col]"No work group found in the local network. It can be a working firewall who block it." (ERROR)[/col] [/row] [row] [col]PC1 On Mandriva 2010.2[/col] [col] PC2 On Mageia 1 and accessed when use [url=smb://192.168.1.12]smb://192.168.1.12[/url] like an URL[/col] [col]Ok (WORK)[/col] [/row] [row] [col]PC1 On Mandriva 2010.2[/col] [col]PC2 On Opensuse 11.4[/col] [col]Ok (WORK)[/col] [/row] [/table] It is not a network problème because it work without mod somethink : -With Gigolo on Mageia 1 -With the samba IP URL -On other distro So, it can be a firewall and dolphin problem on Mageia.[/quote] Thank for your time.
Sorry, i thought than the bugzilla can use some graph for bug report...
Various test done result : -First computer who Boot will be the first line -Second computer who Boot will be the second line -Résult of access of samba file sharing from the second PC (PC2) to the First PC will be the third line(PC1) Test 1 : -PC1 On Mageia 1 -PC2 On Mageia 1 and accessed from dolphin : Network->Samba Shares -"No work group found in the local network. It can be a working firewall who block it." (ERROR) Test 2 : -PC1 On Mageia 1 -PC2 On Mageia 1 and accessed from dolphin : Network->Samba Shares + Firewall disactivated -OK (WORK) Test 3 : -PC2 On Mageia 1 -PC1 On Mageia 1 and accessed from dolphin : Network->Samba Shares -OK (WORK) Test 4 : -PC1 On Mageia 1 -PC2 On OpenSuse 11.4 -OK (WORK) Test 5 -PC1 On Mageia 1 -PC2 On Mageia 1 and accessed when use [url=smb://192.168.1.12]smb://192.168.1.12[/url] like an URL -OK (WORK) Test 6 -PC1 On Mageia 1 -PC2 On Mageia 1 and accessed with Gigolo -Ok (WORK) Test 7 -PC1 On Mandriva 2010.2 -PC2 On Mageia 1 and accessed with dolphin : Network->Samba Shares -"No work group found in the local network. It can be a working firewall who block it." (ERROR) Test 8 -PC1 On Mandriva 2010.2 -PC2 On Mageia 1 and accessed when use [url=smb://192.168.1.12]smb://192.168.1.12[/url] like an URL -Ok (WORK) Test 9 -PC1 On Mandriva 2010.2 -PC2 On Opensuse 11.4 -Ok (WORK)
Created attachment 615 [details] Table made ââof MLO
Hello,Team Mageia I have the same problem with Samba and Dolphin. Attached, here is a snapshot of the table on the MLO forum.
CC: (none) => olivier.delaune
CC: (none) => balcaen.john
Assigning to dolphin maintainer
CC: (none) => stormiAssignee: bugsquad => balcaen.john
What happens to this bug? Nobody has any suggestions? With "Mandriva 2010.2" it works very well, but not with "Mageia 1" unless you disable the firewall.
CC: (none) => geiger.david68210
(In reply to comment #6) > What happens to this bug? Nobody has any suggestions? > > With "Mandriva 2010.2" it works very well, but not with "Mageia 1" unless you > disable the firewall. @ John Balcaen Please set status to ASSIGNED if you think this bug was assigned correctly. If for workflow reasons you can't do that, then please put OK on the whiteboard instead. If you think the culprit is another package than one of yours, please assign to the maintainer of that package or assign back to Bug Squad.
CC: (none) => marja11
Well if the problem is solved by disabling the firewall, i would say that dolphin is not the culprit here. So something needs to be done on the firewall part. I personally did not find the time to test it.
Ok i was able to test & it's indeed related to firewall settings... once it's disable i'm able to browse the smb server available on my NAS. Please note that the port needed to *allow* access to a smb server & the one needed to browse a smb server are quite different. This (old) bug is quite interresting https://bugzilla.redhat.com/show_bug.cgi?id=133478 To be able to browse samba share with firewall enable you need to load this module : nf_conntrack_netbios_ns. Once it's done you'll be able to browse samba share. So reassinging to package drakx-net (which provides drakfirewall). Regards,
Assignee: balcaen.john => bugsquadSource RPM: Dolphin => drakx-net
(In reply to comment #9) > Ok i was able to test & it's indeed related to firewall settings... > once it's disable i'm able to browse the smb server available on my NAS. > Please note that the port needed to *allow* access to a smb server & the one > needed to browse a smb server are quite different. > This (old) bug is quite interresting > https://bugzilla.redhat.com/show_bug.cgi?id=133478 > > To be able to browse samba share with firewall enable you need to load this > module : nf_conntrack_netbios_ns. > Once it's done you'll be able to browse samba share. > So reassinging to package drakx-net (which provides drakfirewall). > > Thanks a lot, John :) assigning to maintainer of drakx-net
Assignee: bugsquad => mageia
(In reply to comment #10) > > assigning to maintainer of drakx-net @ blino Please set status to ASSIGNED if you think this bug was assigned correctly. If for workflow reasons you can't do that, then please put OK on the whiteboard instead.
Excellent, finally there's new: Since the srpm update package shorewall-4.4.19.1-3.1.mga1.src.rpm in Core_Updates_Testing everything is back to normal, the bug 1903 seems to be resolved. To be really sure I continue testing,but the correction of the bug seems to be on track. Apparently the bug 1903 and bug 1147 appears to be related.
Depends on: (none) => 1147
Well, I can now confirm that the bug is resolved. After several test I have nothing to report.A member of MLO has had the same problem and after installing the update shorewall, the bug has been resolved too. http://www.mageialinux-online.org/forum/topic-10430-3+samba-acces-impossible-a-mon-autre-pc.php#m117628 He said : >Well for me, it's good >The update of Shorewall has solved my problem. >I did the update on my two machines and now they are good in Dolphin ->> Network ->> Samba Shares. >Thank you to all who have studied the problem. And congratulations to the team Mageia for the update. >Just, we had to be patient Thank you.
@ David Thanks for the feedback :) @ blino John Balcaen thinks this bug is in drakx-net (drakfirewall), see comment 9 I suppose, that if updating to shorewall-4.4.19.1-3.1.mga1.src.rpm solved this bug, it can still mean that drakfirewall works buggy, but shorewall corrected what drakfirewall did wrong? WDYT?
(In reply to comment #9) [...] > > To be able to browse samba share with firewall enable you need to load this > module : nf_conntrack_netbios_ns. > Once it's done you'll be able to browse samba share. shorewall is able to automatically load kernel's module nf_conntrack*. but the default configuration of shorewall allows to load automatically only uncompressed kernel's modules (*.ko), and our kernel's modules are compressed by default (ko.gz). shorewall-4.4.19.1-3.1.mga1 fixes this bug. (In reply to comment #14) [...] > I suppose, that if updating to shorewall-4.4.19.1-3.1.mga1.src.rpm solved this > bug, it can still mean that drakfirewall works buggy, but shorewall corrected > what drakfirewall did wrong? no, the problem was only in our default shorewall.conf. thanks to all for the feedback. I'm closing this bug as duplicate of bug 1147. *** This bug has been marked as a duplicate of bug 1147 ***
Status: NEW => RESOLVEDCC: (none) => lmenutHardware: x86_64 => AllResolution: (none) => DUPLICATESource RPM: drakx-net => shorewall
I test DVD Mageia 2-beta 3 for x86_64 and the problem is again present,Let me explain: I have two PCs, the first "Laptop_mga.2_1" and the second "desktop_mdv.2010.2_2" When I want to access the "desktop_mdv" from my "laptop_mga" via dolphin: Using Dolphin ->> Network ->> Samba Shares ->> Mgagroup ->> desktop_mdv.2010.2_2 message appears: "Timeout on server desktop_mdv.2010.2_2" Loading folder ,therefore the access is impossible. But if I use the PC's IP address (eg 192.168.1.19) instead of Mgagroup - >> desktop_mdv.2010.2_2, where it works fine and access is possible. Dolphin ->> Network ->> Samba Shares ->> Mgagroup ->> smb://192.168.1.19/ Is that the bug has shorewall or the recent update of Samba ? I reopened this one.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
In console dolphin returns : $ LC_ALL=C dolphin QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap dolphin(25959) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf Loaded services file OK. Warning: Service printers defines a print command, but rameter is ignored when using CUPS libraries. " dolphin(25959) DolphinRemoteEncoding::updateMenu: could not find entry for charset= "Other encoding ()" dolphin(25959) DolphinRemoteEncoding::updateMenu: could not find entry for charset= "Other encoding ()" dolphin(25959) DolphinRemoteEncoding::updateMenu: could not find entry for charset= "Other encoding ()"
Tested on Mageia release 2 (Official) for x86_64 and Kernel 3.3.6-server-2.mga2 on a Dual-processor x86_64 ,this bug is present with shorewall.
Priority: Normal => HighVersion: 1 => 2
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD