Avatar of SteveDallas
SteveDallasFlag for United States of America asked on

New domain server not working

I have set up a new 2003 Server as Domain controller, active directory and DNS.for domain: example.com
There is an existing network with another domain controller: example1.com .  The new Domain controller is set up as new/standalone for preparation to switch users to a new domain in the near future.  New domain appears to be set up but no other machine can join it. I get an error that "Domain Server could not be contacted.:
10.0.1.1  Router/Gateway
10.0.1.142  New domain Server,active directory, dns
10.0.1.146  Server trying to join the new domain.(Is not on any other domain but a workgroup)
10.0.1.128  Old Domain controller, active directory, dns (in use)
I do not want the new domain server to be a part of the domain at all.
Any help would be appreciated.
Windows Server 2003Microsoft Server OSMicrosoft Legacy OS

Avatar of undefined
Last Comment
ChiefIT

8/22/2022 - Mon
craigothy

On your server that you are trying to join to this new domain, do you have the DNS client settings configured to point to 10.0.1.142?
ASKER
SteveDallas

Yes, it is set to look for 10.0.1.142 for DNS.  
ChiefIT

The clients will go to the prefered DNS servers to look for Host A and SRV records. Your old domain DNS server probably doesn't have a DNS host A for this new domain controller. So the client isn't pointed in the right direction to contact the new DC.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
ASKER
SteveDallas

Old Domain Server should not be relevant. I have a new domain controller (stand alone) and trying to connect to it with another new Server that is currently in a workgroup and does not know anything about the old domain controller. I will try to attach a Visio drawing here.
networksimple1.jpg
ASKER CERTIFIED SOLUTION
ChiefIT

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
SteveDallas

I went through these steps to no avail. All appears normal although the two machines are probably communicating across the switch rather than through the router. I am wiping and reloading Server 2003 R2 Domain Controller today and starting over. I will also direct connect this Server to the router and see if that helps.
Thanks for the info.
ASKER
SteveDallas

OS reinstalled. Used wizard to set up Server and the setup went smoothly. Thanks to your steps in the previous message, I was able to get this to work this time. I still need one more answer before awarding and closing this or I can open another request.
Q:   Co-worked wants us to use out actual Internet domain name for out internal domain also. I know that this can sometimes cause problems. Right now I am using:  example.local   rather than  example.com  .
What is recommended?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ChiefIT

I have always worked on .GOV domains. So, I haven't really given this much thought. You shouldn't take my word for it.  

If you don't plan on publishing websites on the web or using your domain for E-commerce, why get one? You will still have internet access through DNS. There are a few headaches that can come from internet domain names. To see the headaches, see this article:
http://www.wipo.int/about-ip/en/studies/publications/domain_names.htm

One thing you should know is if you publish web sites externally and have domain.com on the external website and internal domain, you might have problems accessing your own domain website or domain. So you might consider keeping external web servers and internal domain on different suffixes.

I also like keeping my mail server on different domain suffixes than my internal LAN.

I hope this helps.
ChiefIT

I am not sure you can do that easily with exchange since it likes to work with AD.