DNS/Active Directory just died

Posted on 2004-11-10
Last Modified: 2012-05-05
Heres the situation - a brand-new server, brand new W2k3 server install w/ Exchange 2003. Server install goes flawlessly, we being joining PCs to the domain.  One of my techs come to the 2nd machine, tries to add it and fails. It turns out the PC had the same computer name as the server. All other workstations that we have tried to join are now unable to do so.

Error message on PCs:
Logon failure: the target account name is incorrect.

Server event log reports that DNS and active directory are now failing.

Unfortunately, this is all the information I have right now. i don't have remote access to this server until tomorrow.

Any directions you folks can offer would be appreciated.
Question by:sadasupport
    LVL 16

    Assisted Solution

    DNS and active directory failing is quite a broad description...
    Is the DNS service running?
    Active directory relies heavily on DNS.
    So DNS settings have to be correct first.

    ON the server right click my network places icon on the desktop.
    Right click on the local area connection
    select properties
    double click TCP/IP settings.
    Make sure you are using a static IP.
    Remove all references to DNS and WINS servers
    (We are sorting DNS communication first)

    Do the same for the other adapters installed.
    Only set the default gateway on the adapter used for external communication.

    To resolve external hosts, use forwarders in the DNS server settings.

    -Logon failure: the target account name is incorrect.
    I normally encounter this error when the PC needs to be rejoined to the domain
    To do this right click my computer icon on the desktop
    and select properties
    Select the computer name tab
    select change

    Select member of workgroup
    and enter your domain name.
    enter the local adminstrator account and  password
    click ok.

    Go to the server and delete the computer name from active directory.

    On the workstation
    Click on change again
    and select member of domain
    enter your domain name
    login with the domain administrators account and password
    LVL 3

    Assisted Solution

    Turn off the PC.
    Reboot the server.

    If u turn on the PC, make sure it has the network cable disconnected first.

    Then change it's name, shutdown, connect the cable and restart.
    Then rejoin the domain as per Nyaema above.

    LVL 1

    Author Comment

    The problem is not on the workstations any longer. I can easily change the workstation computer names. My issue is that Active Directory is not working on the server. Computers that were sucessfuly joined to the domain prior to the problem can no longer find the domain, and therefor, cannot log in. The DNS service is still running. I might try reinstalling DNS.
    LVL 1

    Accepted Solution

    As you say, I think you should try re-installing DNS on the server.  Do you have any other AD servers on site or is it only this one?
    LVL 1

    Author Comment

    It was only the one server - Reinstalling DNS fixed one problem, but created another. We were 6 problems deep until we decided to re-image the server with a god backup from the night before and restore the data. To much time would have been spent fixing what was broke.

    A good rule of thumb, make sure you odn't add PCs to the domain that have the same name as the DC.

    thanks anyways folks.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Mapping Drives using Group policy preferences Are you still using old scripts to map your network drives if so this article will show you how to get away for old scripts and move toward Group Policy Preference for mapping them. First things f…
    Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
    This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

    755 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    24 Experts available now in Live!

    Get 1:1 Help Now