Frank Bax wrote:
If I issue this cli command: smbclient -NL //Bob It lists shares on Bob (a Win98 system) when Firewall is disabled, but results in "Connection to Bob failed" when firewall is enabled. Under "Firewall Services", I can see "Samba Server" (which is allowed), but not "Samba Client". How do I fix this?
Frank
Hi Frank,
If you're using SuSEFirewall2, check /var(log/firewall ( or the file you've configured for the log ), check for drooped packets and write down the port(s) that is(are) being dropped. With this you can actually see what port is being rejected and act accordingly.
You can also check /etc/services to search what kind of port/protocol is being dropped.
I know this is not a solution but, it can help you find the problem...
Anyway the ports needed to play with samba are tcp/udp 137->139 and 445 and 53. Which port you are using depends on which client and servers are connected. 137->139 belong to the smb over netbios protocol, while 445 and 53(dns) are used by naked smb over tcp. L.