Route polling over multiple NICs to handle overlapping remote networks without NAT'ing

Routing via multiple Network Cards have always been available for the Orion products for years, and there have been a few customers that have this running to access multiple networks. I currently have 2 networks in my lab that I utilize the internal routing Windows has to send out the traffic via the correct Interface.

This is the guide I reference to access multiple networks. Adding a TCP/IP Route to the Windows Routing Table

Routing via multiple Network Cards have always been available for the Orion products for years, and there have been a few customers that have this running to access multiple networks. I currently have 2 networks in my lab that I utilize the internal routing Windows has to send out the traffic via the correct Interface.

This is the guide I reference to access multiple networks. Adding a TCP/IP Route to the Windows Routing Table

I will clarify: The SolarWinds server is at the HQ site. We want to monitor SiteA and SiteB. SiteA is using the 192.168.1.0/24 range. SiteB is also using the 192.168.1.0/24 range. SiteA and SiteB do not communicate with each other, and never will. I can add routes out either NIC to the appropriate site and ping them with "ping -S" to set the source IP, but there's no way in Orion to tell it to use one NIC or the other for communicating with a node. If SiteA-switch5 is 192.168.1.5 and SiteB-switch5 is also 192.168.1.5 (not the same device, just at a different site), I cannot currently monitor both without NAT'ing one of them to some other unique-to-my-environment IP.