DisableStrictNameChecking CNAME Alias etc 1

[peterlyttle]

Hello,

I was hoping someone could help me out with this one. I have "ServerA" that replicates a folder share to "ServerB"

Clients are pointing at "ServerA" without changing clients/scripts etc I would like "ServerA" to point at "ServerB" for a DR test I am doing (in a real test I would update DNS A records etc.)

But I am confronted with a message "Logon failure: The target account name is incorrect." I have added the DisableStrictNameChecking=1 value and rebooted the server (creating a different CNAME works)

The clients have a host file that looks like so -

127.0.0.1 localhost
10.20.30.41 ServerA

*note 10.20.30.41 is the IP address for "ServerB" I would like to keep "ServerA" online and dont want to remove the account from AD as I need to bring it back up later this weekend.

Any help much appreciated!

Pete

 

[peterlyttle]

We managed to come up with a workaround for this even though a little long winded.

Setup a new DNS server and add A-Records for the DR servers then set it to forward all other DNS requests it doesnt know about to your main DNS servers. Then on the DR server themselves change the DNS servers to point at the new DR DNS Server.

Obviously in a real DR test the real A-Records would be updated but this wasnt an option.