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