I've set up a FreeNAS server that offers to share a disk via CIFS. I can access this share from a WinXP system. I also want to access it from my MEPIS system, on which I've installed the Firestarter firewall. I've opened up ports 137-139 and 445 for everyone, as described in several other LQ posts. When using SMB4K to browse the network, I can see the FreeNAS server but can't see its share. I use Firestarter to look at recent events, and it shows me that the FreeNAS server was trying to access port 1094 on the MEPIS system. If I permit access on port 1094, SMB4K can see the share on the FreeNAS server.

I've used this same method (look at the event log to see what ports are being accessed) on other occasions, and at various times I've needed to open ports 1037, 1045, 1049, 1058, and 1094 to get SMB4K to work. My question is, Is this normal? It seems excessive to me, especially since other LQ posts don't mention needing these ports.

Have I finally identified all the ports that are needed, or will FreeNAS or SMB4K decide I need yet another open port in the future?

TIA,
- TSloth

When your Mepis host access's the FreeNAS host it will open a random source port to send the TCP packet to the destination's host port.

It appears that your firewall needs to accept any returning packets back to the source port that was used.

If possible you should set a rule to allow an application send and receive packets, instead of specifying specific inbound ports.