That should work OK. The lists you see in Network Neighborhood come from
the computer browser service. This is an NT legacy app which uses Netbios
names and LAN broadcasts to build the browse list. When you go to a routed
network or a WAN, some things stop working because broadcasts are restricted
to the local segment.
When you set up your second domain, you will initially get a browse list
built for each site. The machines in each site will see the browse list for
the local domain but nothing for the "other" domain (unless you have a WINS
server and configure all the machines to use WINS). WINS allows the browse
masters to communicate across the WAN link and build a network-wide browse
list. (By using WINS they can convert names to IP addresses and communicate
across the WAN, where broadcast resolution would fail).
If you have a WINS server in each site you will need to set them up to
replicate, so that each WINS server has information about both sites. WINS
is independent of AD and needs its own replication.
"Eric" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
>i guess it's just my lack of knowledge when it comes to networking
> across wan sites....
>
> what the main goal is, is to have multiple locations in Network
> Neighborhood (ie Headquarters, site1, site2, etc....) My understanding
> was to have a dc at each location, and then different domain names (or
> netbios names) at each site to seperate the two places..
>
> as far as duplicate names for computers, we have a particular naming
> convention here, so there will be no name duplication.
>
>
> Bill Grant wrote:
>> You are aware of the problems with Netbios names across sites? Even if
>> you
>> set up WINS, your Netbios name space is like a flat file. Machines will
>> just
>> have a single Netbios name which is not linked to the site they are in,
>> and
>> you cannot have duplicate machine names (ie you cannot have a machine
>> called
>> "fred" in site A if there is one called that in site B). Netbios names
>> are
>> not hierachical like DNS.
>>
>> "Eric" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed) ps.com...
>> > ok this helps..
>> >
>> > what is we want a different netbios name at that site ?
>> >
>> >
>> > Danny Sanders wrote:
>> >> I would suggest adding it as a site in your domain.
>> >> See:
>> >> http://www.windowsitpro.com/Article/...380/13380.html
>> >>
>> >>
>> >> hth
>> >> DDS
>> >> <(E-Mail Removed)> wrote in message
>> >> news:(E-Mail Removed) ups.com...
>> >> > right now we have two locations.. i've simplified the names for
>> >> > desctition and security purposes...
>> >> >
>> >> > ohio = mydomain.us (netbios: mydom-us-ohio)
>> >> >
>> >> > iowa = workgroup: company2
>> >> >
>> >> >
>> >> > mydomain.us has 2 domain controllers, exchange 2003 that handles all
>> >> > of
>> >> > the email in the organization (including the remote site)
>> >> >
>> >> >
>> >> >
>> >> > we want to install a domain controller at the remote location in
>> >> > iowa.
>> >> > convert 'workgroup' to a domain (netbios: mydom-us-iowa)
>> >> >
>> >> >
>> >> > what is the best way to go here ?
>> >> >
>> >> > i'll answer any configuration questions that i can here..
>> >> >
>> >> >
>> >> > thanks
>> >> >
>> >
>
Similar Threads
Linear Mode
