S
scott_max
Hi All 
We have a company with multiple sites. At each Site we have 2 x Subnets / VLANS as follows
> MANAGEMENT
> LAN
On the Management LAN are all of the Hyper-V Servers along with other "management" items such as APC UPS Devices, Managed Switches.
Site 1 Management - 192.168.101.0/24
Site 2 Management - 192.168.102.0/24
Site 3 Management - 192.168.103.0/24
Site 4 Management - 192.168.104.0/24
The "LAN" of these sites contains Domain Controllers + PCs + Laptops etc and are on the following VLAN / Subnets
Site 1 LAN - 192.168.201.0/24
Site 2 LAN - 192.168.202.0/24
Site 3 LAN - 192.168.203.0/24
Site 4 LAN - 192.168.204.0/24
There is full routing between all LAN Subnets, so the domain controllers can replicate etc. So Site 1 LAN has full routing to Site 2 LAN + Site 3 LAN + Site 4 LAN and so fourth. This works perfectly.
The MANAGEMENT Subnet at a particular site, is ONLY able to route to the local site LAN. So Site 1 MANAGEMENT is ONLY able to route to SITE 1 LAN
When trying to join a HYPER-V Server to the Domain, it fails - the specified domain either does not exist or could not be contacted.
This is because when I ping companydomain.local it returns an IP Address of another sites domain controller, which this Management Range does not have routing to.
How do I configure this so that the "Management" range of a Site (AKA Site 1 - 192.168.101.0/24) will only ever return the Domain Controllers within Site 1s LAN (192.168.201.0/24), which will therefore allow me to join these Hyper-V Servers to the domain ?
When I perform an NSLOOKUP and query companydomain.local it returns ALL of the domain controllers in all sites IPs. And I assume that it will simply round robin the request.
Sure I am missing quite simple here I just can't see it for the life of me.
Cheers, Scott
Continue reading...
We have a company with multiple sites. At each Site we have 2 x Subnets / VLANS as follows
> MANAGEMENT
> LAN
On the Management LAN are all of the Hyper-V Servers along with other "management" items such as APC UPS Devices, Managed Switches.
Site 1 Management - 192.168.101.0/24
Site 2 Management - 192.168.102.0/24
Site 3 Management - 192.168.103.0/24
Site 4 Management - 192.168.104.0/24
The "LAN" of these sites contains Domain Controllers + PCs + Laptops etc and are on the following VLAN / Subnets
Site 1 LAN - 192.168.201.0/24
Site 2 LAN - 192.168.202.0/24
Site 3 LAN - 192.168.203.0/24
Site 4 LAN - 192.168.204.0/24
There is full routing between all LAN Subnets, so the domain controllers can replicate etc. So Site 1 LAN has full routing to Site 2 LAN + Site 3 LAN + Site 4 LAN and so fourth. This works perfectly.
The MANAGEMENT Subnet at a particular site, is ONLY able to route to the local site LAN. So Site 1 MANAGEMENT is ONLY able to route to SITE 1 LAN
When trying to join a HYPER-V Server to the Domain, it fails - the specified domain either does not exist or could not be contacted.
This is because when I ping companydomain.local it returns an IP Address of another sites domain controller, which this Management Range does not have routing to.
How do I configure this so that the "Management" range of a Site (AKA Site 1 - 192.168.101.0/24) will only ever return the Domain Controllers within Site 1s LAN (192.168.201.0/24), which will therefore allow me to join these Hyper-V Servers to the domain ?
When I perform an NSLOOKUP and query companydomain.local it returns ALL of the domain controllers in all sites IPs. And I assume that it will simply round robin the request.
Sure I am missing quite simple here
I just can't see it for the life of me.Cheers, Scott
Continue reading...