I think the ports in question will be
137-139 and 445
Or even 139 and 445 should be sufficient. But I would make sure the
firewall rules only allow access on those ports for the samba server IP's.
Browsing over the internet seems a little unreliable. Remote users may
want to know the name/ip of the samba machine and the specific shares.
Actually, I think accessing samba shares over the internet will have
poor performance- I don't think "windows file sharing" was designed
with "slow" Internet/WAN connections in mind.
On 10/13/2010 03:52 AM, Derek Lewis wrote:
I have a question regarding firewall settings and share browsing. I have
set-up my firewall to allow the usual ports for Samba to work and I would
like to control the connections used for providing Windows with share
browsing.
I currently have a range of ports opened to allow browsing as described in
the documentation, and Samba shares are browseable and accessable. Can I
restrict/specify the port to a small range or single port? Would this just
be a matter of a hosts allow (with ports) added to the $IPC share?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
