From: Hoggins! on
Edmundo Valle Neto a ?crit :
> ...
>
> Theres some options that I think are not needed in your config, but
> probably doesnt cause that problem that you have, in exeption of this one:
>
> local master = no
>
> Try to set it to yes, I never tried to set it to no and let it be only
> the DMB to see what happens but the samba docs have something to say
> about that, "If you want Samba to be a DMB, then it is recommended that
> you also set preferred master to yes, because Samba will not become a
> DMB for the whole of your LAN or WAN IF IT IS NOT ALSO A LMB ON ITS OWN
> BROADCAST ISOLATED SUBNET". Anyway its at least recommended to samba be
> the LMB too.

Well, this option was previously set to yes, and it did not work either.
Changing this, I thought it would make difficult the election of a LMB
on other nets, but you say it won't, so I put it back, and maybe the
other things I changed will cause it to work at last !

Do you have any other ideas about this config ?

Thanks,

Hoggins!

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Hoggins! on
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 ?

Hoggins!

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
From: Craig White on
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.

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 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: John H Terpstra on
On Sunday 01 October 2006 18:45, Hoggins! wrote:
> Edmundo Valle Neto a écrit :
> > Hoggins! escreveu:
> >
> > Yes, in that case it should maintain a more complete list. And yes you
> > just must have ONE WINS server.
> > I think you didnt got the point, domain master, local master, domain
> > controllers, wins server, etc are just roles of the same server,
> > enabling some options in smb.conf the same server can be all of them at
> > the same time.
> > BUT, other subnets need local master browsers too, they can be any
> > Windows workstation (normally you should not worry about that), this is
> > one of the reasons that all of them must use the same single WINS server
> > (I am not saying that yours are not), the LMB can be any available
> > workstation (the machines in the subnet should elect one automatically),
> > so any machine ending up beeing a LMB will use the same WINS server to
> > find the DMB and sync. It works that way without you needing to care
> > about it.
> >
> >
> > Ok, if the wireless clients can see each others probably that segment
> > has an LMB with the browse list of that segment but just isnt passing it
> > to the samba server.
> > About the LMBs I just said that to make it clear, that the other
> > networks dont register themselves directly with samba to be included in
> > the browse.dat file, who does that is the LMB of that segment (as
> > explained before).
>
> Thanks, I understand better now how it works.
> So the LMB (any Win machine, elected) of the 192.168.3.0/24 segment must
> send its browse list to the server, right ? I must check this traffic
> with ethereal and/or with debug level 2. Sorry I didn't yet.

Not quite!

The LMB does nothing to contact the DMB. The responsibility for browse list
synchronization belongs to the DMB.

The DMB looks for the LMB registrations in the WINS (wins.dat) database. It
then contacts each LMB to synchronise the browse list.

Ergo, if the WINS database does not contain all machines that are LMBs -
browse list synchronization will not happen.

- John T.

>
> > Yes, it is possible and most of the times the recommended way.
> >
> >
> > Theres some tools and comands to see problems with name resolution on
> > the XP clients, like nbtstat or the netbios browsing console.
> >
> > Putting a log level of 2 in smb.conf, is there any interesting
> > information about elections in the nmbd log? Whould help if you include
> > your smb.conf here too.
>
> Yes, I put debug level to 2, and I saw that the server was always
> elected as the master. And also that the machines successfully
> registered to the server.
> My smb.conf (a bit modified since my first post, but the symptoms are
> the same though) :
>
> [global]
> display charset = ASCII
> workgroup = BOUFFARD
> netbios aliases = hgsserver
> server string = PARTAGES
> interfaces = eth0
> security = SHARE
> map to guest = Bad User
> root directory = /
> pam password change = Yes
> passwd program = /usr/bin/passwd %u
> passwd chat debug = Yes
> username map = /etc/samba/smbusers
> unix password sync = Yes
> # log level = 2
> # syslog = 3
> # syslog only = Yes
> log file = /var/log/samba/%m.log
> max log size = 50
> debug timestamp = No
> time server = Yes
> server signing = auto
> socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
> printcap name = /etc/printcap
> os level = 32
> lm announce = Yes
> preferred master = Yes
> domain master = Yes
> local master = no
> dns proxy = No
> wins support = Yes
> ldap ssl = no
> remote announce = 192.168.3.255/BOUFFARD
> remote browse sync = 192.168.3.255 224.0.0.1
> usershare path =
> winbind enum users = Yes
> winbind enum groups = Yes
> winbind use default domain = Yes
> guest ok = Yes
> hosts allow = 192.168.2.0/24, 192.168.3.0/24
> cups options = raw
>
> [...] (some shares declarations)
>
> I'll come with more results on benchmarks ASAP. Thanks for your help and
> patience.
>
> Regards,
>
> Hoggins!
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba