Ok, so we've made more progress. Correcting the IP address problem had the following results.
Site 1 VPN Server is now publishing an appropriate route to the subnet at Site 1. I can see the Gateway machine at Site 2 from any machine at Site 1 running the Ripclient, so the Ripclient is working at Site 1 as well.
Now for the bad news - the Gateway at Site 2 doesn't appear to be publishing an appropriate routes for machines at Site 2 to see the VPN server or other machines at Site 1.
The good news is that if I manually add a route (192.168.1.0 Mask 255.255.255.0 192.168.2.100) to a workstation at Site 2, then it can see the VPN server and machines at Site 1, and everything seems to work as it should. This says to me that:
1. The Gateway is routing, but not publishing
or
2. The rip client is not picking up the routes
The routes from the Gateway machine are at
http://www.secondlookhomes.com/routes.jpg
It seems to me there should be a route of 192.168.1.0 MASK 255.255.255.0 192.168.2.100 as a published route.
What am I missing? We are soooooo close to having this working.
Kindest Regards