[SLE] SuSEfirewall Samba need Help
Hello All, I have a SuSE server configure with Samba but the problem is in the local network it work fine I can see the samba server and login to it. I cant see the samba server outside the firewall. I have TCP and UDP services ACCEPT for port 137:139 but I still dont see the Samba server. Can any point to exacly what variables shoud be set in the firewall for me to see it outsise the firewall. Is the some other service that I need to start for this to work. The samba is inside the intranet... Thanks for any help.. |__|___|___|__\\|// - ?__|___|_____|___|_____| |__|___|___|__(o o)______|___|_____|___|_____| |__|___|___oOOO(_)OOOo____|___|_____|___|_____| email : ephlodur@rocketmail.com What we need is Awareness we can't get carelless. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On 15/06/06 07:04, MindBender wrote:
Hello All,
I have a SuSE server configure with Samba but the problem is in the local network it work fine I can see the samba server and login to it. I cant see the samba server outside the firewall. I have TCP and UDP services ACCEPT for port 137:139 but I still dont see the Samba server.
Can any point to exacly what variables shoud be set in the firewall for me to see it outsise the firewall. Is the some other service that I need to start for this to work.
The samba is inside the intranet...
Thanks for any help. Open port 445 and start nmbd.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 15 June 2006 15:59, Darryl Gregorash wrote:
On 15/06/06 07:04, MindBender wrote:
Hello All,
I have a SuSE server configure with Samba but the problem is in the local network it work fine I can see the samba server and login to it. I cant see the samba server outside the firewall. I have TCP and UDP services ACCEPT for port 137:139 but I still dont see the Samba server.
Can any point to exacly what variables shoud be set in the firewall for me to see it outsise the firewall. Is the some other service that I need to start for this to work.
The samba is inside the intranet...
Thanks for any help.
Open port 445 and start nmbd.
shouldn't all this port opening happen when the "open port in firewall" button is pressed in Yast? d. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 16 June 2006 4:25 am, kanenas@hawaii.rr.com wrote:
On Thursday 15 June 2006 15:59, Darryl Gregorash wrote:
Open port 445 and start nmbd.
shouldn't all this port opening happen when the "open port in firewall" button is pressed in Yast? d.
You're new here aren't you? But seriously folks... If the SAMBA ports and smbd/nmbd aren't being opened/started properly in SuSEfirewall2 then we need to bugzilla that to get it fixed. I believe that this is a long running problem with SuSEfirewall2 and SAMBA setup. Could we get some verification that this is/is not happening? Thanks and I'll gladly bugzilla it, Stan -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 16 June 2006 02:57, S Glasoe wrote:
On Friday 16 June 2006 4:25 am, kanenas@hawaii.rr.com wrote:
On Thursday 15 June 2006 15:59, Darryl Gregorash wrote:
Open port 445 and start nmbd.
shouldn't all this port opening happen when the "open port in firewall" button is pressed in Yast? d.
You're new here aren't you? But seriously folks...
If the SAMBA ports and smbd/nmbd aren't being opened/started properly in SuSEfirewall2 then we need to bugzilla that to get it fixed. I believe that this is a long running problem with SuSEfirewall2 and SAMBA setup. Could we get some verification that this is/is not happening?
Thanks and I'll gladly bugzilla it, Stan
my samba never worked unless i manually opened the ports myself. since 9.0 i think. d. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I open port 445 TCP/UDP and I also put broadcast to yes .... but it sill dont show outside of the firewall... if I connect to it from windows like \\samba_ip it work
so I guess that will have to do for now...
Thanks for the reply.
Darryl Gregorash
Hello All,
I have a SuSE server configure with Samba but the problem is in the local network it work fine I can see the samba server and login to it. I cant see the samba server outside the firewall. I have TCP and UDP services ACCEPT for port 137:139 but I still dont see the Samba server.
Can any point to exacly what variables shoud be set in the firewall for me to see it outsise the firewall. Is the some other service that I need to start for this to work.
The samba is inside the intranet...
Thanks for any help. Open port 445 and start nmbd.
|__|___|___|__\\|// - ?__|___|_____|___|_____| |__|___|___|__(o o)______|___|_____|___|_____| |__|___|___oOOO(_)OOOo____|___|_____|___|_____| email : ephlodur@rocketmail.com What we need is Awareness we can't get carelless. --------------------------------- Sneak preview the all-new Yahoo.com. It's not radically different. Just radically better.
On 16/06/06 10:37, MindBender wrote:
I open port 445 TCP/UDP and I also put broadcast to yes .... but it sill dont show outside of the firewall... if I connect to it from windows like \\samba_ip it work so I guess that will have to do for now...
Is nmbd running? It won't show up elsewhere in the network unless nmbd is running. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 16/06/06 14:30, Darryl Gregorash wrote:
On 16/06/06 10:37, MindBender wrote:
I open port 445 TCP/UDP and I also put broadcast to yes .... but it sill dont show outside of the firewall... if I connect to it from windows like \\samba_ip it work so I guess that will have to do for now...
Is nmbd running? It won't show up elsewhere in the network unless nmbd is running.
The OP wrote to me privately that nmbd is running. Grrr, another great idea bites the dust :-) Apart from setting up specific shares, this configuration has always been sufficient on my system to enable it as a samba server (a rather minimal one, though): in the firewall config: FW_SERVICES_INT_TCP="microsoft-ds netbios-dgm netbios-ns netbios-ssn" FW_SERVICES_INT_UDP="netbios-ns" in smb.conf: give the server a netbios name and ensure all systems in the network are using the same workgroup name. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Darryl Gregorash wrote:
in the firewall config:
FW_SERVICES_INT_TCP="microsoft-ds netbios-dgm netbios-ns netbios-ssn" FW_SERVICES_INT_UDP="netbios-ns"
I always preferred to use the numbers, otherwise I have to check /etc/services and double check my spelling. Should be, BTW, TCP 139 445, UDP 137 138. -- Joe Morris Registered Linux user 231871 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 16/06/06 19:34, Joe Morris (NTM) wrote:
Darryl Gregorash wrote:
in the firewall config:
FW_SERVICES_INT_TCP="microsoft-ds netbios-dgm netbios-ns netbios-ssn" FW_SERVICES_INT_UDP="netbios-ns"
I always preferred to use the numbers, otherwise I have to check /etc/services and double check my spelling. Should be, BTW, TCP 139 445, UDP 137 138.
My setup seems to work, so I've left it as is for some time. Not saying you're wrong, though.. mine just works. As for names vs. numbes, I prefer to use the names, otherwise I have to remember the numbers :-) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 16 June 2006 7:14 pm, Darryl Gregorash wrote:
On 16/06/06 14:30, Darryl Gregorash wrote: Apart from setting up specific shares, this configuration has always been sufficient on my system to enable it as a samba server (a rather minimal one, though):
in the firewall config:
FW_SERVICES_INT_TCP="microsoft-ds netbios-dgm netbios-ns netbios-ssn" FW_SERVICES_INT_UDP="netbios-ns"
in smb.conf: give the server a netbios name and ensure all systems in the network are using the same workgroup name.
Just for clarity, with the above configuration are other windows machines in the workgroup able to *browse* for the shares with the firewall on the server up? I've tried this as well, and with this setup the machine is indeed able to act as a samba server provided a specific share is requested. I've never gotten browsing to work with the firewall up though. -- Don -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Mon, 2006-06-19 at 11:32 -0600, Don Raboud wrote:
On Friday 16 June 2006 7:14 pm, Darryl Gregorash wrote:
On 16/06/06 14:30, Darryl Gregorash wrote: Apart from setting up specific shares, this configuration has always been sufficient on my system to enable it as a samba server (a rather minimal one, though):
in the firewall config:
FW_SERVICES_INT_TCP="microsoft-ds netbios-dgm netbios-ns netbios-ssn" FW_SERVICES_INT_UDP="netbios-ns"
in smb.conf: give the server a netbios name and ensure all systems in the network are using the same workgroup name.
Just for clarity, with the above configuration are other windows machines in the workgroup able to *browse* for the shares with the firewall on the server up?
I've tried this as well, and with this setup the machine is indeed able to act as a samba server provided a specific share is requested. I've never gotten browsing to work with the firewall up though.
FW_SERVICE_SAMBA="yes" Brad Dameron SeaTab Software www.seatab.com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (7)
-
Brad Dameron -
Darryl Gregorash -
Don Raboud -
Joe Morris (NTM) -
kanenas＠hawaii.rr.com -
MindBender -
S Glasoe