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 ?

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.

Yes sir, once I re name the Comptuer name. after that it showing as A directory does not exsit.

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  one

: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  ONE

:FAIL
ECHO Failed to add computer to domain and place object in correct OU.
GOTO  ONE


  ONE

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"

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

There is some really good stuff on this page