We have a 2003 domain and currently everything is in the Default-First-Site-Name site.
This includes the local domain controllers as well as the ones located miles away connected by WAN. The default first site contains not only my DC's but other child domain DC's as well. Due to bandwidth it is time to start breaking things up. At the moment there are no subnets defined and everything works. I attempted to create a site first for a remote location (created the site, the subnet and moved that locations DC into it) and right after I get this message on my local DC's- None of the IP addresses (x.x.x.x) of this Domain Controller map to the configured site 'Default-First-Site-Name' It seemed once I defined a subnet for the remote site, the servers in the default-first-site lost their minds. I moved the DC back to Default first site, deleted the remote site and subnet I had created and everything went back to normal. If I associate a subnet for a new site, do i then have to create a subnet for everything still in default first site? I thought that by creating a unique site and associating a subnet for it that it would only affect clients in that subnet and make them use that local DC. I have read many "how to's" to do this and it seemed straight forward but I was not expecting this to happen.