Our current server layout has 4 servers running on an external IP address all multi-homed using the 192.168.1.x network for external public access and the 192.168.5.x network for internal communication between all servers.
The 192.168.1.x and 192.168. 5.x networks are individual NICs on each server and run through distinct routers.
We have a bank of IP addresses, 22.214.171.124 being our current main site, the secondary (internal) router we would like to set up for testing and load balancing (mainly to get our system traffic off the same pipe as client traffic).
The 126.96.36.199 traffic works fine through the 192.168.1.x network and the servers all respond to traffic and requests without issue. However, attempting to access the 192.168.5.x network through a new IP address (188.8.131.52) is not working at all. If you are internal to the network, you can access the website on the server at (5.100), but it will not accept traffic through the external router.
However, if we switch the 192.168.5.x router to be on the 184.108.40.206 IP address, we can access our servers.
Is there a way to allow Windows Server 2012 to watch for internet traffic on both the 192.168.1.x and the 192.168.5.x subnets and properly respond to outside requests from them?
Our servers are Windows Server 2012 R2. Router on one side (192.168.1.x subnet / 220.127.116.11 external - default gateway) is a Cisco RV082 (small business router). On the other side (192.168.5.x subnet / 18.104.22.168 external / routing rules set up to pass traffic through 192.168.5.1 router for gateway to 192.168.5.x network - the side that doesn`t work externally) we have a Cisco 2911 router.