Client cannot be managed on DC

Posted on 2009-04-16
Last Modified: 2012-05-06

I get following error on my SBS2003 when i try to manage a pc on the domain "Computer \\clientPC cannot be managed. the network path was not found.   choose 'connect to another computer' from the action menu to manage a different computer."

I can ping and RDP is working fine..

It's only on that one pc, the rest of them works fine..

does anyone know how I can resolve this?

I noticed that there was no A record in the dns, refering to the pc.
after inserting this record in the dns i get following error:
"Computer \\clientPC cannot be managed. you were not connected because a duplicate name exists on the network.  choose 'connect to another computer' from the action menu to manage a different computer."
i checked the pc names they look all fine..

any idea?

Question by:techneitsolutions
    LVL 3

    Expert Comment

    Firewall on the PC?
    LVL 8

    Expert Comment

    by:Frank McCourry
    I've seen this happen when a computer is formatted and reloaded then added back to the domain without resetting the computer account in active directory.  The computer has the same name and appears to connect to the domain, however the problem is that after the reload the computer generates a new SID (Security IDentifier).  Because the Old SID was never cleared in active directory, the new and old SID's do not match, therefore Active directory assumes that 2 computers with the same name exists, meanwhile, you only see one.

    The fix for this is to remove the computer from the domain, then delete the computer object from active directory, force replication (or wait 15 minutes) and then add the computer back to the domain.  I usually rename the comupter before adding it back to the domain, just to be sure.  Sometimes that is not an option, especially if other computers have mapped shares to that computers name.


    Author Comment

    It's not the firewall

    and we already try to move the pc out of the domain, changing his name, rejoin the domain, but the problem is not resolved.

    any suggestions?
    LVL 8

    Accepted Solution

    Make a hardware change after deleting it from the domain and renaming it.  If your network card is replaceable, I would try that first.

    Author Comment

    formatted the workstation and rejoin the domain

    Author Closing Comment

    tried this but no positive result, thx anyways

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    I work for a company that primarily works with small businesses as their outsourced IT vendor. As such the majority of these customers utilize some version of Small Business Server. Due to the economics of running a small business, many of these cus…
    Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
    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 to another domain controller. Log onto the new domain controller with a user account t…
    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 …

    734 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

    19 Experts available now in Live!

    Get 1:1 Help Now