Re: [SLE] samba can't see windows shares
OK. This turns out to be a firewall problem, in that everything works
when I switch the firwall off. So suse firewall 2 is somehow blocking
nmblookup packets. Now, I don't know anything about configuring the
suse firewall, and the docs are written for ppeople who do know what
they are doing.
Can anyone tell me what I should change and where to make the suse
firewall work with nmblookup? It works with every other part of samba
already, and is configured to let through ports 137-139 on the
internal network (I think).
On Fri, 27 Aug 2004 09:46:10 +0100, Andrew Brown
On Thu, 26 Aug 2004 16:01:10 -0500, David Rankin
wrote: Andrew,
What does
smbclient -U% -L localhost
show?
This:
Sharename Type Comment --------- ---- ------- ukraine Disk The old windows ukraine d Disk try this print$ Disk Printer Drivers REP Disk Routledge Encyclopaedia of philosophy DNB Disk DNB OED Disk OED old_c Disk The old MIddle C whoswho Disk bible Disk the bible in english whos_who Disk IPC$ IPC IPC Service (Samba 3.0.4-SUSE) ADMIN$ IPC IPC Service (Samba 3.0.4-SUSE)
Server Comment --------- ------- WOMBAT Samba 3.0.4-SUSE
Workgroup Master --------- ------- WORKGROUP WOMBAT
----- Original Message ----- From: "Andrew Brown"
To: Sent: Thursday, August 26, 2004 3:19 PM Subject: [SLE] samba can't see windows shares I have a strange problem with Samba. Running under Suse 9.1, with Samba 3.04, I can browse the shares on a Linux box from machines running Windows 2k with no problems. Everything works as it should. But I can't see Windows shares (or for that matter, the Linux shares) from any linux file manages. I can, and do access windows drives using smbmount. But whenever I try, using conqueror, or the XFCE file manager, to see shares on the Windows machines, I can't find anything, and the attempt to see things manually, with nmblookup -M gives me a name_query error. Frantic googling turns up nothing helpful. Can anyone here help?
-- Andrew Brown
What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
-- 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
-- Andrew Brown Tel: +44 (0)1799-516812 Mobile: +44 (0)7968-945618
What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
-- Andrew Brown Tel: +44 (0)1799-516812 Mobile: +44 (0)7968-945618 What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
Andrew Brown wrote:
Can anyone tell me what I should change and where to make the suse firewall work with nmblookup? It works with every other part of samba already, and is configured to let through ports 137-139 on the internal network (I think).
Make sure 137 138 UDP and 139 TCP are opened on your internal network. That should work. You could also open 445 TCP if XP is involved, but it is not necessary (Some worms will hit 445 hard). -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Mon, 30 Aug 2004 08:40:40 -0500, Joe Morris (NTM)
Andrew Brown wrote:
Can anyone tell me what I should change and where to make the suse firewall work with nmblookup? It works with every other part of samba already, and is configured to let through ports 137-139 on the internal network (I think).
Make sure 137 138 UDP and 139 TCP are opened on your internal network. That should work. You could also open 445 TCP if XP is involved, but it is not necessary (Some worms will hit 445 hard).
Thanks. I did this -- rather, I enabled them on my trusted net. But now I have the truly weird problem that the system works for a bit after I restart the firewall; then stops again. So I think there must be a second, non-firewall problem here too.
-- 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
-- Andrew Brown Tel: +44 (0)1799-516812 Mobile: +44 (0)7968-945618 What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
Joe Morris (NTM) wrote:
Make sure 137 138 UDP and 139 TCP are opened on your internal network. That should work. You could also open 445 TCP if XP is involved, but it Thanks. This helped me too. I was having that trouble last night and you reminded me that I forgot about the ports.
Damon Register
participants (3)
-
Andrew Brown
-
Damon Register
-
Joe Morris (NTM)