"tkutil" <> wrote in message
news:F992F4C3-779F-44BE-83F3-...
>I have 4 sites with the repective controllers in each site. I have 4
>subnets,
> one for each site. I have a site link for site1 to site2, site1, site3,
> and
> site 1 to site4.
>
> I created the controllers on the network at my location and I believe
> added
> them to the sites at that time. I shipped them to the remote sites and
> changed the IP address for that site. Did I do anything wrong in this
> process.
>
> The other thing that troubles me is the subnet. I used 10.100.x.x/21 to
> cover the ip ranges 0 - 7 at each location. example 10.100.0.0/255255248.0
> Is it OK to do that or do I need to specify subnets 10.100.0.x/24,
> 10.100.1.x/24,...
>
>
The IP subnet block of an IP subnet ID of 10.100.0.0/21 (255.255.248.0), is
10.100.0.1 to 10.100.7.254. Does that descibe each location?
What I am surmizing is that you are trying to say you want the following IP
ranges using a /21 (255.255.248.0). However, it won't work. This is because
the /21 mask includes all of these networks in one subnet. You would need a
/24 (255.255.255.0) for each.
10.100.0.0 to 10.100.0.255
10.100.1.0 to 10.100.1.255
10.100.2.0 to 10.100.2.255
10.100.3.0 to 10.100.3.255
10.100.4.0 to 10.100.4.255
10.100.5.0 to 10.100.5.255
10.100.6.0 to 10.100.6.255
10.100.7.0 to 10.100.7.255
I think if this is how it is currently configured, it may explain why the
client has no site associated to it, because there is no random pick feature
with AD Site assignment.
And yes, I saw earlier that you have all the servers in the
Default-Site-Name. That is because when they were first promoted, they get
assigned to their appopriate site. However, if a DC is moved to a different
location with a different IP and in a different AD Site, or an IP is
changed, they must be dragged and dropped into their new AD Site.
I would also suggest to make sure none of the DCs are multihomed including
if RRAS and/or multiple IPs have been assigned. This also includes if the DC
has multi NICs with one connected to a SAN for backup purposes. This is
problematic, and among the 50 other problems that crop up because of such a
configuration on a DC, a DC cannot be part of more than one AD Site, because
each IP configured will need to be part of one site or another. And if the
private or "other" IP is regsitered into DNS, and a client picks it up as a
genuine authenticating DC, it may not have a route to that subnet.
I hope that helps.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check
http://support.microsoft.com
for regional support phone numbers.