Good evening everyone,
I had a question of a possible solution.
Scenario:
Created a new AD/DC server.
Server crashed over weekend; no backups were made yet.
Obtained a new server.
New server had same settings as old server: domain name, computer name, ip settings, shares...etc.
After upgrade server to DC, cannot get computers to login. Cannot locate domain message.
Once again, all dns addresses on client machines point to the server, same domain name, same ip settings, same computer name, etc.
I was wondering if this issue can be solved by forcing replication?
I tried flushing the dns on client pc's, modifying the lmhost file to point ip address to server. The only way I found to correct this issue was to disconnect from the domain and reconnect to the domain.
I was thinking that there is a guid involved with the server that the clients store.
Any help will be appreciated thanks.
I had a question of a possible solution.
Scenario:
Created a new AD/DC server.
Server crashed over weekend; no backups were made yet.
Obtained a new server.
New server had same settings as old server: domain name, computer name, ip settings, shares...etc.
After upgrade server to DC, cannot get computers to login. Cannot locate domain message.
Once again, all dns addresses on client machines point to the server, same domain name, same ip settings, same computer name, etc.
I was wondering if this issue can be solved by forcing replication?
I tried flushing the dns on client pc's, modifying the lmhost file to point ip address to server. The only way I found to correct this issue was to disconnect from the domain and reconnect to the domain.
I was thinking that there is a guid involved with the server that the clients store.
Any help will be appreciated thanks.