I think the reason im getting problems is the PC that is running SAMBA is also my firewall, and it blocks pretty much all requests, even from internal addresses. What port(s) do I need to open? Or now am I really confused?
On Wed, 2003-01-08 at 14:07, tufkal wrote:> I think the reason im getting problems is the PC that is running SAMBA > is also my firewall, and it blocks pretty much all requests, even from > internal addresses. What port(s) do I need to open? > > Or now am I really confused?port 139 -- kuhn media australia - kma.0catch.com ------------------------------------- stephen & katherine kuhn -PC/Mac/Linux/Consulting/eMarketing- * linux user: 267497 * rh 7.3+ * ------------------------------------ ...and before I knew what I was doing, I had kicked the typewriter and threw it around the room and made it beg for mercy. At this point the typewriter pleaded for me to dress him in feminine attire but instead I pressed his margin release over and over again until the typewriter lost consciousness. Presently, I regained consciousness and realized with shame what I had done. My shame is gone and now I am looking for a submissive typewriter, any color, or model. No electric typewriters please! --Rick Kleiner
tufkal wrote:> I think the reason im getting problems is the PC that is running SAMBA > is also my firewall, and it blocks pretty much all requests, even from > internal addresses. What port(s) do I need to open?137 (used by nmbd for NetBIOS name service) 138 (used for network browsing) 139 (used by smbd for file sharing and other operations) 445, if you want to support Win 2000/XP NetBIOS-free operation 901, if you want to use SWAT from another system on the network. Keep all of the above ports closed, both incoming and outgoing, for outside (e.g., Internet) connections, or in general, systems outside of those you want your Samba server to serve. Jay Ts