AD courpt?

  • Thread starter Thread starter IkkI
  • Start date Start date
I

IkkI

Dear All,


I take a job to repair AD.
there is network......
last IT staff setup that win 2k and win 2k8...to transfer domain
controller...however.. it fail and can not communicate each other.....
then he setup win2k3.....
the problem is that win2k and win2k8 can not talk with each other....
I need to create user twice on win 2k and win2k8......
win2k8 can not seize any role......

I would like to know how to solve it without re-create domain?
 
Hello IkkI,

You are mixing a bit with the OS versions. Please describe in detail what
you have now up and running, amount of DCs, how they are located and what
is crashed. Also describe the kind of backup that is made from the borken
domain.

Also add the output files from the support tools:
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
netdiag /v >c:\netdiag.txt [from each DC, netdiag may work but isn't supported
with Windows server 2008 and higher]
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt (if more then
one DC exists)
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
Howdie!

Am 12.08.2010 03:48, schrieb IkkI:
I take a job to repair AD.
there is network......
last IT staff setup that win 2k and win 2k8...to transfer domain
controller...however.. it fail and can not communicate each other.....
then he setup win2k3.....
the problem is that win2k and win2k8 can not talk with each other....
I need to create user twice on win 2k and win2k8......
win2k8 can not seize any role......

Seriously, you need some professional help that gets you out of this
mess of a domain. Creating users twice is _not_ going to help. You're
just creating two different users. The problems you have are, as you
correctly noticed, connection problems. So you need to find the cause.
Is network connectivity given? Can you actually ping the machine from
one another? Is name resultion working and DNS setup well? DNS is
_vital_ for AD to work, so make sure you have that straight. Once
connectivity is given, I'm sure things straighten out and replication is
kicking in.

Cheers,
Florian
 
They can ping each other....
DNS setup well already on windows 2k...but I can not open it on win2k8
though role is add already...
 
I need to think think what u say as it seem difficult for me....

Meinolf Weber said:
Hello IkkI,

You are mixing a bit with the OS versions. Please describe in detail what
you have now up and running, amount of DCs, how they are located and what
is crashed. Also describe the kind of backup that is made from the borken
domain.

Also add the output files from the support tools:
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
netdiag /v >c:\netdiag.txt [from each DC, netdiag may work but isn't
supported with Windows server 2008 and higher] repadmin /showrepl dc*
/verbose /all /intersite >c:\repl.txt (if more then one DC exists)
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Dear All,

I take a job to repair AD.
there is network......
last IT staff setup that win 2k and win 2k8...to transfer domain
controller...however.. it fail and can not communicate each other.....
then he setup win2k3.....
the problem is that win2k and win2k8 can not talk with each other....
I need to create user twice on win 2k and win2k8......
win2k8 can not seize any role......
I would like to know how to solve it without re-create domain?
 
The DNS server encountered error 13 attempting to load zone domain.local
from Active Directory. The DNS server will attempt to load this zone again
on the next timeout cycle. This can be caused by high Active Directory load
and may be a transient condition.


it seem that error, but user need this dns server to access internet....
 
Howdie!

Am 13.08.2010 04:41, schrieb IkkI:
The DNS server encountered error 13 attempting to load zone domain.local
from Active Directory. The DNS server will attempt to load this zone
again on the next timeout cycle. This can be caused by high Active
Directory load and may be a transient condition.

So is that the error message you get, when you open the DNS console on
the 2008 box? What is its DNS configuration? Does it have itself as a
DNS server and the 2000 box as an additional DNS server?

Cheers,
Florian
 
as b4,win 2k install 1st with DNS....and then install window 2008 installed

I think DNS server of win2k is installed 1st...then dns of 2008
installed....
Next,win 2008 dns can not function well on AD,however, all ppl access dns of
2008 to access internet....but I can not open it on win 2008....


I just start this work and find it is terrible...
 
Back
Top