Computer Account not found on Domain

When logging-in to the Domain from one of our Windows 2003 servers, authenication fails with a message suggesting the computer account is not found. We can login locally OK but not to the Domain. When the login prompt is displayed, we can unplug the network cable, hit enter to login, and plug-in the network cable after Windows starts. We can then see all shared drives on the other servers.

This problem first occurred after rebuilding one of the two mirrored hard drives in the server. Before that, all was well.

This is only a problem with one Win2003 server; all other machines are communicating as expected. Pings work to and from all machines. Net View shows the computer name. Should the server be shut-down before I delete the computer name from AD? What's the proper way to delete the computer name from AD and then later add the same computer name to AD?
BranlonAsked:
Who is Participating?
 
PberConnect With a Mentor Solutions ArchitectCommented:
You are not changing the machine name you are just re-adding it to the domain.  The computer name will remain the same.

Can you ping your domain name?
i.e.
ping domain.com
0
 
PberSolutions ArchitectCommented:
You can just simply delete it from AD and then just remove/add it do the domain.

Have you tried doing a netdom /veryfy or a netdom /resetpwd?
0
 
PberSolutions ArchitectCommented:
woops that should have been.


Have you tried doing a netdom /verify or a netdom /resetpwd?
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
BranlonAuthor Commented:
"netdom verify" fails with "RPC server is unavailable". Remember, this problem server is running Voice Mail services which rely on a fixed machine name. Changing the server's name will have adverse effects.
0
 
BranlonAuthor Commented:
Pinging the IP of the Domain works but not the DomainName. The trust relationship test fails. So, if I just delete the computer name from AD and then add it back in, with the "problem server" up and running, the authenication problem at login will be solved and the trust relationship fixed?
0
 
PberSolutions ArchitectCommented:
I think you have some DNS issues.  On the server I would confirm that your DNS settings for the TCP/IP client are correctly pointing to the AD domain controllers.  I presume your AD domain controllers are hosting DNS.
0
 
BranlonAuthor Commented:
NetDiag and IPConfig confirm IP settings OK. Yes, AD domain controller is hosting DNS. Like you said, maybe Deleting and Adding the computer name will work. I'll try it later today when all the passengers get off.
0
 
prashsaxCommented:
If it is a member server and not a domain controller.

Then you can safely rejoin it to the domain.

If you want, you also do not need to delete the account from the AD.

The account will be overwritten as soon as you rejoin the server with same name.

For sure, you secure channel has become corrupt and machine account is not valid.

Just bring the server in the workgroup. Let the server restart.

Then, login to server as local admin.

Rejoin it to the domain using domain admin account.(Delegated account with permission to add to domain will not work, as server account still exists in the AD.)

Restart the server again, and login to the domain.


0
 
BranlonAuthor Commented:
In the process of adding a new computer to AD, it wants to know if the computer is managed. My gut feeling is "Yes it's managed, what computer isn't ?" But it may be asking about the HW switch? Can I just give it some unique GUID? I don't have any non-Microsoft third-party software here that manages computers or cares about GUIDs. Maybe I can just declare it non-managed and move on.
0
 
PberSolutions ArchitectCommented:
Yes you can say it is non-managed.  You can also add that information later by right clicking the computer object and selecting properties and selecting the Managed By tab.
0
 
BranlonAuthor Commented:
OK, I'll start the process in about two hours and post an update here. Thanks
0
 
BranlonAuthor Commented:
Deleted and added the computer name in AD and shut-down the problem server. Now logged-in locally as Administrator cannot change the server to workgroup using Computer properties. How and from where do I un-join the server from the domain?
0
 
BranlonAuthor Commented:
OK, got ahead of myself. The server is now re-joined properly and the authenication works as expected. Thanks for your help.
0
 
PberSolutions ArchitectCommented:
Good to hear
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.