Re: Not able to create user/ group accounts in Exchange server

From: kamesh_a (kamesh_a_at_hotmail.com)
Date: 04/14/04 

Date: Tue, 13 Apr 2004 22:48:11 -0700

Hi Leif,

There are no more domains other than this ABC. It is a
small keyboad error.

I am still maintaining the old copy of initial domain
configuration in offline. I connected that hard disk and
tried to see the exchange problem. But no use.

The actual Domain moving Phase as gone like this.
Stage1:
Installed win2k on new hardware (DELL) server along with
DNS and executed dcpromo and then moved roles from
operations master of RID, PDC,Infrastructure from the
initially configured domain contoller to this new DELL
server.

stage2: executed DCPROMO on the firstly configured domain
controller and demoted. Uninstalled DNS from this server
and disconnected this harddisk and kept in a safe place.
Still OS remain.

After this, problems are started like

1. Existing domain controller log is showing that valid dns
not able to create any user / group accounts in this
Machine is a PDC of the domain at the root of the forest.
Configure to sync from External time source using the net
command, 'net time /setsntp:<server name>'.

2.Dynamic registration or deregistration of one or more
DNS records failed because no DNS servers are available.

3.The DNS server was unable to complete directory service
enumeration of zone .. This DNS server is configured to
use information obtained from Active Directory for this
zone and is unable to load the zone without it. Check
that the Active Directory is functioning properly and
repeat enumeration of the zone. The event data contains
the error.

The File Replication Service is having trouble enabling
replication from SERVER3 to SERVER1 for
c:\ads\sysvol\domain using the DNS name server3.abc. FRS
will keep retrying.
 Following are some of the reasons you would see this
warning.
 
 [1] FRS can not correctly resolve the DNS name
SERVER3.ABC from this computer.
 [2] FRS is not running on server3.abc.
 [3] The topology information in the Active Directory for
this replica has not yet replicated to all the Domain
Controllers.

It looks that DNS is not configured and even Active
directory.

Can you guide me What is the best way in solving this with
the existing resources.

Thank for the support
Kamesh

>Looks like you have some stalled trust relationships in
your AD (between ABC
>and Vempower?), and hence problems when replicating
Global Catalog, or maybe
>there is no Global Catalog server at all. Your Exchange
server perhaps was
>having problem when trying to connect to Global Catalog
server, not just to
>a DC.
>
>Since you said you deleted the initially configured
domain controller
>(SERVER), you might have deleted also some FSMO roles
and/or Global Catalog.
>
>Have you deleted the initial DC gracefully? (first demote
it from domain
>controllers and remove from domain, only then kill the
OS).
>
>Check if you have some non-responding trusts and
troubleshoot them if any.
>
>If my guess is right - there are quite a few detailed MS
KB articles on how
>to seize the FSMO and GC roles in case the original role
owner is dead.

>Good luck,
>Boris

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: how do i move primary DC from one machine to another
    ... Test omitted by user request: DNS ... Connecting to directory service on server WIN2003DC. ... Replication Site Latency Check ...
    (microsoft.public.windows.server.general)
  • Re: error 8254 DNS Lookup failure
    ... FYI, I repointed the DNS to one server, deleted the contents of _MSDCS ... > in the same site, Replication has been fine up until yesterday, the ... > Starting test: CrossRefValidation ...
    (microsoft.public.win2000.dns)
  • Re: WINS and DNS issue
    ... When I said the that DNS server is configured to to replicate to all other ... Ive had a look at the options under replication, ... It says to set this if you want a 2000 server to load the zone. ...
    (microsoft.public.win2000.dns)