Windows 2003 domain can't ping host names in Windows 2000 domain

I have a Windows 2003 domain trying to ping hosts in a Windows 2000 domain (2 different forests) My goal is  talk to the old domain using non FQDN host names.  Do not want WINS.  I can ping successfully when using the FQDN.  I can also perform an nslookup using the non FQDN host name.  I can not ping and client machines in the new domain can not talk to applications servers in the old domain.   How do I talk to the old domain using non FQDN host names then?  Under Windows 2003 DNS we have configured Conditional Forwarding to the old domain.   Also  tried adding the old domain as a secondary forward lookup zone.  On the Windows 2000 DNS have a delegation record for the new domain.  Tried adding the new domain as a secondary zone on the old domain as well.  This is a migration that might take a while.  
rlmethodAsked:
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.

LauraEHunterMVPCommented:
If I understand you correctly, you have a 2003 forest (let's call it 2003.com) and a 2000 forest (let's call it 2000.com). From a machine in the 2003.com forest, you want to be able to ping server1.2000.com by simply issuing the command "ping server1"?  Have I understood your question correctly?

If so, you need to add "2000.com" to the DNS suffix search list of your clients in the 2003.com forest. You can do this via Group Policy under Administrative Templates\Network\DNS Client\DNS Suffix Search List .

What this will do is as follows:

[1] User types "ping server1"
[2] Workstation will first attempt to resolve "server1.2003.com", since 2003.com is the DNS suffix of the workstation itself.
[3] If server1.2003.com does not respond, workstation will then attempt to ping "server1.2000.com"

(You can see how having a "server1.2003.com" and a "server1.2000.com" would present inconsistent behaviour.  A WINS server would enforce uniqueness of these "single-label" names across both forests; if you do not wish to use WINS as you've stated, enforcing the uniqueness of these names will be something you will need to handle manually/procedurally.)

If I have misunderstood your question, please re-state and/or provide additional details so that I can attempt to help you resolve your issue.

Hope this helps.

Laura E. Hunter - Microsoft MVP: Windows Server - Networking
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
rlmethodAuthor Commented:
Well, just before you replied we did some more testing.  We are using the GPO to set the suffix search order and there is something wrong there.  We turned off the GPO and added the entries manually.  Now everything works.  LOL.  We'll take another look at the GPO next.  THANK YOU FOR YOUR REPLY!!
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
Windows Server 2003

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.