[QUOTE="Chris"] I'm still having problems with all of this, however I can now post some clearer information on the exact problems... Our local network is made up of three subnets: 172.16.1.0/16, 172.16.10.0/16, 172.16.11.0/16. The *majority* of clients live in 172.16.10.0 and 172.16.11.0. A local router (172.16.1.194/16) connects through a directly-connected T1 to a remote router (172.16.26.1/24) for access to a remote network consisting of 172.16.26.0/24 and 172.16.27.0/24. Clients that exist locally in 172.16.1.0/16 *can* ping the local router (172.16.1.194/16) and *can* ping the remote router (172.16.26.1/24) via the T1. Clients that exist locally in 172.16.10.0/16 can ping the local router but *CANNOT* ping the remote router, or any other host across the T1.[/QUOTE] The remote router doesn't have routes for 172.16.10.0/24 or 172.16.11.0/24, and it doesn't have a default route. How do you expect it to know how to send the return traffic to these addresses without a route pointing back to the local router? If the local router is the hub of your network, you should probably just set the remote router's default route to point to it.