Re: WDGC PROBLEM IN MY DOMAIN CONTROLLER2

From: Brian Desmond [MVP] (desmondb_at_payton.cps.k12.il.us)
Date: 07/04/04

  • Next message: Brian Desmond [MVP]: "Re: Domain Controller redundancy" 
    Date: Sun, 4 Jul 2004 13:28:00 -0500

    You have a DNS issue here. Is the second box (problem one) pointed at the
    first box for DNS, and vice versa? That's step one to check.

    Next, do a dcdiag and a netdiag ont he boxes asn see what errors you come up
    with. 

    -- 
-- 
Brian Desmond
Windows Server MVP
desmondb@payton.cps.k12.il.us
http://www.briandesmond.com
"wASIM mASOUD" <waseem_masoud@hotmail.com> wrote in message
news:2faf01c460d4$873cab90$7d02280a@phx.gbl...
> My problem is that I have a LAN in my company consists of
> about 40 PCs and 6 servers, 2 of these servers are domain
> controllers using Windows 2000 server, we have only one
> domain called (GASCO.AL-AMERYA), the problem starts when I
> tried to access the first domain controller (gasco-server)
> from Network Neighborhood, I got "login failure: The
> target account name is incorrect" message although I'm
> administrator, when I unplugged the network UTP cable from
> the second domain controller (gasco-foxboro), I can access
> the first domain controller! I believe that there is no
> problem with the first domain controller; the problem
> exists in the second domain controller. I decided to make
> the second DC as a member server by using the command
> dcpromo and then I can make it again as a DC, during the
> process of removing the active directory from the server
> using dcpromo I got this message:
> "The operation failed because: Managging the network with
> gasco-server.gasco.al-amerya failed "login failure: The
> target account name is incorrect""
> And I  got another one:
> "Naming information cannot be located because: the target
> principal name in incorrect"
> Please, Inform me what to do - in details - as soon as
> possible
> Thank you very much
>
  • Next message: Brian Desmond [MVP]: "Re: Domain Controller redundancy"

    Relevant Pages

    • Issues migrating SBS 2003 domain to Server 2008 Standard
      ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
      (microsoft.public.windows.server.sbs)
    • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
      ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
      (microsoft.public.windows.server.sbs)
    • 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: Issues migrating SBS 2003 domain to Server 2008 Standard
      ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
      (microsoft.public.windows.server.sbs)
    • Re: Big trouble with DC in China
      ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
      (microsoft.public.windows.server.active_directory)