I'm trying to work out an issue I'm running into with deploying Windows Update Services (WSUS) in a multi-site environment. Specifically I'm having trouble with understanding Windows 2003 netmask ordering feature. Here are the basics.
- We have two sites, both of which have a dedicated WSUS server.
- Each site has an Active Directory controller with DNS installed and setup with round robin and net mask ordering configured.
- DNS is setup with two type A records for the name 'WSUS' which point to the respective WSUS servers. This is designed to work with round-robin / net mask ordering.
10.2.0.0 - WSUS server lives here
172.20.0.0 - WiFI network
10.7.0.0 - WSUS server lives here
The goal is to have all clients in their respective sites contact their local WSUS server for updates. Also, when these users/laptops move from site to site they need to be able to contact the local WSUS server to get the needed updates.
Everything is working fine when things are on our wired network because the networks use a similar private IP class and the respective sites WSUS servers live within those networks. The problem is our WiFi network in Site1 uses a different private IP range (172.20.0.0). When laptops using the WiFI network (Site1) contact DNS, netmask ordering thinks it is closer to the 10.7.0.0 network which is located in Site2. So our laptops attempt to go across our WAN in an effort to download and install updates. Our WAN does not have a ton of bandwidth so this is a problem.
How can I force laptops using the WiFi network (172.20.0.0) to go to the WSUS server on 10.2.0.0 instead? I read the following article from Microsoft but I don't think this applies due to the differing IP classes used with our networks. Of course I'm trying to do this without changing the private IP class of the WiFi network.
Any advice? Thanks in advance!