[Samba] Multiple Workgroups and Subnets

Tawanda Kavayi tawanda at earth.co.zw
Wed Jul 28 15:30:33 MDT 2010


Thanks. It worked.


Tawanda

Daniel Müller wrote:
> Yes Group1 Server ist the wins for all
>
> -----------------------------------------------
> EDV Daniel Müller
>
> Leitung EDV
> Tropenklinik Paul-Lechler-Krankenhaus
> Paul-Lechler-Str. 24
> 72076 Tübingen
>
> Tel.: 07071/206-463, Fax: 07071/206-499
> eMail: mueller at tropenklinik.de
> Internet: www.tropenklinik.de
> -----------------------------------------------
>
> -----Ursprüngliche Nachricht-----
> Von: Tawanda Kavayi [mailto:tawanda at earth.co.zw] 
> Gesendet: Mittwoch, 28. Juli 2010 10:15
> An: mueller at tropenklinik.de
> Cc: tms3 at tms3.com; samba at lists.samba.org
> Betreff: Re: AW: [Samba] Multiple Workgroups and Subnets
>
> OK, but what of the client PC's in Group2. Do I assign them the Group1 
> server as their WINS server, or do they now operate without WINS?
>
>
> Tawanda
>
> Daniel Müller wrote:
>   
>> Example
>> On Server1
>>
>> [global]
>>   
>>     
>>>                workgroup = GROUP1
>>>                netbios name = GROUP1_SRV
>>>                domain master = yes
>>>                local master = yes
>>>                preferred master = yes
>>>                os level = 65
>>>                smb ports = 139
>>>                dns proxy = no
>>>                socket options = TCP_NODELAY SO_RCVBUF=8192 
>>> SO_SNDBUF=8192
>>>                wins support = yes
>>>                name resolve order = wins lmhosts bcast host
>>>                interfaces = lo eth0 192.168.10.254/24 127.0.0.1/8
>>>                bind interfaces only = yes
>>>                remote announce = 192.168.20.254/GROUP1
>>>                remote browse sync = 192.168.20.254
>>>                hosts allow = 127. 192.168.10. 192.168.20.
>>>     
>>>       
>> On Server 2
>>
>>
>> [global]
>>   
>>     
>>>                workgroup = GROUP2
>>>                netbios name = GROUP2_SRV
>>>                domain master = yes
>>>                local master = yes
>>>                preferred master = yes
>>>                os level = 65
>>>                smb ports = 139
>>>                dns proxy = no
>>>                socket options = TCP_NODELAY SO_RCVBUF=8192 
>>> SO_SNDBUF=8192
>>>                wins support = no
>>>     
>>>       
>> --------->	     Wins server= IPOFTHESERVER1   <-----------	
>>   
>>     
>>>                name resolve order = wins lmhosts bcast host
>>>                interfaces = lo eth0 192.168.10.254/24 127.0.0.1/8
>>>                bind interfaces only = yes
>>>                remote announce = 192.168.10.254/GROUP2
>>>                remote browse sync = 192.168.10.254
>>>                hosts allow = 127. 192.168.10. 192.168.20.
>>>     
>>>       
>> -----------------------------------------------
>> EDV Daniel Müller
>>
>> Leitung EDV
>> Tropenklinik Paul-Lechler-Krankenhaus
>> Paul-Lechler-Str. 24
>> 72076 Tübingen
>>
>> Tel.: 07071/206-463, Fax: 07071/206-499
>> eMail: mueller at tropenklinik.de
>> Internet: www.tropenklinik.de
>> -----------------------------------------------
>> -----Ursprüngliche Nachricht-----
>> Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
>>     
> Im
>   
>> Auftrag von tms3 at tms3.com
>> Gesendet: Dienstag, 27. Juli 2010 23:27
>> An: Tawanda Kavayi
>> Cc: samba at lists.samba.org
>> Betreff: Re: [Samba] Multiple Workgroups and Subnets
>>
>> Short answer:  Use 1 WINS server.
>>
>>
>>
>>   
>>     
>>> --- Original message ---
>>> Subject: [Samba] Multiple Workgroups and Subnets
>>> From: Tawanda Kavayi <tawanda at earth.co.zw>
>>> To: <samba at lists.samba.org>
>>> Date: Tuesday, 27/07/2010  2:01 PM
>>>
>>> Hi,
>>>
>>> I am configuring a network with two subnets with a different workgroup
>>> in each subnet. My aim is to have users being able to view and access
>>> shares on both workgroups. I have a Samba server in each
>>> subnet/workgroup, configured as both the domain and local master for
>>> each workgroup. Each server is also the WINS server for its subnet. 
>>> The
>>> setup is like this:
>>>
>>> Subnet1:
>>> network - 192.168.10.0/24
>>> server IP - 192.168.10.254
>>> workgroup - Group1
>>>
>>> Subnet2:
>>> network - 192.168.20.0/24
>>> server IP - 192.168.20.254
>>> workgroup - Group2
>>>
>>> The two servers are configured identically, except for the information
>>> above, so the smb.conf for the Group1 server looks like this:
>>>
>>> [global]
>>>                workgroup = GROUP1
>>>                netbios name = GROUP1_SRV
>>>                domain master = yes
>>>                local master = yes
>>>                preferred master = yes
>>>                os level = 65
>>>                smb ports = 139
>>>                dns proxy = no
>>>                socket options = TCP_NODELAY SO_RCVBUF=8192 
>>> SO_SNDBUF=8192
>>>                wins support = yes
>>>                name resolve order = wins lmhosts bcast host
>>>                interfaces = lo eth0 192.168.10.254/24 127.0.0.1/8
>>>                bind interfaces only = yes
>>>                remote announce = 192.168.20.254/GROUP1
>>>                remote browse sync = 192.168.20.254
>>>                hosts allow = 127. 192.168.10. 192.168.20.
>>>
>>> The problem is that a machine in Group1 can see all the machines in 
>>> it's
>>> workgoup, plus the network for Group2 appears in network neighborhood,
>>> but the machines and shares in Group2 do not.
>>>
>>> To troubleshoot, I ran smbtree with debug level 5. What I picked out
>>> from all the output was:
>>>
>>> Cannot find master browser for workgroup GROUP2
>>>
>>> How can I resolve this?
>>>
>>>
>>> Tawanda
>>>
>>>
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/options/samba
>>>     
>>>       
>>   
>>     
>
>
>
>   



More information about the samba mailing list