Clients Connecting to Wrong GUPs
What would cause clients to contact GUPs outside of their subnet? I thought clients locate GUPs inside their subnet fist, if none are found or available they use the SEPM. I have clients connecting to GUPs outside of their subnets all over the place.
GUP A - ip: 10.10.40.2
GUP B - ip: 10.10.50.2
GUP C - ip: 10.10.60.2
All LU Policies below us a Single GUP IP address.
I assigned LU Policy 1 to Group 1. Clients with all ip's of 10.10.40.xxx to use GUP A.
I assigned LU Policy 2 to Group 2. Clients with all ip's of 10.10.50.xxx to use GUP B.
I assigned LU Policy 3 to Group 3. Clients with all ip's of 10.10.60.xxx to use GUP C.
However, all clients are connecting to GUP A, GUP B, GUP C. Seems like most clients are hitting GUP A though. Perhaps because it was the first machine to become a GUP (noticed it was the first to create the SharedUpdates folder). Clients seem like they are not using the subnet filter when searching the list of GUPs from the globallist, which does have the GUPs sorted by subnet.
Am I understanding the use of "subnets" for GUPs correctly?
I also tried configuring one LU Policy inherited down to all Groups using Multiple GUPs but the same thing happened.
Also, not sure if this matters, but all clients and GUPs in all groups use the same subnet mask (255.255.0.0)
I am using the latest version of SEPM (12.1.1101.401 RU MP1). Some clients are still on (12.1.1000.157).