Hi, I have a Domain Controller that was located in a different AD site (site2) via its IP (naturally!). This DC was shut down about 2 weeks ago. I have since powered it back up offnet, given it a new IP (which is defined as a different site (site1)), and rebooted it on net. Some hours later, it still seems to think it is in the original site (site2), at least that is what I see in AD Sites and Services.
Some minutes later...based on some googled and eventide.net info, I put in a specific subnet entry in ADSS for this new IP and associated it with site1. A reboot produced no change. So then I went to AD Sites and Services and did a GUI move of this DC from site2 to site1. Another reboot - no change. I see the dynamically created netlogon.dns file STILL has site2 identified! Any hints on how to "convince" this DC that it should be in site1? Anybody else experience this type of behavior? TIA! Mike Thommes List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
