Creating test network - dangers?

  • Thread starter Thread starter Mark N.
  • Start date Start date
M

Mark N.

I'm in the planning stage for setting up a test network. The goal is to
create a system that is similar to my production environment so that I can
practice implementing active directory. My only fear is that somehow I will
screw up my production domain in the process.
I will, of course, give this network its own PDC and BDC and domain name,
but I will want to connect it to the internet via my T1 connection. Since
I've never operated two independent domains at the same time, this makes me
nervous.
Is there anything I should avoid doing or is there potential for wreaking
havoc on my production domain/network? I guess the one thing I fear is
accidentally making my production domain try to go active directory while I
try to make my test domain do so.

What should I watch out for?

Thanks,
Mark
 
Should not be a problem. You can have more then one domain on a network. You
might want to consider a different IP scheme and subnet mask for the "test"
network. This will ensure that it does not conflict with your current
domain.
 
Should not be a problem. You can have more then one domain on a network.
You
might want to consider a different IP scheme and subnet mask for the "test"
network. This will ensure that it does not conflict with your current
domain.
Click to expand...

Thanks for the reply! I feel a little better now :-)

Mark
 
Back
Top