by adrien » Sep 24 04 4:54 pm
Hi
Not accessible normally indicates problems with routing.
If there is a routing conflict, this should show up in GateKeeper, if you look on the Network tab, and expand out the connected VPN, you should be able to see all the published routes etc, and any that are in conflict will show up as in conflict.
Am I correct in assuming that the VPN server machine is not also the Internet gateway for the server's network? In this case, you may need to solve routing issues on your server's network. There are 3 ways to do this.
1. install the RIP client (available from our VPN downloads page) on any machine you wish to be able to access through the VPN (except the VPN server).
2. manually add routes to the machines that are using the VPN (basically this is what the RIP client does automatically).
3. enable RIP listening on your main company gateway, or manually add a route on this machine to forward packets for the VPN through to the VPN gateway.
Adrien