@alansc9 

It sounds like there is some loop happening, but it also sounds like there is another compatibility issue.

When you connect networks on different subnets, they need to be connected to your internet gateway the same way but with different metrics.

EG.

If I have a network with several routers cascaded behind my main router, they cannot have the same set of addresses to hand out, even with NAT turned off.  If one of them is on a class A, 10.0.0.x, the others can have a class B or C, C being the most common: 192.168.y.x, but the y value in their networking cannot be the same unless the masking of their x value actually allows for it--the subnet mask would look like: 255.255.255.x, where x is any value other than 0 or 255.  You can have several subnets in this manner, all of which sit behind a main outer router (say that 4 times fast), and they can be either private internal nets--which only access the internet and their own resources, or subnetted by purpose--I can have a subnet for printers, a net for video devices, a net for gaming, a net for computers, a net for security devices of specific types.

It sounds like what you've done is try to connect routers to the smart switch in a very odd way.

First, you would need two switches with their own subnets, SA and SB, both at the main network hub where the inside net gets connected to the outside.  These can act as routers for your networks, or as switches, but each needs to be on it's own LAN network metric.  Each needs to have routing internal or have a router connected to hand out addresses, or you can go static and forego this, but they need to have some kind of GATEWAY point (internal or external) that is then connected to the main outer router (your internet gateway).  In fact, one of them can use your main outside router, but the other should use something else, and have that as a gateway.  You will lose speed with double NAT, leave it or don't, up to you, I usually remove it from the second network at the very least.  Both SA and SB have fiber, so I send two fibers across, to SC, another switch with two fiber ports and VLAN capability.  I then use TRUNC to use the wiring for both networks, getting half the ports.  Now here is the kicker, and it's very important.  I use AP wall plugs and switches to separate the networks for Wifi and netting.  I set up the plugs at the main hub, where SA and SB are sitting.  I give the AP's static adresses, and dupelicate this setting in the DHCP of the network they will extend.  When I then plug them in on the other side, they extend only that network, allowing you to connect other devices to them, and have your DHCP carry over.  If you want to have the networks talk to each other, you can set up static routes in the far building to point to the switch, SC, as the first hop, and in the near building, the main router for that network.  On each main router for each network, you then set a static route to the other router, sometimes this will be the outer router, which means you will set one up for that router first, other times the outer router will be the only one you need since it carries the network you wish to talk to.