Windows XP and 2000 DNS

[Ryan Tremblay]

I have a 2000 Server running DNS. I also had another machine running the
Server 2003 beta. I demoted the 2003 beta server back down to a member
server so I can install the 180 day trial of it (instead of beta) then my XP
machine would take 5-10 minutes to log on because of it can't find its
computer name. So I reinstalled DNS, restarted it on the 2000 DC but didn't
help. So I formatted the 2000 machine (tried demoting it and reinstall AD
but then had problems with DNS with AD) I set the option in the forward
lookup zone to yes for dymanic update (so it will register itself) I
rejoined the XP machine to the domain it still didn't register itself in the
DNS. I have another 2000 Pro machine that I didn't disjoin from the old
domain and I noticed it registered itself in the DNS. I also joined my 2003
server to it and it will not register itself in the DNS I want it to be the
secondary zone but it won't even transfer zones from the master. I am
puzzled any help would be appreciated. The 2000 server is running SP4 if
that info is helpful. Thanks

 

[Steve Duff [MVP]]

I would have to guess that your workstation isn't receiving the
correct primary zone name from DHCP, or the correct IP
for the DNS server. The first things to do are to release
from DHCP, and check the error log on the workstation
and server, and do IPCONFIG/ALL on the workstation to
see where the problem might lie.

A workstation does not have to be joined to a domain
to self-register in DNS, provided you have the dynamic
updates setting set to "YES" (and not secure-only). There
are only a few things that could cause it not to, and all
of them I can think of are found in the workstation TCP
IP settings and/or DHCP if you are using that.

Steve Duff, MCSE
Ergodic Systems, Inc.