Re: Problem seeing all machines in workgroup
From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 08/08/04
- Next message: Ace Fekay [MVP]: "Re: A related question"
- Previous message: Robert Moir: "Re: DHCP on domain controller or member server"
- In reply to: Bill Grant: "Re: Problem seeing all machines in workgroup"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 8 Aug 2004 18:01:53 -0400
In news:OeRHxiOfEHA.3928@TK2MSFTNGP11.phx.gbl,
Bill Grant <not.available@online> made a post then I commented below
> Exactly what the DMB role is is explained in the section (not
> surprisingly called "Domain Master Browser Role" ) in KB 188001 .
> Only the PDC has the ability to get the browse lists from the segment
> master browsers, merge them into a networkwide browse list, then
> return the combined browse list to the segment master browsers.
>
> Exactly what happens in a segmented network which is all in one
> workgroup is a situation I haven't ever struck, but I suspect it will
> have problems getting a combined browse list. Even with WINS, my
> guess is that each segment will only see the local segment master
> browser.
>
> Another problem with a workgroup only setup is the way the clients
> interact with WINS. To get a browse list from WINS, the client
> usually sends a name request for <domainname 1B> to WINS. If there
> is no domain set up, this entry doesn't exist, so it resorts to
> broadcast on the local segment to find a browse master. This is one
> reason why remote access clients cannot browse a LAN which is only a
> workgroup, not a domain. The WINS lookup for <domainname 1B> fails,
> and so does broadcasting! There doesn't seem to be a way to make the
> client look for a <name 1D> entry in WINS.
>
> So basically both the browser service itself and the way that the
> client queries WINS assume that there is a domain set up.
>
> Bill Grant
> MVP - Networking
>
Very interesting. I guess the whole idea of Windows networking is assumed to
have a domain. I've never come across this issue since day one dealing with
networks. I've always been around domain scenarios in small and large
infrastructures (multi segmented), and have always had control on who can
install or allow to put a machine up on the network. I've never tested it,
but your explanation makes sense in addition to the article. I wonder why
that ability was never put into the browser service in a workgroup scenario?
At least one thing, it can help isolate a machine if one were to be put up
without joining the domain.
-- Regards, Ace Please direct all replies ONLY to the Microsoft public newsgroups so all can benefit. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP Microsoft Windows MVP - Windows Server - Directory Services Security Is Like An Onion, It Has Layers HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a pig. -- =================================
- Next message: Ace Fekay [MVP]: "Re: A related question"
- Previous message: Robert Moir: "Re: DHCP on domain controller or member server"
- In reply to: Bill Grant: "Re: Problem seeing all machines in workgroup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
