1. The Windows Firewall is best disabled in the Windows **Services** for the sake of testing if you deem it safe. If that resolves the issue then you can turn it back on and add the scope of the remote subnets into the firewall rules on the LAN Clients that are needed. If you have any other personal firewall installed round the place then disable them for the sake of testing if you deem it safe.
2. Regarding your RIP2 question, this definition may help.
VPN Participants:
LAN Clients behind the WinGate VPN Host (Server) or Joiner (Client) that do not run WinGate/VPNOnly Software. To participate in the VPN they will either:
a) Have their default gateways pointing to the WinGate VPN Joiner/Host on their respective side.
b) OR they will run the QBIK Rip2 Utility Service to automatically discover the routes.
http://downloads.qbik.com/qbiknz2/downl ... client.zip
c) OR they will turn on RIP2 on the router, so the router knows to redirect VPN traffic back to the local WinGateVPN installation (Usually on a scenario that WinGate is not their default gateway and do not want to run Qbik RIP2 Utility).
d) Create static routes.
3. When troubleshooting VPN connectivity then use ip address instead of NetBIOS names.
For example:
You are trying to access a VPN Participants called "johnspc" and the ip address of that computer is 192.168.1.100
To test pinging with a NetBIOS name:
(Windows) Start menu --> run --> cmd --> ping johnspc
To test pinging with an ip address:
(Windows) Start menu --> run --> cmd --> ping 192.168.1.100
To test accessing a file share with a NetBIOS name:
(Windows) Start menu --> run --> \\johnspc
To test accessing a file share with an ip address:
(Windows) Start menu --> run --> \\192.168.1.100