From: Craig White on
On Mon, 2006-10-02 at 19:55 -0700, Craig White wrote:
> On Tue, 2006-10-03 at 04:41 +0200, Hoggins! wrote:
> > Okay, I checked on my clients, and what I see is for the most
> > surprising: they only display hosts within the samba server's
> > browse.dat, not even the other hosts on the same subnet (usually, I
> > believe they would have been discovered through broadcast). So the only
> > machines that appear on ALL the machines of all the subnets are :
> > - the server
> > - the XP box, located on the same subnet as the server
> >
> > The other hosts' names can be successfully resolved by the server
> > (checked with Ethereal) when explicitly typed in the explorer bar. But
> > they are not "discovered" by the network browsing.
> >
> > Any idea of the problem ?
> >
> > The local masters don't seem to be doing their job, do they ?
> ----
> Official Samba HowTo suggests that you would need a WINS server on each
> subnet
>
> http://samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id2588936
>
> You might want to review the documentation - there is a possibility
> that
> 'remote browse sync = broadcast_address_of_remote_subnet'
> might work for you.
----
OK correction...I have it on good authority that I have given bad advice
above...

1 - only 1 WINS server
2 - remote browse sync is not what you want
3 - clients need to have proper configuration of WINS server address -
if by DHCP, then you probably need to set the node type (option 44/46)
correctly
4 - OP should check contents of wins.dat (on my RH systems, they are
located in /var/cache/samba but on others, they are in /var/lib/samba
YMMV)

Craig

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: John H Terpstra on
On Thursday 28 September 2006 16:13, Aaron Kincer wrote:
> Barry, Christopher wrote:
> > For each host on 192.168.3.0/24, manually add in the WINS address of
> > hgsserver in the wireless NIC configuration. Because WINS does not jump
> > routers, you'll need to tell the client where to find this information.
>
> This is not entirely correct. Many routers can be configured to forward
> NetBIOS and WINS frames. Firewalls that split subnets off different
> interfaces can do it too. However, it can be messy to forward broadcast
> frames.

WINS uses UDP unicast (directed UDP) which is routable. What you have referred
to is known as "NetBIOS helper agent" - a router configuration option that
can perform forwarding of NetBIOS UDP broadcasts. This option is a VERY bad
thing and is totally unecessary if WINS is correctly configured and if
clients are working as they should.

- John T.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: John H Terpstra on
On Thursday 28 September 2006 12:00, Hoggins! wrote:
> Barry, Christopher a écrit :
> > On Thu, 2006-09-28 at 04:14 +0200, Hoggins! wrote:
> > SNIP...
> >
> > For each host on 192.168.3.0/24, manually add in the WINS address of
> > hgsserver in the wireless NIC configuration. Because WINS does not jump
> > routers, you'll need to tell the client where to find this information.
>
> Well, I already did that. It's not manually added, but it's sent through
> DHCP. I checked that every machine on 192.168.3.0/24 had the correct info.
> So I don't really think the problem comes from the clients, but from the
> server instead. My firewall is apparently not the problem, because it
> blocks nothing on this side.

Ah! Does your DHCP settings include "option netbios-node-type 8"?

- John T.

> My opinion is that my server configuration is faulty. Did you have a
> look at it, and did you find errors ? I'm actually thinking of starting
> from scratch, but I'm not even sure this will solve my problems
>
> Thanks anyway.
>
> If anyone can help me on this, it would be wonderful.
>
> Hoggins!

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: John H Terpstra on
On Thursday 28 September 2006 11:23, Barry, Christopher wrote:
> On Thu, 2006-09-28 at 04:14 +0200, Hoggins! wrote:
> > Hello,
> >
> > I'm trying to make browsing work over several routed subnets, but
> > obviously, something goes wrong. Here's the situation :
> >
> >
> >
> > !-----------!
> > ! hgsserver ! (SAMBA HOST)
> > !-----------!
> >
> > |192.168.2.0/24 !----------! 192.168.3.0/24
> > |-----------------! wifigate !------------- - - -
> > | !----------! (several wireless WinXP boxes)
> >
> > !--------------!
> > ! WinXP box !
> > ! "hoggins" !
> > !--------------!
>
> SNIP...
>
> > My browse.dat does not contain all I need, it just contains my machine
> > ("hoggins") and the server. I would like to have all the other hosts
> > that are on subnet 192.168.3.0/24. These hosts have received the
> > server's IP address as the WINS server in their DHCP transaction, and I
> > can see they communicate with it when doing an ethereal analysis.
> > But the browse list remains desperately empty from these hosts.
> >
> > Any ideas on how to solve this really annoying problem ?
> >
> > Thanks in advance,
> >
> > Hoggins!
>
> For each host on 192.168.3.0/24, manually add in the WINS address of
> hgsserver in the wireless NIC configuration. Because WINS does not jump
> routers, you'll need to tell the client where to find this information.

Wrong! WINS uses directed UDP. Directed UDP is routable. Does your router pass
directed UDP packets?

Check your wins.dat file on hgsserver to see if all clients have registered
with the WINS server.

- John T.

>
>
> --
> Regards,
> Christopher Barry
> Manager of Information Systems
> SilverStorm Technologies, Inc.
> O: 610-233-4870
> F: 610-233-4777
> C: 267-242-9306
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Hoggins! on

>
> Check your wins.dat file on hgsserver to see if all clients have registered
> with the WINS server.
>

Yes, they have, and the infos are accurate. NetBIOS name resolution
works perfectly. The problem is about browsing.

Thanks

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba