hello world,

i'm unable to see smb shares from my workgroup whenever shorewall is running. this despite the fact that i already enabled samba server access in firewall configuration of the mandrake control panel. i can only see windoze shares when i turn off the firewall.

do i have to configure anything manually with shorewall? what ports must be opened to see windoze workgroup shares?

You've enabled Samba server access but to browse Windows shares you also need to enable things like nmb netbios broadcast ports as well.

i did a portscan of my machine and these are the ports that are open:

Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2004-10-10 23:25 PHT
Interesting ports on localhost (127.0.0.1):
(The 1653 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
6000/tcp open X11

Nmap run completed -- 1 IP address (1 host up) scanned in 1.298 seconds

anything else which i have to open?

^^ with the configuration above, i still can't see smb shares

You scanned "localhost" not your ethernet interface.

Big difference.

Check that as well.

i should use netstat on that right? what particular ports should i be looking for?

Pretty much the same as your local ports.

Also do you have Samba installed as a local server (to provide Linux shares to Windows machines)?

If so try connecting to it via the smbclient

e.g.

smbclient -L machinename -U user

and see what shares it finds.

Post the results of the netstat of the ethernet card.

know what. for some strange reason. i can now see the smb shares of the windoze workgroup even with shorewall on. must've been some quirky behavior of my smb front-end (smb4k) - or maybe i was just too impatient to wait for it to establish connection.

anyway, thanks opjose!

You can always check out what your local Samba "sees" on your network by using smbclient.

E.G.

smbclient -L LOCALHOSTNAME -U username

It will report back the windows machines which appear on your LAN (they appear as servers).

Also note that the Samba service kills itself in the background then restarts itself after a few minutes, and then it may take a few minutes for browser elections and propegation to succeed.

When in doubt use the above trick on your Windows machines from your Linux box, to be sure that Linux can establish a connection.

One last note:

You may want to add the IP's of your Windows machines to /etc/hosts esp. if you do not have a local DNS that seems to be picking up the machines names during DHCP negociation.