On Wed, 16 Oct 2002, Chuck wrote:
I am trying to get access to and from my Suse 8.0 pc via Samba to my Windows XP pc. I have gone through Yast2 and opened up port 139, but still no luck. When I bring the firewall down, it works fine, but I don't want to do that. Is there another piece I am missing.
I don't think you need anything special to run smbclient on the internal interface but the troubleshooting advice Togan gave should solve it. For samba (server) having the following in Section 9 of the config works for me FW_SERVICES_INT_TCP="ssh netbios-ssn" FW_SERVICES_INT_UDP="netbios-dgm netbios-ns" (ssh of course has nothing to do with smb -- but I like it and of course if you want to access your SuSE PC from Windows 2K/XP, you can install putty or cygwin) I have read docs that suggested that FW_SERVICES_INT_UDP="netbios-dgm netbios-ns" (ports 137 and 138) are technically not needed, but my simple experimentation indicated that was a special case -- my samba print server (W2K clients) needs them By the way, when testing it seems to me good NOT to use the Windows Network Neighbourhood nor Add Printer Browser -- for a simple 2 PC network you don't need it and it can be confusing as the names can take a while to propagate -- just 10 feet. Instead enter the known IP address at your Win desktop (command line 'net use' and Add Printer - known printer) and your smbclient. Get that working then try the browser dproc