windows 2k3 server cannot join win2k domain

I was trying to add my windows 2003 server to my active
directory domain( it is  win2k server), windows 2003
server is assigned to obtain IP address,and DNS address
automatically using DHCP. When I tried to add this server
to the adc domain it sgiving following error

The following error occurred when DNS was queried for the
service location (SRV) resource record used to locate a
domain controller for domain companyname.com:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.companyname.com

Common causes of this error include the following:

- The DNS SRV records required to locate a domain
controller for the domain are not registered in DNS. These
records are registered with a DNS server automatically
when a domain controller is added to a domain. They are
updated by the domain controller at set intervals. This
computer is configured to use DNS servers with following
IP addresses:

192.168.10.50

- One or more of the following zones do not include
delegation to its child zone:

comapnyname.com
com
.. (the root zone)

For information about correcting this problem, click Help.

How should I troubleshoot this problem?

ketan
ketansahasrabudhe@hotmail.com
.

ketansahasrabudheAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JivkoCommented:
It is not a good idea to use DCHP for domain controller
0
ketansahasrabudheAuthor Commented:
Thanks, but i even triedststic IP also but it still the same error.
0
ketansahasrabudheAuthor Commented:
Thanks, but i even tried static IP , but it still the same error.
0
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

chicagoanCommented:
Is the new machine using the DC for DNS?

is dhcp handing out:
msdcs.companyname.com
?

is that name of your domain?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chicagoanCommented:
0
chicagoanCommented:
which was it?
0
ketansahasrabudheAuthor Commented:
Is the new machine using the DC for DNS?

is dhcp handing out:
msdcs.companyname.com
?

is that name of your domain?
 
Well how to find out answers for these?

Ketan
0
chicagoanCommented:
type IPCONFIG /ALL at the command prompt of the DC and the new machine and compare them

0
ketansahasrabudheAuthor Commented:
ok, the new machine is using the domain controller as dns server.
and what do u mean by "is dhcp handing out:
msdcs.companyname.com ?"

Ketan
0
BarnyRitchleyCommented:
Firstly, before you do anything, you will need to make sure that the 2000 AD has been upgraded.  Even if DNS is a problem, you will still have to do this anyway, as you cannot promote a Windows 2003 server into a 2000 forest without doing the following:

Make sure that Windows 2000 Service Pack 2 or later is installed on all Windows 2000-based domain controllers.

Locate the server that is the schema master, and locate the server that is the infrastructure master.

Disconnect the schema master from the network.

On the schema master, insert the Windows Server 2003, Enterprise Edition Setup CD-ROM in the CD-ROM drive.

Open a command prompt on the schema master:

cd-rom:
cd \i386
adprep /forestprep

where cd-rom is the drive letter of the CD-ROM drive.

After the command is finished on the schema master, use the following methods to verify that the preparation of the forest was successful.

Verify that you received no error messages.

Run any domain controller diagnostic tools that are available (for example, Dcdiag). Keep in mind that replication errors are expected when the domain controller is disconnected from the network.

Use Event Viewer to inspect the system log for errors or unexpected events.

If you received no error messages when you ran the adprep /forestprep command, reconnect the schema master domain controller to the network.

If you received one or more error messages that provided instructions for additional steps when you ran the adprep /forestprep command, follow the error message instructions and then repeat the above.

If the adprep /forestprep command did not run successfully or if a diagnostic tool (for example, Dcdiag) revealed a significant problem, restore the schema master from backup and then use the information that you gathered earlier to troubleshoot the problem.

If the schema master is a different computer from the infrastructure master, wait for the changes made by the adprep /forestprep command to replicate from the schema master to the infrastructure master. Wait at least fifteen minutes, but allow longer (a half day to a full day) if the schema master is not located at the same site as the infrastructure master. If you try to perform the domain preparation on the infrastructure master before the changes are replicated, you receive an error message that states that more time is needed.

On the infrastructure master, insert the Windows Server 2003, Enterprise Edition Setup CD-ROM in the CD-ROM drive.

Open a command prompt on the infrastructure master, and then type the following lines:

cd-rom:
cd \i386
adprep /domainprep

After the command is finished on the infrastructure master, use the following methods to verify that the preparation of the forest was successful.

Verify that you received no error messages.
Run any domain controller diagnostic tools that are available.

Use Event Viewer to inspect the system log for errors or unexpected events.

Evaluate the information that you gathered: If adprep /domainprep ran without errors, carry on!

If you received no error messages when you ran the adprep /domainprep command, reconnect the schema master domain controller to the network.

If you received one or more error messages that provided instructions for additional steps when you ran the adprep /domainprep command, follow the error message instructions and then repeat teh above.
 
Wait for the changes made by the adprep /domainprep command to replicate from the infrastructure master to all other domain controllers. Wait at least fifteen minutes, but allow longer (a half day to a full day) if the network includes a domain controller in a remote site. If you try to upgrade one of the other domain controllers before the changes are replicated, you receive an error message that states that more time is needed.

Once the AD has been upgraded try to promote the 2K3 DC to the 2K AD forest.

Keep us posted on how you get on!



Hope this helps.

Kind Regards


Barny.


0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.