2 Sites

  • Thread starter Thread starter Otlrnc
  • Start date Start date
O

Otlrnc

2 Domains Same nane
Windows 2000 Servers
I have the unfortunate task of detangling 2 Sites East
Div & West Div each acting as root dns for "soandso.com"
now both sites are connected via T1 must be able to map
drive via Universal Path due to proprietery software
Each Eastern Div has 9 sites West Div has 24 sites
East and West must be unified under One AD and or have a
trust between them so that users can travel intersite
with same loggin and or access various Data bases across
all sites for customer support thru 888#
Must use the easiest path with the least disruption about
400 Users combined.

Any help is greatly appreciated.
Anyone, Time is of the essence.........Please
 
In
Otlrnc said:
2 Domains Same nane
Windows 2000 Servers
I have the unfortunate task of detangling 2 Sites East
Div & West Div each acting as root dns for "soandso.com"
now both sites are connected via T1 must be able to map
drive via Universal Path due to proprietery software
Each Eastern Div has 9 sites West Div has 24 sites
East and West must be unified under One AD and or have a
trust between them so that users can travel intersite
with same loggin and or access various Data bases across
all sites for customer support thru 888#
Must use the easiest path with the least disruption about
400 Users combined.

Any help is greatly appreciated.
Anyone, Time is of the essence.........Please

I see you posted this twice. So I'll answer to this more recent post.

Assuming W2k, if these two DNS servers are hosting a primary zone of your
soandso.com domain, they cannot be both SOA in your infrastructure. Assuming
your whole company is part of one domain (no child domains), then I would
suggest to make both zones AD Integrated, which would alleviate any issues
with that.

Also, if this is not the case, can you elaborate on your DNS infrastructure
a bit? Such as:
Does each location have a DNS server?
If so, are they already AD Integrated or secondary zones of sosandso.com?
If not, are the two in the East and West sites the only DNS across the
infrastructure?

Also, to be able to map drives using NetBIOS (Network Neighborhood), since
you weren't clear on that, you'll need WINS to help you out with this.
Otherwise, W2k and W2k3 use a direct SMB connection to map drives if no WINS
is involved, but Network Neighborhood won't be populated with all machines
in the infrastructure and would only show what is just in that subnet just
on that specific machine where you are doing this on that machine is
located.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
WEST ← T1 → EAST
Root DNS for sonadso.com Root DNS for soandso.com
NETBIOS=Aurora NETBIOS=DOMAIN
AD AD
SITES
SITES
1) =1 1)
=1
2) =2 2)
=2
3) → 24 3)
→ 9
I am able to map drive via ip not share manes
 
No Child domains on either East or West Div
Each individual site has a local DC with DNS forwarding to
home main DC either the Aurora or Domain
FSMO resides at Aurora for the WEST and Domain for the EAST
nothing fancy just 2 basic doamins no subzone, Wins on the
WEST Div due to smome 9X Clients.
 
In
I see you posted this twice. So I'll answer to this more recent post.

Assuming W2k, if these two DNS servers are hosting a primary zone of
your soandso.com domain, they cannot be both SOA in your
infrastructure. Assuming your whole company is part of one domain (no
child domains), then I would suggest to make both zones AD
Integrated, which would alleviate any issues with that.

Also, if this is not the case, can you elaborate on your DNS
infrastructure a bit? Such as:
Does each location have a DNS server?
If so, are they already AD Integrated or secondary zones of
sosandso.com? If not, are the two in the East and West sites the only
DNS across the infrastructure?

Also, to be able to map drives using NetBIOS (Network Neighborhood),
since you weren't clear on that, you'll need WINS to help you out
with this. Otherwise, W2k and W2k3 use a direct SMB connection to map
drives if no WINS is involved, but Network Neighborhood won't be
populated with all machines in the infrastructure and would only show
what is just in that subnet just on that specific machine where you
are doing this on that machine is located.
No Child domains on either East or West Div
Each individual site has a local DC with DNS forwarding to
home main DC either the Aurora or Domain
FSMO resides at Aurora for the WEST and Domain for the EAST
nothing fancy just 2 basic doamins no subzone, Wins on the
WEST Div due to smome 9X Clients.

If only one domain in the orgranization (no matter how many Sites), then
it's really rather simple. Just provide a DNS server on the DC at each
individual Sites and have the sosandsos.com zone as AD Integrated.

But you say you have two domains??
1. Are they in the same forest?
2. If in the same forest, is the Aurora domain a child of Domain or the
other way around?

I ask because I'm confused with your statement saying "no child domain". So
I am ASSUMING these two domains are in separate forests???

AD Integrated zones don't work with mutliple domains in W2k.

NOTE: DO NOT FORWARD back to the central home office. This can cause a
FORWARDING LOOP. You'll want to configure a forwarder on each DNS to forward
to the ISP only.

To map by name, you'll need ALL Sites to use your WINS server. Mapping by
name in the matter of what you're looking for is NOT based on DNS, but
rather NetBIOS, which WINS is needed for that support.

Make absolutely sure you are NOT using your ISP's DNS address on any machine
in the infrastructure other than a forwarder. Other issues WILL develop if
you may be doing so.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top