Re: dcdiag




--
Ted Katz MCP ECNE
Moorestown NJ



"chriss3 [MVP]" wrote:

Hello,
Can you provide us with the information about how you transfered the DC from
the out dated hardware to your new hardware?

1. backedup old server data
2. Ran dcpromo and removed the DC fron server (still had dc01a with GC)
3. changed IP address of old server
4. removed wins and dns from old server.
5. Changed IP address and name of new server to old address and name
6. added DC to newserver
7. marked new server to have GC
8. added dns and wins (need wins for ERP app)
At this time I tested access to data from vaious station accross the network
and sent and recieved local mail and mail for out side of our domain.



Did you took the following steps?
http://support.microsoft.com/default.aspx?scid=kb;en-us;263532

--
Regards
Christoffer Andersson, TrueSec
Executive Consultant
Microsoft MVP - Directory Services
----------------------------------------------------------------
http://www.chrisse.se - Active Directory Resources

"Theojkat" <Theojkat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:967B3046-A89C-4FE7-8D3D-D8DE2FEE791F@xxxxxxxxxxxxxxxx
About 2 weeks ago I upgrade a win 2003 server to new hardware. This system
"NT1" was a DC. Set the new server up with same name and ip address.

All look good until I found an error in the app viewer on exchange. after
a
lot of sserching for that erro and getting no real answer I ran dcdiag on
the
new server (the second server DC01A is also a dc both contain the GC).

I get errors from the test NT1 DC fails the advertising test.
Starting test: Advertising
Warning: DsGetDcName returned information for
\\dc01a.formation.com, when we were trying to reach NT1.
Server is not responding or is not considered suitable.
[DC01A] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Server NT1 is advertising as a global catalog, but
it could not be verified that the server thought it was a GC.
......................... NT1 failed test Advertising

In addition
Starting test: KnowsOfRoleHolders
Warning: DC01A is the Schema Owner, but is not responding to DS
RPC
Bind.
Warning: DC01A is the Schema Owner, but is not responding to LDAP
Bind.
Warning: DC01A is the Domain Owner, but is not responding to DS
RPC
Bind.
Warning: DC01A is the Domain Owner, but is not responding to LDAP
Bind.
Warning: DC01A is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: DC01A is the PDC Owner, but is not responding to LDAP
Bind.
Warning: DC01A is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: DC01A is the Rid Owner, but is not responding to LDAP
Bind.
Warning: DC01A is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: DC01A is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
......................... NT1 failed test KnowsOfRoleHolders

I have chaeck DNS from one end to another and do not see any problems.

I am at a lost as to where to look now....???
BTW Exchange works fine except for the error log entries and the network
its
self is functioning whit out error..
--
Ted Katz MCP ECNE
Moorestown NJ



.



Relevant Pages

  • Re: dcdiag
    ... new server (the second server DC01A is also a dc both contain the GC). ... Warning: DC01A is the Schema Owner, but is not responding to DS ... DC01A is the Schema Owner, but is not responding to LDAP ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag
    ... new server (the second server DC01A is also a dc both contain the GC). ... Warning: DC01A is the Schema Owner, but is not responding to DS RPC ...
    (microsoft.public.windows.server.active_directory)
  • urgent: Second win2003 domain controller doesnt process login requests
    ... DCDIAG run on secondary server shows: ... Warning: DC is the Schema Owner, but is not responding to DS ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: RPC Server is Unavailable
    ... The RPC server is unavailable.. ... Warning: AMSDC1-S-03012 is the Schema Owner, ... responding to DS RPC Bind. ...
    (microsoft.public.windows.server.dns)
  • Re: DC cannot boot unless connected to SBS
    ... NEW-SERVER is also looking 1st to SBS for DNS. ... The purpose of this server is to store data for an offsite fundraising ... UDP port 53 responding to queries: ... Warning: SBS-SERVER is the Schema Owner, ...
    (microsoft.public.windows.server.sbs)