Easiest way to achieve one domain 2 segments in windows 2000

  • Thread starter Thread starter Clement Kim
  • Start date Start date
C

Clement Kim

Hi,
I am a newbie to Windows 2000 networking. What is the easiest way to
connect 2 segments under one domain? Here is a description of my
current set up:
First Segment:
Domain A
Has a domain controller (windows 2000 server)
DC runs Active Directory and DNS
Segment ip:172.17.28.x
Cisco 2600 for VPN to colocation (works fine)

Second Segment:
Segment ip:172.17.27.x
Windows 2003 Terminal Server
Linksys VPN for outside clients (works fine)

I tried multihoming (read many messages) and it didn't work for me. Is
this the way to go? I have another Windows 2000 server available;
should I use that as a domain controller for the Second Segment and
then join domain a? If so, how do I do this? Basically, I would like
the Terminal Server to utilize the domain accounts and not local
accounts on the terminal server.

Like I said, I'm a newbie to Windows 2000 networking. Forgive me if I
used the wrong terminology or I if didn't provide the right
information.

Clem
 
Network segments are not a concern to a domain unless there are domain controllers in
each segment and a slow link between them in which case you want to configure "sites"
to control replication or the link is unreliable in which case a second domain
controller may be a solution as authentication failure can occur. As long as you have
reliable network connectivity between both segments via a router, you should not have
a problem. Join the Windows 2003 server to the domain but first configure it to point
to the W2K domain controller as it's preferred dns server. Two domain controllers
however are recommended for redundancy in any AD domain. --- Steve
 
Back
Top