6 replies
by miha.pihler
I am not sure if I got your question right. But if you have your production environment AND your test environment on the network at the same time there will be a problem if environments share DNS (x.com) and NetBIOS (x) name.
If this is the case, Isuggest that you take your test environment off the network (unplug the network cable that connects your test environment) and work on it isolated from the production environment.
Other option is to use different DNS (y.com) and NetBIOS (y) name intest environment.
Hope this helps?
Regards, Mike
MCSA, MCSE
by johanesian
by johanesian
by joseph moore
Well, there already is X.COM (registered to the X.com Corporation in California). That could be your problem. Running DCPROMO in Win2K, a check of DNS records does happen, and probably something that happens is to see if the FQDN you use is available or not.
If I were you, I would change the FQDN to something else that is not valid on the Internet, or before you run DCPROMO, disconnect your test Domain Controller from an outbound Internet connection. That way, it would set up its own DNS server to record that X.COM is its own IP address.
hope this helps
by johanesian
by johanesian
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending