Windows 2003 R2 - Time Changed
Hello Experts,
While I was adjusting the time manually on my Domain Controller, it somehow accidentally changed he date to Decemeber 2011. I changed it back and the date is correct although there are many things not working correct. My file server is now not accessible for user shares. I removed the Member Server from the domain and tried to rejoin and get this error:
Computer Name Changes
The following error occurred attempting to join the domain <domain name>
Logon Failure: The taget account name is incorrect
I need to get my shares accessible again and don't know what to do. Can anyone HELP?!!!
Thanks!
While I was adjusting the time manually on my Domain Controller, it somehow accidentally changed he date to Decemeber 2011. I changed it back and the date is correct although there are many things not working correct. My file server is now not accessible for user shares. I removed the Member Server from the domain and tried to rejoin and get this error:
Computer Name Changes
The following error occurred attempting to join the domain <domain name>
Logon Failure: The taget account name is incorrect
I need to get my shares accessible again and don't know what to do. Can anyone HELP?!!!
Thanks!
Miguel Angel Perez Muñoz
Search on Active Directory users and computers OLD fileserver machine account and delete it. Check that time is correct in fileserver. Then, rejoin to domain.
You will have to wait until the database is completely replicated/updated
Sorry wrong post
As mentioned by Drashiel please delete it manually from AD.
Then try to add
As mentioned by Drashiel please delete it manually from AD.
Then try to add
ASKER
Now I noticed that the branch office DNS server is not working properly. I opened up DNS mmc and the server is not able contact it. I tried to uninstall and reinstall. It is complaining that it cannot contact AD.
ASKER
I can connect using the branch office IP address but not by FQDN.
Error:
The new server cannot be added because there is already a server by this name. Verify that the server name was entered correctly or choose a new server name.
Error:
The new server cannot be added because there is already a server by this name. Verify that the server name was entered correctly or choose a new server name.
Check time on this machines. If difference between clocks (DC and destination server) is more than 10 minutes may have auth problems
Then, on affected servers run this command: ipconfig /registerdns
This force renew DNS entry on your DNS servers. Apply on affected machines.
This force renew DNS entry on your DNS servers. Apply on affected machines.
ASKER
Tried to register dns, it is now saying that my branch domain controller is unable to replicated AD because "Remote system is not available."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was a AD replication problem. Thanks for leading me in the right direction.