Unable to add W2K Pro station to AD

  • Thread starter Thread starter John Morgus
  • Start date Start date
J

John Morgus

After rebuilding the only server in the Active Directory,
removing the workstations from the old AD (the server
died) and rebooting, I am unable to add a Windows 2000
Pro workstation to the new AD. It generates a DNS
error. I can't access the internet either - again DNS
resolution.

This machine was working before the old server died. No
changes were made to the workstation. Other workstations
(all W2K Pro except 1 XP Home) have joined the AD.

This workstation can PING and even attach to the server,
but does not access the DNS to join the AD.

I have not yet run the OS Repair from the CD, that is my
next idea unless there is a simpler solution.
 
You can't join a Windows XP Home to an domain.

use nslookup to troubleshoot name resolution.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
 
Make sure that the clients are getting the correct Lease Options ( 003, 006
and 015 normally ) from the DHCP Server in your Domain. The workstations
will need the correct DNS information in order to contact the correct SRV
records. Please take a look at the following two MSKB Articles:

http://support.microsoft.com/?id=810076
http://support.microsoft.com/?id=314861

And, as Chriss stated, you can not join WINXP Home version to a
domain.....You need WINXP Pro.

HTH,

Cary
 
Interestingly, the XP Home **DID** join the domain, it is
a Windows 2000 Pro that's not joining. There is no DHCP
going on and all addresses are static.
 
John,

How in the world did you get XP Home to join the domain? If you go to My
Computer, right click it and go to the Computer Name tab what does it show
you there? I am asking because if you are using a local user account that
is the same as a domain user account - and the password is the same for
both - then you will have access to a lot of things. it can kinda trick
you.

In any event, I would check to make sure that the DNS information is correct
( meaning, that in your TCP/IP configuration you have only your internal DNS
Server(s) IP Address(es) and -N * O * T - your ISP's....

HTH,

Cary
 
I think that's what happened -- the end user also went
out and got a retail XP Pro and put on the only XP system
(the one I thought was Home).

I ran the Windows 2000 OS Repair (boot to CD, continue as
if you were installing, let it find the Windows 2000
install and press R). All the systems on the domain use
the local DNS server as their Primary DNS. They have the
ISP as alternates. If they don't, they can't access the
internet. I'm checking their system tonight, to see if
they have an addressing issue - the repair finished, but
the office manager thinks she didn't set something up
correctly.
 
John,

S T O P!!!!!

Do not - as I indicated in my first post - have anything other than your
local DNS Server information in your TCP/IP configuration settings. Period!

You need to fix this problem and fix it quickly. What do you mean if they
do not have the ISP information as the secondary then they can not access
the Internet? Open up the DNS MMC and look to see if there is a "." zone.
If there is, delete it. In a few moments you will be able to enter the IP
Address(es) of your ISP's DNS Server(s) in the Forwarders tab. Also, the
Root Hints will become available.

HTH,

Cary
 
Back
Top