can't join a computer to domain when 2000 DC offine, while 2003 DC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We were having a single 2000 DC. I just added a 2003 DC to the domain few
days ago. Now I found if the 2000 DC offline, I can NOT join a workgroup PC
into domain, although the 2003 DC is online! The error msg is like "can not
contact domain controller, make sure the domain name is correct". But I can
ping 2003 DC by computer name and domain name. The 2003 DC is also WINS, DNS
server. And, I have changed the 2003 DC to be a global catalog server.

When I tried to demote this 2000 DC from domain, I also got alike msg "can't
contact domain controller", bla bla. I don't know where should I take a look.

Any idea of this?
 
jinshuang said:
We were having a single 2000 DC. I just added a 2003 DC to the domain few
days ago. Now I found if the 2000 DC offline, I can NOT join a workgroup
PC
into domain, although the 2003 DC is online! The error msg is like "can
not
contact domain controller, make sure the domain name is correct". But I
can
ping 2003 DC by computer name and domain name. The 2003 DC is also WINS,
DNS
server. And, I have changed the 2003 DC to be a global catalog server.
Click to expand...

Ok, DNS & GC is good. (All DCs as GC in single domain forests and at least
several or all DNS servers.)

Chances are you haven't added the NEW DNS (on the DC) Server to the
client machines NIC->IP properties or the equivalent DHCP Server options.
When I tried to demote this 2000 DC from domain, I also got alike msg
"can't
contact domain controller", bla bla. I don't know where should I take a
look.
Click to expand...

Same answer.

Other possibility is that you have two DNS servers but they are not
replicated,
either Primary/Secondary or as AD Integrated DNS servers which all have the
SAME data.
 
Herb Martin said:
Ok, DNS & GC is good. (All DCs as GC in single domain forests and at least
several or all DNS servers.)

Chances are you haven't added the NEW DNS (on the DC) Server to the
client machines NIC->IP properties or the equivalent DHCP Server options.
Click to expand...
The client use DHCP. I have DNS setup in DHCP server, and client get the
right DNS server IP. When I issue nslookup on client, I can get right domain
name IP addresses.
Same answer.

Other possibility is that you have two DNS servers but they are not
replicated,
either Primary/Secondary or as AD Integrated DNS servers which all have the
SAME data.
Click to expand...
Just have two DNS server, the 2003 and the 2000. They are replicated each
other, since there are no error in DNS event log.

Any other possibilities?
 
Got fixed! It is a ntfrs problem.

Herb Martin said:
Ok, DNS & GC is good. (All DCs as GC in single domain forests and at least
several or all DNS servers.)

Chances are you haven't added the NEW DNS (on the DC) Server to the
client machines NIC->IP properties or the equivalent DHCP Server options.


Same answer.

Other possibility is that you have two DNS servers but they are not
replicated,
either Primary/Secondary or as AD Integrated DNS servers which all have the
SAME data.
Click to expand...
 
jinshuang said:
The client use DHCP. I have DNS setup in DHCP server, and client get the
right DNS server IP. When I issue nslookup on client, I can get right
domain
name IP addresses.
Click to expand...
Just have two DNS server, the 2003 and the 2000. They are replicated each
other, since there are no error in DNS event log.
Click to expand...

Well, that doesn't prove they are replicated even if they are.

How are they organized? As Primary/Secodary or as an AD-Integrated Set
Any other possibilities?
Click to expand...

As I wrote the first time, perhaps clients don't have both DNS servers
configured in
NIC->IP properties.

After that firewalls, filters, routing, hardware problems all of which are
less likely
than the first two ideas I gave you.
 
Herb Martin said:
What do you mean by that?

How did this affect the logon?

Were the DCs not replicated?
Click to expand...

The 2003 didn't become a real DC, because the SYSVOL SHARE wasn't replicated
from 2000; The 2003 ntfrs failed becasue the 2000 ntfrs failed; The 2000
ntfrs failed becasue there were no enough space on system drive.
 
Back
Top