Is the "eigrp stub connected summary" command keeping my remote routers from seeing each other? I know this is default configuration because I didn't add it. I know that I can add static and redistributed routes to this command. The attached routing tables show the summary is being propagated but that doesn't seem to be good enough to establish connectivity between the two remotely connected routers.
Thank you for updating this thread to indicate the solution to your problem. Now it makes better sense. If the base image of the switch only supports stub routing in EIGRP that is a major problem when the switch is in the core of the network. With stub you form neighbor relationships but the stub is intended to be the remote router and a stub router does not advertise to neighbors routes that it has dynamically learned from other neighbors.
And it explains why there was no stub statement in the partial configs that you posted from the remote routers. And in my attempt to list the causes of the core not advertising one remote subnet to other remotes it did not occur to me to consider the possibility that the core was configured as a stub.
I am glad that you got it worked out.