https://bugzilla.novell.com/show_bug.cgi?id=240954 Summary: SuSEfirewall won't allow Samba client to browse windows peer to peer network Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: paul@duraden.com QAContact: qa@suse.de I have had various flavours of SuSE from 9.1 to 10.2 running on 4 different Intel 32 bit machines over several years, and on two separate simple windows peer to peer ethernet networks - now all with XP machines. Whilst setting up a Samba server has always worked perfectly, even with the firewall enabled, I have until recently never been able to browse the Windows network from the SuSE Samba client with the firewall enabled. I have just discovered that the workaround for this is to set the firewall variable: FW_ALLOW_INCOMING_HIGHPORTS_UDP to microsoft-ds netbios-ns from YaST System> /etc/sysconfig editor Note: FW_ALLOW_INCOMING_HIGHPORTS_TCP variable does not seem to affect this problem. The fix came from advice on a LinuxForums site with the link http://tweakhound.com/linux/samba/page_5.htm I have tested this workaround several times (on OpenSuSE 10.2)and it behaves consistently, but noting also that changes using this editor do not seem to be effective until the system is rebooted - every time. But I note the following comment in the editor with dismay... "defaults to "no" if not set (good choice) Note: Use of this variable is deprecated and it will likely be removed in the future. If you think it should be kept please report your use case at http://forge.novell.com/modules/xfmod/project/?susefirewall2" If you remove this variable from future updates I know no way of browsing my windows networks except with the firewall disabled. Can you keep this variable in? Or is there a better solution? Many thanks .......... Paul -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.