I have one of the weirdest routing problems I've ever seen in RRAS. I have\nthe following configuration, :\n\nBoston:\n-All clients default routed to the RRAS Server\n-Network: 192.168.1.0\n-RRAS Server: 192.168.1.29\n-\-Windows 2003 SP 2 (Enterprise Server)\n-\-PPTP Server\n-\-Static route set to the remote route on the 192.168.2.0 network\n-\-One NIC, default routed to 192.168.1.1 (DSL Router to the cloud)\n\nFairfax:\n-All clients default routed to the RRAS Server\n-Network: 192.168.2.0\n-RRAS Server: 192.168.2.29\n-\-Windows 2008 (Enterprise Server)\n-\-PPTP Server\n-\-Static route set to the remote route on the 192.168.1.0 network\n-\-One NIC, default routed to 192.168.2.1 (DSL Router to the cloud)\n\nThese servers have a route called BostonFairfaxRoute. It's set up\nidentically on both servers, using that username and the username's password.\nThe RRAS servers connect the remote route successfully.\n\nThe problem lies in the ability to successfully route packets. The following\nscenarios result:\n\n192.168.2.29: CAN PING 192.168.1.29\n192.168.1.29: Cannot ping 192.168.2.29\nClients on 192.168.2.0 network: Cannot ping 192.168.1.29\nClients on the 192.1.0 network: Cannot ping 192.168.2.29\n\nIf the path between 192.168.2.29 and 192.168.1.29 didn't make it either way\nI'd understand the problem. The confusing part is that it works one way! I've\nnever seen this before and have no idea how to solve it. I've verified all of\nthe settings more than once in what's a very common system for me to setup.\n\nAnyone have any ideas?