Unable to Join Domain from Client PC

30 pts.
Tags:
Active Directory
Active Directory Domain
Windows Server 2000
Windows Server configuration
I have configured AD in Windows Server 2000. Then directly created a User/Group in Loacladmin.in Consol. So far everything is fine. But when I joined the domain users from Client computer, it's showing the following message. “The Join Operation was not successfully. This could be because an existing computer having name “XXXXXXX” was previously created using a different set of credentials. Use a different computer name or contact your administrator to remove any stale conflicting account. To the error was Access is denied” Please help me. How can I join the domain users and groups?

Software/Hardware used:
Bothe S/W & H/w

Answer Wiki

Thanks. We'll let you know when a new response is added.

Go to Active Directory then Computers. Find the computer “XXXXXXX” and delete it.
Join the computer again to the domain.

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • carlosdl
    Did you try the suggestions from the error message ? Have you checked if a computer account with that name already exists in the domain ? What troubleshooting have you done so far ?
    68,430 pointsBadges:
    report
  • Tchin
    Is this happening to specific pc's or all pc's? if its only specific ones, have you tried rejoining these machines to the domain? On the client machine, put them into a workgroup > reboot > and then rejoin.
    180 pointsBadges:
    report
  • Sreenivashan
    Yes sir, once I re name the Comptuer name. after that it showing as A directory does not exsit.
    30 pointsBadges:
    report
  • Pjb0222
    You can script your join. Just depends on the level of automation you need. You just need to take into account name collisions on rebuilds.
    netdom join %COMPUTERNAME% /domain:[Domain] /userd:[DMID] /passwordd:([DMPW] | *) /ou:[OU_String],[DC_String]
    IF %ErrorLevel% EQU 2224 (
        Echo Collided with existing account
        GOTO :Rejoin
        )
    IF %ErrorLevel% EQU 2691 (
        Echo Collided with existing account
        GOTO :Rejoin
        )
    IF ErrorLevel 1 (
        ECHO FAILED to join domain
        GOTO :FAIL
        )
    IF %ErrorLevel% EQU 0 ECHO Success
    GOTO :Done
    
    :Rejoin
    cmd /c netdom join %COMPUTERNAME% /domain:[Domain] /userd:[DMID] /passwordd:([DMPW] | *)
    IF ErrorLevel 1 (
        ECHO FAILED to join domain
        GOTO :FAIL
        )
    dsquery computer domainroot -d [Domain] -U [DMID] -P ([DMPW], *) -name %ComputerName%|dsmove -d %JoinWorkgroup% -newparent "[OU_String],[DC_String]" -U [DMID] -P ([DMPW] | *)
    IF ErrorLevel 1 (
        ECHO FAILED moving object
        GOTO :FAIL
        )
    ECHO Success
    GOTo :DONE
    
    :FAIL
    ECHO Failed to add computer to domain and place object in correct OU.
    GOTO :DONE
    
    
    :DONE
    
    OU_String = OU string breakout. DC_String = Domain Name string. i.e. DC=Lvl2,DC=Lvl1,DC=Lvl0 You can use the DSQuery above on a system to see how this breaks out for your domain i.e.
    "CN=[Computer],OU=Level3,OU=Laptop,OU=computerss,DC=dmn2,DC=dmn2,DC=com"
    3,310 pointsBadges:
    report
  • Voodooclanboy
    It happens generally when it is unable to correctly resolve the name of the domain controller in a timely fashion. Mentioned Below is a list of common reasons for the same. In an SBS domain the server should be the DHCP server, and if so, items 2 and 3 below should be automatically set through DHCP. However if addressing is statically assigned or you are using a router you may need to make changes. Items 2 and 3 are also basic networking requirements of a Windows Domain, not just important for joining the domain. 1. If there is more than 1 network adapter installed , wired or wireless, disable all but 1, preferably wired, until after joined to the domain 2. Make sure, using IPconfig /all, that the client's DNS points ONLY to your internal DNS servers, in this case the SBS. Do not allow a router or ISP to be added as an alternate. 3. IPconfig /all should also show next to “Connection-specific DNS Suffix” your internal domain suffix (MyDomain.local). If not you need to add the domain suffix to the client machine. To do so insert it in the "DNS suffix for this connection" box under the DNS tab of the NIC's advanced TCP/IP IPv4 properties 4. If there are any 3rd party firewalls or security suites installed, disable them until joined to the domain 5. If still failing add the connect web site to the “trusted” sites list in Internet Explorer under Internet options / security 6. On a few occasions Bluetooth accessories such as keyboards and mice have been known to interfere with the connect wizards. If necessary temporarily replace these with wired devices until domain joined. hope this would work. Thank you Anil Lepide softwares
    1,140 pointsBadges:
    report
  • Charlie8max
    There is some really good stuff on this page
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following