Re: DNS problem while trying to join windows 7 to samba3x pdc

[Craig White <craigwhite@xxxxxxxxxxx>]

On Thu, 2010-07-08 at 13:43 -0500, Les Mikesell wrote:
> On 7/8/2010 1:15 PM, Craig White wrote:
> >
> > a 'network' is 192.168.x assuming that you are using class C subnet
> > masks (255.255.255.0) and so you should have a WINS server on EACH
> > network (192.168.4, 192.168.5, 192.168.6, etc.)
> 
> I thought the point of WINS was to have a single address that would 
> collate the names/addresses from all your networks.
> 
> > The important thing is to get the WINS working on EACH network. It's
> > also easiest to have your PDC be the WINS server - period.
> 
> But PDC's aren't limited to one subnet either.
----
WINS is a broadcast based protocol and thus it only works on the local
network and each subnet/network MUST necessarily have master browser
elections. The WINS server on each subnet would serve as a clearing
house for name resolution for each subnet/network. That is clearly not
working for him just from that error message.

Samba machines are not limited to one subnet either by multiple network
addresses or via routers but their ability to identify their presence on
other subnets/networks is limited at best (remote announce).

The concept was that computers just find each other on a subnet via
network browsing. When you have a server involved, you want to 'rig' the
browser elections so you have entirely predictable location for
retrieving the current workgroup members instead of the haphazard method
employed by default. This means you put a WINS server on each subnet and
specifically instruct each client (whether a Windows workstation or a
samba server) to specifically interrogate that WINS server for the
latest browse list.

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos